Search Results get_contract_def_roles

Overview

OKL_JTOT_EXTRACT_W is an APPS-owned PL/SQL package belonging to the Oracle E-Business Suite Contracts (OKL / ETRM) module. Its header identifies it as a wrapper package, indicated by the "_W" suffix, and the underlying extraction package OKL_JTOT_EXTRACT supplies the record types used throughout. The package exists to bridge Oracle Contracts data structures and the JTF (Java Technology Foundation / CRM Foundation) table-valued parameter conventions, exposing contract party and role information through a standardized, versioned API surface.

Functionally, the package addresses the need for external callers — particularly integration layers such as JTOT (Oracle's contract extraction or Teradata-oriented extraction routines) — to obtain the set of parties and roles defined against an Oracle Contracts contract, subclass, or contract template. Because JTF interfaces exchange data as PL/SQL associative arrays of VARCHAR2 rather than as rich object types, OKL_JTOT_EXTRACT_W performs the necessary conversion between the strongly typed OKL_JTOT_EXTRACT records and JTF_VARCHAR2_TABLE collections.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P4 — Converts inbound JTF_VARCHAR2_TABLE_100/200/300 arrays into the OKL_JTOT_EXTRACT party table type (party_tab_type). Six array parameters are mapped into the party structure, supporting bulk transfer of party attributes.
• ROSETTA_TABLE_COPY_OUT_P4 — The inverse operation: unpacks the party_tab_type into six OUT arrays so callers receive party data in JTF-compatible form.
• ROSETTA_TABLE_COPY_IN_P6 — Converts two JTF_VARCHAR2_TABLE_100 arrays into the OKL_JTOT_EXTRACT role code table type (rle_code_tbl_type).
• ROSETTA_TABLE_COPY_OUT_P6 — Unpacks the role code table type back into two OUT arrays.
• GET_PARTY — Retrieves party information for a specified contract (p_chr_id), contract line (p_cle_id), role code (p_role_code), and intent, returning the result as six JTF_VARCHAR2_TABLE OUT parameters along with the standard API return status, message count, and message data outputs.
• GET_SUBCLASS_DEF_ROLES — Returns the default roles defined at the contract subclass level (p_scs_code), producing two JTF_VARCHAR2_TABLE OUT arrays.
• GET_CONTRACT_DEF_ROLES — Returns the default roles defined for a contract or contract template, again delivering results through two JTF_VARCHAR2_TABLE OUT parameters. This is the procedure referenced by the search term "get_contract_def_roles".

Tables Accessed

The documented table reference is PLITBLM, an APPS synonym. PLITBLM is the standard Oracle Contracts role and party relationship table (OKL_ROLE_PARTY or its migrated equivalent), used to store the assignment of parties to roles at the contract header, line, and subclass levels. GET_CONTRACT_DEF_ROLES and GET_SUBCLASS_DEF_ROLES query this table to identify default role codes, while GET_PARTY reads it to resolve the parties bound to a given role instance. The Rosetta copy procedures do not access tables directly; they operate purely on the in-memory OKL_JTOT_EXTRACT record types.

Usage Notes

OKL_JTOT_EXTRACT_W is an integration-facing wrapper rather than an end-user API. It is typically invoked by the JTOT extraction layer, by concurrent programs that populate contract data marts, and by custom PL/SQL that must hand contract party and role information to JTF-based interfaces. Callers should initialize the message list via the FND_MSG_PUB or standard API conventions, pass the appropriate API version, and inspect x_return_status before consuming the returned JTF tables. Because the package is owned by APPS and is not referenced by any other documented package, it should be treated as a leaf integration point: customizations should wrap it rather than modify it, and all calls should be schema-qualified as APPS.OKL_JTOT_EXTRACT_W.