Results for “arbv_ar_transactions”

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

Overview

The ARBV_AR_TRANSACTIONS view in the APPS schema presents a flattened, integration-oriented projection of customer transaction data maintained in Oracle Receivables. As documented in the ETRM repository for Oracle E-Business Suite 12.1.1 and 12.2.2, the view exposes information about transactions imported from a foreign or external system into Oracle Receivables. Its object status is VALID, and it belongs to the AR - Receivables product family.

The view is designed primarily for inbound interface and reporting scenarios where an external feeder system must read back the state of transactions it has created or that have been loaded on its behalf. Because it surfaces the original system batch name and a curated set of transaction attributes and identifiers, it functions as a stable, read-consistent contract for external consumers, shielding them from the full width and internal complexity of the underlying transaction table. The view text uses a WITH READ ONLY clause, enforcing that all access is query-only.

Underlying Base Objects

The view is defined over a single documented base object, RA_CUSTOMER_TRX, which is referenced through a SYNONYM. RA_CUSTOMER_TRX is the principal Receivables table holding transaction headers. The view aliases this table as CT and selects a defined subset of its columns rather than exposing the entire row.

Several columns are exposed indirectly through lookup translation expressions rather than as raw stored values. The view text applies the standard "_LA" (lookup attribute) mechanism with references to the AR_LOOKUPS lookup type, mapping coded values to their user-facing MEANING for attributes such as COMPLETE_FLAG, STATUS_TRX (INVOICE_TRX_STATUS), FINANCE_CHARGES, DEFAULT_TAX_EXEMPT_FLAG (TAX_CONTROL_FLAG), FOB_POINT, EDI_PROCESSED_FLAG, PRINTING_PENDING, and REASON_CODE (INVOICING_REASON). No joins to other base tables are documented; the relationship is strictly a projection of the transaction header.

Key Columns

The view exposes a mix of transactional attributes, foreign-key identifiers, and standard WHO columns. Important columns include:

• CUSTOMER_TRX_ID (TRANSACTION_ID): The primary transaction identifier and the principal join key back to RA_CUSTOMER_TRX and related AR tables.
• TRX_NUMBER (TRANSACTION_NUMBER) and DOC_SEQUENCE_VALUE (DOCUMENT_SEQUENCE_NUMBER): The transaction number and its assigned document sequence value.
• TRX_DATE (TRANSACTION_DATE): The accounting transaction date.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE: Currency conversion attributes for the transaction.
• _LA:COMPLETE_FLAG and _LA:TRANSACTION_STATUS: Lookup-derived completeness and status meanings in place of coded values.
• PURCHASE_ORDER, PURCHASE_ORDER_DATE, PURCHASE_ORDER_REVISION: Customer purchase order references carried on the transaction.
• ORIG_SYSTEM_BATCH_NAME and BATCH_ID: The originating (foreign) system batch, central to the import/interface use case.
• Bill-to, ship-to, sold-to, and paying customer/site/contact ID columns: Party and location identifiers for the transaction context.
• ORG_ID and SET_OF_BOOKS_ID: Multi-org operating unit and ledger context; INVOICE_CURRENCY_CODE carries the currency.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY): Audit lineage of the record.

Common Use Cases and Queries

Typical usage centers on reconciliation between a foreign feeder system and Receivables, status reporting on imported batches, and extracts for downstream analytics. Because the view returns transaction headers only, queries requiring lines, distributions, or tax detail must join back to RA_CUSTOMER_TRX_LINES and related tables using CUSTOMER_TRX_ID.

• Retrieving transactions by originating batch: SELECT TRANSACTION_ID, TRANSACTION_NUMBER, TRANSACTION_DATE FROM ARBV_AR_TRANSACTIONS WHERE ORIG_SYSTEM_BATCH_NAME = :batch;
• Status and completeness reporting for imported transactions using the lookup-derived columns.
• Multi-org extracts filtered on ORG_ID and SET_OF_BOOKS_ID for ledger-specific reporting.
• Audit extracts using the WHO columns to identify recently created or modified interface records.

All access is read-only; the view cannot be used to insert or update transactions. It should be treated as an integration-facing interface rather than a substitute for the base transaction table when line-level detail is required.