AP350

myConcerto for SAP
AP350 Functional Design Document

Load Cost of Sales (inclu COGS @ Std) from S/4 to
IBP – Planned + Current

Load Cost of Sales (inclu COGS @ Std) from S/4 to IBP -
Planned + Current
myConcerto for SAP
2019
Modified: 1/17/2020 1:13 AM Page 1 of 23 Last modified by: User

©2019 Accenture. All rights reserved. Confidential Information of Accenture. For use by Accenture
personnel or on Accenture projects.
myConcerto for SAP
Document Review & Approval

Please copy and paste the correct status of this document into the below table. Do not delete this
section.
FD Status
Use these statuses: NOT STARTEDIN DRAFTIN REVIEWAWAITING SIGNOFF
IN REVIEW
Responsibility Names Completed Date

myConcerto for SAP
Contents
Document Review & Approval .................................................................................................. 2
Business Purpose & Requirements ................................................................................................. 5
Review Checklist ........................................................................................................................ 6
Functional Overview ....................................................................................................................... 7
Functional Description ................................................................................................................ 7
Assumptions.............................................................................................................................. 10
Dependencies / Constraints ....................................................................................................... 11
Security Requirements .............................................................................................................. 11
System Details, Direction and Pattern ...................................................................................... 11
Transaction Volume .................................................................................................................. 11
Frequency and Timing .............................................................................................................. 12
Initiating Process / Transaction / Program ................................................................................ 12
Processing Type ........................................................................................................................ 12
Detailed Functional Requirements ................................................................................................ 12
Functional Specification ........................................................................................................... 12
Interface Process Flow Diagram ............................................................................................... 18
Proposed Transfer Method / Program ....................................................................................... 18
Target / Source Data Layout ..................................................................................................... 18
Mapping SAP fields to Source / Target .................................................................................... 18
Selection Screen Details ........................................................................................................... 18
Post Interface Activities ............................................................................................................ 19
Error Handling .......................................................................................................................... 19
Security and Authorization ....................................................................................................... 19
Re-start / Re-processing requirements ...................................................................................... 19
Reconciliation Procedures and Audit Requirement .................................................................. 20
Approach ................................................................................................................................... 20
Testing Requirements ................................................................................................................... 20
Key Business Test Conditions .................................................................................................. 20
Technical Test Conditions ........................................................................................................ 21
Risk and Controls Test Conditions ........................................................................................... 21
Test Result ................................................................................................................................ 21
Testing Considerations/Dependencies ...................................................................................... 22

myConcerto for SAP
Client FD Review / Feedback ................................................................................................... 22

myConcerto for SAP
Business Purpose & Requirements

CLIENT will create "One Client way" for processes across Client where possible, focusing on
best practices. It will be implementing a world-class digital platform enabled by SAP to replace
many of Client's existing systems to allow access to integrated, real time data and analytics.
More specifically, the CLIENT Integrated Business Planning (IBP) work stream, including the
Supply Chain Strategy work stream, will implement SAP S/4HANA as the digital core integrated
with the SAP cloud application SAP IBP and retained system Infor Advanced Scheduler (Infor
AS) and Supply Chain Guru to effect the transformation of business processes.
The Level 2 Capabilities from the Target Operating Model (TOM) in scope of the IBP work
stream, including the SCS sub-stream is as shown below:
The IBP and SCS TOM Level 2 capabilities are enabled by the following Level 4 system
processes:
Overview
At the time of going live, the AOP/CAF plan data will be converted to S/4 and IBP.
After going live, IBP will be the planning application for the Rolling 24 month outlook and
future years' AOPs and CAFs down to Brand Contribution (excluding marketing spend) . The
approved AOP and CAF down to Brand Contribution will be interfaced from IBP to S/4 at
lowest level which will then flow through to Hyperion (via interface designed/owned by R2R) at
a summarized level. Hyperion will hold the full P&L plan incorporating other areas budgeted in
S/4.
The standard unit cost of manufactured products and Traded Finished Goods include all
fixed and variable costs incurred in the production phase for manufactured products, which
includes direct material, direct labour and overhead costs. The standard unit cost of

