Data pedigree collection method, device and storage medium based on SAP BW

Abstract

The present invention relates to the field of data governance and discloses a data lineage collection method, device, and storage medium based on SAP BW. The method comprises: obtaining a data object from SAP BW; analyzing the data type of the data object; when the data type is an output carrier table, using a preset text analyzer to parse the field data using SQL statements to obtain a syntax tree, and extracting the data lineage corresponding to the data object from the syntax tree; when the data type is an ADSO type, parsing the dependency relationship of metadata information through a preset RFC interface to obtain the data lineage corresponding to the data object; when the data type is a calculation view, querying the calculation view definition corresponding to the data object through a preset JDBC interface to obtain XML data in a BW standard format; parsing the data object to obtain the data lineage corresponding to the data object. In an embodiment of the present invention, the collection and acquisition of field-level data lineage relationships in an SAP BW environment is implemented.

Description

Technical Field

[0001] The present invention relates to the field of data governance, and in particular to a data lineage collection method, device, and storage medium based on SAP BW. Background Art

[0002] SAP BW is a powerful business intelligence tool that can be used to manage and analyze enterprise data. However, as enterprise data continues to grow, users face increasing challenges in understanding and managing this data.

[0003] Currently, data lineage is widely used in software fields such as data governance and low-code. Numerous industry reference implementations exist for obtaining the lineage relationships between related data objects from relational databases and big data platforms (Hadoop). Examples include direct retrieval from metadata or parsing from SQL and other code. However, automated retrieval of field-level lineage relationships between data objects in SAP BW environments remains challenging. Due to the diverse range of data objects within SAP BW systems, it is impossible to extract data lineage relationships as is possible with relational databases. Even SAP's data integration (DI) products cannot provide data lineage relationships at the object-to-field level, supporting only object-level data lineage relationships. Consequently, they are unable to capture the lineage relationships between internal SAP BW objects, including information objects, transformations, and processing chains. Since field-level data lineage relationships cannot be effectively obtained within SAP BW environments, a new technology is needed to address this issue. Summary of the Invention

[0004] The main purpose of the present invention is to solve the technical problem that the data lineage relationship at the field level cannot be effectively obtained in the SAP BW environment.

[0005] A first aspect of the present invention provides a data lineage collection method based on SAP BW, the data lineage collection method based on SAP BW comprising:

[0006] Acquire a data object of SAP BW, wherein the data object includes: field data and metadata information corresponding to the field data;

[0007] Analyzing the data type of the data object;

[0008] When the data type is an output carrier table, a preset text analyzer is used to parse the field data into SQL statements to obtain a syntax tree, and a data lineage corresponding to the data object is extracted from the syntax tree;

[0009] When the data type is ADSO type, the dependency relationship of the metadata information is parsed through a preset RFC interface to obtain the data pedigree corresponding to the data object;

[0010] When the data type is a calculation view, the calculation view definition corresponding to the data object is queried through the preset JDBC interface to obtain XML data in the BW standard format;

[0011] Based on the XML data and the creation attributes of the data object, a data pedigree corresponding to the data object is obtained.

[0012] Optionally, in a first implementation of the first aspect of the present invention, obtaining the data pedigree corresponding to the data object based on the XML data and the creation attribute of the data object includes:

[0013] Determine whether the creation attribute of the data object is interface editing creation;

[0014] When creating for interface editing, the XML data is parsed to obtain the data pedigree corresponding to the data object;

[0015] When it is not created for interface editing, a preset text analyzer is called to perform SQL statement parsing on the field data to obtain a syntax tree, and the data lineage corresponding to the data object is extracted from the syntax tree.

[0016] Optionally, in a second implementation of the first aspect of the present invention, before obtaining the SAP BW data object, the method further includes:

[0017] Connect to the pre-installed HANA database through the pre-installed JDBC interface, and connect to the pre-installed BW database through the JCO component.

[0018] Optionally, in a third implementation of the first aspect of the present invention, obtaining the SAP BW data object includes:

[0019] Based on the preset DatabaseMetaData interface, obtain SAP BW entity data from the HANA database;

[0020] Obtaining SAP BW application layer data from the BW database based on a preset RFC interface;

[0021] The entity data and the application layer data are combined and processed to generate a data object.

[0022] Optionally, in a fourth implementation of the first aspect of the present invention, querying the calculation view definition corresponding to the data object through the preset JDBC interface to obtain XML data in the BW standard format includes:

[0023] Query the stored data corresponding to the calculation view from the HANA database through the preset JDBC interface;

