Search Results ams_list_src_fields_s

Overview

The APPS.AMS_LIST_SRC_FIELDS_PKG package body is the implementation layer for the Oracle Marketing (AMS) module's list source field definitions. In Oracle EBS release 12.1.1 and 12.2.2, this package supports the maintenance of the seed and configuration data that maps source fields available for building marketing lists — for example, customer attributes, contact attributes, and related column definitions used by the list generation engine.

The package implements a standard Oracle Application Object Library (AOL)-compliant DML API pattern. This pattern provides a consistent, multi-language-aware interface for inserting, updating, deleting, locking, and loading rows in the underlying AMS_LIST_SRC_FIELDS tables. It is not a business-transaction package; rather, it is a data maintenance API, typically used by concurrent programs, forms, or seeding logic to keep the list source field metadata synchronized. Its API classification is OTHER — meaning it is a general-purpose maintenance API rather than a public, transactional integration interface.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within this package body. These align with the standard AOL table-handler API convention:

• INSERT_ROW — Inserts a new list source field record. It populates both the base table and the associated translation table rows, applying the standard WHO columns and language handling.
• UPDATE_ROW — Modifies an existing list source field record, updating the base row and any corresponding translated description or display values.
• DELETE_ROW — Removes a list source field record together with its language-specific translation entries, ensuring referential integrity across the base and TL tables.
• LOCK_ROW — Obtains and validates a row lock prior to an update or delete, providing concurrency control and preventing lost updates in multi-user environments.
• LOAD_ROW — Performs an upsert operation. It attempts to locate an existing record and delegates to UPDATE_ROW if found, or INSERT_ROW if not. This is the primary interface used by seeding and migration utilities.
• ADD_LANGUAGE — Adds translation rows for a newly installed or enabled language, using FND_LANGUAGES to determine the target languages requiring entries.
• TRANSLATE_ROW — Updates the translated, language-specific text (such as the prompt or display name) for an existing list source field.

Tables Accessed

The package operates over the following APPS-synonym tables:

• AMS_LIST_SRC_FIELDS — The primary base table holding list source field definitions.
• AMS_LIST_SRC_FIELDS_S — The sequence-generated key table, referenced in the search term "ams_list_src_fields_s," used to allocate primary key values.
• AMS_LIST_SRC_FIELDS_TL — The translation table, storing language-specific display text keyed by language.
• FND_LANGUAGES — Consulted by ADD_LANGUAGE to enumerate installed languages and drive translation population.
• DUAL — Used for standard value selection and sequence lookups.

The package also depends on shared infrastructure packages including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTION, which supply the standard API return status, message stacking, and current-user context used throughout the DML routines.

Usage Notes

Because this is a data-maintenance API rather than a runtime business service, it is typically invoked by:

• Concurrent programs used to seed or upgrade marketing list source field definitions during patching and implementation.
• Oracle Forms in the Marketing module that maintain list source field setup data, calling LOAD_ROW or the individual DML routines.
• Custom code and migration scripts that need to programmatically maintain list source field metadata.

The package is not referenced by any other database object except the one dependent package that calls into it, confirming its role as a low-level maintenance utility. Callers should honor the standard API conventions: check the returned status, respect LOCK_ROW before updates, and use LOAD_ROW when the intent is to synchronize rather than insert or update explicitly. Direct DML against the base and translation tables should be avoided in favor of these procedures to preserve multi-language integrity and audit column consistency.