You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Document Links

ERP-2921 - Getting issue details... STATUS

Introduction

This document describes the data flow for objects in the technical space.

Sub-AreaDetailsExample KPIsComments
TECPRO - Signavio Process Manager

Signavio is the source of truth for which task is performed by which process role using which executable (e.g. Fiori app, transaction, report, etc.). However Signavio does not provide sufficient reporting capability to meet the needs of various downstream consumers of this information, who need to use information from the process models to answer various questions in order to perform subsequent work. Examples include:

  • Show me all of the executables assigned to a process role (i.e. swimlane) across all of the L4 models, so that system authorizations can be created accordingly.

  • Show me all of the process roles which contain a particular executable

  • Show me what has changed between two revisions of a process model

  • Show me what has changed across all process models between two different dates

  • Show me what tasks and executables have been added and removed from a particular swimlane (process role) across all process models in a particular POD, between two given dates.

N/A The reporting is focused on comparing versions of data


Jira Request Coverage

The models covered under this DDFS will cater for the requirements raised though the following Jira Requests:

ERP-1107 - Getting issue details... STATUS

Data Flow Diagram



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 NameBuild Jira Ref For Extension InformationComment
TBC Signavio Report

ERP-2408 - Getting issue details... STATUS

Data is extracted from Signavio using a report written by SAP. It will post data to CPI which, in turn, will make this data available to via a REST API.  The functionality to extract data from REST APIs is not available till the Q2 2026 release which (at time of writing) has not yet been delivered.

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_TECPRO_SIGNAVIOPROCESSCHANGES_01

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_TECPRO_SignavioProcessChanges_01

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_TECPRO_SignavioProcessHistory_01

Calculation

Calculated measure: CM_PRICE = Value / Quantity. (Ubiquitously true, reusable change made at lowest level possible).

2VR_TECPRO_SignavioProcessMostRecent_01

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_TECPRO_SignavioSwimLaneChanges_02

Calculation

A line item level calculation which applies specific business rules that are owned by the POD would be added here.

3VR_TECPRO_SignavioProcessUnion_01

Join

Purpose: etc

3VR_TECPRO_SignavioProcessLinkAppToSys_01

Join

Purpose: etc

3VF_TECPRO_SignavioProcessUnion_01

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)

3VF_TECPRO_SignavioSwimLaneChanges_02

Source Current data 

Filter
IT System Category is Null - Only steps executed by humans

Projection
Remove all fields not relevant to swimlanes


Source Previous Snapshot
Filter
IT System Category is Null - Only steps executed by humans

Calculation
Rename all fields relevant to Swimlanes to DCD_ to identify separately in join

Projection 
Remove all fields not relevant to swimlanes


Union
Fields

Calculation
Reorder fields such that field equivalents are alongside each other.

Reporting Layer

4MA_TECPRO_SignavioProcessUnion_01

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

4MA_TECPRO_SignavioSwimLaneChanges_02

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