Results for “rule_information7”

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

Overview

OKL_CURE_RULE_UV is an APPS-owned, VALID database view in the Oracle Lease and Finance Management (OKL) module, delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. The name follows Oracle's convention for a user-facing view: the "UV" suffix indicates a presentation layer intended for direct query by reports, forms, and integrations, as opposed to the "_V" or internal suffixed objects used within business logic. The view consolidates cure-rule configuration and vendor, program, and contract context into a single denormalized result set, allowing reporting tools to retrieve complex cure-rule data without navigating the many internal tables that underpin contract servicing.

Its principal role is to expose the rule parameters that OKL uses to evaluate contract cure conditions and the associated vendor and contract attributes. Because a cure rule can operate across leases, financing arrangements, and third-party vendor programs, the view normalizes these dimensions into one row per qualifying rule, which makes it suitable for ad hoc inquiry, extracts, and downstream integration into external reporting systems.

Underlying Base Objects

The documented base objects are OKC_UTIL (a package) and OKL_C_V_RULES_UV (a view). OKL_CURE_RULE_UV is defined directly over OKL_C_V_RULES_UV. The dependency on OKC_UTIL reflects the shared rule-framework utilities used to resolve rule codes and related attributes within the contract core (OKC) layer on which OKL is built.

The view text filters the source rows with the predicate WHERE CVR.RULE_CODE = 'COCURE'. This restricts the result set to the cure rule category, so the view functions as a category-specific projection of the broader OKL_C_V_RULES_UV rule view. Any change to the underlying rule definition or to the OKC_UTIL package may affect the values returned here, so the view should be treated as read-only metadata.

Key Columns

The projection combines identifier, descriptive, and rule-parameter columns:

• VENDOR_ID, VENDOR_NAME – Identifies the vendor associated with the cure rule.
• VENDOR_PROGRAM_ID, VENDOR_PROGRAM_NUMBER, VENDOR_PROGRAM_NAME – Identify the specific vendor program to which the rule applies.
• CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_DESCRIPTION – Identify the lease or financing contract tied to the rule instance.
• RULE_CODE – The rule category; always 'COCURE' in this view, identifying it as a cure rule.
• RULE_INFORMATION1 through RULE_INFORMATION15 – The general-purpose rule parameter block. The meaning of each slot is defined by the rule setup, not by the view itself.

Within the RULE_INFORMATION block, the view applies conversions that reveal the intended data type of individual slots. Slots 5 and 7 are constructed with TO_DATE(RULE_INFORMATION5 || TO_CHAR(SYSDATE, '-MM-RRRR'), 'DD-MM-RRRR'), appending the current month and year to a stored day value so the result is a valid date. This means slots 5 and 7 hold day-of-month components and are exposed as DATE columns. In the current definition, RULE_INFORMATION6 is projected as RULE_INFORMATION6 RULE_INFORMATION6, a passthrough alias that does not alter the value. Slots 8 through 15 are projected unchanged.

Common Use Cases and Queries

Typical use cases include verifying which contracts and vendor programs have an active cure rule, extracting rule parameter values for audit or reconciliation, feeding external collections or servicing systems, and diagnosing why a contract cured or failed to cure. Because the view already restricts to 'COCURE', queries need not repeat the rule-code filter.

A basic listing of vendor and contract context:

• SELECT vendor_name, contract_number, rule_information1
• FROM apps.okl_cure_rule_uv
• WHERE contract_id = :p_contract_id;

Filtering on a converted date slot, for example slot 5:

• SELECT contract_number, rule_information5
• FROM apps.okl_cure_rule_uv
• WHERE rule_information5 >= SYSDATE - 30;

For reporting extracts, join to OKL contracts or vendor master views using CONTRACT_ID or VENDOR_ID. Always query the view rather than its base objects where the 'COCURE' filter and the date conversions are required.