Document Links
ERP-1040 - Getting issue details... STATUS
Introduction
Below is the data flow diagram from S2P
Source System Extractors
Standard extractors do not need to be documented unless extended.
Where custom extractors / extensions are required, reference the FSD for that enhancement.
| Extractor Name | Build Jira Ref For Extension Information |
|---|---|
Inbound Layer
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.
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.
2VD_PurchaseOrderItem
A dimension view will be created joining 2VR_S4HARM_C_PurchaseOrderDex and 2VR_S4HARM_C_PurchaseOrderItemDex. The join will be an inner join based PO Document Number and Source System Identifier. All unique and relevant attributes from both header and item views will be included in the output.
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
Join Field: POHeader to POHeader
Join type: Left outer join
Cardinality: 1: Many
Projection
Remove fields that occur in both PO Header and Item views leaving fields from PO Header side.
Propagation Layer
3VR_S2PP2R_POHdrItm
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
| Target Field | Source1-Field | Source2-Field |
|---|---|---|
| PO | PO | PO |
| POItem | POItem | POItem |
| MaterialDocument | - | MaterialDocument |
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