Search Results quantity_credited




Overview
Explore in AI Chat

Overview

ARFV_REVENUES is a read-only view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It exposes detailed revenue information associated with transaction line items, joining each invoice line to its accounting rule, unit of measure, operating unit, and the credit and debit memo transactions that originated it. The view is implemented with a WITH READ ONLY clause, so it cannot be used as a DML target; it exists purely for query, reporting, and integration consumption.

Because it flattens the relationships between a transaction line and its revenue schedule definition (RA_RULES), the view is a natural starting point for revenue recognition analysis. The user search term rule_start_date maps directly to the RULE_START_DATE column of RA_CUSTOMER_TRX_LINES, which ARFV_REVENUES exposes unchanged. Rule start date is the anchor used by Receivables when generating revenue recognition schedules, so this view is the primary supported way to report on it together with the accounting rule name and duration.

The view restricts itself to transaction lines where LINE_TYPE = 'LINE', excluding tax, freight, and other line types, so results represent the actual revenue-bearing items of a transaction.

Underlying Base Objects

Per the documented ETRM metadata (12.2.2), ARFV_REVENUES is defined over five referenced base objects, all resolved through APPS synonyms:

  • RA_CUSTOMER_TRX_LINES — the driving table, aliased CTL; supplies line number, extended amount, quantities, unit selling price, sales order references, accounting rule duration, and rule start date.
  • RA_CUSTOMER_TRX — aliased CT; supplies transaction number, transaction date, complete flag, previous and initial transaction identifiers, and organization ID.
  • RA_RULES — aliased RUL; supplies the accounting rule name joined on ACCOUNTING_RULE_ID = RULE_ID.
  • MTL_UNITS_OF_MEASURE — aliased UOM; supplies the unit of measure name joined on UOM_CODE.
  • HR_ALL_ORGANIZATION_UNITS — aliased AOU; supplies the operating unit name joined on ORG_ID.

In the full view text, RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES are also referenced multiple times to resolve the previous (credit) and initial (debit) transactions through outer joins, allowing each line to display its originating and reversing document numbers. All non-driving joins, including RA_RULES, MTL_UNITS_OF_MEASURE, and HR_ALL_ORGANIZATION_UNITS, are outer joins, so lines remain visible even when the rule, UOM, or organization lookup is missing.

Key Columns

Common Use Cases and Queries

The most frequent requirement is reporting revenue by accounting rule and start date, typically for deferred revenue schedules or reconciliation to GL revenue accounts. Because the view already resolves the rule name and operating unit, queries are concise:

  • Revenue by rule start date and rule: 
    SELECT rule_start_date, name AS rule_name, trx_number,
       transaction_line_number, amount
FROM   arfv_revenues
WHERE  rule_start_date BETWEEN :p_start AND :p_end
ORDER  BY rule_start_date;
  • Lines with no accounting rule assigned: 
    SELECT trx_number, transaction_line_number, amount
FROM   arfv_revenues
WHERE  accounting_rule_id IS NULL;
  • Revenue by operating unit for a period: 
    SELECT org_id, trx_date, SUM(amount)
FROM   arfv_revenues
WHERE  trx_date BETWEEN :p_start AND :p_end
GROUP  BY org_id, trx_date;
  • Credit and original document tracing: joining on PREVIOUS_CUSTOMER_TRX_ID and INITIAL_CUSTOMER_TRX_ID to relate credits, debit memos, and their source invoices.

Because it is read-only and contains no bind-sensitive logic, ARFV_REVENUES is safe for ad hoc extracts, BI Publisher data sources, and reconciliation scripts against 12.1.1 and 12.2.2, though large extracts should be filtered on ORG_ID and date ranges to avoid full scans of RA_CUSTOMER_TRX_LINES.