Search Results rosetta_table_copy_out_p3

Overview

AMS_LISTGENERATION_UTIL_PKG_W is an Oracle Marketing (AMS) utility package that supports list generation processing within Oracle E-Business Suite. Its most prominent public entry point, GET_SPLIT_PREVIEW_COUNT, generates preview counts that describe how a target list would be divided or "split" across segments during list generation. This allows marketers to review the projected distribution of a list before committing to the actual generation run.

The "_W" suffix indicates that this is a wrapped or generated wrapper package. It is a thin PL/SQL facade layered over the corresponding non-wrapped implementation package, AMS_LISTGENERATION_UTIL_PKG. The wrapper exists so that dependent callers—typically Forms, OAF pages, or other PL/SQL modules—can invoke the underlying logic through a stable, published signature, while the implementation body itself remains protected. The package body carries the source header identifier amswlgus.pls and a creation date of 2006/02/23, reflecting that the interface has been stable since the early 11i era and carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes three documented procedures.

• GET_SPLIT_PREVIEW_COUNT — The primary functional procedure and the object most commonly associated with this package. It accepts a list header identifier (p_list_header_id) and returns the preview count results for the list split through three out or in-out PL/SQL tables. It also follows the standard Oracle API error-handling convention, returning a status code, a message count, and a message data buffer through its x_return_status, x_msg_count, and x_msg_data parameters. Callers should check x_return_status after invocation and drain the message stack when the status indicates an error.
• ROSETTA_TABLE_COPY_IN_P3 — A generated helper that copies data into the internal preview count table type (spl_preview_count_tbl) from the JTF-based collection types used at the wrapper boundary. It is part of the Rosetta marshalling layer that bridges JDBC/OAF-compatible JTF tables and the native PL/SQL record structures used inside the implementation package.
• ROSETTA_TABLE_COPY_OUT_P3 — The complementary generated helper that copies data out of the internal preview count table type back into the JTF table types for return to the caller. Together with ROSETTA_TABLE_COPY_IN_P3 it forms the conversion pair required for nested table arguments.

The procedures are not intended to be called directly by end users; the two Rosetta routines are implementation-level scaffolding for the wrapper plumbing.

Tables Accessed

According to the documented metadata, the package references the table PLITBLM through an APPS synonym. This is the transient table used by the list generation engine to hold intermediate split and count results while a list is being built. GET_SPLIT_PREVIEW_COUNT reads from this table to derive the projected preview counts for a given list header, rather than persisting any new data. Because it is a read-oriented preview operation, the procedure has no side effects on the underlying list definition.

Usage Notes

GET_SPLIT_PREVIEW_COUNT is invoked from the Oracle Marketing list generation user interface—typically a Forms-based or OAF page—when the user requests a preview of how the current list will be divided across segments. The list header identifier must reference a valid, existing list header record. Because the procedure returns collections rather than a scalar count, callers must allocate the JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_32767 variables before the call. Error handling should always inspect x_return_status; a non-success value accompanied by x_msg_count greater than zero indicates messages that must be retrieved via the standard FND_MSG_PUB API. In custom integrations, the package should be invoked only through the API-dispatched wrapper, and direct calls into the underlying non-wrapped package should be avoided to preserve upgrade safety. Finally, no other documented package references this wrapper, so it is a leaf-level interface driven entirely by UI and external callers.