Search Results ams_import_list_pub




Overview

The APPS.AMS_IMPORT_LIST_PUB package body is a public Application Programming Interface (API) within the Oracle E-Business Suite Advanced Marketing (AMS) module. Its principal business function is to manage the lifecycle of import list headers used by the marketing import process. Import lists represent the staging containers into which external customer and prospect data is loaded before being processed by Marketing's import and de-duplication routines. This package exposes a set of PL/SQL entry points that allow calling programs to create, maintain, lock, and remove import list header records in a controlled, API-compliant manner.

The package follows Oracle's standard public API design conventions defined by FND_API, including API version compatibility checking via FND_API.Compatible_API_Call, message list initialization through FND_MSG_PUB.initialize, savepoint management, and standardized x_return_status, x_msg_count, and x_msg_data output parameters. It also incorporates debug instrumentation keyed off the FND_MSG_PUB message levels (AMS_DEBUG_HIGH_ON, AMS_DEBUG_MEDIUM_ON, and AMS_DEBUG_LOW_ON).

Key Procedures and Functions

The documented package exposes four public procedures:

  • CREATE_IMPORT_LIST — Creates a new import list header record and returns its generated identifier through the x_import_list_header_id output parameter. This is the entry point relevant to the user's search term ("create_import_list"), and it accepts an import record structure along with standard API control parameters.
  • UPDATE_IMPORT_LIST — Modifies the attributes of an existing import list header, allowing callers to change descriptive or status information after creation.
  • DELETE_IMPORT_LIST — Removes an import list header record, typically used when a staged import is abandoned or no longer required.
  • LOCK_IMPORT_LIST — Obtains a logical lock on an import list header to prevent concurrent modification, supporting the concurrency control model typical of Oracle public APIs.

The CREATE_IMPORT_LIST procedure validates the incoming API version against its internal constant (version 1.0) and delegates the substantive insert work to a private package, AMS_IMPORT_LIST_PVT, which is referenced in the source excerpt.

Tables Accessed

The ETRM metadata for this package does not enumerate the underlying base tables directly; table access is abstracted through APPS synonyms and executed within the private AMS_IMPORT_LIST_PVT package. Based on the package's stated purpose, the operations act upon the AMS import list header entity, which stores the identifying and descriptive attributes of each import list. Because the public package wraps the private implementation, direct DML against these tables is not performed at the public layer; instead, the private layer mediates all inserts, updates, deletes, and lock acquisition.

Usage Notes

AMS_IMPORT_LIST_PUB is typically invoked from Oracle Forms-based Marketing setup and import screens, from concurrent programs that stage inbound data feeds, and from custom extensions that need to programmatically register or retire import lists. The metadata records that no documented packages reference this object, indicating it is a top-level integration point rather than an internal dependency. Callers should always inspect x_return_status for FND_API.G_RET_STS_SUCCESS and should honor the p_commit and p_init_msg_list flags in accordance with standard EBS API etiquette. The LOCK_IMPORT_LIST procedure should precede any read-modify-write sequence to avoid lost updates under concurrent access. This behavior is consistent across both EBS 12.1.1 and 12.2.2.