/
Scope of SAP S/4HANA Connector

Scope of SAP S/4HANA Connector

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.

The supported entities for the Object level are the following:

  • Tables

  • Views/CDS Views

  • Function Modules

  • Transactions

  • Data Sources/Extractors

  • ABAP Class

  • ABAP Program/Report

  • Domain

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

Details

In the Details file, we also identify CDS Data Definitions.

These parameters are displayed per object:

  • Object ID

  • Technical Name

  • Object type

  • Data Definition (only for CDS Views)

  • Subtype (only for Tables)

  • Development class

  • Component

  • Language dependent Description

Relations

In the “Relations” file, only entities connected in the data lineage are included, e.g., a View with its base tables.

This information is displayed:

  • Nodes: ID of Objects with a relation to another

  • Edges: Relation ID, ID of Source and Target Object.

Field Level

Data Lineage at Field level for DDIC Entities.

Three files are exported: one file with the buildup of DDIC entities (“Buildups”), one with the descriptions of the fields (“Buildup Descriptions”), and one file with the mappings between the fields (“Mappings”).

 Buildup

The fields and their parameters are displayed per objects like this:

  • Parent ID

    • Field ID

      • Technical name

      • Data type

      • Length

      • Decimals (for data types DEC, CURR, QUAN & FLTP)

Buildup Descriptions

The Buildup Descriptions file lists the IDs and descriptions of all fields.

Mappings

In the “Mappings” file, only fields connected in the data lineage are included.

This information is displayed:

  • Nodes: ID of fields with a relation to another

  • Edges: Relation ID, ID of Source and Target Field.


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.

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

Related content

© 2024 bluetelligence GmbH. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of bluetelligence GmbH. The information contained herein may be changed without prior notice. bluetelligence and Performer Suite and their respective logos are trademarks or registered trademarks of bluetelligence GmbH. SAP, ABAP, BAPI, SAP NetWeaver, SAP BI, SAP BW, SAC, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company. All other product and service names mentioned are the trademarks of their respective companies.
Impressum – Legal Notice: https://bluetelligence.de/en/imprint
Privacy policy: https://bluetelligence.atlassian.net/wiki/spaces/DMA/pages/4188635149/Privacy+Policy
Atlassian privacy policy: https://www.atlassian.com/legal/privacy-policy