Search Results order_tangible_id




Overview
Explore in AI Chat

Overview

APPS.AR_DOCS_RECEIVABLES_V is a multiorg view in the Oracle E-Business Suite Receivables (AR) module, registered under FND Design Data AR.AR_DOCS_RECEIVABLES_V and owned by the APPS schema. It presents a consolidated, reporting-oriented projection of receivables documents — invoices, debit memos, credit memos, chargebacks, and related receipt activity — joined to supplementary document attributes used by external or tangential applications such as trade management, order capture, and treasury integration. The view is classified as a multiorg view, meaning it automatically restricts rows to the operating unit of the current session context established through MOAC (Multi-Org Access Control). Callers therefore see only data belonging to their active operating unit without writing explicit ORG_ID predicates.

Its primary role is to expose a flat structure that maps Receivables transactions and their payment schedules to a set of document-level identifiers and attributes, including the ORDER_TANGIBLE_ID and ORDER_EXT_ID columns that tie receivables documents back to originating order and tangible objects. Because it shields consumers from the normalized joins among transaction, customer, receipt, and payment tables, it is commonly used for inbound/outbound integration, extract feeds, and custom reporting where a single row per receivables document is required.

Underlying Base Objects

The documented base objects for this view are:

  • AR_CUSTOMER_TRX (synonym) — the Receivables transaction header, providing document number, date, currency, type, and amounts.
  • AR_PAYMENT_SCHEDULES (synonym) — payment schedules attached to each transaction, supplying settlement, discount, and payment-term amounts.
  • AR_RECEIVABLE_APPLICATIONS (synonym) — cash application links between receipts and transactions.
  • AR_CASH_RECEIPTS (synonym) — receipt headers for cash receipt details and references.
  • AR_RECEIPT_CLASSES (synonym) and AR_RECEIPT_METHODS (synonym) — lookup tables classifying receipts and their collection methods.
  • IBY_FNDCPT_TX_EXTENSIONS (synonym) — payment-related extension attributes from the Payments module.
  • ARP_TRX_LINE_UTIL (package) — a Receivables utility package used as a programmatic dependency for computation or lookup logic.

Collectively these objects supply the header, line, receipt, and payment extension data that the view flattens into a document-level result set.

Key Columns

ORDER_TANGIBLE_ID (VARCHAR2(80)) is the tangible identifier that associates the receivables document with an order or inventory tangible, and is the column most relevant to callers searching for "order_tangible_id". ORDER_EXT_ID (NUMBER(15)) carries the external order identifier. DOC_UNIQUE_REF and CALLING_APP_DOC_REF_NUMBER provide document uniqueness and calling-application reference keys.

Financial columns include DOCUMENT_AMOUNT, DOCUMENT_CURRENCY_CODE, SETTLEMENT_AMOUNT, DISCOUNT_AMOUNT, LOCAL_TAX_AMOUNT, NATIONAL_TAX_AMOUNT, VAT_TAX_AMOUNT, and DOCUMENT_CURR_CHARGE_AMOUNT. DOCUMENT_DATE, DOCUMENT_TYPE, and DOCUMENT_DESCRIPTION describe the document itself. PO_NUMBER, VAT_REF_NUMBER, CUSTOMER_REFERENCE, and CALLING_APP_DOC_REF_NUMBER carry trading and compliance references. PAYMENT_TRXN_EXTENSION_ID and LEGAL_ENTITY_ID link to payments and legal entity context. ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY provide descriptive flexfield support. Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support concurrency and auditing.

Common Use Cases and Queries

Typical scenarios include extracting receivables documents for downstream reconciliation, mapping order tangibles to invoices, and building treasury or VAT reporting feeds.

  • Locate documents by tangible identifier for order-to-cash traceability.
  • Report document and tax amounts per currency and date for VAT compliance.
  • Reconcile receipts, applications, and payment extensions against invoices.
  • Feed external document management or dispute systems via DOCUMENT_DISPUTED_FLAG and COMMENTS.

Sample query:

  • SELECT ORDER_TANGIBLE_ID, ORDER_EXT_ID, DOC_UNIQUE_REF, DOCUMENT_DATE, DOCUMENT_TYPE, DOCUMENT_AMOUNT, DOCUMENT_CURRENCY_CODE, SETTLEMENT_AMOUNT FROM APPS.AR_DOCS_RECEIVABLES_V WHERE ORDER_TANGIBLE_ID = :p_tangible_id;
  • SELECT ORDER_TANGIBLE_ID, SUM(DOCUMENT_AMOUNT) FROM APPS.AR_DOCS_RECEIVABLES_V WHERE DOCUMENT_DATE BETWEEN :p_from AND :p_to GROUP BY ORDER_TANGIBLE_ID;

Because the view is multiorg, no ORG_ID filter is required; the operating unit is derived from the session context.