Search Results oke_k_organizer_pkg




Overview
Explore in AI Chat

Overview

OKE_K_ORGANIZER_PKG is an APPS-owned PL/SQL package within the Oracle E-Business Suite Contracts (OKE/OKC) module. It supports the Contract Organizer, the tree-based navigation interface used to browse, expand, and filter contract documents by customer, contractor, and related classification criteria. The package is declared with AUTHID CURRENT_USER, meaning its unqualified object references resolve against the privileges of the invoking schema rather than the package owner, a standard pattern for shared APPS utility code.

The package encapsulates three distinct responsibilities: populating query-tree nodes for the Organizer UI, maintaining a per-user FIFO log of recently accessed contract documents, and resolving party names associated with a contract document. A package-level variable, RECORD_COUNT, is initialized from the profile option OKE_K_FIFO_LOG, which governs how many log entries are retained per user. This profile-driven design allows administrators to tune Organizer history behavior without code changes.

Key Procedures and Functions

  • POPULATE_QUERY_NODE — Returns tree node data for the Contract Organizer based on a caller-supplied WHERE clause. It accepts inputs describing the node's user value, icon, owning tree object, node state, and numeric low/high range, and returns a table of node records in the fnd_apptree.node_tbl_type structure together with a return status. This procedure is the core engine that builds the hierarchical result set displayed in the Organizer tree.
  • FIFO_LOG — Updates the contract documents log for a given user. It records the user identifier, the contract document (header) identifier, and the tree object name so that the Organizer can present a most-recently-used list of contracts. The FIFO retention limit is derived from the OKE_K_FIFO_LOG profile option captured in RECORD_COUNT.
  • GET_PARTY_NAME — Resolves and returns the customer or contractor name for a contract document. The caller supplies a party role and the contract header identifier, and the procedure returns the corresponding party name as an OUT parameter. This is the procedure most commonly referenced when users search for get_party_name, typically to display a human-readable party name on a form, report, or custom extension rather than displaying only an internal ID.

Tables Accessed

  • OKC_K_PARTY_ROLES_B — The base table of contract party roles. It supplies the role-to-party relationship used by GET_PARTY_NAME to identify which party occupies the requested role on the specified contract.
  • OKE_K_FIFO_LOGS and OKE_K_FIFO_LOGS_S — The FIFO log table and its sequence, written by FIFO_LOG to persist per-user contract access history.
  • JTF_OBJECTS_B — The CRM/JTT object registry, used to validate or resolve the tree object name passed into FIFO_LOG and POPULATE_QUERY_NODE.
  • DBMS_SQL and DUAL — Dynamic SQL is employed by POPULATE_QUERY_NODE to execute the caller-supplied WHERE clause, with DUAL used for simple scalar evaluations.

Usage Notes

The package is normally invoked indirectly through the Contract Organizer user interface, where form-level and Java/HTML tree components call POPULATE_QUERY_NODE to render nodes and FIFO_LOG to update access history. GET_PARTY_NAME is widely used from custom code and extensions whenever a contract party name must be displayed; because it is an OUT-parameter procedure rather than a function, it must be called from a PL/SQL block or another packaged routine. The ETRM metadata records no packages that reference OKC_K_ORGANIZER_PKG, so it is a top-level entry point rather than a shared dependency. Direct modification is not supported; the package is delivered as Oracle proprietary and confidential code.