Search Results cn_import_pvt




Overview
Explore in AI Chat

Overview

CN_IMPORT_CLIENT_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Oracle Channel Revenue Management (formerly Oracle Trade Management / Channel Management) module. Its header revision identifies it as a component of the CN (Channel) product family, delivered with the script name cnvimpcs.pls. The package is classified as a PVT (private) API, meaning it is not part of the public, supported integration surface of the application; it is intended for internal consumption by the higher-level CN import packages that call it. Its declared purpose is to accept externally staged client import data, expressed as an array of column names and a parallel array of column values, and to persist that data into a designated staging or interface table. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking session/package rather than the defining APPS schema, which supports a delegation model where the calling import program owns the insertion context.

Key Procedures and Functions

The ETRM metadata documents a single procedure, INSERT_DATA. Its documented function is to insert data into the table whose name is supplied by the caller through the p_table_name parameter. The procedure is a private API with no prerequisites and version 1.0 (initial, previous, and current versions coincide). Insert_Data accepts a standard FND_API conforming parameter set together with the import-specific inputs: the import header identifier, the import type code, the target table name, the object version number, a collection of column names, a collection of data values, and a row count, and it returns the standard FND_API output parameters for return status, message count, and message data. The procedure therefore acts as a generic, metadata-driven insert engine: rather than hard-coding a fixed column list, it reconstructs an INSERT statement from the caller-supplied column name and value collections and executes one row insert per call. It is invoked iteratively by the parent import routine, which passes p_row_count to reflect the number of rows in the current batch. The collection types are defined in CN_IMPORT_PVT (char_data_set_type), confirming the tight coupling between the private and client-private layers of the CN import stack. No other procedures or functions are exposed by this package.

Tables Accessed

The documented table references resolve, through APPS synonyms, to CN_IMP_LINES and CN_IMP_LINES_S, the channel import lines tables and their alternate-key/seed counterpart. These are the interface tables into which staged import records are loaded prior to validation and transfer into the base channel revenue management tables. Since the actual target table is parameterized, the metadata-driven insert can be directed to these import lines entities as governed by the parent caller. DUAL appears only to support the generic PL/SQL construction logic common in dynamic SQL routines of this vintage. PLITBLM is the Oracle Applications PL/SQL integer table type (the standard indexed table of PLS_INTEGER used by FND-style APIs), referenced as part of the package environment rather than as a business data source.

Usage Notes

Because the package is a PVT API, it is not invoked directly by end users, Oracle Forms, or supported concurrent programs. It is called internally by the CN import processing packages—the metadata records three packages referencing it—which orchestrate the parsing of inbound files, validation, and loading of the channel import lines. Typical invocation is a looping construct within a parent PL/SQL package or a concurrent program manager routine that, for each staged row, assembles the column name and value arrays and calls Insert_Data with p_commit set per batch policy. The FND_API conventions of p_api_version, p_init_msg_list, and p_commit indicate the caller is responsible for transaction control and message-stack initialization, and that errors are surfaced through x_return_status and the x_msg_count/x_msg_data pair rather than by raising unhandled exceptions. Customizations should avoid direct calls to this private package in favor of the public CN import APIs, since the private signature is subject to change without notice between 12.1.1 and 12.2.2.