Search Results client_stage_data

Overview

APPS.CN_IMPORT_PVT_W is a private PL/SQL wrapper package within the Oracle EBS Channel Management (CN) product family. Its principal responsibility is to expose a public, wrapper-friendly interface to the internal import logic contained in the CN_IMPORT_PVT package, most notably the routine that stages client-supplied import data prior to validation and processing. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the definer, which is characteristic of wrapper packages intended to be called from a controlled entry point. In Oracle EBS 12.1.1 and 12.2.2 the "W" suffix traditionally denotes a wrapper layer that bridges a base private API to callers such as concurrent programs, OAF pages, or other PL/SQL modules, shielding them from the internal data structures used by the implementation package.

Key Procedures and Functions

The package contains five documented routines. Four of these are generated "Rosetta" table conversion helpers that move bulk data between nested-table types used by the base package and their SQL-callable equivalents:

• ROSETTA_TABLE_COPY_IN_P0 — copies an incoming JTF_VARCHAR2_TABLE_2000 into the internal cn_import_pvt.char_data_set_type structure, converting character-based import data for use by the core logic.
• ROSETTA_TABLE_COPY_OUT_P0 — performs the reverse conversion, exporting character data from the internal char_data_set_type back to a JTF_VARCHAR2_TABLE_2000.
• ROSETTA_TABLE_COPY_IN_P1 — copies an incoming JTF_NUMBER_TABLE into the internal cn_import_pvt.num_data_set_type.
• ROSETTA_TABLE_COPY_OUT_P1 — exports numeric data from num_data_set_type back to a JTF_NUMBER_TABLE.
• CLIENT_STAGE_DATA — the functional entry point of the package. It stages client import data for a given import header, receiving a row-oriented collection of character data along with the import header identifier, row count, map object version, and organization identifier. It also accepts API versioning, initialization, commit, and validation-level controls, and returns the standard EBS return status, message count, and message data outputs. This procedure is the routine a caller reaches when searching for client_stage_data.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. PLITBLM is the standard EBS interface table used to buffer incoming rows of staged import data before the import engine validates and migrates them into the application tables. Staging into this table allows large client data sets to be loaded in bulk and then processed in controlled batches.

Usage Notes

This package is not referenced by any other documented package, indicating that it is invoked from an external entry point rather than from within the PL/SQL package hierarchy. Typical callers include concurrent programs, OAF or Forms-based import flows, and custom integration code that must push client data into the Channel Management import pipeline. Because CLIENT_STAGE_DATA accepts commit and validation-level flags, callers control transaction boundaries and the degree of validation applied during staging. Custom code should call the procedures through the APPS schema, respect the AUTHID CURRENT_USER privilege model, and always inspect x_return_status before proceeding, since the Rosetta conversions must precede the staging call whenever collection-based data is supplied.