Results for “rrs_lump”

10 results




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

Overview

APPS.AR_REV_ASSIGN_FOR_STD_V is a reporting and integration view in Oracle E-Business Suite Receivables (AR) that exposes revenue assignment data for standard (non-variable, non-lump-sum-biased) accounting rules applied to customer transaction lines. The view consolidates information from the invoice line, the accounting rule definition, the rule schedule, the general ledger distribution records, and the credit memo amount records to present a single row per revenue distribution event. Its principal purpose is to supply the revenue recognition engine and downstream reporting tools with a normalized, pre-joined representation of the revenue amount, the GL date, and the account type (revenue or credit) for each scheduled recognition period.

In ETRM 12.1.1 and 12.2.2 the view is owned by APPS and is defined entirely in the source text documented in the ETRM metadata. It is designed for standard revenue assignment processing where the accounting rule is a fixed-duration or variable-duration rule, and where lump-sum handling must be reconciled against period-by-period percentages. The view also accounts for the completion flag on the transaction ("COMPLETE_FLAG"), returning a zero amount when the transaction is not yet complete, which makes it safe for use in reporting that should not recognize revenue prematurely.

Underlying Base Objects

The documented referenced base objects are:

The view joins RA_CUSTOMER_TRX_LINES to RA_CUSTOMER_TRX on CUSTOMER_TRX_ID, and links RA_RULES and RA_RULE_SCHEDULES (aliased both for the main schedule and a separate alias for lump-sum handling). AR_PERIODS is joined twice — once for the rule start period and once for the end period — to compute effective GL dates. RA_CUST_TRX_LINE_GL_DIST provides the actual distribution GL date and amount where available, while AR_CREDIT_MEMO_AMOUNTS supplies a credit memo override. AR_LOOKUPS classifies the account type as revenue (REV) or another code, and the sign of the amount is determined by that lookup. GL_SETS_OF_BOOKS and AR_PERIOD_TYPES provide set-of-books and period-type context.

Key Columns

  • CUSTOMER_TRX_LINE_ID — The invoice line identifier being recognized.
  • CUSTOMER_TRX_ID — The parent transaction identifier.
  • PREVIOUS_CUSTOMER_TRX_LINE_ID — The prior line reference for credit or adjustment chains.
  • REQUEST_ID — The concurrent request that generated the distribution, when applicable.
  • Quantity — NVL(QUANTITY_CREDITED, QUANTITY_INVOICED) — the effective quantity for the line.
  • GL DATE — The recognition date derived by NVL from the distribution GL date, credit memo GL date, rule schedule date, or a computed period-relative date.
  • AMOUNT — The recognized revenue amount, computed from the GL distribution, credit memo amount, lump-sum percentage, or rule schedule percentage, and signed according to ACCOUNT_TYPE.
  • ACCOUNT TYPE — AR_LOOKUPS.LOOKUP_CODE, where 'REV' yields a positive sign and all else negative.
  • PERIOD_SET NAME — The accounting period set from the set of books, used to group and report by calendar.

Common Use Cases and Queries

Typical scenarios include reconciling revenue schedules against GL distributions, validating that credit memo overrides are applied correctly, and exporting revenue assignment data to a data warehouse. A sample query to review revenue assignment for a specific transaction:

  • SELECT CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, "GL DATE", AMOUNT, "ACCOUNT TYPE" FROM APPS.AR_REV_ASSIGN_FOR_STD_V WHERE CUSTOMER_TRX_ID = :trx_id ORDER BY "GL DATE";
  • SELECT "PERIOD_SET NAME", SUM(AMOUNT) FROM APPS.AR_REV_ASSIGN_FOR_STD_V WHERE "GL DATE" BETWEEN :start_date AND :end_date GROUP BY "PERIOD_SET NAME";
  • SELECT CUSTOMER_TRX_LINE_ID, "ACCOUNT TYPE", AMOUNT FROM APPS.AR_REV_ASSIGN_FOR_STD_V WHERE "ACCOUNT TYPE" = 'REV' AND AMOUNT <> 0;

Because the view contains no filtering predicates, it returns all scheduled revenue assignment rows for eligible lines; consumers should always constrain by transaction, date range, or period set to avoid full scans on large Receivables tables. The view is intended for read-only reporting and should not be used as the source for revenue recognition updates.