Results for “cn_import_client_pvt”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CN_IMPORT_CLIENT_PVT is a private PL/SQL package body in the Oracle E-Business Suite Channel Revenue Management (formerly Trade Management) module. It belongs to the CN product family, which governs channel rebates, vendor rebates, and the bulk import of transactional channel data. The package is classified as a private (PVT) API, meaning it is intended for internal consumption by the public CN_IMPORT_PVT package rather than for direct invocation by external callers or integration partners. Its primary business function is to manage the client-side portion of the import process, specifically the loading and validation of client records (customers, trading partners, or channel entities) that precede or accompany the import of transactional lines into the CN_IMP_LINES staging structure.

The object is documented as VALID in the APPS schema under EBS 12.2.2, and the same architectural pattern applies to 12.1.1. Notably, the package body is not referenced by any other database object, confirming its role as a terminal internal worker invoked through the public wrapper CN_IMPORT_PVT. Three dependent packages rely on it during execution, and it in turn depends on the standard EBS API infrastructure.

Key Procedures and Functions

The ETRM documentation identifies exactly one documented program unit within this package body:

  • INSERT_DATA — The core procedure responsible for inserting client records into the import staging tables. It accepts collection-based input (evidenced by the JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_2000 dependencies), performs data insertion into CN_IMP_LINES, and returns status and message information to the calling layer through FND_MSG_PUB. The exact parameter list is not documented in the available metadata and should not be assumed.

The procedure follows the standard EBS API conventions, as reflected by its dependencies on FND_API (for the standard API return status constants and initialization), FND_GLOBAL (for user_id, login_id, and responsibility context), and FND_MSG_PUB (for message stack population). Error and warning communication is routed through CN_MESSAGE_PKG, the CN product's centralized message handler.

Tables Accessed

The package references the following tables and objects via APPS synonyms:

  • CN_IMP_LINES — The primary import staging table for channel revenue management transactional lines. INSERT_DATA writes client-related rows into this table as part of the broader import workflow.
  • CN_IMP_LINES_S — The sequence associated with the CN_IMP_LINES table, used to generate primary keys for newly inserted staging rows. This is the object referenced by the search term "cn_imp_lines_s" and represents the surrogate key generator supporting the import insert logic.
  • DUAL — Used for singleton SELECT statements, typically to retrieve sequence values or evaluate expressions.
  • PLITBLM — The standard PL/SQL internal table management package, used implicitly for collection handling within the procedure.

The use of JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_2000 indicates that INSERT_DATA processes data in bulk collections, a performance pattern characteristic of mass import routines where row-by-row DML would be prohibitively expensive.

Usage Notes

CN_IMPORT_CLIENT_PVT is designed for internal use within the CN import framework. It is typically invoked indirectly: user actions in the Channel Revenue Management forms or a concurrent program submit a request to the public CN_IMPORT_PVT API, which validates the request context and then delegates client-level insert operations to INSERT_DATA in this private package. Direct calls from custom code are not recommended.

Because the package commits only through the standard API savepoint and message-handling model, any extension or debugging work should preserve the FND_API initialization and FND_MSG_PUB error propagation. When troubleshooting import failures, the CN_MESSAGE_PKG message stack and CN_IMP_LINES staging contents should be examined first, as INSERT_DATA records both successful inserts and validation rejections in these locations.