Search Results get_subclass_def_roles




Overview
Explore in AI Chat

Overview

OKL_JTOT_EXTRACT is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and shipped as part of the Oracle Lease and Finance Management (OKL) application family in ETRM releases 12.1.1 and 12.2.2. The package is classified under the "OTHER" API category, meaning it is not a formal public API surface such as an OKL_API-style interface package, but rather a supporting extraction and query utility within the OKL/JTOT integration layer. Its declared AUTHID CURRENT_USER clause indicates that it executes with the privileges of the invoking user rather than the definer, so callers must possess the necessary object privileges on the underlying OKC and JTF tables for the routines to succeed. The package header source originates from an early file revision (OKLRJEXS.pls 115.7, dated 2003), confirming it is a long-standing component of the lease contracting data model.

The central purpose of the package is to extract and return related party, contact, and role-definition information associated with lease and contract objects. It packages result sets into PL/SQL associative array types defined in the package specification, making it convenient for callers that need to iterate over multiple party or role rows without issuing repeated queries.

Key Procedures and Functions

The package exposes five documented routines. Two of them, GET_PARTY, are overloaded within the specification.

  • GET_PARTY (contract/line variant) — Fetches all parties attached to a contract or contract line and returns them in a party table structure. The output structure carries role code, party identifier components (ID1 and ID2), name, description, and object code.
  • GET_PARTY (identifier variant) — Fetches the name and description of a party role for a given object identifier pair, returning a single-row lookup rather than a collection.
  • GET_SUBCLASS_DEF_ROLES — Returns the role codes defined against subclasses. This is the routine most directly implicated by the search phrase "get_subclass_def_roles". It supports callers that must enumerate which roles are valid for a given contract subclass, populating the rle_code record type (subclass code plus role code).
  • GET_CONTRACT_DEF_ROLES — Returns role definitions at the contract level, complementing the subclass-level routine.
  • GET_CONTACT — Retrieves contact information linked to contract parties, sourcing the OKC_CONTACT_SOURCES table.

Because the documented metadata does not enumerate parameter signatures, individual argument lists should be confirmed against the deployed package header using ALL_ARGUMENTS or USER_SOURCE before use.

Tables Accessed

The package reads from a focused set of APPS-synonymed tables, consistent with its extraction role:

  • OKC_SUBCLASS_ROLES — authoritative source of subclass-to-role mappings, consumed by GET_SUBCLASS_DEF_ROLES.
  • OKC_K_HEADERS_B — contract header base table, providing the contract (CHR_ID) context for party and contact lookups.
  • JTF_OBJECTS_B — supplies object metadata and codes used to qualify parties and roles in the returned records.
  • OKC_CONTACT_SOURCES — defines contact source associations, consumed by GET_CONTACT.
  • DUAL — used for singleton select constructs and default value materialisation.

Usage Notes

OKL_JTOT_EXTRACT is typically invoked from custom PL/SQL, concurrent program wrappers, or form-level integration code that needs to resolve the parties, contacts, and role definitions attached to a lease or contract. The package is referenced by six other packages in the environment, so changes to its specification carry downstream risk and should be versioned carefully. Callers should observe the standard OKL API conventions visible in the specification, including the check of p_init_msg_list, and should read x_return_status, x_msg_count, and x_msg_data to detect errors. No formal API versioning guarantees apply given the OTHER classification; code that depends on the overloaded GET_PARTY routines or the collection types should be regression tested against target EBS patch levels before deployment.