Datamodel in relation to the value chain

Value Chain: revenue and costs categorized in certain ways that allows analysis accross the valu
Allowing flexibility 1) support the "cost to serve model" while allowing flexibility to support other future reportin
to support other 2)developments
facilitate integration, harmonization standardization and simplication throughout the value
future reporting We should not "close doors" for possible future while designing the solutions.
Common data objects are requires across these 5 pillars marked below
requirements.
Siemens Energy Value Chain

phase 2: Sales/Marketing
phase 1: R&D phase 3: Supply chain
portfolio management Lead generation S&OP
requirement Technology development Opportunities Purchasing
example sales forecasting
product development production
contract negotiations delivery
contract management

same material used

accross the value Material number A Material number B
chain
contract number
visible accross the customer contract number ? customer contract number
value chain

Work item Purpose Teams involved Requirement origin

FiCo

FiCo

FiCo

PLM, Service,FiCo, Project,

Need to tie all financial FiCo
Sales.
2 transactions to a new
installed based or existing HIT topic between finance
installed base
and service

FiCo

FiCo

Service & FiCo and Sales FiCo

Identify the business

3
model.
3 Identify the business
model.

Service, Projects: to inform.

Controling and sales to FiCo

agree.

FiCo

Reporting and breakdown

cost to serve. Based upon
FiCo, Sales, Projects,
coorperate service manual.
Report on seperate items Service. Every E2E proces
4 by cost and revenue. where sales is involved.
Finance in the lead
Relates to supply chain,
customer projects and HIT TOPIC needed
services.

FiCo
11 service, projects, sales to be FiCo
informed.

tie out all transactions in

relation to transferpricing. Controling,
Make sure that when Need to involve Project,
multiple sales orders and service once sales comes
5 company codes are with a proposal FiCo
involved, they all share the Sales in the lead
same customer contract HIT topic
number.

6 CoPa FiCo

7 FiCo

for each sales order

detemine which contract FiCo, sales, projects &
type is involved. Relevant service.
8 for: Finance/TP in the lead FiCo
- transfer pricing & HIT
management reporting.
9 CoPa FiCo

10 CoPa FiCo

MDM, sales, Fico, Service

11 Reporting requirement. FiCo in the lead FiCo
WP only

Sales, project and service.

12 Pricing requirement Sales in the lead FiCo
WP only

13 FiCo

14 FiCo

15 Discuss with FiCo before FiCo

implementing

Group cost and revenue on

16 product group throughout FiCo
the value chain.
 What kind of sourcing we
17 have in order to fulfill sales & projects FiCo
customer requirements.

related to how the profit is FiCo in the lead.

18 recgnized. Reason for FiCo
WP only
destinction unknown

19 FiCo in the lead. FiCo

20 ? FiCo in the lead. FiCo

All other capability teams

21 facilitate audits where needed. FiCo
FiCo in the lead

22 FiCo in the lead. FiCo

HIT

23 FiCo
production example
- please complete support CTS model Fico with production FiCo
list (Eric B)

project datamode
example - please
complete list: support CTS model FiCo with projects FiCo
Matthias
nue and costs categorized in certain ways that allows analysis accross the value chain in order to
cost to serve model" while allowing flexibility to support other future reporting requirements.
gration, harmonization
hile designing standardization and simplication throughout the value chain processes.
the solutions.
Common data objects are requires across these 5 pillars marked below

Siemens Energy Value Chain

phase5: Service
phase 4: Commercial projects training
Project planning and execution operate
design and engineering monitoring
construction maintenance
installation & Commissioning repair
upps & mods

Material number C

customer contract number customer contract number

Requirement Source (discussion/recommendation). Status

will come from customer account assignment group which is

already at header. Source business partner: sold-to. Sales org
External Sales done
specific.
customer account assignment group decided: 14.04.2023

will come from customer account assignment group which is

already at header. Source business partner: sold-to. Sales org
Internal Sales done
specific.
customer account assignment group decided: 14.04.2023

Business Relationship
Reflecting the business relationship with the customer
- New Installed Base Business: New Unit will come from the equipment and this will be at line item open
- Existing Installed Base Business: after market level. User status
Precondition: need to check how installed based is represented in the
new S4 system.

