Search Results get_k_role_party

Overview

OKC_QUERY is a PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Contract Management (OKC) module. It is classified under the generic API classification OTHER and is documented as VALID in ETRM for both release 12.1.1 and 12.2.2. The package functions as a query and retrieval utility layer that consolidates frequently reused lookup operations against contract structures, parties, classes, conditions, and version data. Rather than performing transaction-level DML against the core contract tables, OKC_QUERY exposes helper routines that surface derived display values, hierarchical relationships between contract lines, and descriptive attributes for downstream presentation. Its dependencies confirm this supporting role: the package references OKC_API as a public contract API and STANDARD for standard PL/SQL runtime services. In turn it is consumed by OKC_DBTREE_PVT, OKC_QUERY itself, OKC_RULE_PUB, OKC_TASK_PVT, and a number of contract Launchpad views including OKC_LAUNCH_LGRID_V, OKC_LAUNCH_TASKGRID_V, and OKX_LAUNCHPAD_INBOX_V. Because the object is referenced by six other packages, it behaves as a stable internal service rather than an end-user entry point.

Key Procedures and Functions

The package exposes twenty-three documented procedures and functions. The naming convention reveals three broad groupings.

• Party and amount retrieval: GETCONTRACTPARTYNAME, GETLINEPARTYNAME, GET_K_ROLE_PARTY, and GET_CONTACT return display names or identifiers associated with contract headers, lines, and role assignments. GETCONTRACTDISPLAYAMOUNT surfaces a formatted monetary value for a contract.
• Hierarchy and structure navigation: GETCHILDCOUNT, GETKID, GETKNUMBER, GETKMODIFIER, GETPARENTLINENUMBER, GETGROUPNAME, and SETSUBLINEINDENT furnish tree-walking primitives used to render contract line hierarchies, including the indentation applied to sublines in grid controls.
• Identifier and metadata lookup: GETCONTRACTVERSION, GET_NUMBER, GET_CONTRACT_NUMBER, GET_SOURCE_DOC_NUMBER, GETAUTHORFORMNAME, GETFORMFUNCTIONNAME, GETEBIZLINKNAME, and GETCLASSFUNCTIONNAME resolve version numbers, contract numbers, source document references, and the form or function names associated with authoring and class-driven navigation.

Parameter lists are not reproduced here; consumers should consult the package specification in the target instance before coding against these routines.

Tables Accessed

All table references are resolved through APPS synonyms. Header, party, and structural data are drawn from OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_VERS_NUMBERS, and OKC_K_GRPINGS. Classification and rule context come from OKC_CLASSES_B, OKC_SUBCLASSES_B, OKC_CLASS_OPERATIONS, OKC_CONDITION_HEADERS_B, and OKC_CONDITION_OCCURS. Action and attribute configuration is read from OKC_ACTION_ATTRIBUTES_B and OKC_ACTION_ATT_VALS, while OKC_TIMEVALUES supports time-based condition evaluation. Two non-OKC tables are also queried: FND_FORM_FUNCTIONS, to resolve form and function display names, and JTF_OBJECTS_B, to resolve object metadata. Reads dominate; the package is oriented toward lookup rather than maintenance.

Usage Notes

OKC_QUERY is normally invoked indirectly. Contract Launchpad views (OKC_LAUNCH_LGRID_V, OKC_LAUNCH_TASKGRID_V, OKX_LAUNCHPAD_INBOX_V) call it to render line and task grids, and OKC_DBTREE_PVT and OKC_TASK_PVT use it when constructing hierarchical displays and task lists. OKC_RULE_PUB references it during rule evaluation for descriptive attribute retrieval. Because the documented callers are packages and views rather than forms, direct form-level invocation is not the expected pattern. Custom code should treat OKC_QUERY as an internal utility: it is safe to call from extensions where the same display semantics are required, but it should not be treated as a released public API, and its behavior must be revalidated after patching. Diagnostic queries against the data dictionary, such as those locating dependent objects, should reference the APPS owner explicitly.