Search Results rosetta_table_copy_out_p25




Overview
Explore in AI Chat

Overview

OKL_EXECUTE_FORMULA_PVT_W is a PL/SQL wrapper package in the Oracle E-Business Suite (EBS) Oracle Lease and Finance Management (OKL) module. It is declared with AUTHID CURRENT_USER and exposes a public interface for evaluating lease and finance formulas at runtime. The trailing _W suffix indicates that the package acts as a Rosetta-generated wrapper around the private implementation package OKL_EXECUTE_FORMULA_PVT. The Rosetta layer translates between the weakly typed JTF collection types used by EBS Forms and concurrent interfaces and the strongly typed operand and context value tables defined inside the private package. In EBS 12.1.1 and 12.2.2, this pattern is applied wherever a PL/SQL API must accept or return nested table parameters across the Java/OAF-to-PL/SQL boundary, enabling the formula engine to be invoked from multiple presentation layers without redefining the underlying business logic.

The package does not itself contain the formula parsing or calculation engine; rather, it exposes entry points that delegate to the private implementation. Its primary business purpose is to execute a named formula against a specific lease contract and contract line, returning the evaluated numeric result.

Key Procedures and Functions

The documented interface contains six procedures, all public, organized into three functional groups.

  • ROSETTA_TABLE_COPY_IN_P23 — Transfers operand values from the JTF table types into the private package's operand_val_tbl_type. This is an inbound translation routine used to marshal formula operands before execution.
  • ROSETTA_TABLE_COPY_OUT_P23 — Performs the reverse translation, moving operand_val_tbl_type contents back out into JTF number and varchar2 collections. Used to return operand results to the calling layer.
  • ROSETTA_TABLE_COPY_IN_P25 — Translates context values into the private package's ctxt_val_tbl_type. Context values supply the naming or environment variables required for formula resolution.
  • ROSETTA_TABLE_COPY_OUT_P25 — The outbound counterpart for context values, populating JTF varchar2 collections from ctxt_val_tbl_type.
  • EXECUTE — The principal business procedure, documented with two overloaded signatures. Each accepts a formula name, contract identifier, and line identifier, together with context value arrays (p8_a0, p8_a1), and returns x_value, the computed numeric result. Both overloads also carry the standard EBS API parameters p_api_version, p_init_msg_list, and the out parameters x_return_status, x_msg_count, and x_msg_data. The second overload additionally returns operand value arrays (p9_a0, p9_a1, p9_a2), allowing callers to retrieve intermediate operands alongside the final result.

Tables Accessed

The ETRM metadata documents a single referenced table accessed via an APPS synonym: PLITBLM. This is the EBS "PL/SQL Interface Table Blob/Message" table used to stage and pass large argument payloads (notably collection data) between client and server components. In the context of this package, PLITBLM supports the transport of the JTF table arguments and formula operands across the Forms-to-database boundary. No other base tables are recorded as directly referenced by the wrapper; the underlying formula definitions, contract, and line data are reached through the private implementation package rather than through direct DML in this unit.

Usage Notes

The package is classified under API classification OTHER in the ETRM 12.2.2 repository and is referenced by one other package, confirming that it is called programmatically rather than executed standalone. Typical invocation occurs when an Oracle Forms screen or OAF page in the Lease Management flow requests a formula evaluation — for example, when pricing, valuation, or payment calculations must be performed for a contract or line. The calling form populates JTF collections, which the Rosetta copy-in procedures convert to the private package's nested table types; EXECUTE is then invoked; and the copy-out procedures (or the overload's p9 arrays) return results.

Because the wrapper requires AUTHID CURRENT_USER privileges and depends on JTF collection types, custom code should invoke it through the same APPS connection model used by standard EBS components. Direct calls that bypass the copy-in/copy-out preparation of operand and context tables will not produce valid results. The x_return_status parameter should always be checked before consuming x_value, as formula resolution failures are reported through the standard EBS message stack.