Search Results jtf_varchar2_table_100

Overview

OKL_RULE_EXTRACT_PVT_W is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Lease and Finance Management (OKL) module — historically branded as Oracle Contracts/ETRM (Enterprise Transaction and Rule Management) — and is classified under the generic API category "OTHER." Its name and structure indicate that it serves as a private wrapper package for extracting rule metadata used during contract and rule processing.

The package's defining characteristic is its reliance on Rosetta-generated bulk table-copy procedures. Each ROSETTA_TABLE_COPY_IN_* and ROSETTA_TABLE_COPY_OUT_* pair bridges a strongly typed PL/SQL record collection (defined in the companion package specification OKL_RULE_EXTRACT_PVT) with the generic Oracle JTF scalar collection types. The prominent JTF_VARCHAR2_TABLE_100 and JTF_VARCHAR2_TABLE_300 parameters referenced by user searches confirm this package as one of the standard exchange points between OKL rule structures and the JTF table types.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P22 / _OUT_P22 — Copy data into and out of the rule_tbl_type collection, marshalling rule records to and from JTF_VARCHAR2_TABLE_100 arrays.
• ROSETTA_TABLE_COPY_IN_P24 / _OUT_P24 — Same marshalling pattern for the sc_rg_tbl_type collection (subclass/rule group association), using JTF_VARCHAR2_TABLE_100 and JTF_VARCHAR2_TABLE_300 arrays.
• ROSETTA_TABLE_COPY_IN_P26 / _OUT_P26 — Marshal the rg_rules_tbl_type collection, which maps rule groups to their member rules, across seven JTF_VARCHAR2_TABLE_100 parameters.
• ROSETTA_TABLE_COPY_IN_P28 / _OUT_P28 — Marshal the rule_segment_tbl_type collection, which holds rule condition segments, using JTF varchar tables.
• ROSETTA_TABLE_COPY_IN_P30 / _OUT_P30 — Additional copy pair generated for another rule-related record structure in the private package specification.
• GET_SUBCLASS_RGS — Retrieves rule groups associated with a given subclass, supporting rule selection logic.
• GET_RG_RULES — Returns the rules belonging to a specified rule group.
• GET_RULE_DEF — Fetches the definition of an individual rule.
• GET_RULES_METADATA — Returns the metadata describing available rules, enabling dynamic rule evaluation.

Tables Accessed

The only documented table reference is PLITBLM, an APPS synonym that is a standard JTF/PL/SQL index-by table storage utility. No OKL base tables (such as OKL_RULES or OKL_RULE_GROUPS) appear in the documented table list, which suggests that the four GET_* functions read metadata indirectly through the underlying OKL_RULE_EXTRACT_PVT package rather than querying base tables directly from this wrapper. PLITBLM is used to support array processing within the copy and retrieval routines.

Usage Notes

This is a private package, not a published public API; Oracle does not support direct customer invocation. It is referenced by only one other package, which is the expected caller. Typical invocation occurs through the OKL rules engine when rule definitions and rule group metadata must be extracted — for example during contract authoring, rule evaluation on a lease, or when a depending API passes rule data across package boundaries.

Because it uses AUTHID CURRENT_USER, it executes with the privileges of the calling schema, so callers must have appropriate execute grants. The presence of JTF_VARCHAR2_TABLE_100 parameters means callers must construct JTF collections and pass them positionally; the generated copy-in and copy-out routines handle only data transport, not validation. Customizations should target public OKL APIs and never this wrapper, since its signature is derived from Rosetta-generated code and may change between patch levels or releases.