Search Results ams_imp_list_headers_pkg




Overview
Explore in AI Chat

Overview

APPS.AMS_IMP_LIST_HEADERS_PKG is a PL/SQL package in the Oracle E-Business Suite APPS schema that supports the Oracle Marketing (AMS) module's import list header functionality. The package provides the low-level data manipulation routines required to persist, maintain, and localize records in the marketing import list header entity. Import lists are used within Oracle Marketing to load external contact and prospect data into the application for campaign execution and lead management, and the header records define the top-level attributes of each import list, such as its name, description, and associated metadata.

In the ETRM 12.2.2 documentation the package is classified as an OTHER API, meaning it is not published as a formal open interface but is nevertheless a stable internal API used by Oracle's own code. Its status is VALID, and it is owned by the APPS schema, which is consistent with other Oracle Marketing private APIs. The package is referenced by one other package, AMS_IMPORT_LIST_PVT, which acts as the primary programmatic entry point for import list operations. The package itself depends on the SYS schema object STANDARD, indicating reliance on Oracle's built-in PL/SQL environment.

Key Procedures and Functions

The ETRM metadata documents five subprograms in AMS_IMP_LIST_HEADERS_PKG:

  • INSERT_ROW — Inserts a new import list header record into the base table and its translation table as applicable, establishing the core identity of the list.
  • UPDATE_ROW — Modifies attributes of an existing import list header record, allowing changes to descriptive or status-related fields.
  • DELETE_ROW — Removes an import list header record, typically as part of a purge or cleanup operation.
  • LOCK_ROW — Acquires a row-level lock on a specific import list header, serializing concurrent modifications and protecting transactional consistency.
  • ADD_LANGUAGE — Inserts translated (TL) rows for supported languages, supporting Oracle's multi-language (MLS) architecture for import list header descriptions.

These procedures follow the conventional Oracle EBS private API pattern of one operation per DML verb, with the package body providing the implementation. Parameter lists are not documented in the ETRM metadata and are typically derived from the underlying table columns at runtime; callers should reference the package specification in the database for exact signatures.

Tables Accessed

The package operates against three documented objects, referenced through APPS synonyms:

  • AMS_IMP_LIST_HEADERS_ALL — The base (non-translated) table holding import list header records. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW act on this table.
  • AMS_IMP_LIST_HEADERS_ALL_TL — The translation table storing language-specific descriptions. ADD_LANGUAGE and the MLS-aware portions of INSERT_ROW/UPDATE_ROW write here.
  • FND_LANGUAGES — Oracle's standard language repository, consulted to validate or expand language codes during ADD_LANGUAGE processing.

Usage Notes

AMS_IMP_LIST_HEADERS_PKG is an internal implementation package rather than an end-user or open interface. In practice, it is not invoked directly by customers; instead it is called by AMS_IMPORT_LIST_PVT, which exposes the higher-level business operations for import list management. Forms, concurrent programs, or custom code that need to manipulate import list headers should route requests through AMS_IMPORT_LIST_PVT or the Oracle Marketing public APIs rather than calling this package directly.

Where direct use is unavoidable — for example in controlled data migrations or extensions — developers must supply the appropriate MLS language context, commit or roll back explicitly, and invoke LOCK_ROW before UPDATE_ROW or DELETE_ROW to avoid concurrency conflicts. Because the package is classified as OTHER and is not documented for external consumption, Oracle does not guarantee signature stability across patches, so any direct dependency should be reviewed on each upgrade. In Oracle EBS 12.1.1 and 12.2.2, the package remains valid and is installed as part of the standard Oracle Marketing schema.