Results for “arbr_document_lines_v”

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

Overview

ARBR_DOCUMENT_LINES_V is a public view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and is documented as a component required for payment settlement processing. In practice, the object serves as a conformed, flat record structure that downstream settlement and reconciliation logic can consume without depending on the physical storage of any single transactional table. Its columns describe document line detail — document reference, purchase order, line number, line type, gross amount, pricing, tax, and the standard DFF attribute columns — which is the shape typically required when matching receivables documents against payment or settlement records.

The view carries a VALID status in the ETRM data dictionary, indicating that it compiles cleanly in the supported 12.1.1 and 12.2.2 environments. Because it is exposed in the APPS schema, it is available to any concurrent program, OAF page, or custom SQL that runs under a standard EBS responsibility with the appropriate grants. The user search term "doc_unique_ref" corresponds to the first column of the view and identifies the join key most commonly used when linking settlement data back to a receivables document.

Underlying Base Objects

The documented definition of ARBR_DOCUMENT_LINES_V references a single base object: the DUAL synonym owned by SYS and exposed through APPS. There is no dependency on AR tables such as RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, or AR_PAYMENT_SCHEDULES_ALL. The view text is a single SELECT from DUAL using literal and pseudo-column expressions:

• SELECT 'X', NULL, -3, 'X', -3, NULL, ... , -3, SYSDATE, -3, SYSDATE, NULL, 1 FROM DUAL

Consequently, the view emits exactly one row and never returns customer transaction data. The constants are placeholder values: string literals for DOC_UNIQUE_REF and LINE_TYPE, numeric -3 for numeric columns such as LINE_NUMBER, LINE_GROSS_AMOUNT, UNIT_PRICE, and QUANTITY, SYSDATE for CREATION_DATE and LAST_UPDATE_DATE, and 1 for OBJECT_VERSION_NUMBER. This construct is characteristic of a stub or signature view used by an integration layer that requires a stable column contract even when no source rows exist.

Key Columns

The view projects 38 columns. The most significant for settlement processing are:

• DOC_UNIQUE_REF — the document identifier referenced in the user's search; in this view it is hard-coded to 'X'.
• PO_NUMBER, LINE_NUMBER, LINE_TYPE — purchase order and line identifiers, with LINE_NUMBER populated as -3 and LINE_TYPE as 'X'.
• LINE_GROSS_AMOUNT, EXTENDED_AMOUNT, DISCOUNT_AMOUNT, SALES_TAX_AMOUNT, VAT_TAX_AMOUNT, TAX_RATE, TAX_CODE — monetary and tax attributes, all returned as NULL.
• UNIT_PRICE, QUANTITY, UNIT_OF_MEASURE, INVENTORY_ITEM_ID, DESCRIPTION — item and pricing detail, returned as NULL except where the constant -3 appears.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard descriptive flexfield columns, all NULL.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — the standard WHO and version columns, populated with SYSDATE, -3, and 1 respectively.

Common Use Cases and Queries

The principal use case is structural: providing the settlement interface with a guaranteed result set of the expected shape so that calling code, PL/SQL record types, or BI Publisher layouts compile and execute without raising NO_DATA_FOUND. Typical queries include introspection and signature validation rather than analytical reporting:

• SELECT * FROM apps.arbr_document_lines_v; — returns a single all-placeholder row; useful to confirm the view is deployed and valid.
• SELECT doc_unique_ref, line_number, line_gross_amount FROM apps.arbr_document_lines_v WHERE doc_unique_ref = :p_ref; — the natural filter pattern for settlement lookups, though against this view it will not yield real data.
• SELECT column_name, data_type FROM all_tab_columns WHERE table_name = 'ARBR_DOCUMENT_LINES_V'; — verifies the 38-column contract expected by the settlement integration.

Because the view is defined over DUAL and returns no operational data, it should not be used as a reporting source. Analysts seeking actual receivables document lines must query the underlying AR transaction tables instead. ARBR_DOCUMENT_LINES_V should be treated as an interface contract object maintained for payment settlement compatibility in R12.1.1 and R12.2.2.