Results for “report_header_id”

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

Overview

AP_AUD_AUDIT_REASONS is a Payables module table in the AP schema that stores the reasons why an expense report is audited. It functions as a master listing of audit reason entries, with each row representing a distinct audit reason associated with a specific expense report header. The table is registered as VALID in Oracle EBS 12.1.1 and 12.2.2.

The table holds eight documented columns and is anchored by primary key constraint AP_AUD_AUDIT_REASONS_PK on the AUDIT_REASON_ID column. A unique index, AP_AUD_AUDIT_REASONS_U1 on AUDIT_REASON_ID, serves as the documented business-key candidate. From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table carries descriptive audit-reason context keyed to a parent business entity (the expense report header), rather than defining independent business keys of its own.

Key Information Stored

The most significant columns include:

• AUDIT_REASON_ID — surrogate primary key of the table, uniquely identifying each audit reason record and enforced through AP_AUD_AUDIT_REASONS_PK and the unique index AP_AUD_AUDIT_REASONS_U1.
• REPORT_HEADER_ID — foreign key column referencing AP_EXPENSE_REPORT_HEADERS_ALL. This links each audit reason to the expense report header it describes, establishing the parent-child relationship at the heart of the table.
• AUDIT_REASON_CODE — the coded value identifying the specific reason an expense report was flagged for audit.
• CREATION_DATE — the date the audit reason record was created.
• CREATED_BY — the user who created the audit reason record.
• LAST_UPDATE_DATE — the date the record was most recently modified.
• LAST_UPDATED_BY — the user who last modified the record.
• LAST_UPDATE_LOGIN — the login context associated with the most recent update.

The WHO-column quartet (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) plus LAST_UPDATE_LOGIN provides the standard Oracle EBS audit trail. The distinction between the surrogate key (AUDIT_REASON_ID) and the foreign-key reference (REPORT_HEADER_ID) is important: the surrogate uniquely identifies the row, while the foreign key establishes the business association to the expense report.

Common Use Cases and Queries

Typical uses include reporting on why expense reports were selected for audit, supporting audit-compliance and expense analytics, and tracing audit decisions back to a specific expense report.

A representative query joining audit reasons to their parent header:

• SELECT r.audit_reason_id, r.audit_reason_code, h.report_header_id, h.expense_report_number FROM ap.ap_aud_audit_reasons r JOIN ap.ap_expense_report_headers_all h ON r.report_header_id = h.report_header_id WHERE h.report_header_id = :p_report_header_id;

Other patterns include counting audit reasons per expense report, aggregating by AUDIT_REASON_CODE for trend reporting, and auditing the WHO columns to detect recent changes or identify the last user who modified an audit reason.

Related Objects

The following objects are most significant in relation to AP_AUD_AUDIT_REASONS:

• AP_EXPENSE_REPORT_HEADERS_ALL — the parent table referenced by AP_AUD_AUDIT_REASONS.REPORT_HEADER_ID. This is the sole documented foreign-key relationship; joins should use REPORT_HEADER_ID on both sides.
• AP_AUD_AUDIT_REASONS_PK — the primary key constraint over AUDIT_REASON_ID.
• AP_AUD_AUDIT_REASONS_U1 — the unique index on AUDIT_REASON_ID, the documented business-key candidate.
• AP_EXPENSE_REPORT_HEADERS_ALL audit-related columns and dependent expense report distribution and line tables — these commonly extend reporting on the same expense report identified through the header join.

Because the documented FK chain centers on a single parent (the expense report header), AP_AUD_AUDIT_REASONS is best treated as a satellite attached to that header entity, with REPORT_HEADER_ID as the driving join column in any reporting or integration query.