[0024] According to a preset query function, query the system table in the stored data to obtain the calculation view definition corresponding to the data object;

[0025] Based on the preset BW standard format, the calculation view definition corresponding to the data object is converted to obtain XML data in the BW standard format.

[0026] Optionally, in a fifth implementation of the first aspect of the present invention, querying a system table in the stored data according to a preset query function to obtain a calculation view definition corresponding to the data object includes:

[0027] According to the preset query function, the _SYS_REPO.ACTIVE_OBJECT system table in the stored data is queried to obtain the calculation view definition corresponding to the data object.

[0028] Optionally, in a sixth implementation of the first aspect of the present invention, the using a preset text analyzer to perform SQL statement parsing on the field data to obtain a syntax tree includes:

[0029] The preset JavaCC analyzer is used to perform SQL statement parsing processing on the field data to obtain a syntax tree.

[0030] Optionally, in a seventh implementation of the first aspect of the present invention, after acquiring the SAP BW data object and before analyzing the data type of the data object, the method further includes:

[0031] The access path of the data object is MD5-encoded to obtain an encrypted access path, and the encrypted access path is stored in a preset history database.

[0032] A second aspect of the present invention provides a data lineage acquisition device based on SAP BW, comprising: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; the at least one processor calls the instructions in the memory so that the data lineage acquisition device based on SAP BW executes the above-mentioned data lineage acquisition method based on SAP BW.

[0033] A third aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the above-mentioned data lineage collection method based on SAP BW.

[0034] In an embodiment of the present invention, by first obtaining the data objects of the SAP BW tool and then analyzing the types of the data objects, using SQL parsing to extract metadata objects and data lineages based on the type classification of the data objects, or obtaining the data lineages of more BW data objects through the call of the RFC interface, a complete field-level data graph relationship map can be returned, effectively supporting data governance scenarios and upper-level applications using data graph relationships, overcoming the inability to effectively obtain field-level data lineage relationships in the SAP BW environment, and realizing the collection and acquisition of field-level data lineage relationships in the SAP BW environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 Schematic diagram of an embodiment of a data lineage collection method based on SAP BW in an embodiment of the present invention;

[0036] Figure 2 102 is a schematic diagram of an embodiment of the data lineage collection method based on SAP BW in an embodiment of the present invention;

[0037] Figure 3 105 is a schematic diagram of an embodiment of the data lineage collection method based on SAP BW in an embodiment of the present invention;

[0038] Figure 4 106 is a schematic diagram of an embodiment of the data lineage collection method based on SAP BW in an embodiment of the present invention;

[0039] Figure 5 Schematic diagram of an embodiment of a data lineage acquisition device based on SAP BW in an embodiment of the present invention. DETAILED DESCRIPTION

[0040] Embodiments of the present invention provide a data lineage collection method, device, and storage medium based on SAP BW.

[0041] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0042] In the description of the embodiments disclosed herein, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to." The term "based on" should be understood as "based, at least in part, on." The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0043] For ease of understanding, the specific process of the embodiment of the present invention is described below. Figure 1 In one embodiment of the present invention, a data lineage collection method based on SAP BW includes:

[0044] 101. Obtain a data object of SAP BW, wherein the data object includes: field data and metadata information corresponding to the field data;

[0045] In this embodiment, SAP BW (Business Warehouse) is an enterprise-level data warehouse platform. It allows enterprises to integrate, transform, and merge relevant business information from SAP applications and external data sources. Data objects whose data lineages require collection are obtained from the SAP BW platform. These data objects contain field data and metadata corresponding to the field data. Metadata is obtained from the data source and classified, uniformly coded, and the lineage of the data objects is collected to generate a data map for analysis and use. The processed metadata is stored in a database for subsequent query and analysis.

[0046] Specifically, before step 101, the following steps are also included:

[0047] 1011. Connect to the pre-installed HANA database through the pre-installed JDBC interface, and connect to the pre-installed BW database through the JCO component.

[0048] In step 1011, a connection to SAP BW is established based on the configured and registered data source. The connection includes connecting to the HANA database using the JDBC interface and connecting to the BW database through the JCO component.

[0049] JDBC (Java Database Connectivity) is a Java API that provides a standard way for Java programs to connect to databases and execute SQL statements. JDBC is a database-independent interface, meaning it allows developers to write database applications in Java without having to worry about the specific details of the underlying database. JDBC also makes it easy for developers to switch between different databases because it provides a unified interface for accessing multiple databases.

