Mapping of a transactional data model to a reporting data model

• US 20070239711A1
• Filed: 03/28/2006
• Published: 10/11/2007
• Est. Priority Date: 03/28/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Unnebrink, Stefan, Moehl, Roman
• Granted Patent: US 7,720,803 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP

Abstract

Systems and techniques for mapping of a transactional data model to a reporting data model are described. In one aspect, an article includes one or more machine-readable media storing instructions operable to cause one or more machines to perform operations. The operations include receiving a transactional data model and a view that includes a collection of view fields, each view field referencing an object in the transactional data model, mapping one or more of a plurality of view fields in the collection to one or more of a plurality of data warehouse objects, and grouping the mapped data warehouse objects into a reporting data model.

Claims

1. An article comprising one or more machine-readable media storing instructions operable to cause one or more machines to perform operations comprising:

receiving a transactional data model and a view that includes a collection of view fields, each view field referencing an object in the transactional data model;

mapping one or more of a plurality of view fields in the collection to one or more of a plurality of data warehouse objects; and

grouping the mapped data warehouse objects into a reporting data model.

2. The article of claim 1, wherein mapping the individual view fields comprises mapping at least some of the individual view fields based on existing references to objects in the transactional data model.

3. The article of claim 2, wherein mapping the individual view fields comprises:

determining if an existing data warehouse object references a first object in the transactional data model, wherein the first object is also referenced by a first view field; and

mapping the first view field to the existing data warehouse object.

4. The article of claim 2, wherein mapping the individual view fields comprises:

determining if a second field in a second view references a first object in the transactional data model, wherein the first object is also referenced by the first view field and the second field is already mapped to an existing data warehouse object; and

mapping the first view field to the existing data warehouse object.

5. The article of claim 1, wherein mapping the individual view fields comprises:

creating a new data warehouse object; and

mapping at least some of the individual view fields to the new data warehouse object.

6. The article of claim 5, wherein:

mapping the individual view fields further comprises determining that a first view field is numeric;

creating the new data warehouse object comprises creating a new measure object; and

mapping at least some of the individual view fields comprises mapping the first view field to the new measure object.

7. The article of claim 5, wherein:

mapping the individual view fields further comprises determining that a first view field is not numeric;

creating the new data warehouse object comprises creating a new dimension object; and

mapping at least some of the individual view fields comprises mapping the first view field to the new dimension object.

8. The article of claim 7, wherein creating the new dimension object comprises creating a new dimension view object.

9. The article of claim 1, wherein:

the transactional data model comprises a collection of objects that are comparably sized to common change transactions; and

the reporting data model comprises a star schema.

10. A computer-implemented method comprising:

receiving a transactional data model and a view that includes a collection of view fields;

selecting a first view field from the collection, wherein the first view field references a first object in the transactional data model;

determining whether a second object in the transactional data model is associated with the first object;

creating a dimension view object in response to determining that the second object in the transactional data model is associated with the first object; and

mapping the first view field to the dimension view object,

wherein the dimension view object is to join a first of the two or more measures to a single class of dimension object in a reporting data model.

11. The method of claim 10, wherein dimension view object comprises relationship information that identifies a relationship between the first of the two or more measures and a dimension object.

12. The method of claim 10, wherein creating the dimension view object comprises determining if there is an existing dimension object that references the associated transactional object.

13. The method of claim 12, further comprising responding to a determination that there is an existing dimension object that references the associated transactional object by creating the new dimension view object to characterize the existing dimension object.

14. The method of claim 12, further comprising responding to a determination that there is no existing dimension object references the associated transactional object by:

creating a new dimension object with a reference to the associated transactional object; and

creating the new dimension view object to characterize the new dimension object.

15. The method of claim 10, further comprising selecting a second view field from the collection, wherein the second view field references a second object in the transactional data model.

16. The method of claim 10, wherein the first view field references one of an attribute, a method, an interface, and a relationship of the first object.

17. The method of claim 10, wherein the first view field always comprises a numeric field.