Search Results revrec_event_name

Overview

OKL_REVENUE_CONTINGENCIES_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the Oracle Lease and Finance Management (OKL) product family. Its documented purpose is to hold revenue contingencies originating from Oracle Receivables (AR). In practice, the view exposes the subset of revenue contingency actions that are relevant to lease and finance contracts, specifically limiting its output to the collectibility contingency used by OKL.

The view functions as a reporting and integration bridge. Rather than querying the underlying AR contingency tables directly — which contain many contingency types and are not filtered for OKL semantics — consumers can select from this view to retrieve only the definitions that pertain to lease revenue recognition. It is a read-only construct; no DML is supported against it. Because lease accounting depends heavily on collectibility determinations before revenue can be recognized, this view provides the reference data that drives that evaluation. It also enriches raw AR codes with human-readable names by invoking the OKL_ACCOUNTING_UTIL package, which performs lookup translation at query time.

Underlying Base Objects

According to the documented view text, the definition is built over the following objects:

• AR_CONT_ACTIONS_ALL (SYNONYM) — the primary source table, containing contingency action definitions in Oracle Receivables. The view filters this table on CONTINGENCY_CODE = 'OKL_COLLECTIBILITY', restricting output to the single contingency relevant to lease revenue recognition.
• OKL_ACCOUNTING_UTIL (PACKAGE) — a procedural package referenced twice through its GET_LOOKUP_MEANING function. It translates the stored contingency code and revenue recognition event code into their display meanings, passing the lookup types AR_REVENUE_CONTINGENCIES and AR_REVREC_EVENTS respectively, with language parameters (222) resolved from the calling session.

The dependency on AR_CONT_ACTIONS_ALL makes this view sensitive to Receivables setup. Changes to contingency actions, revenue recognition events, or their lookup values in AR are immediately reflected the next time the view is queried. The package dependency means the view cannot return values unless OKL_ACCOUNTING_UTIL is valid and compiled.

Key Columns

The view exposes the following columns, carried over from AR_CONT_ACTIONS_ALL with two derived additions:

• CONTINGENCY_CODE — the stored contingency identifier. Always 'OKL_COLLECTIBILITY' in this view by virtue of the WHERE clause.
• CONTINGENCY_NAME — derived column; the lookup meaning for CONTINGENCY_CODE, returned by OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING against the AR_REVENUE_CONTINGENCIES lookup type.
• REVREC_EVENT_CODE — the revenue recognition event associated with the contingency action.
• REVREC_EVENT_NAME — derived column; the lookup meaning for REVREC_EVENT_CODE against the AR_REVREC_EVENTS lookup type.
• DAYS — the number of days applied to the contingency action definition.
• START_DATE / END_DATE — the effective date range during which the contingency action applies.
• ORG_ID — the operating unit identifier, supporting multi-org data separation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns describing record creation and modification.

Common Use Cases and Queries

Typical consumers include lease accounting reports, revenue recognition diagnostics, and integration extracts that must validate collectibility configuration before processing lease transactions. A basic query returning all configured contingencies is:

• SELECT contingency_code, contingency_name, revrec_event_code, revrec_event_name, days, start_date, end_date, org_id FROM okl_revenue_contingencies_v;

To inspect the configuration for a specific operating unit, constrain by ORG_ID:

• SELECT contingency_name, revrec_event_name, start_date, end_date FROM okl_revenue_contingencies_v WHERE org_id = :p_org_id;

Often the view is joined to lease or AR transaction data to determine which revenue recognition event applies to a contract at a given date. For example, comparing a lease start date against the effective range:

• SELECT c.contingency_name, c.revrec_event_name FROM okl_revenue_contingencies_v c WHERE TRUNC(SYSDATE) BETWEEN c.start_date AND NVL(c.end_date, TRUNC(SYSDATE)) AND c.org_id = :p_org_id;

Because column names are fully exposed and no joins are embedded in the view itself, it can be treated as a simple filtered lookup source within larger reporting queries. Note that queries depend on OKL_ACCOUNTING_UTIL being valid; if the package is invalid, derived name columns will fail to resolve.