Introduction 

This Data Flow Specification (DFS) defines the end-to-end data flow required to meet the following requirements:

Customs
Customs Analysis including Import and ExportThis will be built using enhanced SAP Standard Business Content
Compliance
Compliance AnalysisThis is entirely Custom as no Business Content nor standard CDS views Exist
Preferences
Preference AnalysisThis is entirely Custom as no Business Content nor standard CDS views Exist
Intrastat
Intrastat AnalysisThis is entirely Custom as no Business Content nor standard CDS views Exist


Import Declaration Items Model

The import declaration item Analytic Model contains item data enhanced with master data associations to importer, exporter, Customs product and text associations.


Export Declaration Items Model

The export declaration item Analytic Model contains item data enhanced with master data associations to importer, exporter, Customs product and text associations.






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 CodeExtractor NameBuild Jira Ref For Extension Information
XE_Exp_DecItemC_EXPORTDECLARATIONITEMDEX
XE_Imp_DecItemC_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

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

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 FieldSource1-FieldSource2-Field
POPOPO 
POItemPOItemPOItem
MaterialDocument-MaterialDocument

Associations to master data

List objects where material master associations are to be made.

Calculated Measures (Pre-Aggregation Calculations)

Facts

Tier 1 — simple event-based facts (no snapshots):

  • FACT_SPL_SCREENING
  • FACT_BLOCKED_DOCUMENT
  • FACT_LICENSE_USAGE
  • FACT_CLASSIFICATION_ACTIVITY
  • FACT_PRODUCT_CREATION
  • FACT_LTSD_REQUEST
  • FACT_PREFERENCE_RESULT
  • FACT_CUSTOMS_DOC (built directly on DEX views with simple enrichment)
  • FACT_CUSTOMS_CORRECTIONS
  • FACT_CUSTOMS_DATA_QUALITY
  • FACT_INTRASTAT_MATERIAL_REQUEST (if in scope)

Tier 2 — periodic snapshots for state representation:

  • FACT_LICENSE_PORTFOLIO — weekly snapshot
  • FACT_LTSD_COVERAGE — weekly snapshot
  • FACT_CLASSIFICATION_CURRENT — daily snapshot
  • FACT_CLASSIFICATION_LEAD_TIME — periodic snapshot
  • FACT_PARTNER_AVAILABILITY — periodic snapshot of master state
  • FACT_CAMPAIGN_RELEVANT_MATERIALS — periodic snapshot
  • FACT_CUSTOMS_CYCLE_TIME — depends on TM/broker timestamp availability

Tier 3 — audit-grade snapshots:

  • FACT_PREFERENCE_SAVINGS — monthly snapshot with locked tariff rates
  • FACT_TRADE_COMPLIANCE_OVERVIEW — daily snapshot with as-of-date dimensional state

Reporting Layer

4VA_S2PP2R_POHisAcc


  • AM_CustomsDeclarations — duty spend, declaration volumes, data quality, corrections
  • AM_CustomsCycleTime — cycle times and SLA adherence (subject to data availability)
  • AM_ComplianceActivity — SPL screening and partner activity
  • AM_BlockedDocuments — document blocks and releases by regulation
  • AM_LicensePortfolio — license analytics and usage
  • AM_ClassificationAnalytics — classification activity, coverage, lead times
  • AM_PreferenceResults — eligibility analytics with all status codes
  • AM_LTSDManagement — LTSD operations and campaign management
  • AM_PreferenceSavings — realized savings, potential, leakage
  • AM_TradeComplianceOverview — cross-module risk view
  • AM_Intrastat (if in scope) — Intrastat material request analytics

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

Data access controls

Outbound Layer

  • No labels