Search Results arbv_revenues

Overview

ARBV_REVENUES is a read-only Oracle EBS view owned by the APPS schema within the Oracle Receivables (AR) product family. The "B" in its name designates it as a backward-compatibility, or "retrofitted," object, which signals that it delivers a legacy column contract on top of the current Receivables transaction-line model. The view exposes customer transaction line data filtered to LINE-type records, presenting them through an interface originally defined for Oracle's earlier revenue reporting and integration components.

In EBS 12.1.1 and 12.2.2 the object is documented as a VIEW with VALID status. Its purpose is to give reporting tools, custom concurrent programs, and downstream integrations a stable set of column names and business labels that abstract away the physical layout of RA_CUSTOMER_TRX_LINES. Because the view is defined WITH READ ONLY, it supports query-only access and cannot be used as the target of DML within Receivables.

The view text also embeds presentation metadata, notably the literal '_LA:CTL.REASON_CODE:AR_LOOKUPS:INVOICING_REASON:MEANING', which instructs the Oracle Business Intelligence (BI) / XML Publisher layer to resolve a reason code against the AR_LOOKUPS lookup type INVOICING_REASON and display the MEANING column as the "_LA:REASON" output column.

Underlying Base Objects

The documented ETRM metadata identifies a single referenced base object for this view in the 12.2.2 dictionary:

• RA_CUSTOMER_TRX_LINES (referenced in the view definition as the synonym/alias CTL). RA_CUSTOMER_TRX_LINES is the core Receivables table that stores line-level detail for every customer transaction — invoices, credit memos, debit memos, chargebacks, deposits, and guarantees.

The view is essentially a projection of selected columns from that base table, with a fixed WHERE predicate of CTL.LINE_TYPE = 'LINE'. As a result, it returns only true revenue or billing lines and excludes tax lines, freight lines, and other non-LINE line types. The view therefore reflects the current value of RA_CUSTOMER_TRX_LINES in real time and carries no materialized or cached copies of the data.

Key Columns

The exposed columns map directly to RA_CUSTOMER_TRX_LINES attributes, renamed to the retrofitted interface:

• TRANSACTION_LINE_ID — maps to CTL.CUSTOMER_TRX_LINE_ID; the unique identifier of the line and the primary key from the base table.
• AMOUNT — maps to CTL.EXTENDED_AMOUNT; the extended selling amount for the line.
• "_LA:REASON" — derived lookup column resolving CTL.REASON_CODE against the INVOICING_REASON lookup type.
• ITEM_DESCRIPTION — maps to CTL.DESCRIPTION, the free-text line description.
• QUANTITY_ORDERED / QUANTITY_INVOICED — ordered and invoiced quantities for the line.
• UNIT_PRICE — maps to CTL.UNIT_SELLING_PRICE.
• SALES_ORDER_NUMBER, SALES_ORDER_LINE, SALES_ORDER_DATE — the originating sales order reference data, populated when the line is linked to Order Management.
• ACCOUNTING_RULE_DURATION and ACCOUNTING_RULE_ID — the revenue recognition rule applied to the line.
• CUSTOMER_TRX_ID — the header transaction identifier. Companion ID columns include PREVIOUS_CUSTOMER_TRX_ID, PREVIOUS_CUSTOMER_TRX_LINE_ID, and INITIAL_CUSTOMER_TRX_LINE_ID, used to trace line ancestry across credit memos and adjustments.
• INVENTORY_ITEM_ID, MEMO_LINE_ID, UOM_CODE, ORG_ID — item, memo linkage, unit of measure, and operating unit context.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY for audit traceability.

Common Use Cases and Queries

ARBV_REVENUES is typically queried for revenue reporting, reconciliation, and integration extracts where the legacy column contract is required. Typical uses include revenue-by-item analysis, sales order linkage reporting, and feeds into receivable subledger or revenue recognition processes.

Example: retrieve revenue lines for a transaction.

SELECT transaction_line_id, amount, item_description,
       unit_price, sales_order_number, org_id
FROM   apps.arbv_revenues
WHERE  customer_trx_id = :p_trx_id
ORDER  BY transaction_line_id;

Example: summarize revenue by inventory item for an operating unit.

SELECT inventory_item_id, SUM(amount) revenue, COUNT(*) line_count
FROM   apps.arbv_revenues
WHERE  org_id = :p_org_id
GROUP  BY inventory_item_id;

Because the view filters on LINE_TYPE = 'LINE', it is well suited to revenue-focused queries; users seeking tax, freight, or other line classes must query RA_CUSTOMER_TRX_LINES directly with the appropriate LINE_TYPE predicate. The WITH READ ONLY clause guarantees that these queries cannot inadvertently modify Receivables data, making the view safe for ad-hoc and production reporting.