Oracle International Corporation

Mohan K Arthur

George Kellner

Deena Philip

Paul Johl

Roberto Irribarren

Revathy Narasimhan

Siddhartha Agarwal

Mark E Haseltine

Mohit Doshi

Sayantan Chatterjee

Yash Pal Talreja

Anuranjana Nambiar

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

A computer-implemented method of presenting an electronic bill from a biller to a customer over a computer network includes steps of receiving biller-originated bill data and bill format data over the network into a bill presentment and payment database. The inputted bill data and bill format data are then stored in a first area of the bill presentment and payment database. The stored bill data and/or the bill format data is then validated and the validated bill data and/or the format data is swapped from the first area to a second area of the bill presentment and payment database, the second area being accessible to the customer. The bill, now incorporating the validated bill data and formatted according to the bill format data, may then be presented to the customer. A third, customer accessible area may be included in the database to archive the bills. The bill format data may include a plurality of bill templates, each of which may define a distinct appearance for the bill. A plurality of bill template selection rules may be applied to the validated bill data. Based on this evaluation, one of the plurality of bill templates may then be selected to format the bill presented to the customer.

Growing community of inventors

Fremont, CA, United States of America

Mohan K Arthur