Search Results contingency_code




Overview
Explore in AI Chat

Overview

APPS.OKL_REVENUE_CONTINGENCIES_V is an Oracle E-Business Suite view belonging to the Lease Management (OKL) module, part of the Enterprise Contracts and Trade Management (ETRM) family. It exposes revenue contingency configurations maintained in Oracle Receivables and reused by Oracle Lease Management. In lease accounting, a revenue contingency is the rule that determines when revenue may be recognized — for example, deferring revenue until a receivable is actually collected. The view filters the Receivables contingency setup to a single lease-specific contingency type, OKL_COLLECTIBILITY, and decorates each row with human-readable names resolved from EBS lookups.

Within Oracle EBS 12.1.1 and 12.2.2, the object behaves as a read-only reporting and integration layer. It is not itself a table and holds no data; it is a projection over shared Oracle Receivables setup. The view is typically referenced by lease accounting logic, period-end reports, and custom extensions that need to know the collectibility contingency parameters (days, start and end dates) applicable to a given operating unit. Because it is defined in the APPS schema, it inherits the standard APPS grants and is available to any responsibility with access to the OKL/AR synonyms.

Underlying Base Objects

The view is defined over two documented objects:

Because AR_CONT_ACTIONS_ALL is referenced through a synonym, the view is decoupled from the physical AR schema at compile time, which is consistent with standard EBS cross-application setup sharing between Receivables and Lease Management.

Key Columns

  • CONTINGENCY_CODE — the lookup code identifying the contingency; always 'OKL_COLLECTIBILITY' in this view.
  • CONTINGENCY_NAME — the display meaning resolved from the AR_REVENUE_CONTINGENCIES lookup, providing the user-facing label for the code.
  • REVREC_EVENT_CODE — the revenue recognition event that triggers handling of the contingency.
  • REVREC_EVENT_NAME — the descriptive meaning of that event, resolved from the AR_REVREC_EVENTS lookup.
  • DAYS — the number of days associated with the contingency rule, used in date-driven recognition logic.
  • START_DATE / END_DATE — the effective window during which the contingency configuration applies.
  • ORG_ID — the operating unit to which the setup row belongs, enabling multi-org filtering.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns for change tracking.

Common Use Cases and Queries

The view is most often used to validate or report the collectibility contingency configuration for an operating unit, and to join setup to lease contracts or receivables activity. A typical query listing all configured rows is:

SELECT contingency_code, contingency_name, revrec_event_code, revrec_event_name, days, start_date, end_date, org_id FROM apps.okl_revenue_contingencies_v WHERE org_id = :p_org_id;

Because the view already restricts data to OKL_COLLECTIBILITY, the only additional predicate ordinarily required is ORG_ID for multi-org environments. Integration scenarios include custom lease revenue-recognition reports, diagnostic queries confirming that the contingency window (START_DATE/END_DATE) is current, and extensions that need the resolved lookup meaning rather than the raw code. When troubleshooting missing or unexpected revenue deferral behavior in Lease Management, this view is a first point of inspection, since an absent or expired row in AR_CONT_ACTIONS_ALL for OKL_COLLECTIBILITY will directly affect recognition outcomes.