Search Results get_term_value

Overview

OKE_DELIVERABLE_UTILS is a public PL/SQL utility package owned by the APPS schema and declared with AUTHID CURRENT_USER. Within the Oracle E-Business Suite, it belongs to the family of packages supporting Oracle Contract Terms and Deliverables (ETRM / OKE), the module responsible for tracking contractual deliverables, their statuses, actions, and the associated terms and party roles negotiated against an agreement. The package provides read-oriented helper routines that resolve commonly needed attributes of a deliverable — the value of a contract term, the identifier of a party playing a given role, and a knowledge reference — without requiring calling code to embed the underlying joins against the OKC and OKE base tables. Its header, carrying the revision marker $Header: OKEDUTLS.pls 115.4 ... $, indicates a compact, stable interface of three functions that has remained essentially unchanged across the 11i through 12.x code lines, and the same source is shipped in both 12.1.1 and 12.2.2. Because the API is classified as OTHER rather than a formal public API, it is intended primarily for internal consumption by OKE and OKC forms, concurrent programs, and tightly coupled custom extensions that already have a deliverable identifier in hand.

Key Procedures and Functions

• GET_TERM_VALUE — Returns the value of a specified contract term for a given deliverable. The caller supplies the deliverable identifier together with a term code, and the function returns the resolved term value as a character string. This is the routine most frequently referenced when developers search for get_term_value, since it abstracts the lookup of a negotiated term value associated with a deliverable.
• GET_PARTY — Returns the party identifier for a given deliverable and role code. It accepts a deliverable identifier and a role code and returns the corresponding party as a number, allowing callers to determine, for example, which party occupies a particular contractual role on the deliverable.
• GET_K_REFERENCE — Returns a knowledge (K) reference for the deliverable. It accepts the deliverable identifier and a source code, the latter defaulting to 'OKE', and returns the reference as a character string. The default parameter makes the function convenient for OKE-originated calls while allowing other source systems to be addressed explicitly.

The package declares no documented procedures beyond these three functions, and no parameter lists should be assumed beyond those shown in the source header.

Tables Accessed

The package resolves its data from both the OKE deliverables tables and the core OKC contract knowledge tables, accessed through APPS synonyms. On the OKE side, OKE_DELIVERABLES_B and OKE_K_DELIVERABLES_B hold the deliverable definition and its knowledge-side counterpart; OKE_DELIVERABLE_ACTIONS records actions recorded against deliverables; and OKE_K_TERMS stores the term values that GET_TERM_VALUE resolves. On the OKC side, OKC_K_HEADERS_ALL_B, OKC_K_LINES_B, and OKC_K_PARTY_ROLES_B supply the contract header, line, and party-role context used by GET_PARTY and GET_K_REFERENCE, while OKC_ANCESTRYS provides the hierarchical ancestry relationships used to trace a deliverable's position within the contract structure. The package is predominantly a read utility: it queries these tables to return values rather than performing inserts or updates, and callers should expect no side effects on the underlying deliverable or contract data.

Usage Notes

OKE_DELIVERABLE_UTILS is typically invoked from within OKE and OKC Forms, from concurrent programs that need to enrich deliverable or term data during processing, and from custom PL/SQL that must display or evaluate a deliverable's term value, party, or knowledge reference. Because the functions are scalar lookups keyed on a deliverable identifier, they are well suited to per-row calls in a query or loop, though in set-based processing the equivalent joins may perform better. The package is referenced by one other documented package, confirming its role as a shared internal utility rather than an entry point. Developers extending or debugging OKE behaviour should treat it as a stable but non-public interface: the AUTHID CURRENT_USER declaration means privilege resolution follows the invoking user, and because the API classification is OTHER, Oracle does not guarantee backward compatibility of the signature in the way it does for formally published APIs. As with all ETRM customizations in 12.1.1 and 12.2.2, callers should be validated in a test instance before deployment.