Search Results get_rec_status

Overview

OKL_UTIL is the shared utility package for the Oracle Lease and Finance Management (OKL) module in Oracle E-Business Suite, delivered under the APPS schema. It is classified in the ETRM metadata as a UTIL package, meaning it exposes a library of reusable validation, lookup, and data-retrieval routines consumed throughout the leasing application rather than a discrete business transaction. The package body carries a header revision of 120.2.12010000.2 dated 2008/11/13, consistent with the 12.1.1 and 12.2.2 code lines.

A substantial portion of OKL_UTIL is dedicated to instrumentation. It declares file handles and flags for trace and output logging (l_trace_path, l_trace_file, l_output_file, l_trace_flag, l_log_flag, l_output_flag), request and program context variables (l_request_id, l_program, l_module), and standard trace naming constants (g_trc_trace_file_prefix set to 'okl_', g_trc_trace_file_suffix set to '.trc'). It also defines public record and collection types — unq_rec_type, unq_tbl_type, lenchk_rec_type, lenchk_tbl_type — that support uniqueness and column-length validation, plus the error message tokens generated by OKL_Api.G_APP_NAME and related constants such as G_EXPECTED_ERROR ('OKL_VALUE_ERROR') used to translate Oracle errors into OKL application messages. The largest single consumer signal is that the package is referenced by 78 other packages, confirming its role as foundational infrastructure.

Key Procedures and Functions

The ETRM metadata documents 11 procedures and functions:

• CHECK_LOOKUP_CODE — Validates a value against an Oracle EBS lookup code, the routine identified by the user search term.
• CHECK_DOMAIN_YN — Validates a value against the Yes/No domain.
• CHECK_DOMAIN_AMOUNT — Validates a value against the amount domain.
• CHECK_FROM_TO_DATE_RANGE — Verifies that a supplied From/To pair of dates is in valid sequence.
• CHECK_FROM_TO_NUMBER_RANGE — Verifies that a supplied From/To pair of numbers is in valid sequence.
• CHECK_ORG_ID — Validates an organization identifier against the operating unit context.
• GET_PREACTIVE_LINE_INST — Retrieves pre-active line instance information.
• GET_ACTIVE_LINE_INST_COUNTRY — Retrieves the country associated with an active line instance.
• GET_REC_STATUS — Returns the record status for a supplied entity.
• GET_NEXT_SEQ_NUM — Obtains the next sequence number.
• VALIDATE_SEQ_NUM — Validates a supplied sequence number.

Collectively these routines standardize the lookups, date and number screening, organization checks, and sequence handling used across OKL forms and concurrent programs.

Tables Accessed

Via APPS synonyms, OKL_UTIL references several core and cross-module tables. FND_LANGUAGES supplies the installed language list that populates global language data in the package body, and UTL_FILE supports trace and output logging to the database server filesystem. Leasing contract structures are read through OKC_K_ITEMS, OKC_K_LINES_B, and OKC_LINE_STYLES_B. Asset instance data comes from CSI_ITEM_INSTANCES and OKL_TXL_ITM_INSTS. Organization and location validation uses HR_ALL_ORGANIZATION_UNITS, HZ_LOCATIONS, and HZ_PARTY_SITES. System-level defaults and sequence values are read from OKL_SYSTEM_PARAMS, which underpins GET_NEXT_SEQ_NUM and VALIDATE_SEQ_NUM.

Usage Notes

OKL_UTIL is not typically invoked directly by end users. It is called from Oracle Forms event handlers, from concurrent programs executing leasing batch processes, and from custom extensions layered on the OKL module. Because 78 packages depend on it, OKL_UTIL sits directly on critical application paths; callers rely on its exception tokens (for example OKL_VALUE_ERROR) to raise consistent, user-facing validation messages. Trace and output flags should be enabled selectively in production, as file output is written through UTL_FILE to the database server directory defined by l_trace_path.