Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7
outlinetrue
indent10px
separatornone

Standard Edition

Object Level

Data Lineage at Object level for

BW

DDIC Entities.
We export two files: one file with all the relations of

BW

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

a

the data

flow

lineage. E.g.

an Advanced DSO without an incoming or outgoing transformation or an Composite or Open ODS View on top is not listed in the data

a View with its base tables.

In the Details file, we identify CDS Data Definition.

The supported entities for the

standard edition Premium Edition

Object level are the following:

  • BW Queries

  • Restricted Key Figures

  • Calculated Key Figures

  • Composite Providers

  • Advanced Data Store Objects (ADSO)

  • Open ODS Views

  • InfoSources

  • DataSources

  • InfoObjects as InfoProviders

  • Open Hub Destinations

  • Aggregation Levels

  • AfO Workbooks stored in BW

  • MultiProvider

  • Data Store Objects

  • InfoCubes

  • InfoSets

  • HybridProvider

  • HANA Artifacts consumed by Composite Providers and Open ODS Views

In Standard Edition we display the relations of InfoProvider to reusable Key Figures (restricted and calculated Key Figure) only. The definitions of key figures and their relation among each other and BW Queries are part of the Premium Edition.

  • Tables

  • Views

  • CDS Data Definitions

  • Transactions

(info) Structures (INTTAB) and Append-Structures (APPEND) are not supported.

Field Level

Data Lineage at Field

/InfoObject

level for

BW

DDIC Entities.

Every origin of and between Fields

and InfoObjects

will be part of the premium edition.

Which mappings are supported:

  • Mappings in Composite Providers

    • Direct Assignment

    • Formulas

    • Constants

  • Mappings in Open ODS Views

  • Assignments/rules in Transformations

    • Description of rules in Transformations

    • Type of rules in transformations (Constant, Formula, Field Routine, Lookup, End Routine, Start Routine, Expert Routine Direct Mapping)

    • Value of constants rules

    • Definition of formulas rules

    • Lookup object of lookup rules

All field and InfoObjects Mappings are supported for the BWonHANA entities only. That are the following:

  • BW Queries

  • Composite Providers

  • Advanced Data Store Objects (ADSO)

  • Open ODS Views

  • InfoSources

  • DataSources

  • InfoObjects as InfoProviders

  • Open Hub Destinations

  • Aggregation Levels

  • HANA Artifacts consumed by Composite Providers and Open ODS Views

Definition of Key Figures

The Premium edition reads out also the definitions of key figures on Reporting level. The definition of the following entity types are collected:

  • Calculated Key Figures

  • Restricted Key Figures

  • Local Formulas

  • Local Selections

Extended Edition

The Extended Edition includes more information about the transformations and rules of Field/InfoObject Data Lineage.

The following information is part of the Extended Edition:

  • Lookups and calls of

    • Tables

    • Views

    • Function Modules

    • Methods

    • CDS Entities

    • ABAP Reports or Includes

  • in

    • Start Routines (ABAP & AMDP)

    • End Routines (ABAP & AMDP)

    • Expert Routines (ABAP & AMDP)

    • and Field Routines (ABAP & AMDP)

Limitations

No differentiation is made between different rule groups.

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


Parsing 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 Metadata API. Get in touch with us and create a Feature Request at https://bluetelligence.atlassian.net/servicedesk