SAP BW-based data pedigree acquisition method and device, and storage medium

Abstract

The invention relates to the field of data management, and discloses a data pedigree collection method and device based on SAP BW and a storage medium. The method comprises the following steps: acquiring a data object of the SAP BW; analyzing the data type of the data object; when the data type is an output carrier table, performing SQL statement analysis processing on the field data by using a preset text analyzer to obtain a syntax tree, and extracting a data pedigree corresponding to the data object from the syntax tree; when the data type is an ADSO type, analyzing the dependency relationship of the metadata information through a preset RFC interface to obtain a data pedigree corresponding to the data object; when the data type is a calculation view, querying a calculation view definition corresponding to the data object through a preset JDBC interface to obtain XML data in a BW standard format; and analyzing the data object to obtain a data pedigree corresponding to the data object. In the embodiment of the invention, the collection and acquisition of the field-level data pedigree relationship in the SAP BW environment are realized.

Description

Technical Field

[0001] The present invention relates to the field of data governance, and in particular to a data pedigree 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 more and more challenges in understanding and managing this data.

[0003] At present, data lineage has been widely used in software fields such as data governance and low-code. There are also many reference implementations in the industry on how to obtain the lineage relationship between related data objects from relational databases and big data platforms (Hadoop). For example, directly obtaining from metadata or parsing from SQL and other codes. However, there are still many problems in automatically obtaining the lineage relationship at the field level between data objects in the SAP BW environment. Due to the wide variety of data objects in the SAP BW system, it is impossible to extract data lineage relationship data like relational databases. Even SAP's DI product cannot provide data lineage relationships at the object to field level, and can only support data lineage relationships at the object level. Therefore, it is impossible to obtain the lineage relationship between internal objects in SAP BW, which include information objects, transformations, processing chains, etc. Since it is impossible to effectively obtain field-level data lineage relationships in the SAP BW environment, a new technology is needed to solve the current problem. 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 pedigree collection method based on SAP BW, the data pedigree 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 perform SQL statement parsing on the field data to obtain a syntax tree, and a data pedigree 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 a 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 manner 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 processing on the field data to obtain a syntax tree, and the data pedigree 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 acquiring 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, acquiring the data object of SAP BW includes:

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

[0020] Based on the preset RFC interface, obtain the application layer data of SAP BW from the BW database;

