Results for “ap_aud_expense_headers_sec_v”

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

Overview

AP_AUD_EXPENSE_HEADERS_SEC_V is a security-enabled view owned by the APPS schema within the Oracle Payables (AP) module. It exposes a filtered subset of expense report header records from the underlying AP_EXPENSE_REPORT_HEADERS_ALL table, deliberately restricting the rows returned based on the organization-level security profile assigned to the currently connected user session. The view is part of the broader Oracle E-Business Suite "SEC_V" family of secured views, typically used by auditing, reporting, and integration components that must respect Multi-Org Access Control (MOAC) restrictions without requiring the calling application to implement that logic itself.

Its primary role is to present expense report header data — the top-level record for an employee expense report — in a manner that is automatically scoped to the operating units the user is authorized to access. Because the security predicate is embedded in the view definition, any tool or concurrent program that queries the view inherits the same row-level filtering, ensuring that users cannot inadvertently view or process expense reports belonging to organizations outside their security profile.

Underlying Base Objects

The view is defined over four documented base objects:

• AP_EXPENSE_REPORT_HEADERS_ALL (SYNONYM) — the primary transactional table holding expense report header information, including the report header identifier, invoice number, and organization identifier.
• PER_ORGANIZATION_LIST (SYNONYM) — the organization security list that maps security profiles to the set of organizations a user may access.
• FND_PROFILE (PACKAGE) — used at runtime to retrieve the value of the XLA_MO_SECURITY_PROFILE_LEVEL profile option, which determines the active MOAC security profile level.
• DUAL (SYNONYM) — used in the inline UNION construct to seed the current session's organization value from the client information environment.

The view text selects REPORT_HEADER_ID, INVOICE_NUM, and ORG_ID from AP_EXPENSE_REPORT_HEADERS_ALL and applies a WHERE clause that compares the record's ORG_ID against either the current session organization (derived from USERENV('CLIENT_INFO')) or the list of organization identifiers returned by PER_ORGANIZATION_LIST for the active security profile. A sentinel value of -99 is applied when ORG_ID or the session value is null, ensuring null-safe matching.

Key Columns

• REPORT_HEADER_ID — the unique primary key of the expense report header in AP_EXPENSE_REPORT_HEADERS_ALL. This is the join key to expense report lines and distributions.
• INVOICE_NUM — the invoice number associated with the expense report header. In Oracle Payables, expense reports are treated as invoices, so this column carries the user-facing invoice number that a search on invoice_num would target.
• ORG_ID — the operating unit (organization) identifier to which the expense report belongs. This is the column that drives the MOAC security filtering performed by the view.

Common Use Cases and Queries

A frequent scenario is a user searching for an expense report by its invoice number while respecting the security profile in force. Because the view already enforces organization security, the query does not need to add MOAC predicates:

• SELECT report_header_id, invoice_num, org_id FROM apps.ap_aud_expense_headers_sec_v WHERE invoice_num = :invoice_num;

• SELECT report_header_id, invoice_num, org_id FROM apps.ap_aud_expense_headers_sec_v WHERE invoice_num LIKE 'EXP%';

Other typical uses include auditing routines that must enumerate expense reports visible to a given operating unit, integration interfaces that pull header identifiers for downstream processing, and reporting tools that rely on the view to inherit MOAC filtering automatically. Because the view returns only three columns, applications typically join REPORT_HEADER_ID back to AP_EXPENSE_REPORT_HEADERS_ALL or the corresponding lines table when full header detail is required. Note that the view's behavior depends on the session context set by the Oracle Applications framework; direct SQL*Plus sessions without a proper CLIENT_INFO value may return only records matching the sentinel organization.