Metadata-driven audit reporting system
First Claim
1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to report audit data comprising a history of modifications made to data in a software application, the reporting comprising:
- defining metadata for an attribute of a business object of the software application stored in a base database table, the metadata including;
a business object identifier,an attribute identifier,an auditing enabled flag that identifies whether auditing is enabled for the attribute,a shadow database table name that identifies a shadow database table associated with the base database table, anda shadow database column name that identifies a column of the shadow database table associated with the attribute of the business object;
configuring the metadata to enable auditing for the attribute of the business object, including setting the auditing enabled flag of the metadata to a value that indicates that auditing is enabled for the attribute;
during execution of the software application and in response to a modification to data stored within the base database table, generating first audit data for the attribute of the business object only when the auditing enabled flag of the metadata is set to the value that indicates that auditing is enabled, the first audit data including a history of one or more modifications to the attribute of the business object;
storing the first audit data for the attribute of the business object within the shadow database table identified by the shadow database table name and the shadow database column name, the first audit data comprising data stored within the base database table prior to the modification and data stored within the base database table after the modification;
during execution of the software application and in response to an event occurrence at the base database table, generating second audit data and storing the second audit data in an event database table, wherein the event comprises a login failure event of the software application and wherein the event database table has a different format than the shadow database table; and
displaying the first audit data and the second audit data within a user interface using a single format for the first audit data and the second audit data.
1 Assignment
0 Petitions
Accused Products
Abstract
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.
-
Citations
17 Claims
-
1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to report audit data comprising a history of modifications made to data in a software application, the reporting comprising:
-
defining metadata for an attribute of a business object of the software application stored in a base database table, the metadata including; a business object identifier, an attribute identifier, an auditing enabled flag that identifies whether auditing is enabled for the attribute, a shadow database table name that identifies a shadow database table associated with the base database table, and a shadow database column name that identifies a column of the shadow database table associated with the attribute of the business object; configuring the metadata to enable auditing for the attribute of the business object, including setting the auditing enabled flag of the metadata to a value that indicates that auditing is enabled for the attribute; during execution of the software application and in response to a modification to data stored within the base database table, generating first audit data for the attribute of the business object only when the auditing enabled flag of the metadata is set to the value that indicates that auditing is enabled, the first audit data including a history of one or more modifications to the attribute of the business object; storing the first audit data for the attribute of the business object within the shadow database table identified by the shadow database table name and the shadow database column name, the first audit data comprising data stored within the base database table prior to the modification and data stored within the base database table after the modification; during execution of the software application and in response to an event occurrence at the base database table, generating second audit data and storing the second audit data in an event database table, wherein the event comprises a login failure event of the software application and wherein the event database table has a different format than the shadow database table; and displaying the first audit data and the second audit data within a user interface using a single format for the first audit data and the second audit data. - View Dependent Claims (2, 3, 4, 5, 6, 12, 15)
-
-
7. A computer-implemented method for reporting audit data comprising a history of modifications made to data in a software application, the computer-implemented method comprising:
-
defining metadata for an attribute of a business object of the software application stored in a base database table, the metadata including; a business object identifier, an attribute identifier, an auditing enabled flag that identifies whether auditing is enabled for the attribute, a shadow database table name that identifies a shadow database table associated with the base database table, and a shadow database column name that identifies a column of the shadow database table associated with the attribute of the business object; configuring the metadata to enable auditing for the attribute of the business object, including setting the auditing enabled flag of the metadata to a value that indicates that auditing is enabled for the attribute; during execution of the software application and in response to a modification to data stored within the base database table, generating first audit data for the attribute of the business object only when the auditing enabled flag of the metadata is set to the value that indicates that auditing is enabled, the first audit data including a history of one or more modifications to the attribute of the business object storing the first audit data for the attribute of the business object within the shadow database table identified by the shadow database table name and the shadow database column name, the first audit data comprising data stored within the base database table prior to the modification and data stored within the base database table after the modification; during execution of the software application and in response to an event occurrence at the base database table, generating second audit data and storing the second audit data in an event database table, wherein the event comprises a login failure event of the software application and wherein the event database table has a different format than the shadow database table; and displaying the first audit data and the second audit data within a user interface using a single format for the first audit data and the second audit data. - View Dependent Claims (8, 9, 13, 16)
-
-
10. A system for reporting audit data comprising a history of modifications made to data in a software application, the system comprising:
-
a processor; and a memory, coupled to the processor, storing a metadata definition module, a metadata configuration module, an audit data generation module, an audit data storage module and an audit data display module, wherein; the metadata definition module, when executed by the processor, defines metadata for an attribute of a business object of the software application stored in a base database table, the metadata including; a business object identifier, an attribute identifier, an auditing enabled flag that identifies whether auditing is enabled for the attribute, a shadow database table name that identifies a shadow database table associated with the base database table, and a shadow database column name that identifies a column of the shadow database table associated with the attribute of the business object; the metadata configuration module, when executed by the processor, configures the metadata to enable auditing for the attribute of the business object, including setting the auditing enabled flag of the metadata to a value that indicates that auditing is enabled for the attribute; the audit data generation module, when executed by the processor, during execution of the software application and in response to a modification to data stored within the base database table, generates first audit data for the attribute of the business object only when the auditing enabled flag of the metadata is set to the value that indicates that auditing is enabled, the first audit data including a history of one or more modifications to the attribute of the business object; the audit data storage module, when executed by the processor, stores the first audit data for the attribute of the business object within the shadow database table identified by the shadow database table name and the shadow database column name, the first audit data comprising data stored within the base database table prior to the modification and data stored within the base database table after the modification and during execution of the software application and in response to an event occurrence at the base database table, generating second audit data and storing the second audit data in an event database table, wherein the event comprises a login failure event of the software application and wherein the event database table has a different format than the shadow database table; and the audit data display module, when executed by the processor, displays the first audit data and the second audit data within a user interface using a single format for the first audit data and the second audit data. - View Dependent Claims (11, 14, 17)
-
Specification