will come from the equipment and this will be at line item
level. User status =NEW of top level Equipment (installed
New Installed Base based). Equipment Status is under discussion. Check with open
Mathias.
When do they create a New equipment

will come from the equipment and this will be at line item
level. User status = Delivered or PAC of top level Equipment
Addition To Existing Installed Base (installed based). Equipment Status is under discussion. open
Check with Mathias.

will come from the equipment and this will be at line item
level. User status = "handed over to service” of top level
Servicing Existing Installed Base Equipment (installed based). Equipment Status is under open
discussion. Check with Mathias.

Differentiation will be all other sales document types except

Long Term Contract.
Need to se difference between: All sales order types will represent Open Market Contracts.
1) Open Market Contract. To be reviewed by Service.
2) Long Term Contract (different types distinguished O&M, LTP...etc. . Wait for service what kind of document will be used for LTC done, agreed
Related to services. (not a sales order type),
14.04.2023: dc can be user probably. Wait for service to be
clear.
 Item division will be used here, reporting can be done from
POB/Line Item: Type of business the billing item. Material item division will be populated in the
sales order item and needs to be manually changed if
Example as below: necessary to reflect the correct value.
10 New product business BRD needed to have division item as mandatory field. done, agreed
20 New systems Business Requirement finance: have GPU in item division on top level
30 New solution Business products. Discussed and rejected.
.....
header division is used

Type of service
Using the division in the line item might work as long as we clearly
separate the service types from the GPU's
The GPU in the master record of the equipment is being used to
derive the GPU for the work done. This is not the same as the type of
work.
Type of service
SV - Consulting
SV - Design open
SV - Build
SV - Operate
SV - Maintenance
SV - Digital Services
SV - Rentals
SV - Recycling
SV - Training
SV - Finance

Type of work In october 2023 new functionality released by SAP will

Consulting presumably cover these requirements. Functionality in
Design - Civil Works question: EBRR, UPA and statistical revenue.
Design - Structural Works
Design - Products
Installation & Commissioning
Systems Integration
Products
Construction
Build Others
Operate
Remote Monitoring
Spare Parts--> item division
open
Field Service
OnSite Repair
Inhouse Repairs
Mods & Ups
Digital Services
Digital Services
Rentals
Recycling
Training
Financing
Field Service
- supervising
- recommissioning
- maintenance
- onsite repair
 This can be something pulled from material master?
Product hierarchy has GPU. GPU do not change and resemble
a grouping of products. Take from Material master.

This would allow postings in CoPa to get the GPU. Finance

Also, the core products developed, manufactured and delivered are postings will not have GPU....and it’s needed there. Solution
being assigned to a product division. This is to support other relevant will need to be discussed within finance team: canceled
KDD's for retrieving the GPU and the BU/BA, to support TP and to
Support Consolidation Background: After SEEM; we have factories that produce and
sell from multiple GPU’s (e.g. Finspång). Also two or more
business areas. Need to reflect those in the systems.
Suggestion to use business area functionality.

product hierarchy has GPU. item no longer relevant

Group Master Contract - SE Contract Number

- The Overall SE Master Contract New field on sales order where the customer facing order
- Used for Profit Recognition number is entered. ongoing
- Used for Connecting Individual legal Contracts Also new field for WUPID (for projects).
- Especially used in case of Consortium.

Document Type
Identifies The Sales Process
Inquiry
Quotation Sales Header – Order Type
Contract done
Delivery Ok, Order type; decided.
Billing
Return
Credit Memo

Individual Legal Contract Nr

Not necessarily a contract as in Long term service agreement. Sales Header
Basically: every sales is a contract....even if it’s just 1 o-ring.
- Contract Number Decided: Sales order number.
- Group Customer Contract Nr done
- Legal Customer Contract Nr
- "Contract Number
- Group Customer Contract Nr Sales order number is legal contract, not the customer PO.
- Legal Customer Contract Nr"

Type of contract (called type of Business Model by SE).

Need to know what type of contract it is.
Commission
- Agency Is info coming from project or sales order? are there non
- BoA Regular project sales orders that would need to report this? clarify
- BoA 5 with FIN
- BoA 6
- BoA NCM Create new work item/workpackage for this.
- BoA Silent Consortium 0) Internal or external sales --> determine PP
- BoA Open Consortium 1) What is the type of contract --> determine PP open
- BoA Contract Split 2) For which business model is the contract--> determine PP
3) type of Service: will determine price
Regular: 4) type of work: will determine price
- Consortium Type 5
- Consortium Type 6
- NCM Consortium
- Silent Consortium
- Contract Split Commission
 Sales Header (Partner function at header)
