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 |
The models covered under this DDFS will cater for the requirements raised though the following Jira Requests:
| 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.
This table will contain data from the most recent file load ONLY! |
Prior to each new load of data, the existing data in this table will be moved to 2TL_TECPRO_SignavioProcessChanges_01 using transformation flow 2FT_TECPRO_SignavioProcessChanges_01 and then the contents of 1TL_TECPRO_SIGNAVIOPROCESSCHANGES_01 will be deleted. This is required to support the swimlane comparison reporting.
The table will receive fields delivered by the SAP report:
Process ID
Process name
Revision number
L1-L4 decomposition
Process Owner
Last change date
Last changed by
POD
Release
Sub-Function
Task name
Task type
Task ID
Pool name
Lane name
IT System title
IT System category name
LeanIX Link
Executable name
Executable category name
App ID
App name
App type
UI technology
Application component
Dictionary Link
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.
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.
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.
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.
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: 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.
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.
Link to FSD (Each Analytic model should have its own FSD).
Include technical details for:
Detail restrictions
Detail rate type, from currency
Link to FSD (Each Analytic model should have its own FSD).
Include technical details for:
Detail restrictions
Detail rate type, from currency