myConcerto for SAP
manufactured products are maintained in SAP S/4 HANA per material/plant combination in the
base unit of currency.
From SAP IBP perspective, the requirement is to calculate the standard cost of manufactured
products and Traded Finished Goods based on forecast sales quantity. This input is needed to
Forecast Gross
Profit @ standard for each product and then calculate down to the Brand Contribution for
each Brand/Category.
This FD is to upload COGS components in SKU level to IBP key figures on weekly basis. This COGS values
will be projected over 24 months.
Purpose
The purpose of this Functional Design document is to interface the monthly Cost of Goods Sold -
Standard Unit Cost of manufactured products in cost component level from SAP S/4 to IBP. The IBP
forecasting cycle is performed once a month in the current fiscal (Year 0). The interface will extract
these data and update all the relevant data in the next 24 months.
Review Checklist
Standards and Consistency
 Has the correct template been used and all sections been completed as required?
 Are the correct details (Business Owner for sign-off, status etc.) displayed on the front
page?
 For integrations with 3rd Party Logistics, has the document been reviewed with
Third party and Retained Systems team? (Only applicable to 3PL specific interfaces)
 Have all the assumptions been documented properly so that there are no open issues in
the document?
 Has the document history been continuously updated?
 Is the work package created?
Integration and Dependencies
 Have all inputs and outputs been identified and confirmed?

 Have all referenced documents been listed (other business process designs, sub process
designs, spreadsheets, information papers, etc.)?
Design
 Has an extension development technique been identified?

myConcerto for SAP
 Has an example of existing WRICEF object been included?

 Has the extension been approved?
 Have all areas of impact been identified?
 Has the interim state requirement been considered?
Performance
 Have the performance implications, metrics and targets been documented?

 Has the performance and volume usage of the report development been considered?
Exceptions and Error Handling
 Have the exceptions and likely errors been defined and listed?
 Does the document describe what steps (if any) need to be taken after an exception has
been raised?
 Have all the applicable business scenarios been considered, along with the corresponding
test conditions?
Usability – From the user perspective
 Has the extension attempted to maximize the efficiency of the user (i.e. simple to use,
intuitive, quick to use)?
 Are any manual steps clearly defined and carefully designed?
Flexibility – From a business perspective
 Have all steps been clearly identified and documented so new functionality can be added
in the future?
Additional information
 Has security been considered (e.g. authority checking considered, target group of users
who should be given access to the report etc.)?
 Are the test conditions sufficiently detailed to enable a full test of all required
functionality?
Functional Overview
Functional Description
The standard unit cost of manufactured products and Traded Finished Goods include all
fixed and variable costs incurred in the production phase for manufactured products, which
includes direct material, direct labour and overhead costs. The standard unit cost of

myConcerto for SAP
manufactured products are maintained in SAP S/4 HANA per material/plant combination in the
base unit of currency.
From SAP IBP perspective, the requirement is to calculate the standard cost of manufactured
products and Traded Finished Goods based on forecast sales quantity. This input is needed to
Forecast Gross Profit @ standard for each product and then calculate down to the Brand
Contribution for each Brand/Category.
The standard unit cost for all manufactured products will be imported to IBP from S/4 and will
be populated as a custom key figure. For Traded Finished Goods or products that are purchased
from other sources, the standard unit price values are in the Material Master records for Material
Type ZTRA.
After the implementation of S/4 HANA, the IBP key figures Cost of Sales Plan data will
be sourced from S/4 and loaded to the IBP system at the product level for all the weeks for the
month in the current fiscal year. The components of the IBP Key Figures for Cost of Goods Sold
- Plan (Standard) data are listed below:
Cost of Goods Sold - Plan Unit Cost Raw Material (GL 5000000)
Cost of Goods Sold - Plan Unit Cost Semi Finished Goods (GL 5001000)
Cost of Goods Sold - Plan Unit Cost Traded Finished Goods (GL 5002000)
Cost of Goods Sold - Plan Unit Cost Packaging (GL 5003000)
Cost of Goods Sold - Plan Unit Cost Shuttle (GL 5004000)
Cost of Goods Sold - Plan Unit Cost Linehaul (GL 5005000)
Cost of Goods Sold - Plan Unit Cost Manufacturing Overheads (GL 5006000)
Cost of Goods Sold - Plan Unit Cost Warehousing (GL 5007000)
(NOTE: GL chart of accounts to be finalised, SAP sets have defined for the FD, any changes in
GL can be referred to SAP sets, no changes needed in the interface program.)
A key business requirement is to interface the GL components of the monthly Cost of Goods
Sold - Unit Cost planned (standard) data from Client's new S/4 HANA system to IBP. This will
serve as the basis for the planned data in the periods/ weeks after go live. The planned data will
be interfaced to IBP on a monthly basis after go live. The approved standard unit cost for
Products in S/4 Hana are calculated once a year and all the months for the fiscal year have the
same value (unless the standards are changed within the fiscal year).

