Results for “interface_header_context”

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

Overview

AR_OEX_INVOICE_VIEW is an APPS-owned reporting view in the Oracle Receivables (AR) module, defined specifically to expose invoice data exchanged through Oracle Exchange. The view consolidates invoice header information from Receivables transaction tables with payment schedule balances, customer site usage, and lookup-based decode of class and status values. Its principal purpose is to provide a denormalized, read-only projection of inbound exchange invoices, including the raw interface attribute columns used during the Oracle Exchange import process.

The object is particularly relevant when searching for invoice_trx_status. That term corresponds to the AR_LOOKUPS lookup type that the view joins against to translate the internal STATUS code on the payment schedule into a user-facing meaning. Because the view performs this join internally and surfaces the result as AL_STATUS_MEANING, it spares report authors and integration developers from writing the lookup join themselves, ensuring the returned status wording matches the seeded Receivables lookup values.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over four referenced objects:

• AR_LOOKUPS (VIEW) — joined twice, once as AL_STATUS filtered on LOOKUP_TYPE = 'INVOICE_TRX_STATUS' and once as AL_CLASS filtered on LOOKUP_TYPE = 'INV/CM'.
• AR_PAYMENT_SCHEDULES_ALL (SYNONYM) — aliased PS; the driving source of invoice number, date, currency, customer, class, status, and due amounts.
• HZ_CUST_SITE_USES_ALL (SYNONYM) — aliased SU; supplies the site-use context and is joined on ORG_ID and SITE_USE_ID.
• RA_CUSTOMER_TRX_ALL (SYNONYM) — aliased CT; supplies the purchase order, previous transaction reference, and interface header context/attribute columns.

The join predicates enforce multi-org consistency: CT.ORG_ID = SU.ORG_ID, SU.ORG_ID = PS.ORG_ID, PS.CUSTOMER_SITE_USE_ID = SU.SITE_USE_ID, and PS.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID. The comment embedded in the view text (attributed to Shiv Ragunat, 10/10/96) records that the lookup tables were added to obtain the functional currency context for functional amount calculation. Because the view filters AL_CLASS.LOOKUP_CODE = 'INV', it returns invoices only, excluding credit memos and other transaction classes. In 12.1.1 the same definition applies; differences between 12.1.1 and 12.2.2 are confined to underlying table changes rather than view logic.

Key Columns

• CUSTOMER_TRX_ID / TRX_NUMBER / TRX_DATE — Transaction identifier, invoice number, and invoice date.
• STATUS and AL_STATUS_MEANING — The coded status and its meaning derived from the INVOICE_TRX_STATUS lookup type; the column most associated with the invoice_trx_status search.
• CLASS and AL_CLASS_MEANING — Class code (restricted to 'INV') and its lookup meaning.
• AMOUNT_DUE_ORIGINAL / AMOUNT_DUE_REMAINING — Original and open balances from the payment schedule.
• DUE_DATE, INVOICE_CURRENCY_CODE, TERMS_SEQUENCE_NUMBER — Terms and currency attributes.
• CUSTOMER_ID, CUSTOMER_SITE_USE_ID, BILL_TO_PARTY_ID, BILL_TO_SITE_USE_ID — Customer and bill-to identifiers.
• CT_PURCHASE_ORDER, CT_PREVIOUS_CUSTOMER_TRX_ID — Exchange-related purchase order and prior transaction reference.
• INTERFACE_HEADER_CONTEXT, INTERFACE_HEADER_ATTRIBUTE1–4 — Descriptive flexfield context and attribute values captured during import.
• BILLING_INTERFACE_REQUEST_ID, BILLING_PERIOD — Billing interface and period references.

Common Use Cases and Queries

The view is typically queried for reconciliation of exchange invoices, status reporting, and extracting interface attribute data. A typical status report:

• SELECT TRX_NUMBER, TRX_DATE, STATUS, AL_STATUS_MEANING, AMOUNT_DUE_REMAINING FROM APPS.AR_OEX_INVOICE_VIEW WHERE ORG_ID = :p_org_id AND STATUS = :p_status;
• SELECT TRX_NUMBER, AL_STATUS_MEANING, AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING FROM APPS.AR_OEX_INVOICE_VIEW WHERE CUSTOMER_TRX_ID = :p_customer_trx_id;
• SELECT INTERFACE_HEADER_CONTEXT, INTERFACE_HEADER_ATTRIBUTE1 FROM APPS.AR_OEX_INVOICE_VIEW WHERE TRX_NUMBER = :p_trx_number;

Because the view hard-codes CLASS = 'INV' and joins to lookups internally, callers cannot retrieve credit memos or override status decoding. Queries should always constrain ORG_ID in multi-org environments.