Results for “ar_rev_assign_for_std_v”

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

Overview

The AR_REV_ASSIGN_FOR_STD_V view in the APPS schema is a reporting and integration object within the Oracle Receivables (AR) module. Its documented purpose is to determine the revenue recognition schedules for invoices that use invoicing rules. In practical terms, the view generates the per-period distribution of revenue for a customer transaction line, calculating the amount to be recognized in each accounting period based on the assigned accounting rule. It acts as the orchestration layer that converts a rule definition, a rule schedule, and the line's revenue amount into discrete, dated revenue rows.

Because it surfaces a derived amount and a derived GL date per schedule period, the view is heavily used by revenue recognition reporting, period-close validation, and downstream subledger accounting processes that need to understand how invoice revenue is spread over time. In releases 12.1.1 and 12.2.2 the logic is materially identical, since the underlying rule and schedule tables did not change between these releases.

Underlying Base Objects

The view is defined over the following documented base objects, joined to assemble the schedule:

• RA_CUSTOMER_TRX_LINES (synonym) — the invoice line supplying quantity invoiced or credited, revenue amount, accounting rule duration, and rule start date.
• RA_CUSTOMER_TRX (synonym) — the transaction header, used for the complete flag that suppresses revenue when a transaction is incomplete.
• RA_RULES (synonym) — the accounting/invoicing rule definition, including the rule type (for example type 'A' for a fixed schedule versus a variable duration rule).
• RA_RULE_SCHEDULES (synonym) — the period-by-period schedule of the rule, supplying the period number, percent, and rule date; it is referenced twice (aliased RRS and RRS_LUMP) to isolate the lump-sum period.
• RA_CUST_TRX_LINE_GL_DIST (synonym) — existing line-level GL distributions; if a distribution amount exists it takes precedence over the calculated amount.
• AR_CREDIT_MEMO_AMOUNTS (synonym) — specific credit memo amounts that override the derived value when present.
• AR_PERIODS (synonym) — referenced twice to derive GL dates by mapping the rule start date onto the set of books' period calendar.
• AR_PERIOD_TYPES, GL_SETS_OF_BOOKS, and AR_LOOKUPS (lookups, periods, and set of books) — supporting objects providing period type validation, the set of books identifier, and the account type lookup code used to set the amount sign.

Key Columns

• CUSTOMER_TRX_LINE_ID — primary identifier linking each row back to its invoice line.
• CUSTOMER_TRX_ID and PREVIOUS_CUSTOMER_TRX_LINE_ID — transaction linkage and credit-line reference.
• REQUEST_ID — the concurrent request that generated the data, useful for auditing.
• Quantity — NVL(QUANTITY_CREDITED, QUANTITY_INVOICED), the effective quantity for the schedule row.
• GL DATE — derived using a precedence chain: existing credit memo GL date, then rule schedule date, then a prorated date computed from the period calendar.
• AMOUNT — the revenue amount for the period, prorated from the line's revenue amount by schedule percent, adjusted for lump-sum periods and a variable duration rule (the "acc_dur", or accounting rule duration, denominator). The sign is inverted via the lookup code so that revenue is positive and credit/offset rows are negative.
• ACCOUNT TYPE — the lookup code (for example 'REV') indicating whether the row is revenue or an offsetting account.
• PERIOD_SET NAME — the accounting calendar from the set of books, confirming the period context of the GL date.

Common Use Cases and Queries

Typical uses include auditing the spread of revenue for a given invoice, reconciling schedule rows against posted GL distributions, and diagnosing variable duration rules where the accounting rule duration ("acc_dur") drives the proration. A representative query follows:

• SELECT customer_trx_id, customer_trx_line_id, gl_date, amount, account_type, period_set_name FROM ar_rev_assign_for_std_v WHERE customer_trx_id = :trx_id ORDER BY gl_date;
• Aggregate recognized revenue by period: SELECT account_type, SUM(amount) FROM ar_rev_assign_for_std_v WHERE customer_trx_id = :trx_id GROUP BY account_type;
• Audit the originating concurrent request: SELECT request_id, COUNT(*) FROM ar_rev_assign_for_std_v GROUP BY request_id;

Because the view encapsulates the proration, lump-sum, and GL date precedence logic, querying it is preferable to reimplementing that logic against RA_RULE_SCHEDULES directly.