0% found this document useful (0 votes)
38 views11 pages

Utility Report Base

SAP CO base report

Uploaded by

Deva Saga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views11 pages

Utility Report Base

SAP CO base report

Uploaded by

Deva Saga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 11

Tolaram SAP S4 HANA implementation

Functional Specification Document


Utility Report for OTA

Version 1.0 | 21-04-2023

Page 1 of 11
Tolaram SAP S4 HANA implementation

Table of Contents
Revision History.......................................................................................................................... 2

References................................................................................................................................. 2

Responsible Persons................................................................................................................... 4

Scope of this document............................................................................................................... 4

Definitions, Abbreviation and Acronyms.......................................................................................4

1 Reference Documents.......................................................................................................... 5

2 Sign Off Functional Specification........................................................................................... 5

3 Purpose................................................................................................................................ 5

4 Scope................................................................................................................................... 6

5 Definitions, Abbreviation and Acronyms.................................................................................6

6 Functional Specification Requirements..................................................................................6

6.1 Business Requirement..............................................................................6


7 Process Logic....................................................................................................................... 7

7.1 Enhancement...........................................................................................7
7.1.1 Design of desired enhancement...................................................7
7.1.2 Standard Form Model...................................................................8
7.1.3 Desired Output.............................................................................8

8 Exception Handling............................................................................................................... 9

9 Dependencies....................................................................................................................... 9

10 Constraints........................................................................................................................... 9

11 Authorizations....................................................................................................................... 9

12 Impact Analysis..................................................................................................................... 9

12.1 Impact on Processes including application controls.................................9


12.2 Impact on Data.........................................................................................9
12.3 Impact on System.....................................................................................9
13 Test Specification................................................................................................................ 10

Page 2 of 11
Tolaram SAP S4 HANA implementation

13.1 Functional Test Scenario........................................................................10

Revision History

Please keep the latest version on top

Version Change Description Sections Date Author Reviewer

1.0 New Document All

References

Reader should read this document in conjunction with the following documents

No Document Name Version Location

1 Statement of Work Latest Version

Responsible Persons

S.No Role Tolaram Thirdparty

1 Consultant

Scope of this document

Definitions, Abbreviation and Acronyms

Acronym Description

Page 3 of 11
Tolaram SAP S4 HANA implementation

1 Reference Documents

SNo Document Name Version Location

Priority: High Medium Low

2 Sign Off Functional Specification

Sign off – Functional Specification


Prepared By Date Approved By Date

CA Rajesh Porwal 21-04-23

3 Purpose

4 Scope

5 Functional Specification Requirements

5.1 Business Requirement

View Utility Variances on a Daily basis.

Since Utility Order settlement and Allocation cycle will be run periodically, every Month-end, the variances will be
available only after the month-end cycle is run. To enable Business get a Daily picture of Utility costs, a Report as per
attached XLS file is required.

Page 4 of 11
Tolaram SAP S4 HANA implementation

In OTA Plant, the Power produced is used between Noodles and Seasoning Plants. This is recorded as Power
consumption in KWH as per Meter reading in SKF, on a daily basis. This will be used to distribute the Power costs
between Noodles and Seasoning.

Report should show data on a Daily basis as well as Monthly.

6 Process Logic

6.1 Enhancement

6.1.1 Design of desired enhancement

Report Name – Utility Variance Analysis – OTA


Tcode – ZCO_UTIL_NG01

Z Tables to be created/modified

1. ZCO_AOP_MASTER1 – Existing Table. Create Tcode ZCO_UTIL_AOP for SM30 Maintenance.


Table is now only in Dev, so should be included in Transport.

Selection Screen

Company Code – Single Field, only Display, Default NG10


Plant – Single Input, Mandatory. T001W-WERKS. Default = A110.
Posting Date – Range, Mandatory.
Utility – Drop Down Selection – 2 Inputs – POWER, STEAM. Default – POWER.
Checkbox – SUMMARY.

Allow only A110 or A810 in Plant field. Else, throw Error – This Report is only for OTA Plants

Selection Logic

Step 1. Master Data

If Utility Drop-down is Power, then Variable PLSTAR = 1000, if Steam, then PLSTAR = 2000.

If PLSTAR = 1000, Get Power Meter readings from SKF Data. Read COBK with KOKRS = 1000, VRGNG
= RKS, BUDAT = Posting Date. Get BELNR. If COBK-STOKZ = X or STFLG = X, Ignore as these are