Contract Entity on selling side
- SE Contracting Entity Sales org is contract entity in case sold to is external
- SE Entity owning the contract
- One in Case Of Non-Consortium Sales organization number will be used to identify the done
- Multiple in Case of Consortium contract entity on selling side.
- SE Supplying Legal Entities

Contract Customer (AG partner type)

- Customer Legal Entity Sales Header (Partner function at header)
- Receiving Customer Site Customer Legal Entity: sold-to
- Invoice Receiving Customer Entity Receiving Customer Site: ship-to done
- Invoice Paying Customer Entity Invoice Receiving Customer Entity; bill-to
- Customer Installed Base Country. country of installation will use the Invoice Paying Customer Entity: payer
EU partner role and substitute the country of installation into the Customer Installed Base country: end user (EU partner).
parter consilidation unit.

Customer HQ Customer hierachy

Identifying the Customer HQ Entity BRD/KDD needed open

Sales Header (Partner function at header)

Partner 1A: e.g. BP Europe, but sold-to is BP NL.

Question for Javier: why do we maintain 1A partner on

Pricing partner global equipment master and not on customer master? Check PS1. open
Need to know the total sales to e.g. Shell DR-Jamy Irons. Checked: used for the notification. Notification
is not avalable anymore in S4E solution.

Different Partner function needed: global pricing partner

BRD/KDD needed.

Customer Type
Private Company
Derived from Customer master
Public Company
Should be a certain field, but field not decided. Need to follow
Semi-Public Company done
up with Daniel Reisberger. Sales will follow up.
Government Owned Entity
Semi-Government Entity Needs to be on general data
Government Entity

Customer Classification Derived from customer master

Energy Value Chain Segment Should be a certain field, but field not decided. Need to follow
Industry up with Daniel Reisberger. Sales will follow up done
Industry Segment (SI code) Needs to be on general data
Need to have distinction between sold-to and holding.

SE-Contract Owner (internal).

Reflecting Internal Contract Owner. Should be business areas & Sales Header (legal owner)
Business units
Sales Group – Volt Business Areas & independant Business
Units.
- Gas services
Distributed 23.02.2023:
Centralized Agree on direction, but need to verify and validate – use sales
- Grid Technology group. See how it fits in US, Germany, CN. done
- Transformation of industry - GS -C
Steam - GS-D
Compressors - GT
AED - TI- SES
- TI-EAD
Needs to show up in P&L. Will this work under Volt? Will this work for - TI-STG
IFRS8 ? - TI-C

Product Grouping
Reflecting Major Product Groups Sales item (Product Hierarchy)
Based on Energy Value Chain Clear KDD for product hierarchy approved. done
Organizational Agnostic
 Assumption: The sales document driven sourcing will only be
controlled by item category (partially true).

Type of Sourcing Reflecting the type of sourcing Procurement key, strategy group and MRP group will not
Purchased From Stock – not available impact the sales document behavior.
Purchased To Order (yes – ITC)
Sell From Stock – not available Purchased From Stock – not available
Make To Order (yes, ITC) Purchased To Order (yes – ITC)
Configured To Order – not discussed yet. Sell From Stock – not available done
Engineered To Order – Not in sales order (WBS) Make To Order (yes, ITC)
Systems Project To Order – Not in sales order (WBS) Configured To Order – not discussed yet.
Solutions Project To Order – Not in sales order (WBS) Engineered To Order – Not in sales order (WBS)
Systems Project To Order – Not in sales order (WBS)
Solutions Project To Order – Not in sales order (WBS)