myConcerto for SAP
The planned data willl be interfaced from S/4 to IBP at the WKPRODLOC or Week/ Product
Group/ Location Planning level on a monthly basis.
SCR925
According to Finance Team(R2R), new Cost Component "9. Excise" has been added to Product
costing, it will split Excise cost from costing estimate for any products which held Excise duty
paid. This FD is required to be updated to pull Excise component of COGS from S/4 to IBP. The
Excise component will be used to calculate Std. Unit cost in IBP.
This FD is to be modified to add "Excise" to the cost component list and get data from S/4
BAPI, and the Mapping files are also need to be updated.
In IBP, Excise Paid Planned(ZFIN) Key Figure will be created in IBP at Product/Location level
NGPP-24400
Below 2 newly added cost components caused differences for unit cost@std. between S/4 and
IBP.
10 Warehouse (negative)
11 Sub-Contracting
IBP interfaces need to be updated to resolve this issue,
 For Planned data
The value from “10 Warehouse (negative)” will always be a offset of “6. Warehouse”, it should
not be send to IBP.
The value from “11 Sub-Contracting” will be added into IBP key figure for cost component “5.
Manuf. Overheads”
This FD will be updated to extract Sub-Contracting value from Cost Estimate and send to IBP.
After this change, the total Unit Cost@Std in IBP should be consistant with S/4. no new Key
Figures need to be created.
Since there are no new Key figures, then no changes are needed for the Interfaces which send
planned data back to S/4

myConcerto for SAP
 For Actual data
Regarding to Warehouse and Manuf. Overheads, currently IBP interfaces bring below account
balance to IBP,
5006000 COGS - Manufacturing Overheads
5007000 COGS - Warehousing
For sub-contracting actual@Std., the GL is a COGS variance Account, it will send to IBP as
COGS Variance(IBP121). No change in FD is needed.
Toll Manufacturing
For Toll manufacturing, new Cost Component "12. Toll Manufacturing" has been added
to Product costing, it will split Toll Manufacturing cost from costing estimate for any Toll
manufacturing products. This FD is updated to pull this new cost component from S/4 and
send to IBP.
This FD will be updated to add "12. Toll Manufacturing" to the cost component list and
get data from S/4 BAPI, the Mapping files will be updated as well.
In IBP, Toll Manufacturing Cost Planned (ZFIN) Key Figure will be created at
Product/Location level
Assumptions
The following assumptions apply:
 Unit cost is transferred to IBP for Finished (manufactured) Goods and Traded
Finished Goods only.
 Unit costs are maintained at plant level in S/4 either as a Standard Price for Finished
Goods (manufactured) and for Traded Finished Goods.
 Contract packed goods is part of Finished Goods.
 Planned unit cost changes are not maintained for Finished goods and trading goods in
S/4. Finance team does currently not have plans to use planned prices - hence planned
unit cost is out of scope in this design.
 All the relevant product locations are present in IBP.
 Unit cost calculation is done at the base currency of the business unit i.e. AU for
Australian plants and NZ for New Zealand plants
 Unit costs is calculated at the base UOM of the products.

