ADAPTIVE DATA MODEL AND WAREHOUSE PALETTE

• US 20130066826A1
• Filed: 09/09/2011
• Published: 03/14/2013
• Est. Priority Date: 09/09/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: McDONALD, Jason, Azcue, Jeff
• Granted Patent: US 8,886,591 B2
• Time in Patent Office: Days
• US Class Current: 707/602
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses

Abstract

Systems, methods, and other embodiments associated with and\ adaptive data model and warehouse palette are provided. In one embodiment, a method includes providing a user interface for collecting item definition attributes from a user. A database structure is generated to store item data according to collected the item definition attributes. An extract, transform, and load (ETL) layer is generated to extract item data from user data, transform the extracted data for storing in the database structure, and load the transformed extracted data into the database structure.

Claims

1. A non-transitory computer-readable medium storing computer-executable instructions that when executed by a computer cause the computer to perform a method, the method comprising:

providing a user interface for collecting item definition attributes from a user;

generating a adaptive database structure to store item data corresponding to the collected item definition attributes and interface rules that map item data for the item definition attributes to portions of the database structure; and

generating an extract, transform, and load (ETL) layer configured to extract item data from user data and load the extracted data into the adaptive database structure as mapped by the interface rules.

2. The non-transitory computer-readable medium of claim 1, where the user interface is configured to collect a history preference for an item definition attribute from the user, and where the instructions further comprise storing previous versions of records of changed item definition attributes having an enabled history preference.

3. The non-transitory computer-readable medium of claim 1, where generating a data structure comprises:

creating an XML payload file comprising a document containing the collected item definition attributes; and

passing the XML payload file to a definition engine.

4. The non-transitory computer-readable medium of claim 3, where generating the ETL layer comprises executing stored instructions for an ETL tool that cause the ETL tool to identify the collected item definition attributes in the XML payload file and create interfaces and data structures for storing the collected item definition attributes.

5. The non-transitory computer-readable medium of claim 1, comprising integrating the adaptive database structure and ETL layer with a core database structure and a core ETL layer.

6. The non-transitory computer-readable medium of claim 5 comprising creating a data mart schema comprising core fact tables for data stored in the core database structure and extension fact tables for data stored in the database structure, where the core fact tables and extension fact tables include join keys that can be used to join the core fact tables with selected extension fact tables to create a view that corresponds to an extended fact table for data from both the core database structure and the adaptive database structure.

7. The non-transitory computer-readable medium of claim 6 where the core and extension fact tables store records corresponding to transactions and further where the data mart schema comprises dimension tables that are keyed to columns of the fact tables and store records corresponding to attributes of the transaction.

8. A computing system, comprising:

a palette logic configured to provide a user interface for collecting item definition attributes from a user;

a definition engine configured to;

generate an adaptive database structure to store item data corresponding to the collected item definition attributes and interface rules that map item data for the item definition attributes to portions of the adaptive database structure;

generate an extract, transform, and load (ETL) layer configured to extract item data from user data and load the extracted data into the adaptive database structure as mapped by the interface rules; and

a data store configured to store a populated adaptive database structure.

9. The computing system of claim 8, where the palette logic is configured to:

create an XML payload file comprising a document containing the collected item definition attributes;

pass the XML payload file to the definition engine.

10. The computing system of claim 9, where the definition engine and ETL layer comprise an ETL tool and further where the definition engine is configured to generate the ETL layer by generating instructions for the ETL tool that cause the ETL tool to identify the collected item definition attributes in the XML payload file and create interfaces and data structures for storing the collected item definition attributes.

11. The computing system of claim 8, where the definition engine is configured to generate the ETL layer by extracting metadata from the collected item definition attributes and storing the metadata in an ETL tool metadata repository.

12. The computing system of claim 8, where the definition engine is configured to integrate the generated database structure and ETL layer with a core database structure and a core ETL layer.

13. The computing system of claim 12, where the definition engine is configured to create a data mart schema comprising core fact tables for data stored in the core database structure and extension fact tables for data stored in the adaptive database structure, where the core fact tables and extension fact tables include join keys that can be used to join the core fact tables with selected extension fact tables to create a view that corresponds to an extended fact table for data from both the core database structure and the adaptive database structure.

14. A computer-implemented method comprising:

providing an interface for collecting risk item attributes for an insurance line of business;

generating an XML file containing metadata describing the collected risk items;

with an ETL tool, receiving the XML file and identifying the collected risk items in the XML file, and generating an ETL layer comprising interface rules for populating line of business tables; and

populating the line of business tables with user data using the ETL layer.

15. The computer-implemented method of claim 14 comprising integrating the line of business tables into a set of core tables that store user data that is common to all lines of business.

16. The computer-implemented method of claim 14 where instructions for the ETL tool to identify the collected risk items in the XML file and generate an ETL layer are generated automatically in response to receiving the XML file.

17. The computer-implemented method of claim 15 comprising creating a data mart schema comprising core fact tables for data stored in the core database tables and extension fact tables for data stored in the line of business database tables, where the core fact tables do not store data corresponding to risk item attributes collected from the user.

18. The computer-implemented method of claim 17 where the core fact tables and extension fact tables include join keys that can be used to join the core fact tables with the extension fact tables, the method comprising creating a materialized view for a selected line of business that corresponds to an extended fact table for data from both the core database tables and the line of business database tables by joining the core fact tables with one or more extension fact tables that store data for the selected line of business.

19. The computer-implemented method of claim 17 where the core and extension fact tables store records corresponding to transactions and further where the data mart schema comprises dimension tables that are keyed to columns of the fact tables and store records corresponding to attributes of the transaction.

20. The computer-implemented method of claim 14 where providing an interface comprises providing a web based interface to access an ETL tool in a remote server.