IP Library › Granted Patent US 8,495,104
Granted Patent B2
US 8,495,104 · App. 12/253,810 · Granted Jul 23, 2013

Database child object wizard

Inventors: Manoj Tahiliani (Mountain View, CA); Lalitha Gunasekaran (Santa Clara, CA); Lindy Chan (Elk Grove, CA); Cynthia Mee Yee Chan (San Jose, CA)
Assignee: Oracle International Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,495,104
App. No.
12/253,810
Granted
Jul 23, 2013
Kind
B2
Abstract

Embodiments presented herein provide systems and methods for creating child objects for a database. A child object wizard provides one or more user interfaces that allow a database administrator to select or create a child object. One or more other interfaces allow the administrator generate object attributes. The user interfaces allow the database administrator to follow a simpler process to create a child object. The process saves time and money for the database administrator.

Claims (58)

1. A method executed on a computer system for creating a child object in a data object hierarchy of a database, comprising:

receiving at a database application of the computer system a selection from a first user interface display to create a new child object within the data object hierarchy;

providing by the database application of the computer system a second user interface display allowing a user to input selections for the new child object;

receiving at the database application of the computer system a selection from the second user interface display for a parent object, wherein the parent object comprises an object from which the child object will depend within the data object hierarchy;

receiving at the database application of the computer system a selection from the second user interface display for one or more attributes of the child object;

providing by the database application of the computer system a third user interface display allowing the user to input selection of a new source data history object associated with the new child object, wherein the new source data history object comprises metadata about a history of the data in the new child object;

receiving at the database application of the computer system a selection from the third user interface display for one or more attributes of the new source data history object associated with the new child object;

providing by the database application of the computer system a fourth user interface display allowing the user to input selection of a new source data history integration object associated with the new child object, wherein the new source data history integration object comprises metadata linking the data in the new child object to one or more other databases;

receiving at the database application of the computer system a selection from the third user interface display for one or more attributes of the new source data history integration object associated with the new child object;

automatically creating by the database application of the computer system the new child object, the new source data history object, and the new source data history integration object; and

storing by the database application of the computer system the new child object in the data object hierarchy of the database.

2. The method as defined in claim 1 , further comprising receiving at the database application of the computer system a selection from the second user interface display for one or more children objects of the new child object, wherein the one or more children objects of the new child object will depend from the new child object within the data object hierarchy.

3. The method as defined in claim 1 , further comprising receiving at the database application of the computer system a selection from the second user interface display for one or more components of a source data file associated with the database.

4. The method as defined in claim 1 , further comprising:

generating by the database application of the computer system source code for the new child object; and

storing by the database application of the computer system the source code in a logic layer database.

5. The method as defined in claim 4 , further comprising:

generating by the database application of the computer system one or more source data files associated with the source code; and

storing by the database application of the computer system the source data files in a data layer database.

6. The method as defined in claim 5 , wherein a Master Data Management (MDM) database includes the new child object.

7. The method as defined in claim 1 , further comprising:

generating by the database application of the computer system the new source data history object associated with the new child object based on the received one or more attributes for the new source data history object;

generating by the database application of the computer system one or more source data history data files associated with the source data history object;

generating by the database application of the computer system the new source data history integration object associated with the new child object based on the received one or more attributes for the new source data history integration object; and

storing by the database application of the computer system the new source data history object, the one or more source data history data files, and the new source data history integration object.

8. A system comprising:

a processor; and

a memory coupled with and readable by the processor and having stored therein a sequence of instructions which, when executed by the processor, causes the processor to create a child object in a data object hierarchy of a database by a selection from a first user interface display to create a new child object within the data object hierarchy, providing a second user interface display allowing a user to input selections for the new child object, receiving a selection from the second user interface display for a parent object, wherein the parent object comprises an object from which the child object will depend within the data object hierarchy, receiving a selection from the second user interface display for one or more attributes of the child object, providing a third user interface display allowing the user to input selection of a new source data history object associated with the new child object, wherein the new source data history object comprises metadata about a history of the data in the new child object, receiving a selection from the third user interface display for one or more attributes of the new source data history object associated with the new child object, providing a fourth user interface display allowing the user to input selection of a new source data history integration object associated with the new child object, wherein the new source data history integration object comprises metadata linking the data in the new child object to one or more other databases, receiving a selection from the third user interface display for one or more attributes of the new source data history integration object associated with the new child object, automatically creating the new child object, the new source data history object, and the new source data history integration object, and storing the new child object in the data object hierarchy of the database.

9. The system as defined in claim 8 , further comprising receiving a selection from the second user interface display for one or more children objects of the new child object, wherein the one or more children objects of the new child object will depend from the new child object within the data object hierarchy.

10. The system as defined in claim 8 , further comprising receiving a selection from the second user interface display for one or more components of a source data file associated with the database.

11. The system as defined in claim 8 , further comprising:

generating source code for the new child object; and

storing the source code in a logic layer database.

12. The system as defined in claim 11 , further comprising:

generating one or more source data files associated with the source code; and

storing the source data files in a data layer database.

13. The system as defined in claim 12 , wherein a Master Data Management (MDM) database includes the new child object.

14. The system as defined in claim 8 , further comprising:

generating the new source data history object associated with the new child object based on the received one or more attributes for the new source data history object;

generating one or more source data history data files associated with the source data history object;

generating the new source data history integration object associated with the new child object based on the received one or more attributes for the new source data history integration object; and

storing the new source data history object, the one or more source data history data files, and the new source data history integration object.

15. A computer-readable memory having stored thereon a sequence of instructions which, when executed by a processor, cause the processor to create a child object in a data object hierarchy of a database by:

receiving a selection from a first user interface display to create a new child object within the data object hierarchy;

providing a second user interface display allowing a user to input selections for the new child object;

receiving a selection from the second user interface display for a parent object, wherein the parent object comprises an object from which the child object will depend within the data object hierarchy;

receiving a selection from the second user interface display for one or more attributes of the child object;

providing a third user interface display allowing the user to input selection of a new source data history object associated with the new child object, wherein the new source data history object comprises metadata about a history of the data in the new child object;

receiving a selection from the third user interface display for one or more attributes of the new source data history object associated with the new child object;

providing a fourth user interface display allowing the user to input selection of a new source data history integration object associated with the new child object, wherein the new source data history integration object comprises metadata linking the data in the new child object to one or more other databases;

receiving a selection from the third user interface display for one or more attributes of the new source data history integration object associated with the new child object;

automatically creating the new child object, the new source data history object, and the new source data history integration object; and

storing the new child object in the data object hierarchy of the database.

16. The computer-readable memory as defined in claim 15 , further comprising:

the new source data history object associated with the new child object based on the received one or more attributes for the new source data history object;

generating one or more source data history data files associated with the source data history object;

generating the new source data history integration object associated with the new child object based on the received one or more attributes for the new source data history integration object; and

storing the new source data history object, the one or more source data history data files, and the new source data history integration object.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2008
From: TAHILIANI, MANOJ; GUNASEKARAN, LALITHA; CHAN, LINDY; CHAN, CYNTHIA MEE YEE
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 021699/0299 →
Continuity (1)
Related Publication 20100114987A1 · May 6, 2010