This Data Flow Specification (DFS) defines the end-to-end data flow required to meet the following requirements:
| Customs | Customs Analysis including Import and Export | This will be built using enhanced SAP Standard Business Content | ||
| Compliance | Compliance Analysis | This is entirely Custom as no Business Content nor standard CDS views Exist | ||
| Preferences | Preference Analysis | This is entirely Custom as no Business Content nor standard CDS views Exist | ||
| Intrastat | Intrastat Analysis | This is entirely Custom as no Business Content nor standard CDS views Exist |
The import declaration item Analytic Model contains item data enhanced with master data associations to importer, exporter, Customs product and text associations.
The export declaration item Analytic Model contains item data enhanced with master data associations to importer, exporter, Customs product and text associations.
![]()
Standard extractors do not need to be documented unless extended.
Where custom extractors / extensions are required, reference the FSD for that enhancement.
| Extractor Code | Extractor Name | Build Jira Ref For Extension Information |
|---|---|---|
| XE_Exp_DecItem | C_EXPORTDECLARATIONITEMDEX | |
| XE_Imp_DecItem | C_IMPORTDECLARATIONITEMDEX | |
| XE_CusDoc_Com | /SYQ/C_CUSTOMSDOC_COMPLETENESS | |
| XE_CusDoc_Cor | /SYQ/C_CUSTOMSDOC_CORRECTIONS | |
| XE_Intra_Mat | /SYQ/C_INTRASTAT_MATERIALREQUEST | |
| XE_Intra_Mov | /SYQ/C_INTRASTAT_MOVEMENT | |
| XE_LTSD_Inbnd | ||
| XE_LTSD_Outbd | ||
| XE_LTSD_Req | ||
| XE_PrefResult | ||
| XE_VendDec_Cv | /SYQ/C_VENDORDECLARATION_COVERAGE | |
| XE_SPL_Aud | /SYQ/C_SPLHIT_AUDIT | |
| XE_BlkDoc_Aud | /SYQ/C_BLOCKEDDOCUMENTAUDIT | |
| XE_PartStatHist | /SYQ/C_PARTNERCOMPSTATUS_HISTORY | |
| XE_LicenseMas | /SYQ/C_LICENSE_MASTER | |
| XE_LicenseDep | /SYQ/C_LICENSE_DEPLETION | |
| XE_License_Val | /SYQ/C_LICENSEUSAGE_WITHVALUE | |
| XE_TariffRate | /SYQ/C_TARIFF_RATE | |
| /SYQ/C_CLASSIFICATION_CURRENT | ||
| /SYQ/C_CLASSIFICATIONCHANGE_HISTORY | ||
| /SYQ/C_PRODUCTCREATION_EVENTS | ||
| /SYQ/C_CLASSIFICATIONACTIVITY_BYUSER | ||
| /SYQ/C_CLASSIFICATIONLEADTIME |
Inbound layer objects only need documentation if some field adjustment is made (over and above the standard load date / time and source system stamp).
Field XYZ converted to date.
Field ABC converted from BIGINT to...
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.
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).
Calculated measure: CM_PRICE = Value / Quantity. (Ubiquitously true, reusable change made at lowest level possible).
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
Remove fields that occur in both PO Header and Item views leaving fields from PO Header side.
A line item level calculation which applies specific business rules that are owned by the POD would be added here.
Purpose: etc
Purpose: etc
Purpose: etc
Calculated measure: CM_DocItemValue = DocQuantity * CM_PRICE
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 |
List objects where material master associations are to be made.
Facts
Tier 1 — simple event-based facts (no snapshots):
Tier 2 — periodic snapshots for state representation:
Tier 3 — audit-grade snapshots:
Link to FSD (Each Analytic model should have its own FSD).
Include technical details for:
Detail restrictions
Detail rate type, from currency