Search Results rosetta_table_copy_out_p13




Overview

The OKL_CASH_RULES_SUMRY_PVT_W package is a private PL/SQL wrapper (indicated by the _PVT_W suffix) defined in the APPS schema of Oracle E-Business Suite. It belongs to the Oracle Leasing (OKL) module, the component of Oracle EBS that manages lease and financing contracts. The package is declared with AUTHID CURRENT_USER, meaning that its procedures execute with the privileges of the invoking user rather than the definer, a characteristic typical of wrapper layers used by Oracle Forms, OAF pages, or other clients that call server-side logic under the caller's credentials.

Its functional purpose is to expose summarized cash rule information to the middle-tier presentation layer. In the leasing architecture, "cash rules" govern how cash flows, payment schedules, and accounting events are derived for a lease or loan contract. The handle_cash_rl_sumry procedure is the substantive business entry point, while the two Rosetta procedures exist solely to marshal data between PL/SQL collection types and the tabular structures consumed by the Oracle Forms client.

Key Procedures and Functions

  • rosetta_table_copy_in_p13 — A generated marshalling routine that copies an incoming JTF_NUMBER_TABLE (the generic numeric table type used by the JTF/Forms integration layer) into the package's native okl_cash_rl_sumry_tbl_type collection. The _p13 suffix denotes a position/identifier distinguishing this generated shim from other similar copy routines within the OKL codebase. It is declared with an OUT NOCOPY parameter for the target collection, so no data is copied back to the caller.
  • rosetta_table_copy_out_p13 — The inverse operation. It reads a native okl_cash_rl_sumry_tbl_type instance and repopulates a JTF_NUMBER_TABLE, which is returned to the caller via an OUT NOCOPY parameter. This supports returning result sets from the server to a Forms block.
  • handle_cash_rl_sumry — The primary public API of the package. It accepts a standard EBS API signature, including p_api_version and p_init_msg_list, and returns the conventional error-handling outputs x_return_status, x_msg_count, and x_msg_data. It additionally receives the numeric table p5_a0, which carries the summary cash rule rows being processed. This procedure encapsulates the business logic for creating, updating, or validating cash rule summary records on behalf of the calling form.

Tables Accessed

The only documented table reference is the APPS synonym PLITBLM. Based on the naming convention used throughout Oracle Applications, PLITBLM is a PL/SQL table (index-by table) storage structure historically associated with the Forms-to-database handshake, used to stage tabular data passed between the client and server. Access to it is consistent with the Rosetta copy routines, which move data between the JTF numeric table and the package's local collection before handle_cash_rl_sumry performs its processing. The package does not appear to perform direct DML against the base leasing cash rule tables itself; that work is delegated to the underlying OKL_CASH_RULES_SUMRY_PVT package, whose types this wrapper references.

Usage Notes

This package is an internal wrapper and is not intended for direct invocation by end users or third-party integrations. It is referenced by one other package in the EBS metadata, indicating that it sits within a call chain rather than at the top of the stack. Typical invocation occurs when an Oracle Leasing form or OAF page needs to pass a block of cash rule summary data to the database tier: the middle layer populates a JTF_NUMBER_TABLE, calls rosetta_table_copy_in_p13 to convert it, then invokes handle_cash_rl_sumry to execute the business transaction. Because the naming and structure mirror the generated Rosetta shims found across EBS modules, the package should be treated as version-sensitive and internal; customizations should call the public private-API layer (OKL_CASH_RULES_SUMRY_PVT) instead of this wrapper wherever possible.