| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Standard Edition
Object Level
Data Lineage at Object level for DDIC Entities.
We export two files: one file with all the relations of DDC Entities (“Relations”) and one file with more details (e.g. Technical Name and descriptions) (“Details”) of the entities.
In the “Relations” file only entities are included that have a connection in the data lineage. E.g.
a View with
its base tables.
In the Details file, we identify CDS Data Definition.
The supported entities for the
Object level are the following:
Tables
Views
CDS Data Definitions
Transactions
Structures (INTTAB) and Append-Structures (APPEND) are not supported.
Field Level
Data Lineage at Field level for DDIC Entities.
Every origin of and between Fields will be part of the premium edition. We do not parse code (at the moment) and simply show the 1on1 Mappings of tables and views we get from SAP.
We export 3 more files:
Buildups - with all buildups of tables, views, and data definitions. Datatype, length, and decimals of fields.
BuildupDescriptions - with the descriptions of the fields
Mappings - with the 1on1 Mapping of the fields between tables, views, and data definitions
Extended Edition
currently, there is no extended edition for parsing the codeParsing the ABAP Code
Wit the S/4HANA connector it is possible to scan the ABAP code too. We identify which ABAP code is calling other ABAP codes. We also find out which tables are modified and which are read by the ABAP code. This is how we map a data lineage. Here you can find a list of key words which are identified in ABAP code.
| Info |
|---|
If you want to see more in the Data Lineage Metadata API. Get in touch with us and create a Feature Request at https://bluetelligence.atlassian.net/servicedesk |