[0050] SAP Java Connector (JCO) is a middleware component used to facilitate communication between Java applications and SAP systems. SAP JCO supports two types of connections: inbound remote function calls (Java calling ABAP) and outbound remote function calls (ABAP calling Java). This component enables Java applications to access the RFC (Remote Function Call) functionality of the SAP system, enabling data exchange and processing. SAP JCO can be used in desktop and web applications, and can also be embedded as a component in other programs, such as SAP Business Connector and SAP Web Application Server.

[0051] For details, please refer to Figure 2 , Figure 2 This is an embodiment of step 102 of the data lineage collection method based on SAP BW in an embodiment of the present invention. In the embodiment of step 1011, step 101 includes the following specific implementation methods:

[0052] 1012. Based on the preset DatabaseMetaData interface, obtain SAP BW entity data from the HANA database;

[0053] 1013. Acquire SAP BW application layer data from the BW database based on a preset RFC interface;

[0054] 1014. Combine the entity data and the application layer data to generate a data object.

[0055] In steps 1012-1014, the DatabaseMetaData interface is part of the JDBC API. It provides metadata about the database and retrieves SAP BW entity data from the HANA database, including schemas, tables, and views, as well as the fields and related metadata contained in these entity data.

[0056] The Remote Function Call (RFC) interface is a standard communication method that allows SAP BW to exchange data and communicate programs with other SAP and non-SAP systems. The RFC interface retrieves BW application-layer objects, including advanced storage objects (ADSOs), visualization views, composite information objects (CPs), information objects (IOs), process chains, transformations, and query objects.

[0057] Finally, the obtained entity data and application layer data are combined and processed to generate data objects.

[0058] 102. Analyze the data type of the data object;

[0059] In this embodiment, the data type of the data object is analyzed, and different parsing processors are called based on the data type.

[0060] Furthermore, after step 101 and before step 102, the following specific implementation methods are also included:

[0061] 1021. Perform MD5 encoding on the access path of the data object to obtain an encrypted access path, and store the encrypted access path in a preset history database.

[0062] In step 1021, all data object acquisition access paths are MD5-encoded to obtain encrypted access paths, and the encrypted access paths are stored in a preset historical database so that the data object acquisition method can be directly traced back through the access path to track the source of the data object.

[0063] 103. When the data type is an output carrier table, a preset text analyzer is used to parse the field data into an SQL statement to obtain a syntax tree, and a data lineage corresponding to the data object is extracted from the syntax tree;

[0064] In this embodiment, when the data type is an output carrier table, that is, some data output carrier tables used in the SAP BW platform, they are simplified into queries, composite providers, and infoobjects in BW / 4HANA.

[0065] Query: In BW / 4HANA, a query is a data output medium that provides data based on HANA views and allows calculation views of these output mediums to be generated in the HANA underlying layer. This allows front-end tools to use these data sources individually or in combination, just like general HANA views.

[0066] Composite Provider: Composite Provider allows you to merge data from BW InfoProviders with HANA modeling views and provide data externally by combining other virtual objects.

[0067] InfoObject: The concept of information object is retained in BW / 4HANA as a fundamental element of data modeling.

[0068] Use the syntax parser and lexical parser to parse the field data. The statement in the form of "SELECT view dependent data object field list FROM view dependent object WHERE dependent restriction conditions" is translated into an abstract syntax tree. The data lineage corresponding to the view field-level data objects is extracted from the syntax tree.

[0069] Specifically, step 103 includes the following specific implementation methods:

[0070] 1031. Use a preset JavaCC analyzer to parse the field data using SQL statements to obtain a syntax tree.

[0071] In step 1031, JavaCC (Java Compiler) is a tool used to generate a lexical analyzer and a parser. It reads a lexical and grammatical description file (usually ending in .jj) and generates a Java program that includes the lexical analyzer and parser. The lexical analyzer generated by JavaCC can parse the input character sequence into individual tokens and classify these tokens. Therefore, the JavaCC analyzer is used to parse the SQL statement on the field data to generate a syntax tree.

[0072] 104. When the data type is ADSO type, the dependency relationship of the metadata information is parsed through a preset RFC interface to obtain a data pedigree corresponding to the data object;

[0073] In this example, ADSO-type data is a key data model object in SAP BW / 4HANA, used to store and manage factual data within the data warehouse. In BW / 4HANA, traditional cubes and DSOs are converted to Advanced DSOs for data storage and integration. This approach directly retrieves data object metadata within the BW database through the RFC interface. During metadata retrieval, dependencies within objects such as processing chains and transformations are resolved to extract field-level data lineages.

[0074] 105. When the data type is a calculation view, query the calculation view definition corresponding to the data object through the preset JDBC interface to obtain XML data in the BW standard format;