[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, the querying of the calculation view definition corresponding to the data object through the preset JDBC interface to obtain the XML data in the BW standard format includes:

[0023] Query the storage 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 system table and the ACTIVE_OBJECT system table in the stored data are 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 of a preset text analyzer to perform SQL statement parsing processing 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 manner of the first aspect of the present invention, after acquiring the data object of SAP BW 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 instructions are stored in the memory, and the memory and the at least one processor are interconnected via lines; 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 pedigree collection method based on SAP BW.

[0034] In an embodiment of the present invention, by first acquiring 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 types of data objects, or acquiring 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 It is a schematic diagram of an embodiment of a data pedigree collection method based on SAP BW in an embodiment of the present invention;

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

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

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

[0039] Figure 5 The figure is a schematic diagram of an embodiment of a data pedigree acquisition device based on SAP BW in an embodiment of the present invention. DETAILED DESCRIPTION

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

[0041] The embodiments disclosed in the present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments disclosed in the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments disclosed in the present invention are only for exemplary purposes and are not intended to limit the scope of protection disclosed in the present invention.

[0042] In the description of the embodiments disclosed in the present invention, the term "including" and similar terms should be understood as open inclusion, that is, "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 pedigree collection method based on SAP BW includes:

[0044] 101. Acquire 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, convert, and merge relevant business information from SAP applications and external data sources. The data object whose data lineage needs to be collected is obtained from the SAP BW platform. The data object contains field data and metadata information corresponding to the field data. The metadata of the data source is obtained, and the obtained metadata is classified, uniformly coded, and the lineage of the data object is collected, so as to generate a data map that can be analyzed and used, and the processed metadata of various types is stored in the database for subsequent query and analysis.

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

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

[0048] In step 1011, a connection with SAP BW is established based on the configured and registered data source. The connection includes connecting to the HANA database through 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, which means that it allows developers to write database applications in Java without having to worry about the specific details of the underlying database. JDBC enables developers to easily switch between different databases because JDBC provides a unified interface to access multiple databases.

[0050] JCO is SAP Java Connector (SAP JCO), a middleware component used to implement communication between Java applications and SAP systems. SAP JCO supports two directions of connection: inbound remote function call (Java calls ABAP) and outbound remote function call (ABAP calls Java). This component enables Java applications to access the RFC (Remote Function Call) function of the SAP system to achieve data interaction and processing. SAP JCO can be used in desktop applications 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 pedigree 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 a preset DatabaseMetaData interface, obtain SAP BW entity data from the HANA database;

[0053] 1013. Acquire the application layer data of SAP BW from the BW database based on the 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 a part of the JDBC API, which provides metadata information about the database, obtains SAP BW entity data from the HANA database, including Schema, Table, View, etc., and obtains the fields and related metadata information contained in these entity data.

[0056] RFC interface is the Remote Function Call interface, which is a standard communication method that allows SAP BW to exchange data and program communications with other SAP systems or non-SAP systems. Objects of the BW application layer are obtained from the RFC interface, including application layer data such as advanced storage objects ADSO, visualization views, composite information objects CP, information objects IO, processing 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 implementations 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 perform SQL statement parsing on the field data to obtain a syntax tree, and a data pedigree 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, are simplified to query, composite provider, advanced DSO and InfoObject in BW / 4HANA.

[0065] Query: In BW / 4HANA, query is one of the data output carriers. It can provide data based on HANA views and allow calculation views of these output carriers to be generated at the bottom of HANA. In this way, it can be used by front-end tools individually or in combination like general HANA views.

[0066] Composite Provider: Composite Provider allows merging data from BW InfoProviders with HANA modeling views and provides data externally by combining other virtual objects.

[0067] Advanced Data Store Object (ADSO): In BW / 4HANA, traditional Cubes, DSOs, etc. are converted to Advanced DSOs for storing and integrating data.

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

[0069] 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 condition" is translated into an abstract syntax tree. The data lineage corresponding to the field-level data object of the view is extracted from the syntax tree.

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

[0071] 1031. Use a preset JavaCC analyzer to perform SQL statement parsing on the field data to obtain a syntax tree.

[0072] In step 1031, JavaCC (Java Compiler Compiler) is a tool for generating a lexical analyzer and a syntax analyzer. It generates a Java program by reading a lexical and syntax description file (usually ending with .jj), and this Java program includes a lexical analyzer and a syntax analyzer. The lexical analyzer generated by JavaCC can parse the input character sequence into individual identifiers (Tokens) and classify these identifiers. Therefore, the JavaCC analyzer is used to parse the field data for SQL statements to obtain a syntax tree.

[0073] 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;

[0074] In this embodiment, ADSO type data is an important data model object in SAP BW / 4HANA, which is used to store and manage factual data in the data warehouse. Through the RFC interface, the metadata of the data object in the BW database is directly obtained. In the process of obtaining the metadata, the dependencies in the processing chain, transformation and other objects are parsed to extract the data lineage at the field level.

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

[0076] In this embodiment, in the SAP BW environment, calculation views are an advanced feature in the SAP HANA database, which allows users to create complex SQL queries and data processing logic through a graphical interface or SQL scripts. The calculation view definition corresponding to the system table of the HANA database is queried using the JDBC interface, and the calculation view definition is saved as XML data in the BW standard format.

[0077] For details, please refer to Figure 3 , Figure 3 This is an embodiment of step 105 of the data pedigree 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:

[0078] 1051. Query the storage data corresponding to the calculation view from the HANA database through the preset JDBC interface;

[0079] 1052. 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;

[0080] 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.

[0081] In steps 1051-1053, the storage data corresponding to the calculation view is queried from the HANA database through the preset JDBC interface. Then, according to the preset query function, the system table "_SYS_REPO"."ACTIVE_OBJECT" in the storage data is queried to obtain the visualization view definition. The visualization view definition is stored as an XML document in the BW standard format, and then the data map of the visualization view is obtained by parsing the XML document.

[0082] Further, in step 1052, the following specific implementations are included in step 1052:

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

[0084] In step 10521, the preset query function is used to directly retrieve the _SYS_REPO system table and the ACTIVE_OBJECT system table to obtain the calculation view definition corresponding to the data object, where "_SYS_REPO" is a system schema in SAP HANA, which is used to store design-time models and runtime objects. "ACTIVE_OBJECT" is a table in this schema, which is used to store metadata information of active objects. In SAP HANA, model views are ultimately managed uniformly by the user _SYS_REPO. Therefore, the "_SYS_REPO"."ACTIVE_OBJECT" table contains detailed information about active objects, which is crucial for the management and maintenance of the SAP HANA database.

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

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

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

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

[0089] 1062. When the interface is edited and created, the XML data is parsed to obtain the data pedigree corresponding to the data object;

[0090] 1063. 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 a data pedigree corresponding to the data object is extracted from the syntax tree.

[0091] In steps 1061-1063, it is first determined whether the creation attribute of the data object is created by interface editing. If the creation attribute of the data object is created by interface editing, the XML data is parsed and analyzed to obtain the data pedigree corresponding to the data object. If the creation attribute of the data object is not created by interface editing, it is considered to be created by SQL, and the javacc text analyzer is called to parse the field data for SQL statements to obtain a syntax tree, and then the data pedigree corresponding to the data object is extracted from the syntax tree.

[0092] 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 the 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 binding storage of data related to the data lineage.

[0093] In an embodiment of the present invention, by first acquiring 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 types of data objects, or acquiring 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.

[0094] Figure 5 1 is a schematic diagram of the structure of a data pedigree collection device based on SAP BW provided by an embodiment of the present invention. The data pedigree collection device 500 based on SAP BW may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 510 (for example, one or more processors) and a memory 520, and one or more storage media 530 (for example, one or more mass storage devices) storing application programs 533 or data 532. Among them, the memory 520 and the storage medium 530 may be temporary storage or permanent storage. The program stored in the storage medium 530 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the data pedigree collection device 500 based on SAP BW. Furthermore, the processor 510 may be configured to communicate with the storage medium 530 to execute a series of instruction operations in the storage medium 530 on the data pedigree collection device 500 based on SAP BW.

[0095] The SAP BW-based data pedigree acquisition device 500 may also 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 Serve, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that Figure 5 The structure of the SAP BW-based data lineage acquisition device shown does not constitute a limitation on the SAP BW-based data lineage acquisition device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0096] 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, wherein instructions are stored in the computer, and when the instructions are executed on a computer, the computer executes the steps of the data lineage collection method based on SAP BW.

