Search Results jtf_date_table

Overview

The APPS.OKL_SEC_INVESTOR_PVT_W package is a private PL/SQL wrapper belonging to the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It provides the programmatic interface used to maintain secondary investor information associated with lease and finance contracts. Within ETRM (Enterprise Territory and Resource Management taxonomy referenced for OKL), the package is classified under API classification OTHER, indicating it is not a public, externally supported API surface but rather an internal helper consumed by adjacent OKL components.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema (typically APPS) rather than the definer. The header carries the identifier $Header: OKLUSZIS.pls 115.2 2003/10/22 23:15:17 ashariff noship $, confirming its origin as part of the OKL source set and its "noship" designation (internal build, not shipped as a standalone deliverable). The primary architectural purpose of the package is to bridge PL/SQL record collections and the flattened, column-oriented table types used by the Rosetta/AOL integration layer — hence its central dependence on the JTF_*_TABLE collection family.

Key Procedures and Functions

ETRM documents five procedures for this package:

• ROSETTA_TABLE_COPY_IN_P1 — Converts the incoming column-wise JTF collections (numbers, varchar2 buffers of length 100/200/2000/400, and dates) into the structured PL/SQL record table type okl_sec_investor_pvt.inv_tbl_type. This is the inbound marshalling step that normalizes Rosetta-supplied data before business logic executes.
• ROSETTA_TABLE_COPY_OUT_P1 — Performs the inverse operation, decomposing an inv_tbl_type record table back into the individual JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_*, and JTF_DATE_TABLE output collections for downstream Rosetta processing.
• CREATE_INVESTOR — Inserts a new secondary investor record, populating the investor table from the marshalled record collection.
• UPDATE_INVESTOR — Modifies an existing secondary investor record identified by its primary key attributes.
• DELETE_INVESTOR — Removes a secondary investor record from the repository.

The significant number of date-typed arguments (a14, a15, a16, a22, a23, a25–a28, a32, a36) reflects the heavy date-bearing nature of investor agreements — effective dates, termination dates, and secondary sale dates in particular. Neither boundary procedure nor the CRUD procedures exposes documented business-side parameter lists beyond these collection signatures.

Tables Accessed

The only table documented against this package is PLITBLM, referenced through an APPS synonym. PLITBLM is the standard Oracle PL/SQL "table lookup" store used by the Rosetta integration framework to persist transient collection data across calls. The package reads and writes entries in this table during the copy-in/copy-out conversion cycle so that the bulk JTF collections can be materialized, transformed, and re-serialized correctly. The actual OKL investor entity table (the OKL_SEC_INVESTORS family) is not listed among the documented references, though the CRUD procedures necessarily affect the underlying investor repository.

Usage Notes

Because the package is private (_PVT_W) and authenticated as CURRENT_USER, it is not intended for direct invocation by end users or supported customizations. It is invoked indirectly:

• Rosetta/AOL integration flows — when the OKL secondary investor user interface or a Web-services wrapper must pass multi-row investor data across the PL/SQL boundary. The COPY_IN and COPY_OUT procedures are the entry points called by the generated Rosetta glue code.
• OKL forms — the Secondary Investor UI in Oracle Lease Management triggers the CREATE/UPDATE/DELETE procedures via the standard form-to-package wiring.
• Custom integrations — developers should prefer the public OKL APIs. Any direct call must respect the inv_tbl_type collection shape and MLE/JTF typing conventions; mismatched collection element counts will cause runtime VALUE_ERROR or NO_DATA_FOUND exceptions during marshalling.

The package is referenced by zero other packages per ETRM, confirming it occupies a leaf position in the OKL call graph.