Search Results party_role_rec

Overview

OKL_JTOT_CONTACT_EXTRACT_PVT is a private (PVT) PL/SQL package body in the Oracle EBS Contracts (OKL / OKC) module, delivered under the APPS schema. It belongs to the JTOT (Joint Task / Joint Operating Agreement) contact extraction framework within Oracle Lease and Finance Management, providing the runtime implementation of the specification OKL_JTOT_CONTACT_EXTRACT_PVT. Its primary business function is to resolve and return the SQL strings and cursor logic used by the JTOT extract process to identify party roles, contacts, subclass-defined roles, and contract-defined roles for a given lease or contract. The package therefore acts as a supporting engine for the contact data extraction that feeds downstream JTOT processing, rather than as a public API. The source header identifies revision 120.7 dated 09-Aug-2007, indicating this is a mature, stable component carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes five documented program units:

• GET_PARTY — Returns the SQL string used to drive a list of values (LOV) for a party role. The body ships several reference cursors that support this LOV: OKX_SALEPERS_CSR (object code OKX_SALEPERS, over OKX_SALESREPS_V), OKX_PCONTACT_CSR (OKX_PCONTACT, over OKX_PARTY_CONTACTS_V), OKX_PARTY_CSR (OKX_PARTY, over OKX_PARTIES_V), and OKX_OPERUNIT_CSR (OKX_OPERUNIT, over OKX_ORGANIZATION_DEFS_V, restricted to OPERATING_UNIT / Operating Unit Information). Each cursor filters by name and the ID1/ID2 keys and orders by name; the salesperson and operating unit cursors additionally honour the current operating unit via mo_global.get_current_org_id.
• GET_SUBCLASS_DEF_ROLES — Retrieves the roles defined at the contract subclass level, used to determine which party roles are applicable to a subclass during extraction.
• GET_CONTRACT_DEF_ROLES — Retrieves the roles defined directly at the contract level, complementing the subclass role set.
• GET_CONTACT — Resolves the contact information associated with the identified party or role, returning the data required for the JTOT contact extract output.

Tables Accessed

The documented tables accessed through APPS synonyms are:

• OKC_SUBCLASS_ROLES — Source of subclass-level role definitions consumed by GET_SUBCLASS_DEF_ROLES.
• JTF_OBJECTS_B — Object-code metadata used to map JTOT / OKX object codes to their underlying entities.
• OKC_CONTACT_SOURCES — Defines the valid contact sources used when resolving contacts in GET_CONTACT.
• DUAL — Utility selection used for scalar lookups and default handling.

In addition, the cursor definitions query the OKX views OKX_SALESREPS_V and OKX_ORGANIZATION_DEFS_V (with organziation-specific predicates) and the public synonyms for OKX_PARTY_CONTACTS_V and OKX_PARTIES_V, which are used to build the party role LOV.

Usage Notes

As a private package, OKL_JTOT_CONTACT_EXTRACT_PVT is not intended for direct customer invocation. It is referenced by one other package and is driven by the OKL JTOT extract flow. Typical invocation occurs when a JTOT extract is run for a contract or set of contracts, where the calling package supplies the name and ID1/ID2 filter criteria and receives the assembled SQL string or role/contact data. Because the LOV cursors bind mo_global.get_current_org_id, correct multi-org initialization is required; results are properly secured to the current operating unit where applicable. In 12.1.1 and 12.2.2 the package follows standard APPS calling conventions, and any extension or troubleshooting should target the documented procedures (GET_PARTY, GET_SUBCLASS_DEF_ROLES, GET_CONTRACT_DEF_ROLES, GET_CONTACT) rather than the underlying private cursors, which are internal implementation details subject to change.