Results for “sequence_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_AUDITS is the central audit repository within the Oracle E-Business Suite HR schema, owned by the HR user and classified under the PAY (Payroll) product module. It records the transactional history captured against any audited table in the EBS database by reading from that table's corresponding shadow table. When Oracle EBS auditing is enabled for a given table, changes to rows are written to a shadow object; HR_AUDITS then serves as the master header-level audit record that ties those changes to a specific database session, a commit point, a user, and a timestamp. The table is therefore the anchor of the EBS audit trail for HR-related objects.

In Data Vault modeling terms, the heuristic classification provided for this object is satellite-leaning. The audit rows are descriptive, time-stamped attributes attached to a driving key, rather than independent business entities or pure relationship records. Analysts modeling EBS audit data in a warehouse should treat HR_AUDITS as a satellite-like table hanging off the audited source entities, keyed by AUDIT_ID.

Key Information Stored

The documented schema contains fourteen columns. The most significant are:

• AUDIT_ID — the surrogate primary key, enforced by the unique index HR_AUDITS_PK. It uniquely identifies each audit event and is the column most often used in joins and lookups.
• USER_NAME — the EBS application user responsible for the audited transaction. It carries a foreign key to FND_USER.
• TABLE_NAME — the name of the audited source table that generated the audit row.
• PRIMARY_KEY and PRIMARY_KEY_VALUE — identify the primary key column of the audited table and the specific value of the affected row.
• TRANSACTION and TRANSACTION_TYPE — describe the nature of the change (for example, insert, update, or delete).
• TIMESTAMP — the moment the audited transaction occurred.
• SESSION_ID, CURRENT_SESSION_ID, and COMMIT_ID — correlate audits to database sessions and commit events.
• SEQUENCE_ID — orders audit records within a session.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — provide the effective dating window for the audit record.

AUDIT_ID is the only documented unique index and therefore the sole business-key candidate; the remaining columns function as descriptive attributes.

Common Use Cases and Queries

Typical reporting scenarios include investigating who changed a specific HR record, reconstructing the history of a payroll-relevant setup, and producing audit compliance extracts. A common pattern joins the audit header to its audited entity using PRIMARY_KEY_VALUE:

• SELECT audit_id, user_name, table_name, transaction_type, timestamp FROM hr.hr_audits WHERE primary_key_value = :id ORDER BY timestamp DESC;
• SELECT * FROM hr.hr_audits WHERE user_name = :user AND timestamp BETWEEN :from AND :to;
• SELECT * FROM hr.hr_audits WHERE table_name = 'PER_ALL_PEOPLE_F' AND session_id = :sid;

Because each audit header fans out to its changed columns through HR_AUDIT_COLUMNS, detailed before-and-after reporting requires joining on AUDIT_ID to obtain the field-level values.

Related Objects

The following objects interact most directly with HR_AUDITS:

• FND_USER — referenced by HR_AUDITS.USER_NAME; supplies the application user identity behind each audit event.
• HR_AUDIT_COLUMNS — the child table; HR_AUDIT_COLUMNS.AUDIT_ID references HR_AUDITS, providing column-level change detail.
• Shadow tables — the source tables mirrored by EBS auditing, from which HR_AUDITS rows are derived.
• The audited base tables — identified dynamically via TABLE_NAME and PRIMARY_KEY_VALUE, allowing audits to be traced back to the originating HR or Payroll entity.
• HR_AUDITS_PK — the supporting unique index guaranteeing AUDIT_ID uniqueness.

Together these objects form the audit trail backbone used by compliance reporting, forensic analysis, and change-history reconstruction across the HR and Payroll schemas.