Search Results rosetta_table_copy_in_p31

Overview

The OKL_COPY_CONTRACT_PVT_W package is a private PL/SQL wrapper belonging to the Oracle E-Business Suite Oracle Lease and Finance Management (OLFM/OKL) module. Its business purpose is to service the contract copy operation — duplicating an existing lease or finance contract, including its components and lines, into a new or target contract header. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the APPS owner, which is characteristic of a thin marshalling wrapper.

The "_W" suffix and the presence of rosetta_table_copy_in and rosetta_table_copy_out procedures confirm that this package is generated by the EBS Rosetta integration framework. Rosetta generates wrapper packages to move bulk PL/SQL table parameters in and out of JTF scalar/array structures, typically so that Java-based or web-service callers (in this case the OLFM contract copy UI) can pass multi-row bind data across the PL/SQL boundary without colon-delimited or REF CURSOR conventions. The core business logic resides in the sibling package OKL_COPY_CONTRACT_PVT, which the metadata shows being referenced by this wrapper.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P29 / ROSETTA_TABLE_COPY_OUT_P29 — Rosetta marshalling pair that converts between the JTF scalar-array types and the okl_copy_contract_pvt.api_components_tbl PL/SQL table. The _in variant populates the api_components_tbl from caller-supplied JTF arrays; the _out variant performs the reverse, returning the api_components_tbl contents to the caller as JTF arrays. No business rules are applied here; this is pure data conversion for API component records.
• ROSETTA_TABLE_COPY_IN_P31 / ROSETTA_TABLE_COPY_OUT_P31 — The corresponding marshalling pair for okl_copy_contract_pvt.api_lines_tbl, the contract line records. The _in variant accepts four JTF numeric arrays and one JTF_VARCHAR2_TABLE_100 array and populates the line table; the _out variant reverses this conversion for outbound results. This is the pair searched for as "rosetta_table_copy_in_p31".
• IS_COPY_ALLOWED — Determines, for a given contract identifier and status code, whether the contract may be copied. The result is returned through a boolean OUT parameter (the ddrosetta_retval_bool convention).
• IS_SUBCONTRACT_ALLOWED — Parallel eligibility check that returns whether subcontracting is permitted for the given contract and status.
• UPDATE_TARGET_CONTRACT — Finalises the target contract header after copy processing, returning a status indicator via the boolean OUT parameter.
• COPY_COMPONENTS — The principal entry point. It performs the contract copy, accepting a standard EBS API message list and return-status signature together with the source and target contract identifiers, contract number and modifier, template flag, copy reference, line-party copy flag, and the component and line PL/SQL tables (supplied through the Rosetta _in procedures).

Tables Accessed

The only table directly referenced through APPS synonyms is PLITBLM, the Rosetta/CPE line-mapping table used by the integration framework to stage or translate row identifiers between external and internal representations. All other read and write activity against the OKL contract headers, components, lines, and associated party tables is performed indirectly through calls into OKL_COPY_CONTRACT_PVT. Because the package is a wrapper, it holds no table state of its own.

Usage Notes

This package is not ordinarily called directly by end users or concurrent programs. It is invoked by the OLFM contract copy form in Oracle Forms / OA Framework, which passes multi-row line and component selections through the Rosetta-generated wrappers. Custom integrations that need to copy contracts programmatically should prefer the public OKL_COPY_CONTRACT_PVT API; only callers already working within the Rosetta JTF array convention need this "_W" layer. Because it runs AUTHID CURRENT_USER, the invoking session must have appropriate execution and object privileges, and the caller should respect the standard EBS API conventions — initialise the message list, honour x_return_status, and inspect x_msg_count/x_msg_data for diagnostics. No direct manipulation of PLITBLM is expected from custom code.