myConcerto for SAP
 It is not necessary to send across the UOM or UOM conversion as these master data are
send with other interfaces.
 We bring over costs for all materials regardless of the cross-plant material status.
 Unit cost is send to IBP every month for all weeks of all month within the forecast
period ahead.
 SAP IBP users will be trained in SAP CPI-DS troubleshooting and Error Handling.
Dependencies / Constraints
In case the finance solution is changed to include planned unit cost for either finished goods
and/or trading goods, this interface should be redesigned to capture planned costs for future
periods.
 Relevant Planning Area should be active in SAP IBP.

 Steps required to set upSAP Cloud Platform Integration for data services is completed,
for e.g. creation of data sources, import of metadata, Web-UI config.
 The data integration project and tasks is created.
 Sales & Operations planning (S&OP) will be performed in SAP-IBP and forecasts will be
‘cashed up’ by applying rates/prices from appropriate sources in SAP
Security Requirements
 Identified Client SAP IBP super user(s) and technical support team must have access to
manage error handling
 Identified Client SAP IBP super user(s) and technical support team must have access to
initiate the interface manually, where required
System Details, Direction and Pattern

Source System SAP S/4HANA
Target System SAP IBP
Direction Uni-direction
Pattern Asynchronous
Transaction Volume
Sales Volumes, Aus Beer
By Region (like State), Buying Group, SKU, Month and Account

myConcerto for SAP
Volume only
189,477 records
Sales Volumes, NZ
By Region (like State), Consolidated Group, Product Group, Month and Account
Volume only, includes LGM, Maltexo and US Wine
189,477 records
Frequency and Timing

Weekly basis.
Initiating Process / Transaction / Program

 Scheduled monthly Batch Job at defined time for IBP weekly forecast timeframe
 Additionally, the interface will be triggered manually on an ad-hoc basis from CPI-DS
Processing Type
BATCH with INSERT UPDATE Mode.
Detailed Functional Requirements

Functional Specification
To be able to cash up the forecast in IBP and derive Gross Profit@standard and Brand
Contribution calculations, several interim calculations needs to take place. One of them is the
COGS calculations which requires the components of the material standard unit cost. The
components of the material unit cost is calculated and maintained in Material Master and Product
Costing tables in SAP S/4HANA as part of standard costing procedure by R2R Finance team.
 Finished goods is based on standard costs and includes material, production and overhead
costs. Standard costs are updated in SAP S/4HANA normally on a yearly basis or as
required.
 Trading goods is based on standard costs.

myConcerto for SAP
 Raw materials is based on moving average price opposed to standard costs. Moving
average price is dynamically updated in SAP S/4HANA for every goods receipt made in
the system
Both costing types (price control for standard price (cost) and moving average price) are based
on a base quantity as well as a currency which needs to be considered in the design of the
interface. The programming logic should check for the costing procedures used by checking the
Price control indicator in Material Master and pick the value of the corresponding field. This
value, associated with the material/plant and currency, will be sent to IBP and populated in the
component unit cost key figure listed below in a weekly bucket for the following 2 years.
SAP S/4HANA and SAP CPI-DS logic
Step 1 - Global Filter Variables
CPI-DS will apply the following filters to the lookup in standard SAP S/4HANA tables: KEKO,
KEPH, TCKH3, MARA, MARC, MBEW. A few BAPIs have been provided by SAP, they can
be used for this development.
As part of CLIENT Release 1.0, the following filter criteria must be incorporated, with the
ability for the SAP IBP super user and/or technical team to switch-on or switch-off the filter
criteria or change filter values with ease; the proposed filter conditions to be set as CPI-DS
Global variables are
 Material (KEKO-MATNR) - Optional, Multiple selection allowed - default value blank

 Material Type (MARA-MTART) - Mandatory, Multiple selection allowed - default
value 'ZFIN'
 MRP Type (MARC-DISMM) - Optional, Multiple selection allowed - default value blank
 Plant (KEKO-WERKS) - Optional, Multiple selection allowed - default value blank
 Costing Date From(KEKO-KADAT) - Mandatory, Multiple selection allowed - default