[0097] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may 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 may 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.

[0098] In addition, although each operation is described in a specific order, this should be understood as requiring such operation to be performed in the specific order shown or in a sequential order, or requiring that all illustrated operations should be performed to obtain desired results. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a 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 can also be implemented in multiple implementations individually or in any suitable sub-combination mode.

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

Claims

1. A data pedigree collection method based on SAP BW, characterized in that: Includes 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 pedigree corresponding to the data object is extracted from the syntax tree; 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 a preset JDBC interface to obtain XML data in the BW standard format; Based on the XML data and the creation attributes of the data object, a data pedigree corresponding to the data object is obtained.

2. The data pedigree 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 comprises: 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 processing on the field data to obtain a syntax tree, and the data pedigree corresponding to the data object is extracted from the syntax tree.

3. The data pedigree collection method based on SAP BW according to claim 1, characterized in that: Before obtaining the SAP BW data object, the following steps are also included: 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.

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

5. The data pedigree collection method based on SAP BW according to claim 4, characterized in that: The method of querying the calculation view definition corresponding to the data object through the preset JDBC interface to obtain the XML data in the BW standard format includes: Query the storage 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.

6. The data pedigree collection method based on SAP BW according to claim 5, characterized in that: The querying of the system table in the stored data according to the preset query function to obtain the calculation view definition corresponding to the data object includes: According to the preset query function, the _SYS_REPO system table and the ACTIVE_OBJECT system table in the stored data are queried to obtain the calculation view definition corresponding to the data object.

7. The data source tracing method based on SAP BW according to claim 1 is characterized in that: The preset text analyzer is used to perform SQL statement parsing on the field data 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.

8. The data pedigree collection method based on SAP BW according to claim 1, characterized in that: After acquiring the data object of SAP BW 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.

9. A data pedigree collection device based on SAP BW, characterized in that: The data pedigree acquisition device based on SAP BW includes: a memory and at least one processor, 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-8.

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

Images