Search Results rosetta_table_copy_out_p12

Overview

CSK_SETUP_UTILITY_PKG_W is a public PL/SQL wrapper package deployed in the APPS schema of Oracle E-Business Suite. It belongs to the Customer Service (CSK) product family and supports setup utility processing, most notably the programmatic creation of solutions within the Service module. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking session rather than the definer, a standard convention for EBS wrapper packages that must respect the caller's data security context.

A significant portion of the package body consists of Rosetta-style conversion routines whose suffixes (P12, P13) denote positional parameter signatures. These routines shuttle data between the strongly typed collection types defined in CSK_SETUP_UTILITY_PKG and the generic JTF collection types (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_2000) used across the Oracle Application Framework and JTF (Java-based Technology Foundation) integration layer. This design allows the package to exchange structured record sets with Java clients, forms, or other PL/SQL consumers that cannot bind directly to the custom object types.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P12 — Populates a CSK_SETUP_UTILITY_PKG statement table collection from six inbound JTF collection parameters. It is the inbound conversion path for the P12 signature, translating generic arrays into the package's internal statement type.
• ROSETTA_TABLE_COPY_OUT_P12 — Performs the inverse operation for the same P12 signature, splitting a statement table collection into six outbound JTF arrays. This is the routine surfaced by the search term "rosetta_table_copy_out_p12"; it is invoked whenever a calling application needs to receive statement data in the flattened generic format.
• ROSETTA_TABLE_COPY_IN_P13 — Converts a single inbound JTF_NUMBER_TABLE into the package's catalogue (cat_tbl_type) collection, supplying category identifiers to downstream logic.
• ROSETTA_TABLE_COPY_OUT_P13 — Returns a cat_tbl_type collection as a single outbound JTF_NUMBER_TABLE. Note that the P13 signatures contain no status or message parameters, so error handling for these conversions is limited to raised exceptions.
• CREATE_SOLUTION — The primary business API of the package. It creates a solution record using the standard EBS API conventions: an API version, initialization-message flag, commit flag, and validation level, together with standard return status, message count, and message data outputs. In addition, it accepts scalar attributes (p7_a0 through p7_a4), six JTF collections representing solution lines or related detail rows (p8_a0 through p8_a5), a category collection, and a publish flag. The numeric suffixes in the parameter names mirror the Rosetta conversion routines, confirming that callers pass data in the same flattened layout.

Tables Accessed

The only documented table reference is PLITBLM, accessed through an APPS synonym. In EBS, PLITBLM is the standard concurrent-program / PL/SQL interface table that stores temporary message and error information for APIs that manage message stacks. CREATE_SOLUTION's message count and message data outputs are consistent with this dependency. No other base or interface tables are listed in the ETRM metadata, so the package's direct persistence footprint appears narrow; the actual solution records are presumed to be written by the underlying CSK solution API that CREATE_SOLUTION delegates to.

Usage Notes

The package is referenced by zero other documented packages, indicating it is an entry-point wrapper rather than a building block consumed by other PL/SQL units inside ETRM. It is therefore most likely invoked from Oracle Forms or OAF-based Service setup screens, from Java clients that require the Rosetta conversion layer, or from custom concurrent programs and integration scripts that need to mass-create solutions. For most requirements, calling CREATE_SOLUTION with the appropriate JTF and category collections is preferred over invoking the Rosetta routines directly, since CREATE_SOLUTION encapsulates validation, message handling, and commit control. Callers should set p_init_msg_list and inspect x_return_status before proceeding, in line with standard EBS API error-handling practice, and should supply the same P12/P13 collection layouts the Rosetta routines expect.