Nested relational data model

• US 20010047372A1
• Filed: 02/12/2001
• Published: 11/29/2001
• Est. Priority Date: 02/11/2000
• Status: Abandoned Application

• Current Assignee: Acta Technology, Inc. (SAP SE)
• Original Assignee: Acta Technology, Inc. (SAP SE)
• Inventors: Yee, Mon F., Grantimahapatruni, Sridhar, Syed, Awez I., Chawla, Sachinder S., Gorelik, Alexander, Burda, Leon
• Application Number:
  US09/782,186
• Publication Number:
  US 20010047372A1
• Time in Patent Office: Days
• US Class Current: 715/514
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 16/84 Mapping; Conversion

Abstract

In a data processing system, hierarchical documents or hierarchical messages are mapped to a Nested Relational Data Model to allow for transformation and manipulation using declarative statements. The resulting nested data can be converted to a relational format and mapped to multiple relational tables, and/or converted from a nested relational format to an external hierarchical format, such as XML. The system can specify and execute declarative rules to extract, transform, integrate, load and update hierarchical and relational data. The system can also be used for extending documents with relational and non-relational data and applying updates based on these documents to relational database targets. The system can also be used for mapping Nested Relational Data to function calls that accept tables as parameters and return multiple scalar and table parameters as output.

Claims

1. An apparatus for processing data representable in a hierarchical form, the apparatus comprising:

an importer having inputs to receive a schema and a structured document from a data source, wherein the importer outputs a first nested relational data model (NRDM) data structure representing the structured document according to the received schema;

an transformation engine that is capable of transforming the first NRDM data structure output by the importer into a second NRDM data structure according to a declarative specification of a transform; and

an exporter having an input to receive the second NRDM data structure, wherein the exporter outputs a transformed hierarchical document in a data structure other than an NRDM data structure in a form suitable for a data target.

2. The apparatus of

claim 1

, further comprising means for converting relational data to an NRDM data structure by vertically partitioning a relation and nesting parts of the relational data as a nested table.

3. The apparatus of

claim 1

, further comprising means for converting nested relational data to relational data by unnesting the nested tables using a cross-product between a parent row and a child subtable.

4. The apparatus of

claim 1

, further comprising means for performing a grouping operation on a nested table that generates a resulting nested table containing a union of all the nested tables grouped by the operation.

5. The apparatus of

claim 1

, further comprising means for performing multi-step transformations, wherein an input to a transformation is results of a previous transformation, a data source, or both.

6. The apparatus of

claim 1

, wherein the transformation engine operates on rules that are applied to data independent of data format.

7. The apparatus of

claim 1

, wherein the exported is adapted to output one or more of an XML file, a relational table or a flat file.

8. A metadata mapper comprising:

an input for receiving a document description for hierarchical documents; and

an output for outputting an NRDM data structure representing the document description.

9. An apparatus for transforming data representable in a hierarchical form, the apparatus comprising:

an importer having inputs to receive a schema and a structured document from a data source, from a data transformer, or from both, wherein the importer outputs a first nested relational data model (NRDM) data structure representing the structured document according to the received schema;

an transformation engine that is capable of transforming the first NRDM data structure output by the importer into a second NRDM data structure according to a declarative specification of a transform; and

an exporter having an input to receive the second NRDM data structure, wherein the exporter outputs a transformed hierarchical document in a data structure other than an NRDM data structure in a form suitable for a data target.

10. A method for providing data to an application through a data platform in a computer system in response to request from the application, the method comprising:

accepting declarative rules for accessing the data from data sources and declarative rules for transforming the data into a format requested by the application;

mapping relational and non-relational data sources to an NRDM data structure;

interpreting a request;

retrieving data from the data sources;

transforming the data according to the declarative rules; and

returning the transformed data to the application.

11. The method of

claim 10

, wherein requests are processed as messages and request messages contain sufficient information to drive data extraction into a data-oriented interface.

12. The method of

claim 10

, wherein the requests are application programming interface function calls.

13. A method for updating a plurality of data targets from a message, comprising:

making an update request through a data-oriented interface;

specifying declarative rules for updating the data targets;

importing metadata that maps relational and non-relational data targets to NRDM data structures;

interpreting incoming update requests;

transforming the data according to the declarative rules; and

updating the data targets.

14. The method of

claim 13

, further comprising:

making an update request using an application; and

causing one of a response to be sent to the application, an update of data, or both.

15. The method of

claim 13

, further comprising a step of combining the update request with other data before updating the data targets.

16. A method of providing input to an application expecting one or more tables as parameters to an input message, the method comprising:

mapping data in a NRDM data structure to function parameters; and

making a function calls to the application using the NRDM mapped data structure.