Search Results ct_purchase_order




Overview
Explore in AI Chat

Overview

APPS.AR_OEX_INVOICE_VIEW is a supplementary view in the Oracle E-Business Suite Receivables (AR) module, registered in FND Design Data as AR.AR_OEX_INVOICE_VIEW and documented with a status of VALID. It is classified in the ETRM metadata as a "supplementary view used to simplify forms coding," which means it exists to support Oracle Forms-based user interfaces rather than to serve as a stable public data access point. Oracle explicitly warns that querying or altering data through this view is not recommended, since its definition may change dramatically in subsequent minor or major releases.

In the 12.1.1 and 12.2.2 releases, the view presents a denormalized, form-oriented projection of invoice (transaction) data drawn from the core Receivables transaction tables. It surfaces transaction identifiers, customer identifiers, currency, class and status values with their lookup meanings, and balances, together with a set of order-entry related attributes such as CT_PURCHASE_ORDER and CT_PREVIOUS_CUSTOMER_TRX_ID. The "OEX" prefix in the name references Order Entry (OEX), reflecting the historical integration between Order Management and Receivables that this view supports.

Underlying Base Objects

According to the documented dependency metadata for 12.2.2, APPS.AR_OEX_INVOICE_VIEW references the following objects:

The ETRM metadata records that APPS.AR_OEX_INVOICE_VIEW is not referenced by any database object. Consequently it is a leaf node in the dependency chain: it consumes data from the base objects listed above but does not feed any dependent database object, reinforcing its role as a forms-support construct rather than a data source for other database logic.

Key Columns

The view exposes the following columns and datatypes, as documented:

  • ORG_ID (NUMBER) — organization identifier, supporting multi-org filtered access.
  • TRX_NUMBER (VARCHAR2(30)) — the transaction (invoice) number.
  • TRX_DATE (DATE) — the transaction date.
  • TERMS_SEQUENCE_NUMBER (NUMBER) — payment terms sequence reference.
  • INVOICE_CURRENCY_CODE (VARCHAR2(15)) — the invoice currency.
  • CUSTOMER_ID / CUSTOMER_SITE_USE_ID (NUMBER) — customer and site-use identifiers.
  • CUSTOMER_TRX_ID (NUMBER) — the primary key linking to RA_CUSTOMER_TRX_ALL.
  • CLASS (VARCHAR2(20)) and STATUS (VARCHAR2(30)) — transaction class and status codes.
  • CT_PURCHASE_ORDER (VARCHAR2(50)) — the customer purchase order number captured on the transaction. This is the column most relevant to the user's search term "ct_purchase_order".
  • CT_PREVIOUS_CUSTOMER_TRX_ID (NUMBER) — reference to a prior related transaction.
  • DUE_DATE (DATE), AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING (NUMBER) — payment schedule amounts and due date.
  • AL_CLASS_MEANING and AL_STATUS_MEANING (VARCHAR2(80)) — decoded lookup meanings for class and status.
  • INTERFACE_HEADER_CONTEXT (VARCHAR2(30)) — context for interface processing.
  • BILL_TO_PARTY_ID, BILL_TO_SITE_USE_ID, BILLING_INTERFACE_REQUEST_ID, BILLING_PERIOD (all VARCHAR2(150)) — bill-to and billing interface attributes surfaced as character columns.

Common Use Cases and Queries

Because AR_OEX_INVOICE_VIEW is a forms-support view and Oracle does not recommend direct querying, the primary recommendation is to build reporting and integration extracts against the underlying base tables instead. Nevertheless, the view is frequently encountered in support diagnostics and in the customer purchase order context, since CT_PURCHASE_ORDER provides the invoiced purchase order number directly. A representative query used for investigative purposes is:

SELECT TRX_NUMBER, TRX_DATE, CUSTOMER_TRX_ID, CT_PURCHASE_ORDER, INVOICE_CURRENCY_CODE, AMOUNT_DUE_REMAINING FROM APPS.AR_OEX_INVOICE_VIEW WHERE CT_PURCHASE_ORDER = :p_po_number;

For multi-org environments, a filter on ORG_ID is added to constrain results to the appropriate operating unit. Where decoded values are required, AL_CLASS_MEANING and AL_STATUS_MEANING provide the lookup meanings without an additional join to AR_LOOKUPS.

For production reporting, the equivalent supported pattern joins RA_CUSTOMER_TRX_ALL, AR_PAYMENT_SCHEDULES_ALL, and HZ_CUST_SITE_USES_ALL directly, decoding class and status through AR_LOOKUPS and reading the purchase order from RA_CUSTOMER_TRX_ALL.CT_PURCHASE_ORDER. This approach avoids the stability risk that Oracle associates with the supplementary forms view while returning equivalent data.