Results for “rosetta_table_copy_out_p40”

36 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_AEL_PVT_W is the public wrapper package for the private PL/SQL package OKL_AEL_PVT, which belongs to the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite Applications (APPS). Its principal business function is to bridge the strongly typed PL/SQL record structure okl_ael_pvt.ael_tbl_type with the generic JTF collection types (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_800, JTF_DATE_TABLE) that the Oracle Application Framework (OAF)/EBS technology stack uses for bulk transport of tabular data. This "Rosetta Stone" pattern is common in EBS internal APIs: the private package works with compiled record types for performance and compile-time validation, while the public wrapper exposes procedure signatures that accept and return the loosely typed JTF arrays that can be marshalled across the OAF/Java and PL/SQL boundary. In practice the package supports accounting event (AEL) processing for lease contracts — the creation and movement of accounting events and their associated distributions — by allowing callers to pass entire sets of event lines as collections rather than one row at a time. Because the wrapper contains no business rules of its own, it is best understood as a data-shape adapter rather than a business API.

Key Procedures and Functions

The documented interface consists of paired copy procedures. The core pattern is represented by ROSETTA_TABLE_COPY_IN_P2 and ROSETTA_TABLE_COPY_OUT_P2: the _IN procedures accept a large, fixed list of JTF typed table parameters and populate the internal ael_tbl_type record table, while the _OUT procedures perform the reverse conversion, unpacking the internal record table back into the individual JTF arrays. The numbering suffix (_P2, _P5, _P6, _P7, _P8, _P9, _P10, _P11, _P12, _P13) identifies distinct overload variants that map different column sets of the AEL table structure, giving the caller the option to pass only the attributes relevant to a particular accounting event scenario. In the _P2 variant, for example, the input signature contains a mixture of numeric, varchar2 and date arrays, with the wide-column attributes carried through JTF_VARCHAR2_TABLE_800 parameters — the element type the user's search term "jtf_varchar2_table_800" refers to. All 129 documented procedures follow the same naming convention, confirming that OKL_AEL_PVT_W is purely a conversion layer. No business validation, event creation, or distribution logic is documented in this wrapper; such logic resides in OKL_AEL_PVT and its supporting packages. Callers must therefore invoke the private package (or the appropriate public business API) after completing the copy-in step.

Tables Accessed

The ETRM metadata records a single referenced object for this package: the APPS synonym PLITBLM. This is the standard PL/SQL table/collection handling table used by the Oracle Forms and OAF infrastructure to persist and retrieve PL/SQL table data between client and server tiers. Its presence is consistent with the package's role as a collection transport utility: the JTF tables passed into and out of the Rosetta procedures are, in interactive contexts, materialized through PLITBLM. OKL_AEL_PVT_W performs no direct DML against OKL accounting event tables; all persistent reads and writes are delegated to the private package. The only documented database interaction attributed to the wrapper is therefore the collection staging performed via PLITBLM.

Usage Notes

OKL_AEL_PVT_W is an internal, non-customer-facing package. It is not intended to be called directly by end users or by customizations; Oracle classifies it as OTHER rather than as a public API. It is invoked in two principal ways. First, from OAF-based Lease Management pages, where the JTF collection signatures allow an entire block of accounting event rows to cross the Java/PL/SQL boundary in a single call, with the _IN variant loading data into ael_tbl_type for processing and the _OUT variant returning processed results to the middle tier. Second, from other PL/SQL packages: the metadata shows OKL_AEL_PVT_W is referenced by two other packages, which call the copy routines as a preparatory step before invoking private AEL logic. The JTF_VARCHAR2_TABLE_800 parameters in particular carry the long descriptive and reference attributes of accounting event lines that exceed the 100-character length of the more common JTF_VARCHAR2_TABLE_100 type. Because the _P2 through _P13 variants differ only in which attribute sets they map, integrators must select the variant matching the event type being processed. Custom code should not call this wrapper; supported integration should target the documented public Lease Management APIs, which invoke the private package internally.