value from first day of Previous Period to last day of Current period.
 Costing Variant(KEKO-KLVAR) - Mandatory, default value "ZPC1"
 Costing Version (KEKO-TVERS) - Mandatory, default value "01"
 Costing Status (KEKO-FEH_STA) - Mandatory, Multiple selection allowed - default
value "VO" and "FR" (Both)
 Cost component View(TCKH8-SICHT )Mandatory, default value "02"
Default values are subjected to change based on R2R configuration or user requirements

myConcerto for SAP
Step 2 - Lookup cost estimate lists
The following logic should be used to determine what cost component per material should be
passed through to the mapping file.
Below BAPIs will be used for the development,
 BAPI_COSTESTIMATE_GETLIST: Determine cost estimate lists

 BAPI_COSTESTIMATE_GETDETAIL: Determine detailed information for a cost
estimate
 BAPI_COSTESTIMATE_ITEMIZATION: Determine itemization for a cost estimate
SAP has also provided the sample program SAPBAPICOPC to demonstrate, with examples, how
to use above BAPIs.
Below is the screenshot for the selection of Program SAPBAPICOPC.
3. Output Details
 Use BAPI BAPI_COSTESTIMATE_GETLIST to get estimate list per material&plant

during the Costing date range and apply other filters which were given in above Step 1,
(Table MARA and MARC may be used for Material type and MRP type), below is an
test run screenshot.

myConcerto for SAP
 Then run below BAPIs to output cost component value per material&plant.
o BAPI_COSTESTIMATE_GETDETAIL: Determine detailed information for a
cost estimate. please see a test run screenshot below.
 For the costing run per material&plant, it should have below cost components, these
components list can be found in table TCKH3
1. Ingredients
2. Semi-Finished Goods
3. Finished Goods
4. Packaging
5. Manufacturing Overheads
6. Warehousing

myConcerto for SAP
7. Shuttle
8. Linehaul
9. Excise
10. Warehousing(Negative)
11. Sub-Contracting
12. Toll Manufacturing
Cost component structure - Including "Excise" and "Sub-Contracting"
 Get above cost component value (KEPH-KST*) to mapping file.

o Final output should be
 Material Number (MARA-MATNR)
 Plant (MARC-WERKS)

myConcerto for SAP
 Currency Key (KEKO-FWAER_KPF)

 Costing date from (KEKO-KADAT) (Convert to Monday of the week)
 Cost Lot Size(KEKO-LOSGR)
o Per material&plant output cost component value (component list refer to above)
 Cost component value (KEPH-KST*/KEKO-LOSGR)
Step 4 Create Mapping File
When the output fields were retrieved in Step 2 it should be mapped to the following mapping
file format. Each material&plant should have 8 cost components.
Please note, Cost component "11 Sub-Contracting" is mapped to

KF ZCOGSSTDMOPLANNEDRATE as well.
Step 5 Loading Mapping file to IBP
CPI-DS should load Mapping file and extend same data structure to next 24 periods, then loaded
to IBP for all key figures of unit cost components per plant&material for totally 24 period
onwards in IBP. Data are loaded in weekly bucket from key figure date which has been given.
 8 value Key Figures for unit cost components.
Key Figure ID Key Figure Description

ZCOGSSTDRMPLANNEDRATE COGS @ Std - Raw Materials - $/L
ZCOGSSTDSFGPLANNEDRATE COGS @ Std - Semi Finished Goods - $/L
ZCOGSSTDFGPLANNEDRATE COGS @ Std - Finished Goods - $/L
ZCOGSSTDPACKAGEPLANNEDRATE COGS @ Std - Packaging - $/L
ZCOGSSTDSHUTTLEPLANNEDRATE COGS @ Std - Shuttle - $/L
ZCOGSSTDLINEHAULPLANNEDRATE COGS @ Std - Linehaul - $/L

myConcerto for SAP
COGS @ Std - Manufacturing Overheads

