...
Introduction
The DDFS covers the end to end Datasphere data flows for S2S area. The sub area it covers include EHS - Environment, Health & Safety , PRC - Product Compliance, SCT - Sustainability Control Tower and SFM - Sustainability Footprint Management. Below are the details on each sub area and KPIS it will cover:
| Sub-Area | Details | Example KPIs | Comments |
|---|---|---|---|
| EHS - Environment, Health & Safety | The SAP EHS (Environment, Health and Safety) module is designed to help organizations capture, analyse and communicate safety, environmental and compliance data in a structured way. At its core, SAP EHS reporting consolidates data from different subcomponents like incident management, occupational health, product safety, and environmental compliance into meaningful outputs for both operational and regulatory use. | Emissions, waste, and resource usage (air, water, energy), tracking workplace incidents, near misses, injuries, and illnesses | |
| PRC - Product Compliance | The SAP Product Compliance (PRC) is part of SAP’s EHS and product stewardship portfolio. From a reporting perspective, its main role is to ensure companies can track, document, and report regulatory compliance data for products across global markets. It is created as a separate sub-module in Datasphere considering the authorisation rules to only provide a sub-user group access to this data. | Compliance reporting, SVT, SVHC, Substance & Composition Reporting | |
| SCT -Sustainability Control Tower | SAP Sustainability Control Tower (SCT) is designed to centralize, standardize, and automate ESG (Environmental, Social, Governance) data reporting across an organization. It enables automated, compliant and audit-ready sustainability reporting. SCT relies on SAP Datasphere for data foundation and scalability. SAP Datasphere acts as the data layer beneath SCT. It integrates data from various SAP and non-SAP sources, models and harmonizes this data before it reaches SCT. This integration happens via SAP supplied DPI (Data Provisioning & Integration). | Emissions, Energy, Water Management, Waste, Social KPIs, Carbon Credits, Financial KPIs | |
| SFM - Sustainability Footprint Management. | SAP Sustainability Footprint Management (SFM) is a cloud-based solution designed to calculate, analyse, and report product and corporate level carbon footprints. From a reporting perspective, its value lies in turning complex emissions data into structured, auditable and decision ready outputs. Datasphere will be used to send some of the already consolidated data (like waste) and also to extract the footprint data to be used in reporting. | Product Carbon Footprints (PCF) per product and supplier |
Jira Requests Coverage
The models covered under this DDFS will cater towards requirements from the following Jira Requests -
Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-481 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-781 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-782 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-1089 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-1172 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-1746 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-2196 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-826 Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-1069
Data Flow Diagram
There is no SAP provided business content for S2S except for the DPIs used for SCT. Each DPI comprises of a table and a view on top of it. The business content has to be used as is for the integration between SCT and Datasphere to work. data flow diagram from S2S
| draw.io Diagram | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Table of Contents | ||||
|---|---|---|---|---|
|
Source System Extractors
Standard extractors do not need to be documented unless extended.Where custom extractors / extensions are required, reference the FSD for that enhancementare listed in the data flow diagram (above) and are not documented here unless extended.
| Extractor Name | Details | Build Jira Ref For Extension Information |
|---|---|---|
| /SYQ/I_WasteTransportDocument | CDS view on top of 'I_WasteAnalyticsDimension' with associations created similar to 'I_WasteAnalyticsCube'. This view will be extraction and delta enabled. | |
| /SYQ/I_* | A custom CDS view on top of a table (name to be confirmed) to extract emissions threshold information. | |
Inbound Layer
1TL* Tables
Inbound layer objects only need documentation if some field adjustment is made (over and above the standard load date / time and source system stamp).
1TL_S4Hx_C_PURCHASEORDERDEX
Field XYZ converted to date.
Field ABC converted from BIGINT to...
Harmonisation Layer
Every table will have it's own harmonization view. This only needs to be documented if field adjustments are required. E.g. Conversion of data field / type.
Where actions are performed to improve reusability, e.g. joining header and item tables, details of the join (left outer, which is left, which is right, fields to join with, cardinality etc) should listed.
Each node inside the view will appear as a heading 3 in this document detailing what it does and, if not obvious, why.
2VR_S4HARM_C_PurchaseOrderDex
Calculation
Calculated dimension CD_PLANT to change length of field 'Plant' from 4 to 5 to align with WHM plant. (Ubiquitously true, reusable change made at lowest level possible).
2VR_S4HARM_C_PurchaseOrderItemDex
Calculation
Calculated measure: CM_PRICE = Value / Quantity. (Ubiquitously true, reusable change made at lowest level possible).
2VR_S4HARM_POHdrItm
Join
Purpose: Join PO header and item to create reusable view at item level that contains all fields from PO header
LHS: 2VR_S4H_C_PurchaseOrderDex
RHS: 2VR_S4H_C_PurchaseOrderItemDex
Each 1TL* table in the Inbound layer of S/4 systems will be populated as 1:1 with the corresponding S/4 CDS views.
Three new fields, Source System Identifier, Date and Time will be added to each of 1TL* tables.
1TL_CNTROL_SERFCODES
The ESG reporting for Syensqo is done via Serf Codes. The waste transport document is the main controller of the waste KPIs, it contains R&D code which are mapped to Serf Codes. Further the serf codes are classified into categories which help to classify waste into disposal or recovery types. The mapping file will be provided by the functional consultant, which will be then uploaded into this table.
Below are the columns from the mapping file,
- R&D Code - Code from the waste transport document
- SERF Code - Corresponding code for R&D code
- Disposal Type - Waste disposal type, e.g. incineration, etc
- Recovery Type - Waste recovery type, e.g. recycling, etc
1TL_CNTROL_SCTWATERDPIFILTER
The ESG reporting for Syensqo is done via Serf Codes. The Environment Management (EM) module will hold all the input and calculated amounts for water management against various Serf Codes. A subset of these Serf Codes are only required by SCT and it will be configured using this table as a control for mapping what needs to be sent to SCT from Datasphere.
Below are the columns and values for the table,
Data Collection Name/Serf Codes | Use Type | Stress Category | Water Source | Water Usage | Discharge Type | Water Losses(Custom Dimension) |
|---|---|---|---|---|---|---|
E74000 | C | Evaporative water losses | ||||
E74010 | C | Non-evaporative water losses (leakages) | ||||
E74020 | C | Water incorporated into end products | ||||
E74030 | C | Water incorporated into waste materials | ||||
E113070 - AI | C | STRESS_CAT_05 | ||||
E74040 | R | Cooling | ||||
E74050 | R | Process Water | ||||
Calc | C | |||||
E113078 | W | Z_SOURCE_08 | ||||
E113065 - AI | W | Z_SOURCE_07 | ||||
E113065 - AI | W | STRESS_CAT_04 |
1TL_CNTROL_SCTEMISSIONSDPIFILTER
The ESG reporting for Syensqo is done via Serf Codes. The EM module will hold all the input and calculated amounts for air & water emissions against various Serf Codes. A subset of these Serf Codes are only required by SCT and it will be configured using this table as a control for mapping what needs to be sent to SCT from Datasphere.
Below are the columns and values for the table,
This is still under discussion with S2S consultants.
Harmonisation Layer
2TL* Tables
Each 2TL* table in the Harmonisation layer will be populated from the corresponding 1TL* tables for each source system (RoW and China).
A Source System Identifier will be included as part of the primary key in the 2TL* tables to uniquely distinguish records originating from different source systems.
2VR_S4HARM_C_EHSAmount
Purpose
Join EHS Amounts (from EM) with Data Classification data to create a reusable view for periodic amounts against various classifiers used in EM. This will provide contextual data combining amounts against serf codes.
Join
LHS: 2TL_S4HARM_C_EHSAmountDex
RHS: 2TL_S4HARM_SYQI_EHSDataCollectionClsfrDex
Join Field: EHSAmountSourceUUID to DataCollectionUUIDJoin Field: POHeader to POHeader
Join type: Left outer join
Cardinality: 1: Many
Projection
...
n
Other 2VR* Relational Views
Remaining each 2VR* view in the Harmonisation layer will be built on corresponding 2TL* tables. These views will be used to harmonise the data before applying business rules.
Propagation Layer
...
3TL_
...
S2SEHS_
...
WASTEHISTORY
Calculation
A line item level calculation which applies specific business rules that are owned by the POD would be added here.
3VR_S2PP2R_POHisAcc
Join
Purpose: etc
Join
Purpose: etc
Join
Purpose: etc
Calculation
Calculated measure: CM_DocItemValue = DocQuantity * CM_PRICE
3VF_S2PP2R_POHisAcc
Union
Purpose: To bring in values from PO level alongside lower level granularity documents
...
Associations to master data
List objects where material master associations are to be made.
Calculated Measures (Pre-Aggregation Calculations)
Reporting Layer
4VA_S2PP2R_POHisAcc
Link to FSD (Each Analytic model should have its own FSD).
Include technical details for:
Calculated Measures (Post Aggregation Calculations / exception aggregation etc)
Restricted Measures
Detail restrictions
Currency Conversions
Detail rate type, from currency
Variables
A 2 year history (.csv) file for waste data will be provided by Syniti and uploaded into this table. The layout of the file is still under discussion and will be confirmed during the functional specification stage. Syniti will be responsible for all data mappings and validations and the file provided will be uploaded as is in Datasphere. No transformation to the base file is required in Datasphere.
Reporting Layer
...