[0075] In this example, calculation views are an advanced feature of the SAP HANA database in the SAP BW environment. They allow users to create complex SQL queries and data processing logic using a graphical interface or SQL scripts. The calculation view definitions corresponding to the HANA database system tables are queried using the JDBC interface and saved as XML data in the BW standard format.

[0076] For details, please refer to Figure 3 , Figure 3 This is an embodiment of step 105 of the data lineage collection method based on SAP BW in an embodiment of the present invention. In the embodiment of step 1011, step 105 includes the following specific implementation methods:

[0077] 1051. Query the stored data corresponding to the calculation view from the HANA database through a preset JDBC interface.

[0078] 1052. Query the system table in the stored data according to a preset query function to obtain the calculation view definition corresponding to the data object;

[0079] 1053. Based on the preset BW standard format, the calculation view definition corresponding to the data object is converted to obtain XML data in the BW standard format.

[0080] In steps 1051-1053, the stored data corresponding to the calculation view is retrieved from the HANA database using a pre-configured JDBC interface. Then, using a pre-configured query function, the system table "_SYS_REPO."ACTIVE_OBJECT" in the stored data is queried to obtain the visualization view definition. The visualization view definition is stored as an XML document in the BW standard format. This XML document is then parsed to obtain the visualization view's data map.

[0081] Furthermore, in step 1052, the following specific implementations are included in step 1052:

[0082] 10521. According to a preset query function, query the _SYS_REPO.ACTIVE_OBJECT system table in the stored data to obtain the calculation view definition corresponding to the data object.

[0083] In step 10521, a preset query function is used to directly retrieve the _SYS_REPO.ACTIVE_OBJECT system table to obtain the calculation view definition corresponding to the data object. "_SYS_REPO" is a system schema in SAP HANA that stores design-time models and runtime objects. "ACTIVE_OBJECT" is a table within this schema that stores metadata about active objects. In SAP HANA, models and views are ultimately managed centrally by the _SYS_REPO user. Therefore, the "_SYS_REPO."ACTIVE_OBJECT" table contains detailed information about active objects, which is crucial for managing and maintaining the SAP HANA database.

[0084] 106. Based on the XML data and the creation attributes of the data object, obtain the data pedigree corresponding to the data object.

[0085] In this embodiment, when the data object is created for interface creation, the content in the XML data is parsed to obtain the data pedigree corresponding to the data object.

[0086] For further information, see Figure 4 , Figure 4 This is an embodiment of step 106 of the data lineage collection method based on SAP BW in an embodiment of the present invention. Step 106 also includes the following specific implementation methods:

[0087] 1061. Determine whether the creation attribute of the data object is interface editing creation;

[0088] 1062. When creating an interface for editing, the XML data is parsed to obtain a data pedigree corresponding to the data object;

[0089] 1063. When the interface is not edited and created, a preset text analyzer is called to perform SQL statement parsing on the field data to obtain a syntax tree, and the data lineage corresponding to the data object is extracted from the syntax tree.

[0090] In steps 1061-1063, a determination is made as to whether the data object's creation attribute indicates "created by interface editing." If so, the XML data is parsed to obtain the data lineage corresponding to the data object. If not, the data object is considered to have been created using SQL. The Javacc text analyzer is then invoked to parse the field data using SQL statements to obtain a syntax tree. The data lineage corresponding to the data object is then extracted from the syntax tree.

[0091] After obtaining the data lineage, you can first store the metadata information of the data object and its fields, and then store the data lineage between data objects. All data objects are MD5-encoded according to their complete unique access path, and then the unique access path is stored to achieve bound storage of data related to the data lineage.

[0092] In an embodiment of the present invention, by first obtaining the data objects of the SAP BW tool and then analyzing the types of the data objects, using SQL parsing to extract metadata objects and data lineages based on the type classification of the data objects, or obtaining the data lineages of more BW data objects through the call of the RFC interface, a complete field-level data graph relationship map can be returned, effectively supporting data governance scenarios and upper-level applications using data graph relationships, overcoming the inability to effectively obtain field-level data lineage relationships in the SAP BW environment, and realizing the collection and acquisition of field-level data lineage relationships in the SAP BW environment.

[0093] Figure 5 This is a schematic diagram of the structure of a SAP BW-based data lineage collection device provided by an embodiment of the present invention. This SAP BW-based data lineage collection device 500 can vary significantly depending on configuration or performance. It may include one or more central processing units (CPUs) 510 (e.g., one or more processors), memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) for storing application programs 533 or data 532. The memory 520 and storage media 530 may be either transient or persistent storage. The program stored in the storage medium 530 may include one or more modules (not shown), each of which may include a series of instructions for operating on the SAP BW-based data lineage collection device 500. Furthermore, the processor 510 may be configured to communicate with the storage medium 530 to execute the series of instructions stored in the storage medium 530 on the SAP BW-based data lineage collection device 500.