Page 5 of 11
Tolaram SAP S4 HANA implementation

Reversed documents. Pass COBK-BELNR to COEPR-BELNR, get SMEBTR (Qty or KWH), STAGR
(Meter Area – Seasoning or Noodles)

Reference Internal Table IT1

Create 2 Fields in this Internal Table IT1 to store Allocation % based on STAGR.

Field 1 - NALLOC = ( SMEBTR per BUDAT where STAGR = ONL001 / Sum of SMEBTR per BUDAT)
Example from above data – 8000 / 8000+2000

Field 2 - SALLOC = ( SMEBTR per BUDAT where STAGR = OSM001 / Sum of SMEBTR per BUDAT)
Example from above data – 2000 / 8000+2000

There is no data NALLOC = 1 , SALLOC = 1.

Read all Data from ZCO_UTIL_AOP for given Plant, Year (from Posting date), LSTAR = PLSTAR. If no
data exists, give Error message and exit. Error Message – AOP data not maintained for Plant xxxx in
ZCO_UTIL_AOP Table

Page 6 of 11
Tolaram SAP S4 HANA implementation

Reference Internal Table IT2

Step 2. Utility Consumption data

Pass Posting Date Range, Plant, ZCO_UTIL_AOP-MATNR to AUFM-BUDAT, WERKS, MATNR,


BWART = 261, 262

If PLSTAR = 1000 and Plant is A810, pass A110 instead to AUFM for Consumption Data.

Get above fields + SHKZG, DMBTR, WAERS, MENGE, MEINS, AUFNR. Filter AUFNR with AUFK-
AUFNR where AUFK-AUART = ZUTL.

Revision V1.2

Filter AUFNR with AFKO-AUFNR, Pass PLNBEZ = ‘20000000’ IF PLSTAR = 1000 or PLNBEZ =
‘20000001’ IF PLSTAR = 2000.

Filter the Records as per AFKO-AUFNR.

Example – 2 records for 13.05.2023, Material 5800010 in AUFM

Only 1 Order from AUFM for PLSTAR – 1000 (PLNBEZ – 20000000) after Filtering AFKO-AUFNR

Page 7 of 11
Tolaram SAP S4 HANA implementation

Summarise DMBTR and MENGE data per posting date and Material. If AUFM-BWART is 262, multiply
DMBTR and MENGE with -1 before totalling per BUDAT and MATNR

Reference Internal Table IT3

Step 3. FG Production data

Pass Posting Date range to COBK-BUDAT with COBK-VRGNG = RKL and get BELNR. Pass COBK-
BELNR to COEP-BELNR, Plant to COEP-WERKS, Utility to COEP-PLSTAR, COEP-KOKRS = 1000,
COEP-VERSN = 0

From COEP, get above fields + MEGBTR + COBK-BUDAT.

Summarise MEGBTR for Posting Date.

Reference Internal Table IT4

Page 8 of 11
Tolaram SAP S4 HANA implementation

Step 4. Output Table

If SUMMARY Checkbox is not Ticked – we will present data Date-wise as per attached Output.

For each Data Line in ZCO_AOP_MASTER1, match MATNR and attach data from Step 2 as additional
fields. See below how data should be combined.

For each line in above step, match Posting Date in Step 3 and attach data. Since there are 2 Materials, same
line from Step 3 will be attached to each Material Line.

Attached Output Format with Calculation Fields.

If SUMMARY is Ticked.

In Table IT1, SUM SMEBTR per STAGR.

In Table IT2, nothing.

In Table IT3, SUM DMBTR, MENGE per MATNR. For BWART = 262, multiply with -1

In Table IT4, SUM MEGBTR for all data

Output Form logic works in the same way.

6.1.2 Standard Form Model

Not Applicable.

6.1.3 Desired Output

Give a pictorial view of the desired output


Not Applicable.

Page 9 of 11
Tolaram SAP S4 HANA implementation

7 Exception Handling

8 Dependencies

9 Constraints

10 Authorizations

11 Impact Analysis

11.1 Impact on Processes including application controls

11.2 Impact on Data

11.3 Impact on System

12 Test Specification

12.1 Functional Test Scenario

ID Test Scenario Expected Result Comments


1
2
3
4
5

6
7
8

Page 10 of 11
Tolaram SAP S4 HANA implementation

9
10
11
12
13
14
15
16

Page 11 of 11

You might also like