Search Results rosetta_table_copy_in_p24

Overview

OKL_FORMULAEVALUATE_PVT_W is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that provides the server-side evaluation engine for formulae used within Oracle Lease and Finance Management (OKL). It belongs to the family of "rosetta" style private packages that Oracle uses to bridge Java-based middle-tier form logic and PL/SQL business logic through strongly typed JTF collection tables. The package is classified under OTHER in the ETRM 12.2.2 metadata, signaling that it is an internal, non-public API (note the _PVT_W suffix, meaning private wrapper) and is not intended for direct customer invocation. Its principal business purpose is to resolve formula identifiers, retrieve parameter definitions and values for a given contract and line, and compute the resulting function value that drives lease pricing, calculations, and rule evaluation. In Oracle EBS 12.1.1 and 12.2.2, this package remains materially unchanged from the 12.0.x lineage evidenced by its $Header ($Header: OKLEEVAS.pls 120.1 2005/07/11 ...). The file is marked "noship," confirming it is an internal support object packaged with the OKL product family.

Key Procedures and Functions

The documented package exposes seven callable units:

• ROSETTA_TABLE_COPY_IN_P24 – Converts JTF collection tables into the CTXPARAMETER_TBL type used by the parameter evaluation layer. This is a marshalling helper for the parameter context.
• ROSETTA_TABLE_COPY_OUT_P24 – The inverse operation, returning CTXPARAMETER_TBL data back into JTF collection tables for consumption by the Java middle tier.
• ROSETTA_TABLE_COPY_IN_P26 – Marshals JTF collection tables into the FUNCTION_TBL type, which carries the function/parameter definitions supplied to the evaluation engine. This is the procedure the searcher encountered.
• ROSETTA_TABLE_COPY_OUT_P26 – The corresponding outbound marshalling routine for FUNCTION_TBL.
• EVA_GETPARAMETERIDS – Returns the identifiers of the parameters associated with a formula (identified by p_fma_id) as JTF collection tables.
• EVA_GETPARAMETERVALUES – Retrieves the actual parameter values for a formula on a given contract and line, returning results via outbound JTF tables and standard API return status/message variables.
• EVA_GETFUNCTIONVALUE – Evaluates the formula and returns the computed function value for the specified formula, contract, and line, again using the standard API status pattern.

All evaluation entry points follow the EBS API convention of p_api_version, p_init_msg_list, x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The ETRM metadata documents a single referenced table accessed through APPS synonyms: PLITBLM. PLITBLM is the standard Oracle Applications interface used by PL/SQL to write to and read from the FND log/temporary storage mechanism that underpins the JTF collection table transfer into Java. Its presence confirms that the "_W" (wrapper) procedures depend on the PL/SQL-to-Java interface layer for their rosetta marshalling. The formula, parameter, and function metadata needed by EVA_GETPARAMETERIDS, EVA_GETPARAMETERVALUES, and EVA_GETFUNCTIONVALUE are sourced from the OKL formula repository tables (such as OKL_FORMULA_LINES and related entities); the metadata excerpt does not enumerate them directly, but the package name and API signatures make the dependency explicit.

Usage Notes

Because OKL_FORMULAEVALUATE_PVT_W is a private wrapper (PVT_W), it is invoked almost exclusively from the Java-based OKL Forms/OCM middle tier rather than from customer PL/SQL. The rosetta_table_copy_in/out routines are called by generated Java wrappers to marshal JTF collection tables across the JDBC boundary; the EVA_ procedures are the business entry points that Forms and the OKL pricing engine call when evaluating lease formulae during contract authoring or repricing. It is referenced by one other package, which typically is the public OKL_FORMULAEVALUATE API or an OKL pricing caller. In both 12.1.1 and 12.2.2, custom developers should treat this object as internal and call the corresponding public OKL APIs instead; direct calls risk bypassing validation and error handling. Diagnostic tracing can be enabled through FND logging because the package writes to PLITBLM.