Search Results revenue_contingency

Overview

APPS.AR_LINE_CONTINGENCIES_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema and registered in FND Design Data as AR.AR_LINE_CONTINGENCIES_V. The view consolidates revenue contingency information at the transaction line level, joining transaction, customer, revenue scheduling, and general ledger context into a single denormalized result set. Its purpose is to expose the state of revenue contingencies — situations where revenue recognition on a line is deferred or restricted until a specified condition (such as customer acceptance) is satisfied.

The view is marked Internal and carries Oracle's standard warning that access is unsupported except from standard Oracle Applications programs. Its columns include descriptive business attributes (customer name and number, transaction number and date, salesperson, line number, description) alongside monetary and contingency-specific fields such as LINE_AMOUNT, RULE_NAME, REVENUE_CONTINGENCY, REVREC_EVENT, EXPIRATION_DATE, REASON_REMOVAL_DATE, SCHEDULED_REVENUE, UNSCHEDULED_REVENUE, and CREDIT_MEMOS. Because the user searched on "rec_gl_date," the REC_GL_DATE column is of particular interest: it carries the GL accounting date associated with the receivable, providing the accounting-period context for the transaction line. In 12.1.1 and 12.2.2 the column definitions are consistent, as the underlying revenue contingency and deferred revenue model is unchanged between those releases.

Underlying Base Objects

The ETRM metadata documents the view as defined over the following objects: ARPT_SQL_FUNC_UTIL (package), ARP_BAL_UTIL (package), AR_DEFERRAL_REASONS (synonym), AR_DEFERRED_LINES (synonym), AR_LINE_CONTS (synonym), AR_LOOKUPS (view), GL_SETS_OF_BOOKS (view), HZ_CUST_ACCOUNTS (synonym), HZ_PARTIES (synonym), RA_CUSTOMER_TRX (synonym), RA_CUSTOMER_TRX_LINES (synonym), RA_CUST_TRX_LINE_GL_DIST (synonym), and RA_RULES (synonym).

The structural core is the pairing of RA_CUSTOMER_TRX (transaction header) with RA_CUSTOMER_TRX_LINES (transaction lines), augmented by AR_LINE_CONTS, which holds the line-level contingency assignment, and AR_DEFERRED_LINES and AR_DEFERRAL_REASONS, which record deferral and reason information. RA_RULES supplies the revenue recognition rule name, while RA_CUST_TRX_LINE_GL_DIST and GL_SETS_OF_BOOKS contribute accounting and set-of-books context used to derive REC_GL_DATE and SET_OF_BOOKS_NAME/ID. Customer identity is resolved through HZ_CUST_ACCOUNTS and HZ_PARTIES, and AR_LOOKUPS resolves lookup-coded values. The two packages, ARPT_SQL_FUNC_UTIL and ARP_BAL_UTIL, supply server-side functions (for example, name formatting and balance calculations) used within the view's SQL. The view is not referenced by any other database object, confirming it is a terminal reporting object.

Key Columns

• SET_OF_BOOKS_NAME / SET_OF_BOOKS_ID / CURRENCY_CODE — Accounting ledger and currency context for the transaction.
• CUSTOMER_NAME / CUSTOMER_NUMBER — Party and account identifiers resolved from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• TRX_NUMBER / TRX_DATE / LINE_NUMBER — Transaction and line identifiers.
• REC_GL_DATE — The GL accounting date of the receivable associated with the transaction line; the field most frequently used to slice contingency balances by accounting period.
• SALESREP_NAME / REFERENCE_NUMBER / DESCRIPTION — Descriptive attributes, with SALESREP_NAME and REFERENCE_NUMBER exposed at length 4000 due to function-based resolution.
• LINE_AMOUNT / RULE_NAME — Line value and the revenue recognition rule applied.
• REVENUE_CONTINGENCY / REVREC_EVENT — Contingency definition and the event that governs recognition.
• EXPIRATION_DATE / REASON_REMOVAL_DATE — Dates on which the contingency expires or is removed.
• SCHEDULED_REVENUE / UNSCHEDULED_REVENUE / CREDIT_MEMOS — Balances showing revenue already scheduled, still unscheduled, and related credit memos.

Common Use Cases and Queries

Typical uses include contingency aging by accounting period, reconciliation of scheduled versus unscheduled revenue, and audit reporting on deferred recognition. A representative query filtering on REC_GL_DATE:

SELECT TRX_NUMBER, LINE_NUMBER, CUSTOMER_NAME,
       TRX_DATE, REC_GL_DATE, RULE_NAME,
       REVENUE_CONTINGENCY, LINE_AMOUNT,
       SCHEDULED_REVENUE, UNSCHEDULED_REVENUE
FROM   APPS.AR_LINE_CONTINGENCIES_V
WHERE  REC_GL_DATE BETWEEN :p_from_date AND :p_to_date
ORDER  BY REC_GL_DATE, TRX_NUMBER, LINE_NUMBER;

Aggregate reporting by ledger and contingency can be performed with a GROUP BY on SET_OF_BOOKS_NAME and REVENUE_CONTINGENCY. Because metadata flags the object Internal and Oracle does not support direct access, production use should be confined to controlled reporting or extraction, with the standard caveat that the view definition may change without notice in future patches.