Document Links
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
This document describes the data flow for objects in the technical space.
| Sub-Area | Details | Example KPIs | Comments |
|---|---|---|---|
| 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:
| 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:
Jira server Syensqo's Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId d8efc1ef-48bd-3b4e-8714-ad827f4f059b key ERP-1107
Data Flow Diagram
| draw.io Diagram | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Table of Contents | ||||
|---|---|---|---|---|
|
Source System Extractors
| Extractor Name | Build Jira Ref For Extension Information | Comment | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TBC Signavio Report |
| 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. |
N.B. The file extract is a shared program which produces the data for multiple use cases, including stand alone CSV/Excel files. It was requested to have normalised files separating process and master data but this was rejected.
Inbound Layer
1TL_TECPRO_SIGNAVIOPROCESSCHANGES_01
| Warning |
|---|
This table will contain data from the most recent file load ONLY! |
...
An additional column 'export timestamp' is appended to the data. This is added to the file header by the Signavio report and applied by CPI.
Harmonisation Layer
2TL_TECPRO_SignavioProcessChanges_01
This table will store historical snapshots of data loaded from 1TL_TECPRO_SIGNAVIOPROCESSCHANGES_01. It should never contain the most recent data. The process for the population of this table is described under 1TL_TECPRO_SIGNAVIOPROCESSCHANGES_01.
2VR_TECPRO_SignavioProcessHistory_01
Purpose
Prepare table data for use.
Source
2TL_TECPRO_SignavioProcessChanges_01
Calculation
Fields used in comparison logic in subsequent views will be checked to ensure that they are not null. If they are null then the null value will be replaced by space. These fields are: Process ID, Task ID, Lane Name, App ID, Dictionary Link, ExportTimestamp.
2VR_TECPRO_SignavioProcessMostRecent_01
Purpose
Prepare table data for use.
Source
1TL_TECPRO_SIGNAVIOPROCESSCHANGES_01
Calculation
Fields used in comparison logic in subsequent views will be checked to ensure that they are not null. If they are null then the null value will be replaced by space. These fields are: Process ID, Task ID, Lane Name, App ID, Dictionary Link, ExportTimestamp.
Propagation Layer
3VR_TECPRO_SignavioSwimLaneChanges_02
Calculation
Source 1
2VR_TECPRO_SignavioProcessHistory_01
Filter
"IT System category name" is null
Calculation
Map fields to equivalent DCD name to allow them to be identifiable as being from a different source post full join.
Projection
Restrict field list to that just new DCD fields
Source 2
2VR_TECPRO_SignavioProcessMostRecent_01
Filter
"IT System category name" is null
Projection
Restrict to equivalent fields as seen in projection from source 1.
Join
Full join of data from Source 1 and Source 2 as Many:Many
Key fields are: Process ID, Task ID, Lane Name, Dictionary LinkA 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 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)
3VF_TECPRO_SignavioSwimLaneChanges_02
Source Current data
Filter
IT System Category is Null - Only steps executed by humans
...
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