ZCOGSSTDMOPLANNEDRATE
- $/L
ZCOGSSTDWHPLANNEDRATE COGS @ Std - Warehousing - $/L
ZCOGSSTDEXCISEPLANNEDRATE COGS @Std - Excise Paid - $/L
ZCOGSSTDTOLLMFGPLANNEDRA COGS @Std - Toll Manufacturing
Interface Process Flow Diagram
Proposed Transfer Method / Program

SAP CPI-DS by applying global parameter-based filters and table joins to extract data from S4
standard tables and load to target system IBP using INSERT-UPDATE method.
Target / Source Data Layout

Refer next section.
Mapping SAP fields to Source / Target

Selection Screen Details
Not applicable.

myConcerto for SAP
Post Interface Activities

Post Interface run, the SAP IBP Super users must check if there are any
 Data Integration Job errors

 Analyse cause of error
 Apply fix
 Re-Run interface (complete re-run, not delta), if required
 Note: The capability to re-run only the delta load is currently being worked with SAP
and CPI-DS team.
Error Handling
SAP IBP
 There is standard out of the box functionality in IBP, using that rejected records can
be checked and downloaded in "data integration jobs" fiori app in IBP side for the
respective data load. Individual error needs to be analyzed, correction action should
be taken and then interface can be re-processedeither from CPI-DS or using application
job or Application Job templates Fiori app from IBP
o Example - "Master data not available".
o Resolution - Check the relevant master data, if missing then first run the master
data interface and then rerun the failed interface.
 SAP CPI-DS
o Exception Handling for all the error within CPI-DS will be managed by Technical
Team and/or SAP IBP super users by referring standard trace log, monitor log and
error log
Security and Authorization

Refer Security Requirements section.
Re-start / Re-processing requirements

Analyze the Trace Log, Monitor log and Error log of CPI-DS

myConcerto for SAP
 Analyze rejected records from "Data integration Job" Fiori App in IBP, take the
corrective action and rerun the interface (complete re-run, not delta) either from CPI-DS
or using application job or Application Job templates Fiori app from IBP.
 Note: The capability to re-run only the delta load is currently being worked with SAP
and CPI-DS team.
Reconciliation Procedures and Audit Requirement

Verify the record count in Data Integration Job app in SAP IBP.
 Check records are matching and check sampling for audit. Sampling size will dependt on
the amount of errors.
 Responsibility of this task will be alligned with the future support structure.
Approach
The standard Data Integration Job app provides the number of records successfully loaded and
failed. For failed records, there will be standard out of the box rejection codes and
descriptions available.
Testing Requirements
Key Business Test Conditions
ID Condition Expected results
Verify whether all
All COGS@STD
the correct cost
cost components
components have
1 are mapped to
been included in
the right key
load based on the
figures
material type
Check calculation Rate per unit
of rate per unit must be correct
and ensure rate and assigned to
2
has been loaded the right
to the right SKU/Plant in
SKU/Plant IBP

myConcerto for SAP
The most recent

Check if the latest
planned
information is
3 COGS@Std
being transferred
must be picked
into IBP
up from S/4
Excise Value
Check Cost
Planned in IBP
Component 9.
4 has been
Excise has been
updated
send to IBP
scucessfully
Technical Test Conditions

To be performed by Technical Team

Verified in data
Interface
integration app in IBP
1 Executed
that interface is executed
Successfully
successfully
Risk and Controls Test Conditions

Test Result
Date Task Name Result
IBP_KF_COGSPLANCUR_S4HANA Faced "Connection Error to HCI system"

myConcerto for SAP
Testing Considerations/Dependencies
Not Applicable
Client FD Review / Feedback

Status
# Section Description Response Accepted/Rejected/No

action Reqd/More
info Reqd
Please, Is this
logic correct
based on the
last
discussions?
The
programming
logic should
check for the
Functional costing Yes, This
1 No Action Reqd
Specification procedures is correct
used by
checking the
Price control
indicator in
Material
Master and
pick the value
of the
corresponding
field

