Search Results ar_line_contingencies_v




Overview
Explore in AI Chat

Overview

AR_LINE_CONTINGENCIES_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and is documented as holding contingency information for a deferred billing line. In the Oracle EBS revenue recognition model, a contingency represents a condition or event that must be satisfied before revenue associated with a deferred line can be recognized. This view consolidates that contingency context with the originating transaction, customer, sales representative, accounting rule, and revenue scheduling data, making it a single reporting surface for analyzing deferred revenue and the events that gate its recognition.

Because the view joins transactional, distribution, deferral, and party data, it is typically used for reporting and reconciliation rather than for transactional data entry. Analysts and subledger accountants use it to investigate why revenue on a specific deferred line has not yet been recognized, when the contingency expires, and what the scheduled versus unscheduled revenue position looks like at any point in time.

Underlying Base Objects

The view is defined as a MAX-aggregated SELECT over a multi-table join. Documented base objects include:

Several joins are outer joins, notably to RA_RULES (RULE_ID) and, in the documented excerpt, to the customer party tables, reflecting that some lines may lack those attributes.

Key Columns

Common Use Cases and Queries

Typical scenarios include deferred revenue aging, contingency expiration monitoring, and reconciliation of scheduled versus unscheduled revenue. The following query lists open contingencies by transaction:

SELECT trx_number, customer_name, line_number,
       revenue_contingency, revrec_event,
       expiration_date, scheduled_revenue, unscheduled_revenue
  FROM apps.ar_line_contingencies_v
 WHERE unscheduled_revenue > 0
 ORDER BY expiration_date;

A second query totals deferred balances by contingency:

SELECT revenue_contingency,
       COUNT(*)                 line_count,
       SUM(scheduled_revenue)   recognized,
       SUM(unscheduled_revenue) deferred
  FROM apps.ar_line_contingencies_v
 GROUP BY revenue_contingency
 ORDER BY deferred DESC;

Because the view returns at most one row per deferred line (using MAX aggregation), it is suitable as a reporting source but should not be used to extract raw distribution-level detail, which must be obtained from the underlying base tables directly.