[0094] The SAP BW-based data lineage acquisition device 500 may further include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input and output interfaces 560, and / or one or more operating systems 531, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. It will be understood by those skilled in the art that Figure 5The structure of the SAP BW-based data lineage acquisition device shown does not limit the SAP BW-based data lineage acquisition device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0095] The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to execute the steps of the SAP BW-based data lineage acquisition method.

[0096] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0097] In addition, although adopting specific order to describe each operation, this should be understood as requiring such operation to be carried out in the specific order shown or in sequential order, or requiring that all illustrated operations should be carried out to obtain desired results. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although comprising some specific implementation details in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of separate embodiment can also be implemented in a single implementation in combination. On the contrary, the various features described in the context of a single implementation also can be implemented in a plurality of implementations individually or in the mode of any suitable subcombination.

[0098] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A data lineage collection method based on SAP BW, characterized in that: Including steps: Acquire a data object of SAP BW, wherein the data object includes: field data and metadata information corresponding to the field data; Analyzing the data type of the data object; When the data type is an output carrier table, a preset text analyzer is used to perform SQL statement parsing on the field data to obtain a syntax tree, and a data lineage corresponding to the data object is extracted from the syntax tree, wherein the output carrier table includes: query, composite provider, and information object; When the data type is ADSO type, the dependency relationship of the metadata information is parsed through a preset RFC interface to obtain the data pedigree corresponding to the data object; When the data type is a calculation view, the calculation view definition corresponding to the data object is queried through the preset JDBC interface to obtain XML data in the BW standard format; Obtaining a data pedigree corresponding to the data object based on the XML data and creation attributes of the data object; Before obtaining the SAP BW data object, the method further includes: Connect to the pre-installed HANA database through the pre-installed JDBC interface, and connect to the pre-installed BW database through the JCO component; The step of querying the calculation view definition corresponding to the data object through the preset JDBC interface to obtain XML data in the BW standard format includes: Query the stored data corresponding to the calculation view from the HANA database through the preset JDBC interface; According to a preset query function, query the system table in the stored data to obtain the calculation view definition corresponding to the data object; Based on the preset BW standard format, the calculation view definition corresponding to the data object is converted to obtain XML data in the BW standard format; The step of querying the system table in the stored data according to a preset query function to obtain the calculation view definition corresponding to the data object includes: According to the preset query function, the _SYS_REPO.ACTIVE_OBJECT system table in the stored data is queried to obtain the calculation view definition corresponding to the data object.

2. The data lineage collection method based on SAP BW according to claim 1, characterized in that: The obtaining of the data pedigree corresponding to the data object based on the XML data and the creation attribute of the data object includes: Determine whether the creation attribute of the data object is interface editing creation; When creating for interface editing, the XML data is parsed to obtain the data pedigree corresponding to the data object; When it is not created for interface editing, a preset text analyzer is called to perform SQL statement parsing on the field data to obtain a syntax tree, and the data lineage corresponding to the data object is extracted from the syntax tree.

3. The data lineage collection method based on SAP BW according to claim 1, characterized in that: The data object of obtaining SAPBW includes: Based on the preset DatabaseMetaData interface, obtain SAP BW entity data from the HANA database; Obtaining SAP BW application layer data from the BW database based on a preset RFC interface; The entity data and the application layer data are combined and processed to generate a data object.

4. The data lineage collection method based on SAP BW according to claim 1, characterized in that: The SQL statement parsing process is performed on the field data by using a preset text analyzer to obtain a syntax tree including: The preset JavaCC analyzer is used to perform SQL statement parsing processing on the field data to obtain a syntax tree.

5. The data lineage collection method based on SAP BW according to claim 1, characterized in that: After acquiring the SAP BW data object and before analyzing the data type of the data object, the method further includes: The access path of the data object is MD5-encoded to obtain an encrypted access path, and the encrypted access path is stored in a preset history database.

6. A data lineage collection device based on SAP BW, characterized in that: The SAP BW-based data pedigree acquisition device includes: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor calls the instructions in the memory to enable the SAP BW-based data lineage collection device to execute the SAP BW-based data lineage collection method according to any one of claims 1 to 5.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for collecting data lineage based on SAP BW according to any one of claims 1 to 5 is implemented.

Images