myConcerto for SAP
Guanglin is
going to
confirm
whether is
possible to get
Based on
this info from
discussion
Product
Functional with Nara
2 Costing. We No Action Reqd
Specification it will be
still don't
product
know if
costing
COPA is
holding
Actuals and
Planning data
together.


AP350

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

AP350

Hochgeladen von

Copyright:

Verfügbare Formate

myConcerto for SAP

AP350 Functional Design Document

AP350 Functional Design Document

Modified: 1/17/2020 1:13 AM Page 1 of 23 Last modified by: User

Document Review & Approval

Use these statuses: NOT STARTEDIN DRAFTIN REVIEWAWAITING SIGNOFF

Responsibility Names Completed Date

Modified: 1/17/2020 1:13 AM Page 2 of 23 Last modified by: User

Modified: 1/17/2020 1:13 AM Page 3 of 23 Last modified by: User

Client FD Review / Feedback ................................................................................................... 22

Modified: 1/17/2020 1:13 AM Page 4 of 23 Last modified by: User

Business Purpose & Requirements

Modified: 1/17/2020 1:13 AM Page 5 of 23 Last modified by: User

Integration and Dependencies

 Have all inputs and outputs been identified and confirmed?

 Has an extension development technique been identified?

Modified: 1/17/2020 1:13 AM Page 6 of 23 Last modified by: User

 Has an example of existing WRICEF object been included?

 Have the performance implications, metrics and targets been documented?

Exceptions and Error Handling

Usability – From the user perspective

Flexibility – From a business perspective

Modified: 1/17/2020 1:13 AM Page 7 of 23 Last modified by: User

Cost of Goods Sold - Plan Unit Cost Packaging (GL 5003000)

Cost of Goods Sold - Plan Unit Cost Shuttle (GL 5004000)

Cost of Goods Sold - Plan Unit Cost Linehaul (GL 5005000)

Cost of Goods Sold - Plan Unit Cost Warehousing (GL 5007000)

Modified: 1/17/2020 1:13 AM Page 8 of 23 Last modified by: User

IBP interfaces need to be updated to resolve this issue,

 For Planned data

Modified: 1/17/2020 1:13 AM Page 9 of 23 Last modified by: User

 For Actual data

5006000 COGS - Manufacturing Overheads

5007000 COGS - Warehousing

Modified: 1/17/2020 1:13 AM Page 10 of 23 Last modified by: User

 Relevant Planning Area should be active in SAP IBP.

System Details, Direction and Pattern

By Region (like State), Buying Group, SKU, Month and Account

Modified: 1/17/2020 1:13 AM Page 11 of 23 Last modified by: User

Volume only, includes LGM, Maltexo and US Wine

Frequency and Timing

Initiating Process / Transaction / Program

Detailed Functional Requirements

Modified: 1/17/2020 1:13 AM Page 12 of 23 Last modified by: User

SAP S/4HANA and SAP CPI-DS logic

Step 1 - Global Filter Variables

 Material (KEKO-MATNR) - Optional, Multiple selection allowed - default value blank

Modified: 1/17/2020 1:13 AM Page 13 of 23 Last modified by: User

Step 2 - Lookup cost estimate lists

Below BAPIs will be used for the development,

 BAPI_COSTESTIMATE_GETLIST: Determine cost estimate lists

Below is the screenshot for the selection of Program SAPBAPICOPC.

 Use BAPI BAPI_COSTESTIMATE_GETLIST to get estimate list per material&plant

Modified: 1/17/2020 1:13 AM Page 14 of 23 Last modified by: User

Modified: 1/17/2020 1:13 AM Page 15 of 23 Last modified by: User

Cost component structure - Including "Excise" and "Sub-Contracting"

 Get above cost component value (KEPH-KST*) to mapping file.

Modified: 1/17/2020 1:13 AM Page 16 of 23 Last modified by: User

 Currency Key (KEKO-FWAER_KPF)

Step 4 Create Mapping File

Please note, Cost component "11 Sub-Contracting" is mapped to

Step 5 Loading Mapping file to IBP

 8 value Key Figures for unit cost components.

Key Figure ID Key Figure Description