Search Results rosetta_table_copy_out_p14

Overview

OKL_CURE_RECON_PVT_W is a public wrapper package within the Oracle Lease Management (OKL) module of Oracle E-Business Suite. It belongs to the Cure Reconciliation process, which governs the handling of delinquent lease and loan contracts that have entered the "cure" period — the contractual window during which a lessee may remedy a default by paying past-due amounts. The package serves as the externally callable interface, or wrapper, layered over the private package OKL_CURE_RECON_PVT. Its principal business purpose is to expose the logic that updates cure invoices with corrected or reconciled amount data, primarily for use by Oracle Forms-based user interfaces and, in some deployments, by concurrent programs or custom integrations.

The "_W" suffix denotes a wrapper package generated or maintained for the EBS Forms interoperability layer. The header comment indicates a source version dated 2003, reflecting the maturity of this object within the OKL codebase; it remains present and callable in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package declares three documented procedures, all public:

• ROSETTA_TABLE_COPY_IN_P14 — A generated data-marshalling routine that copies tabular data from generic JTF collection types into the package's strongly typed PL/SQL record table, specifically the cure_amount_tbl structure defined in the private package. It supports inbound transfer of numeric and varchar2 columns, allowing Oracle Forms or other callers to pass multi-row amount data into PL/SQL.
• ROSETTA_TABLE_COPY_OUT_P14 — The inverse routine. It copies data from the internal cure_amount_tbl back into JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_100 collection types for consumption by the calling client layer.
• UPDATE_CURE_INVOICE — The core business procedure. It updates cure invoice records based on supplied amount collections and an operation indicator. It follows the standard EBS API convention, accepting API version, initialization message list, commit flag, report identifier, invoice date, the p5-prefixed amount collections, and an operation parameter. It returns standard EBS status outputs: x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The documented metadata identifies a single referenced table via APPS synonym: PLITBLM. In Oracle EBS, PLITBLM is the standard temporary (global temporary table) used by the FND_MSG_PUB messaging infrastructure to stage and retrieve error and information messages generated during API execution. The package references it indirectly to support the standard message-handling contract — that is, to populate and return meaningful message text through x_msg_data when x_return_status indicates failure. The actual cure invoice and cure amount data manipulated by UPDATE_CURE_INVOICE resides in the underlying OKL transaction and invoice tables accessed through the private package OKL_CURE_RECON_PVT, not directly in this wrapper.

Usage Notes

This wrapper is invoked primarily from the Oracle Forms front end of the Lease Management Cure Reconciliation screens. When a user submits a set of reconciled cure amounts, the form invokes ROSETTA_TABLE_COPY_IN_P14 to marshal the multi-row block data into the PL/SQL table, then calls UPDATE_CURE_INVOICE to apply the reconciliation, and finally expects status and message data to be reflected back through the standard API output parameters. The adoption of JTF collection types and Rosetta-style copy routines is characteristic of EBS Forms-PLSQL integration, where tabular form blocks must be passed as arrays.

Custom code and concurrent program developers may call UPDATE_CURE_INVOICE directly, but must honor the standard EBS API invocation sequence: initialize the message list when requested, inspect x_return_status for 'S', 'E', or 'U', and iterate x_msg_count to retrieve all messages. Because the package is declared AUTHID CURRENT_USER, privileges are evaluated against the calling schema, so grants to the invoking user or role are required. The package is not referenced by other documented packages, confirming its role as a terminal entry point rather than an internal dependency.