Introduction

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

• ERP-xx Business Case
• etc.

The models below are designed for

• semantic tag - gl account
• fixed assets (need all depreciation areas)
• Lease FX
• tax
• cash flow (flows?) - maybe covered by GR rather
• SKF
• Headcount

Can remove the measures for alternate currency /quantity as we will not use these as per KDD047 Universal parallel Ledgers. But then how does this fit in with currency roles?

Reporting is done in tons so store rather than calc. Where if we dont persist again

Probably the same for value at bud rate

A consolidated view of all the Requirements, KPIs and the supplying views covered by this DFS.

GL Account Semantic Tags (Model)

Overview:

GL transactions grouped by GL Accounts as defined by a particular Account Hierarchy

Based on Business Content

Recreates the S/4 model in a more logical fashion that in S/4 (removes the hard coding in the CDS views)

Differs in some way to the Functional Area Semantic Tag model

Purpose:

Simplified reporting using semantic tags

This flow will be shared with other POD's

Notes:

Source System Extractors

Inbound Layer

No inbound field adjustments are applied. Standard technical fields (load date/time, source system) are retained as delivered.

Harmonisation Layer

2TL_HARM_I_GLACCOUNTLINEITEMRAWDATA

Source: 1TL_S4Hx_I_GLACCOUNTLINEITEMRAWDATA

Purpose:

• Union China with RoW for performance reasons

2VR_HARM_

Source: 2TL_HARM_I_GLACCOUNTLINEITEMRAWDATA

Purpose:

• H

2VR_A2DAMM_PMNotifMaintenanceData

Source: 1TL_S4Hx_Z_I_PMNotifMaintenanceData

Purpose:

• Harmonise notification maintenance data.
• Preserve raw downtime duration (seconds) and malfunction timestamps.
• Align technical object identifiers with order data.

Propagation Layer

3VR_A2DAMM_PlannedDownTime

Source: 2VR_A2DAMM_MaintOrderTech

Transformations/Calculations:

• Planned downtime window derived from Scheduled Basic Start and End date/time.
• PlannedVsUnplanned flag set to 'PLANNED'.
• SourceType set to 'ORDER'.

3VR_A2DAMM_UnplannedDownTime

Source: 2VR_A2DAMM_PMNotifMaintenanceData

Calculation:

• Unplanned downtime duration sourced from MaintObjectDowntimeDuration (seconds). 
• PlannedVsUnplanned flag set to 'UNPLANNED'.
• SourceType set to 'NOTIF'.

3VF_A2MAMM_PMNotifMaintenanceData

Source: 2VR_PMNotif

Logic / Adjustments:

• Project the notification-centric reporting grain (1 row per Maintenance Notification).
• Include required dimensions from the FS (e.g., Notification Type/Priority/Origin, Maintenance Plant, Creation Date/Time, Equipment, Functional Location).
• Include raw downtime duration (seconds) and derived hours where required (no pre-aggregation).

3VF_A2DAMM_DowntimeFact

Union:
Purpose: Combine planned and unplanned downtime into a single reusable downtime fact.

Union of: 3VR_A2DAMM_UnplannedDownTime & 3VR_A2DAMM_PlannedDownTime

Target Field Mapping:
- Technical Object fields aligned across both sources.
- Downtime duration stored in hours (conversion applied where required).

No aggregation is performed at this stage.

Datamodel, calculations and associations.

Projection:

Projection before union. Two objectives: 

Create a shared downtime schema. 

• SourceType = 'ORDER' / 'NOTIF'
• PlannedVsUnplanned = 'PLANNED' / 'UNPLANNED'
• DowntimeSeconds and/or DowntimeHours
• Normalise Functional Location: I_PMNotifMaintenanceData.RelevantFunctionalLocation & I_MaintOrderTechObjCube._LocationAccountAssignment.FunctionalLocation

Standardise time fields

• Planned: map scheduled basic start/end into StartDateTime, EndDateTime

• Unplanned: map malfunction start/end into StartDateTime, EndDateTime

Union:

Common fields

• Equipment
• Functional Location
• MaintenancePlanningPlant
• MaintenancePlannerGroup
• MaintenancePlant

Reporting Layer

4MA_A2DAMM_DowntimeFact

Supports:

• ERP-1012 Asset Down Time Planned vs Unplanned
• ERP-1012 Loss Driver (# breakdown hours)

Includes technical details for:

• Post-aggregation calculations
• Restricted measures
• Time-based analysis and drill-through

Calculated Measures (Post Aggregation Calculations / exception aggregation etc)

Restricted Measures

tbd

Currency Conversions

tbd

Variables

Data access controls

4MA_A2DAMM_PMNotifMaintenanceData

Supports:

• ERP-1012 Loss Driver (# breakdown hours) – unplanned downtime hours from notifications
• ERP-1012 Loss Driver (# notifications) – notification counts and status-driven slicing
• ERP-1012 Technical Availability (input measures) – unplanned downtime and breakdown flags used in SAC availability calculations
• ERP-1013 MTBF assuming the definition is "Time between failure events".*

*Since this potentially is the difference between two consecutive breakdown records, more calculations may be required in a separate model. Complexity ramps up if it requires actual operating hours between failures.

Includes technical details for:

• Post-aggregation calculations in SAC (e.g., hours conversions, ratios, availability formulas)
• Restricted measures by breakdown / downtime flags and status
• Time-based analysis (malfunction start/end, creation dates) and drill-through to Maintenance Notification

Dimensions & Measures are defined in the Functional Specification under “Dimensions & Measures: Requirements View”; the analytical model exposes those fields at notification grain without pre-aggregation.

Calculated Measures (Post Aggregation Calculations / exception aggregation etc)

Outbound Layer