Search Results okc_xprt_xrule_values_pvt_w




Overview
Explore in AI Chat

Overview

OKC_XPRT_XRULE_VALUES_PVT_W is an Oracle Applications (APPS) PL/SQL package body within the Oracle Contracts (OKC) module, part of the iReceivables/Contracts Intelligence family. It belongs to the Expression Processor (XPRT) subsystem, which evaluates the rule values and expressions that drive contract terms, pricing, and conditions in Oracle EBS 12.1.1 and 12.2.2. The package acts as the private implementation layer for the OKC_XPRT_XRULE_VALUES_PVT specification, providing the runtime mechanics that resolve rule variable values during contract authoring, validation, and document generation.

The "_W" suffix conventionally denotes a wrapper package generated to support Oracle Forms integration (typically for Rosetta-style table transfer between a form block and the database). This is confirmed by the presence of numerous ROSETTA_TABLE_COPY_IN and ROSETTA_TABLE_COPY_OUT procedures, which shuttle data between PL/SQL tables and database structures.

Key Procedures and Functions

The package exposes 19 documented procedures spanning two functional groups:

  • ROSETTA_TABLE_COPY_IN_P4 through P11 and ROSETTA_TABLE_COPY_OUT_P4 through P11 — These paired procedures handle inbound and outbound bulk transfer of data between Oracle Forms block level PL/SQL tables and the underlying rule-value structures. Each numbered variant (P4, P5, P6, P7, P9, P10, P11) corresponds to a distinct form block or record group configuration, allowing the same generic transfer logic to service multiple UI contexts.
  • GET_SYSTEM_VARIABLES — Retrieves system-defined variables available for rule evaluation.
  • GET_CONSTANT_VALUES — Returns constant values referenced by contract rules.
  • GET_LINE_SYSTEM_VARIABLES — Fetches system variables scoped specifically to a contract line.
  • GET_USER_DEFINED_VARIABLES — Resolves user-defined variables supplied through contract setup or extended attributes.
  • GET_DOCUMENT_VALUES — Extracts document-level values used to resolve rule expressions for a given contract document.

The GET_* functions collectively populate the value dictionary that the XPRT expression engine consumes when evaluating contract rule expressions. The ROSETTA procedures marshal those results into Forms-bound tables.

Tables Accessed

The only documented base table referenced is PLITBLM, a standard Oracle tool table used for storing PL/SQL index-by tables, consistent with the Rosetta table transfer mechanism. Notably, no OKC transactional tables are listed as direct dependencies, which indicates that this package operates purely on in-memory PL/SQL table structures passed in by the calling form or the sibling package OKC_XPRT_XRULE_VALUES_PVT. Data retrieval against contract entities is delegated to OKC_XPRT_XRULE_VALUES_PVT, while this wrapper focuses on shaping and transferring results. The package further relies on the FND_API framework for standard API return status handling and on the JTF_VARCHAR2_TABLE_100/200/300/2500 and JTF_NUMBER_TABLE collection types for parameter passing.

Usage Notes

OKC_XPRT_XRULE_VALUES_PVT_W is not referenced by any other database object, confirming it is an entry point invoked directly by Oracle Forms (OKC contract authoring, terms, and rule-value maintenance screens) rather than called internally by other server-side code. Typical invocation scenarios include:

  • Contract rule definition forms that need to display available system, constant, user-defined, and document variables to the user.
  • Rule-value maintenance windows where Rosetta copy procedures synchronize a form block with the PL/SQL table representation of rule values.
  • Document generation flows where GET_DOCUMENT_VALUES supplies the value context for expression evaluation.

Because the package is classified as a private wrapper (OTHER API classification), custom code should not call it directly; developers requiring rule value resolution should invoke the sibling OKC_XPRT_XRULE_VALUES_PVT specification, which offers a supported interface. The package is valid in both 12.1.1 and 12.2.2 and requires the OKC, JTF, and FND schemas to be present. Any modification risks breaking the Forms integration layer across roughly eight distinct form block contexts.