Oracle International Corporation

Deena Philip

George Kellner

Mohan K Arthur

Paul Johl

Sayantan Chatterjee

Anuranjana Nambiar

Revathy Narasimhan

Kunal Desai

A system is provided that reports audit data. The system retrieves audit data that is stored in database tables, where the audit data includes a history of modifications to data, and where the audit data includes data values. The system further retrieves a display name that is stored in a lookup table, where the display name is associated with a data value of the data values within the lookup table. The system further displays the audit data within a user interface, where the display name is displayed within the user interface.

Metadata-driven audit reporting system with dynamically created display names

A pluggable migration framework can interface with a plurality of repositories that store metadata related to one or more applications. A user can customize the applications to suit the user's business requirements. The user can develop and test the customized applications in a source environment, and the customized features can be stored as metadata in one or more of the plurality of repositories. When the customized application is ready to be used by others, it can be migrated to a target environment. The pluggable migration framework can include an orchestrator that enables the user to export metadata from the plurality of repositories in the source environment, and import the metadata to a plurality of repositories in the target environment, without requiring the user to re-implement the custom features.

Extensible customization migration via pluggable interface

A system is provided that reports audit data. The system defines audit metadata that defines a business object of an application module and an attribute of the business object as being auditable. The system further defines business object metadata that defines a hierarchical relationship between the business object and a child business object. The system further generates audit data for the attribute of the business object based on the audit metadata, where the audit data includes a history of modifications to the attribute of the business object. The system further displays the audit data within a user interface. The system further displays the business object and the hierarchical relationship between the business object and the child business object within the user interface based on the business object metadata.

Metadata-driven audit reporting system with hierarchical relationships

A system is provided that reports audit data. The system defines metadata that defines a business object of an application module and an attribute of the business object as being auditable. The system further configures the metadata to enable auditing for the attribute of the business object. The system further generates audit data for the attribute of the business object based on the metadata, where the audit data includes a history of one or more modifications to the attribute of the business object. The system further stores the audit data within a shadow database table based on the metadata. The system further displays the audit data within a user interface.

Metadata-driven audit reporting system

A system that directs a user to an object in response to a selection of a deep link uniform resource identifier ('URL') that includes an identity of a web service, an object type and action, accesses a database table. The system uses the object type and the action as a first index key and a second index key of the database table to generate a query. In response to the query, the system retrieves additional parameters to append to the deep link URL to generate a full URL. The system then directs the user to the object that corresponds to the full URL.

Deep linking to application objects

A system is provided that reports audit data. The system defines metadata that defines security conditions for a business object. The system further receives a request from a user to retrieve audit data contained within a database table, where the audit data includes a history of modifications to an attribute of the business object. The system further retrieves the audit data from the first database table. The system further applies the security conditions to the audit data based on the metadata. The system further displays the audit data within a user interface when the security conditions are satisfied.

Metadata-driven audit reporting system that applies data security to audit data

Techniques for identifying duplicate records in data to be imported into a data hub. In one set of embodiments, a batch of records to be imported into a data hub is received and a match rule for the batch of records is selected. The match rule includes a set of match criteria for matching records in the inbound batch to records stored in the data hub. A matching process is then carried out, prior to importing the batch of records, to determine whether any of the records in the batch are duplicates of records stored in the data hub. By identifying potential duplicate records before (rather than after) importation, the problems associated with prior art duplicate identification techniques are minimized or avoided. In a particular embodiment, an import workbench application comprising a plurality of user interface screens is provided for aiding a user in managing the matching process.

Growing community of inventors

Sunnyvale, CA, United States of America

Deena Philip