Search Results oke_utils




Overview
Explore in AI Chat

Overview

OKE_UTILS is a shared utility package in the Oracle EBS Applications (APPS) schema that supports the Oracle Contracts (OKE/OKC) family of modules. Its classification in the ETRM repository is OTHER, reflecting that it is not a business-facing API in its own right but rather an internal helper library consumed by other contracts-related packages and forms. The package centralizes a heterogeneous set of reusable functions and procedures: session and user context resolution, lookup translation, contract change-request lookup, inventory item and location description retrieval, payment term retrieval, organization context management, and diagnostic/debug helpers. Because these capabilities recur across the Contracts modules, OKE_UTILS exists to prevent duplicated logic and to provide a single, consistent implementation of common queries against EBS foundation and contracts tables. The metadata records 24 documented procedures and functions, and the package is referenced by 26 other packages, confirming its role as a low-level dependency in the Contracts code stack.

Key Procedures and Functions

The documented program units fall into several functional groups.

  • CURR_EMP_ID / CURR_EMP_NAME — return the employee identifier and employee name derived from the currently logged-in user; CUR_EMP_NAME expects FND_GLOBAL.INITIALIZE to have run.
  • YES_NO / SYS_YES_NO — translate a lookup code into the corresponding Yes/No string using the YES_NO and SYS_YES_NO lookup types respectively.
  • CHG_REQUEST_NUM — returns the related change request number and change status for a given contract, either for the current version or for a specified major version.
  • ITEM_NUMBER / ITEM_DESCRIPTION — return the item number and description for a given inventory organization and item ID.
  • CHECK_UNIQUE — a validation helper used to determine uniqueness of a supplied value.
  • GET_LOCATION_DESCRIPTION — resolves a descriptive location string from the location identifiers supplied to it.
  • GET_TERM_VALUES / GET_TERM_VALUE — retrieve payment or contract term values, singly or as a set.
  • GET_USERENV_LANG — returns the language associated with the current user environment.
  • GET_K_CURR_FMT_MASK — the function matching the user's search term; it returns the currency format mask used by the Contracts modules for formatting monetary values in the current context.
  • SET_ORG_CONTEXT / ORG_ID / CROSS_ORG_ACCESS — manage and expose the multi-org context, including setting the current organization and determining whether cross-organization access is permitted.
  • ENABLE_DEBUG / DISABLE_DEBUG / DEBUG_MODE / DEBUG — diagnostic helpers controlling and emitting debug output during package execution.

Tables Accessed

The package reads and, where appropriate, writes through APPS synonyms. User and session data comes from FND_USER, FND_LANGUAGES, and PER_ALL_PEOPLE_F. Contract headers and terms are read from OKC_K_HEADERS_B, OKE_K_HEADERS, OKE_K_TERMS, and OKE_TERMS_B. Payment terms are sourced from AP_TERMS and RA_TERMS, with freight terms from ORG_FREIGHT. Location descriptions are resolved from HR_LOCATIONS_ALL and HZ_LOCATIONS. Inventory data is drawn from MTL_SYSTEM_ITEMS. Project-related context comes from PA_PROJECTS_ALL and PA_PROJECT_PARTIES. These accesses support the utility functions' purpose of returning descriptive, user-facing values rather than performing transactional updates.

Usage Notes

OKE_UTILS is typically invoked indirectly. Contracts forms, concurrent programs, and other Contracts packages call its functions to resolve user identity, translate lookups, format currency, obtain term and location descriptions, and manage organization context without reimplementing these queries. The GET_K_CURR_FMT_MASK function in particular is used where contract amounts must be displayed or validated according to the session's currency format. Custom code and extensions in the Contracts area may call these utilities directly, but callers should observe the stated prerequisites, notably the FND_GLOBAL.INITIALIZE requirement for CURR_EMP_NAME. Because 26 packages depend on it, changes to OKE_UTILS signatures carry broad impact and should be treated as high-risk.