Results for “arbv_invoice_ars”

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

Overview

ARBV_INVOICE_ARS is a read-only Oracle EBS view owned by the APPS schema and registered as a valid object within the Receivables (AR) product. The "ARBV" prefix follows the Oracle Applications convention for a read-only (B-coded) view, while the metadata description records the object as "Retrofitted," indicating that it was reconstructed to preserve a pre-existing interface contract while its implementation was redirected onto the standard base tables. The view presents a single logical row per Receivables invoice transaction, and it exposes only invoice-type transactions: the defining query restricts the result set to transaction types whose TYPE is 'INV'. Because the view is declared WITH READ ONLY, it can be queried but not used as a target for DML.

The view functions as a reporting and integration surface over the transaction header table. It normalizes lookup-driven attributes — flags such as complete_flag, status_trx, finance_charges, default_tax_exempt_flag, fob_point, edi_processed_flag, and printing_pending — into their decoded MEANING values through embedded AR_LOOKUPS lookups, so that consumers receive descriptive text rather than raw code values. This makes it well suited to ad hoc reporting, custom concurrent programs, and outbound interfaces that require invoice header data in a stable, human-readable form.

Underlying Base Objects

The documented view definition references two base objects, both exposed to APPS through synonyms:

• RA_CUSTOMER_TRX (aliased CT) — the transaction header table supplying all attribute and identifier columns.
• RA_CUST_TRX_TYPES (aliased CTT) — the transaction type table, joined on CUST_TRX_TYPE_ID to constrain rows to invoice types.

The join condition is: CT.CUST_TRX_TYPE_ID = CTT.CUST_TRX_TYPE_ID, qualified by an OR expansion that permits transactions with a null transaction type, together with an organization predicate, NVL(CT.ORG_ID, -12345) = NVL(CTT.ORG_ID, -12345). Although the WHERE clause places the 'INV' filter on the CTT.TYPE column, the OR construct ensures that rows are not silently dropped when the type identifier is null. Because RA_CUSTOMER_TRX is partitioned by ORG_ID in a multi-org environment, the org predicate effectively scopes the transaction type lookup to the correct operating unit, preventing cross-organization type collisions in shared or seeded transaction types.

Key Columns

The view projects four functional groupings of columns from RA_CUSTOMER_TRX:

• TRANSACTION_ID (CUSTOMER_TRX_ID), the primary unique identifier; the view text marks it with the UNIQUE ATTRIBUTES directive, making it the logical key.
• Regular attributes including TRANSACTION_NUMBER (TRX_NUMBER), DOCUMENT_SEQUENCE_NUMBER (DOC_SEQUENCE_VALUE), TRANSACTION_DATE (TRX_DATE), currency conversion fields (CURRENCY_EXCHANGE_RATE, CURRENCY_EXCHANGE_RATE_TYPE, CURRENCY_EXCHANGE_RATE_DATE), PURCHASE_ORDER, CUSTOMER_REFERENCE, TERM_DUE_DATE, and shipping information.
• Lookup-translated fields: COMPLETE_FLAG, STATUS_TRX, FINANCE_CHARGES, DEFAULT_TAX_EXEMPT_FLAG, FOB_POINT, EDI_PROCESSED_FLAG, and PRINTING_PENDING are each resolved to their AR_LOOKUPS MEANING.
• Identifier columns and WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY), plus the ORG_ID required for multi-org context.

Common Use Cases and Queries

Typical consumption includes invoice registers and status extracts, integration staging for downstream systems, and reconciliation of billing activity by operating unit. Because the view already decodes lookup meanings, it simplifies reporting logic. A representative query:

SELECT transaction_id, transaction_number, transaction_date, status_trx, complete_flag, term_due_date FROM apps.arbv_invoice_ars WHERE org_id = :p_org_id AND transaction_date BETWEEN :p_start AND :p_end ORDER BY transaction_date;

To retrieve invoices with an outstanding balance, the view can be joined to AR_PAYMENT_SCHEDULES_ALL on TRANSACTION_ID. Filtering by ORG_ID is essential in multi-org deployments to preserve correct operating unit isolation.