Search Results okl_duplicate_cure_request

Overview

OKL_UTIL is a shared utility package body owned by APPS within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It is classified as a UTIL package, meaning it does not implement a business transaction API but instead supplies reusable helper routines consumed by other OKL packages and forms. The package addresses two broad categories of functionality: derivation of installation-related geography for lease financial lines, and generic validation and sequence-generation services used across lease contracts, assets, and reporting components. In EBS 12.1.1 and 12.2.2, OKL_UTIL is referenced by 78 other packages, confirming its role as a low-level dependency in the OKL call stack. The source header indicates the file was last modified under the 120.7 release stream (OKLRUTLB.pls), which places it firmly in the R12 code line. Because the user query referenced "okl_duplicate_cure_request," it is worth noting that OKL_UTIL does not itself implement cure or duplication request logic; rather, packages handling such workflows depend on the generic validation and lookup routines exposed here.

Key Procedures and Functions

• GET_PREACTIVE_LINE_INST — Returns the country code associated with the installation site of a financial line before that line becomes active. It resolves the INSTALL_AT party site usage joined to the free-form line structure.
• GET_ACTIVE_LINE_INST_COUNTRY — Performs the equivalent country lookup for a financial line that is already active, using the instance CLE relationships.
• CHECK_LOOKUP_CODE — Validates that a supplied code exists in the relevant Oracle lookup type, providing a reusable referential check for form and API code.
• CHECK_DOMAIN_YN — Confirms that a value belongs to a Yes/No domain, standardizing boolean-style validation.
• CHECK_DOMAIN_AMOUNT — Validates that a supplied amount falls within acceptable numeric bounds or domain rules.
• CHECK_FROM_TO_DATE_RANGE — Verifies that a start date precedes an end date, a common precondition in lease term and calendar validation.
• CHECK_FROM_TO_NUMBER_RANGE — Performs the numeric analogue of the date range check for paired range values.
• CHECK_ORG_ID — Confirms that an organization identifier is valid and consistent with the calling context, supporting multi-org access control.
• GET_REC_STATUS — Retrieves the current status of a record, allowing callers to branch on lifecycle state.
• GET_NEXT_SEQ_NUM — Allocates the next available sequence number for a given sequence context.
• VALIDATE_SEQ_NUM — Validates that a supplied sequence number is legitimate and has not been superseded.

Tables Accessed

The installation-site functions join OKL_TXL_ITM_INSTS to OKX_PARTY_SITE_USES_V and the OKC contract line tables, OKC_K_LINES_B and OKC_LINE_STYLES_B, to navigate from a free-form financial line through the INST_ITEM structure to a physical site. OKC_K_ITEMS provides the contract item context. Geographic resolution depends on HZ_LOCATIONS and HZ_PARTY_SITES, while CSI_ITEM_INSTANCES supplies installed asset information. HR_ALL_ORGANIZATION_UNITS supports organization-level validation for CHECK_ORG_ID, and OKL_SYSTEM_PARAMS supplies configurable defaults and sequence settings. UTL_FILE is referenced for file-based diagnostic output rather than business data. All tables are accessed through APPS synonyms, so the package executes under standard EBS schema resolution.

Usage Notes

OKL_UTIL is not exposed directly to end users. It is invoked programmatically by other OKL packages during lease booking, asset installation updates, and contract validation. Forms within the Lease Management responsibility call these helpers through their underlying package layers to enforce date ranges, lookup validity, and organization security before committing data. Concurrent programs and custom extensions should call the individual functions rather than reimplementing the same checks, since the 78 dependent packages rely on consistent behavior. Because the package performs read-only lookups and utility validation, it is safe to call repeatedly within a transaction; however, sequence-generation functions should be treated as stateful and not retried casually. When debugging issues around installation country derivation, tracing into GET_PREACTIVE_LINE_INST or GET_ACTIVE_LINE_INST_COUNTRY is the correct first step, as both depend on the correct population of OKL_TXL_ITM_INSTS and the associated party site usage records.