Search Results insert_list_data
Overview
APPS.AMS_IMPORTCLIENT_PVT_W is the public wrapper package for the Oracle Marketing (AMS) client import process, known within EBS as the Import Client activity. Its companion private package, AMS_IMPORTCLIENT_PVT, contains the core import logic, while this wrapper exposes a callable interface and converts Oracle Marketing's internal PL/SQL collection types into the flat, generic JTF collection types that callers such as concurrent programs, the Import Client form, and external interfaces can supply. The documented source header shows the current version as 115.9, last modified in May 2003, confirming that this object is a long-standing inherited artifact of the Oracle Marketing schema rather than a recent addition. In EBS 12.1.1 and 12.2.2 the package continues to be deployed under APPS with AUTHID CURRENT_USER, meaning that name resolution and privilege checking occur in the caller's schema. Its operations centre on bulk insertion of lead and list data staged for a specific import list header, providing return status and error-row reporting to the invoker.
Key Procedures and Functions
The package documents ten procedures. The first eight are "Rosetta" conversion utilities, so named because they translate between type representations, for the four collection families used by the import interface:
- rosetta_table_copy_in_p0 / rosetta_table_copy_out_p0 — convert character data sets to and from the JTF_VARCHAR2_TABLE_4000 collection type.
- rosetta_table_copy_in_p1 / rosetta_table_copy_out_p1 — convert numeric data sets to and from the JTF_NUMBER_TABLE collection type.
- rosetta_table_copy_in_p2 / rosetta_table_copy_out_p2 — convert varchar2_4000 set types to and from JTF_VARCHAR2_TABLE_4000.
- rosetta_table_copy_in_p3 / rosetta_table_copy_out_p3 — convert varchar2_150 set types to and from the JTF_VARCHAR2_TABLE_200 collection type.
The remaining two procedures perform the substantive import work, both keyed by an import list header identifier and both returning standard EBS API status values (return status, message count, message data):
- insert_lead_data — inserts lead records for the identified import list header, accepting the incoming data payload plus a numeric array of row numbers that failed, and returning the count of rows processed.
- insert_list_data — inserts list records for the identified import list header. This is the procedure exposed to users searching for "insert_list_data." It accepts the API version, initialisation and commit flags, the import list header ID, the flat character data payload, a row count, and an error-rows number table, returning completion status and message information. The insert_lead_data routine differs only in the ordering of its payload and error-row arguments.
Tables Accessed
The ETRM metadata records a single referenced table, PLITBLM, reached through an APPS synonym. PL/SQL tables of records in the Oracle Marketing schema are stored in this table, and the import wrapper writes the collected lead and list rows into it as part of the bulk insert path. No other base tables are documented as directly accessed by this wrapper; the underlying AMS_IMPORTCLIENT_PVT package performs the wider validation and insertion against the marketing lead and list tables.
Usage Notes
This package is an API-layer object and is not typically invoked directly from a user interface. It is called by Oracle Marketing's Import Client concurrent program and related setup forms, and it is available to custom code that needs to load client, lead, or list data programmatically against a staged import list header. Because the documented procedures use JTF collection parameters, callers first populate JTF_VARCHAR2_TABLE_4000 or JTF_NUMBER_TABLE collections and rely on the Rosetta copy procedures to map them into the package's internal types. The metadata reports no other packages referencing this wrapper, so dependencies flow into it rather than out of it. Invokers should pass p_commit carefully, since the commit flag governs whether inserted rows are persisted immediately or left for the calling transaction.
-
APPS.AMS_IMPORTCLIENT_PVT_W SQL Statements
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT_W SQL Statements
12.2.2
-
PACKAGE: APPS.AMS_IMPORTCLIENT_PVT_W
12.1.1
-
PACKAGE: APPS.AMS_IMPORTCLIENT_PVT
12.1.1
-
PACKAGE: APPS.AMS_IMPORTCLIENT_PVT_W
12.2.2
-
PACKAGE: APPS.AMS_IMPORTCLIENT_PVT
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT SQL Statements
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AMS_IMPORTCLIENT_PVT_W
12.2.2
-
PACKAGE BODY: APPS.AMS_IMPORTCLIENT_PVT_W
12.1.1
-
PACKAGE BODY: APPS.AMS_IMPORTCLIENT_PVT
12.1.1
-
PACKAGE BODY: APPS.AMS_IMPORTCLIENT_PVT
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on FND_API
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on FND_API
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on AMS_IMP_LIST_HEADERS_ALL
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on AMS_IMP_LIST_HEADERS_ALL
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT_W dependencies on JTF_VARCHAR2_TABLE_4000
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT_W dependencies on JTF_VARCHAR2_TABLE_4000
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT_W dependencies on JTF_VARCHAR2_TABLE_4000
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on AMS_IMP_SOURCE_LINES
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on AMS_IMP_SOURCE_LINES
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT_W dependencies on JTF_VARCHAR2_TABLE_4000
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on STANDARD
12.1.1
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on STANDARD
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on FND_API
12.2.2
-
APPS.AMS_IMPORTCLIENT_PVT dependencies on FND_API
12.1.1