CoPa solution: ITC and valuation class will give information

(best we have - not bullet proof)

2022-12-13 Sales: Can be derived from the billing type within

Type of Billing the item category.
Fixed Price (Lumpsum):
Reflecting the billing agreement with the customer
Fixed Price (Lumpsum): Fixed Price (Milestones):
Time & Material (RRB): ongoing
Fixed Price (Milestones):
Down payment - ISSUE
Time & Material (RRB):
Down payment CoPa solution: look at billing type. Check in wave 7 if this
solution is holding evaluate soltuionin wave 7: start with WHY
we actually need this information.

Sales item (account assignment and item category)

Type Of Profit Recognition 2022-12-13 Sales: We see two scenarios.
Reflecting the profit recognition method applicable for the POB 1. RAR scenario uses WBS element as account assignment. By
Completed Contract Method (CCM) choice of item category POC or CCM is decided. => POC/CCM
Percentage of Completion (POC) 2. Spare parts order uses EBRR (Event Based Revenue done
Recognition) controlled by requirement type assigned to the
"Completed Contract Method (CCM) item category. => CCM
Percentage of Completion (POC)" For reporting the RA key are assumed to be irrelevant
Need to re-check for EBRR

2022-12-13 Sales:
What kind of plant is meant? Delivering plant is available.
Sourcing plant from Stock Transfer Order is not available.
Supplier comes from purchase order or production order but
Supplier
not from sales document.
Vendor 4711
Work item explaining the limitations of current set-up in Sales:
Vendor 4712
Plant 4711 - Only delivering plant
Plant 4713 - Only Vendor in case of Purchase order directly linked to done
sales order item
what & why?
- NO link available to find OEM (e.g. plant in different
company code).
- No link in case the part is purchased to stock. Not needed.
- How far back in the supply chain do you want to go?
action: FiCo to determine the requirements: what is needed
and why?

extract from system. all tables that have accounting impact need to Different tables, Not a datamodel requirement.suggest to pick
be tagged. need to have dataviews on all audit critical data. define all open
up as a FiCo requirement
tables that are not SAP standard.
EU-Taxonomie more specification needed open
External Sales needs to be reported with EU-Tax-Codes
Pending Contracts/ Rejecter
Customer has not agreed to the transfer of the contract from Siemens Only small quantity of contract left, so possible that is not
AG to Siemens Energy; Legacy from Carve Out needed anymore after migration to S4. parked
No datamodel topic, part of datamigration for each roll-out.
 Within the supply chain the Cost to Serve model reflects the
main activities performed and executed in an E2E manner:
0) Materials
1) Mfg Support
2) Customer Order Engineering
3) Procurement
4) Logistics
5) Order Planning & Execution
6) Mfg Support
7) Manufacturing
8) QM Testing
Production datamodel 9) Delivery
done
related to point 4 type of work ype of service
The costs of bringing purchased materials to its storage
location are reflected as MM Condition Types in the regular
PO. These values get posted at the time of GR and thereby
updating inventory values correctly with all the relevant costs
of bringing it to its location.
On production orders the activities are represented by activity
types and used for hour sconfirmation, overhead charges and
business process charges.

The CTS Model is represented as cost components within std

cost estimates and as functional areas in COPA.

Project datamodel:
WUPID ID, used in CoPa WUPID is derieved from the sales order...etc etc and then visibl done
 SEEM relevant Other teams
SAP Technical field Prio Action Action owner
Go live october involved

VBKD-KTGRD (Acc Assignment sales define SAP field Sales: Parag

Group Customer ) = 01 (Third H yes finance: discuss account FiCo:
Party) determination (501*) Eric/Chanintorn

sales define SAP field

VBKD-KTGRD (Acc Assignment Sales: Parag
finance: discuss account
Group Customer ) = 02 or 03 H yes FiCo:
determination (501*),
(Inter Company , Intra company) Intracompany is 511, 512, 513) Eric/Chanintorn

N No HIT topic Eric B PLM, Service,FiCo,

Project

M No Review with Service team Sales: Parag/Lynn Service & FiCo

 M No Review with Service team Sales: Parag/Lynn Service & FiCo

