Search Results okx_operunit_csr

Overview

OKL_JTOT_EXTRACT is an APPS-owned PL/SQL package body in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its principal business role is to extract and resolve reference data — particularly party, contact, and role information associated with lease and finance contracts — so that this information can be surfaced through the Oracle JTF (Java Technology Foundation) object query and search framework. The package bridges OKL contract data with the JTF object model by translating contract-level entities such as parties, contacts, contracts, and role definitions into the generic name/id1/id2 query interface consumed by JTF-based search and lookup components.

The header identifies the source file as OKLRJEXB.pls and the package as a "noship" (not shipped in a specific form-specific sense) backend utility. Internally, the package defines several global message tokens and constants used to raise and tokenize error messages, including G_JTF_OBJECT_QUERY_FAILED ('OKL_LLA_JTF_OBJ_QUERY'), G_MISS_CHR_CLE ('OKL_LLA_MISSING_PARMETERS'), G_UNABLE_TO_FIND_PARTY_ROLE ('OKL_LLA_JTF_OBJ_QUERY_FAIL'), and G_MISSING_CONTRACT ('OKL_LLA_CONTRACT_NOT_FOUND'). These constants demonstrate that the package is a key participant in the OKL "LLA" (lookup/list of values adapter) error-handling convention, feeding tokenized messages back to the JTF framework.

Key Procedures and Functions

• GET_PARTY — Resolves and returns party-related query data for the JTF object query interface. It aligns with the package's okx_party_csr cursor logic, which selects id1, id2, name, and description from the OKX parties view using optional name/id filters.
• GET_SUBCLASS_DEF_ROLES — Retrieves role definitions tied to a contract subclass definition. It supports the role-tokenization constants (G_RLE_CODE_TOKEN 'JTOT_OBJECT_CODE', G_PARTY_ROLE_TOKEN 'ENTITY') used to map roles into JTF object queries.
• GET_CONTRACT_DEF_ROLES — Returns role definitions associated with a contract definition, complementing the subclass-level role retrieval for contract-based role resolution.
• GET_CONTACT — Resolves contact information, consistent with the OKC contact source data model, for use in JTF object query population.

The package also implicitly supports operating unit and vendor lookups through its internal cursors (okx_operunit_csr, okx_vendor_csr), though these are not among the documented procedures.

Tables Accessed

• OKC_SUBCLASS_ROLES — Source of subclass-level role definitions used by GET_SUBCLASS_DEF_ROLES.
• OKC_CONTACT_SOURCES — Provides contact source records consumed by GET_CONTACT.
• OKC_K_HEADERS_B — The contract header base table, used to validate and resolve contract identifiers (G_CONTRACT_ID_TOKEN 'CONTRACT_ID').
• JTF_OBJECTS_B — The JTF object registry base table, used to register/resolve JTF object definitions referenced by the query.
• DUAL — Used for single-row expressions and constant evaluations.

These tables are referenced through APPS synonyms, confirming the package executes with APPS schema privileges and reads primarily from OKC (Contracts Core) and JTF objects.

Usage Notes

OKL_JTOT_EXTRACT is an internal integration package rather than a user-facing API. It is typically invoked indirectly through the JTF object query framework when OKL lease and contract entities are exposed to search, lookup, or LOV components. The user search term "okl_lla_jtf_obj_query" corresponds to the package's error message constant OKL_LLA_JTF_OBJ_QUERY and the related OKL_LLA_JTF_OBJ_QUERY_FAIL message, indicating the package participates in the OKL LLA object query adapter path.

Because the package is referenced by six other packages, modifications should be treated with caution; it forms part of a shared dependency chain within OKL. Customizations should avoid altering the tokenized error message constants, since downstream JTF components and message resolution rely on them. In Oracle EBS 12.1.1 and 12.2.2, the package remains a backend utility invoked during contract and party lookups rather than a directly called concurrent program or form API.