item division discussion

level1: type of business

level 2: type of service
H yes
level 3: type of work

Related to cost to serve model

and transfer price model

ERIC B Service & FiCo

 More discussion needed
service, projects,
M yes - Controling: investigate BA FiCo sales to be
functionality
informed.
- No action for Sales

Controling,
Sales -Parag, Need to involve
H yes Folow up needed Peter, Boris. Project, service
once sales comes
with a proposal

For VBAK-AUART (Sales

Document Type)  read TVAK- H yes Define SAP field Parag
VBTYP ( SD Document Category)

VBAK-VBELN (Sales Document

H yes Define SAP field Parag
Number)

workitem for sales and controling.

Sales to make proposal for
Sales: Peter
Customer group 2 H yes contract type. Related to PP Parag, Boris. FiCo
determination.
VBAK-VKORG (Sales Org) H yes define SAP field Parag

For a given VBAK-VBELN (Sales

Document Number)  Read
table VBPA- PARVW (Partner Define SAP field + partner
Function) function
SP Sold to Party H yes Parag
EU End user Foreign Trade reposting of country of installtion
BP Bill to party to be addressed by finance.
PY Payer
SH Ship to Party

L No follow up by Controling/Finance FiCo

M No Sales to define new partner type Sales: Javier and

Christian

Need to follow up with Daniel

Reisberger. Controling will follow
KNA-KUKLA
H No up. if not NEB relevance. Send FiCo
extend list from legacy systems
BRD to Daniel. Inform Yusnelli for
CM.

Need to follow up with Daniel

KNA1-BRSCH in legacy system H No Reisberger. Controling will follow FiCo
(SI Code).
up

Discuss with FiCo

VBAK-VKGRP (Sales Group) H yes define SAP field & investigate Parag before
implementing

VBAP-PRODH (Product
Hierarchy) H yes define SAP field Parag
 L no controling to check FICo sales & projects

VBAP – PSTYV: Item Category. M no define SAP field sales

VBAP-PSTYV H yes define field sales

M no investigate Controling

All other capability

H yes Present PS1 DART and discuss Controling
teams

no

no
WI Work package

WI 2000008731 - sales: define SAP field

WI - FiCO discuss account determination 1000005527

WI 2000008732 - sales: define SAP field

WI - FiCO discuss account determination 1000005527

WI 2000008744: define business relation ship based

upon Equipment user status. 1000005531

1000005531

Use division for identifying business model

Use division for identifying business model

1000005527

HIT topic deined

WI: investigate and implement Business area
functionality

WI 2000008734: group master contract discussion 1000005527

WI 2000008735 - define SAP field 1000005527

WI 2000008736 - define SAP field 1000005527

WI 2000008737: type of contract: how to represent in

saes documents. 1000005527
WI 2000008738- define SAP field 1000005527

WI 2000008739 - define SAP field 1000005527

WI: implement product hierarchy in S4E

WI 2000008746- new partner type: Global Pricing Partner 1000005531

WI configure customer type on business partner basic

data

WI configure customer classification on business partner

basic data

WI 2000008740 - configure sales group 1000005527

WI 2000008741 - define field and continue. what

happens in case of commercial sales order (for projects). 1000005527
WI controling to investigate and implement workable
solution.

WI 2000008747: controlig to investigate further. detail

the requirement and relevancy of requirement. 1000005531

WI 2000008742- define logic/SAP field for all scenarios 1000005527

WI further investigate sccenarios and solutions.

WI - implement DART
 phase 1: R&D phase 2: Sales/Marketing phase 3: Supply chain
Lead generation
portfolio management S&OP
requirement example Technology development Opportunities Purchasing
sales forecasting
product development production
contract negotiations delivery
contract management

same material used accross the value chain Material number A Material number B

contract number visible accross the value chain customer contract number ? customer contract number

Internal/external sales
Busines type x x
 phase5: Service
phase 4: Commercial projects training
Project planning and execution operate
design and engineering monitoring
construction maintenance
installation & Commissioning repair
upps & mods

Material number C

customer contract number customer contract number

x x