Search Results create_mapping

Overview

The APPS.AMS_LIST_SRC_MAPPING package body is a member of the Oracle Marketing (AMS) module of Oracle E-Business Suite. Its principal business function is to create and persist the mapping between an external import source and the internal list source structures used by Oracle Marketing's list management and import facilities. In practical terms, the package translates the columns supplied by a customer-facing import file (or source definition) into the corresponding source type and source field records recognized by the AMS list model, so that imported records can be staged, validated, and committed against the correct target fields.

The package is classified as an OTHER API in ETRM, indicating it is not a public, fully versioned interface in the same sense as the FND_API-compliant public APIs, but it is nonetheless constructed in the standard API idiom: it accepts p_api_version, p_init_msg_list, p_commit, and p_validation_level inputs and returns x_return_status, x_msg_count, and x_msg_data outputs, with the caller-visible identifiers returned through an OUT NOCOPY parameter. The header history dates the package to 2002 and records enhancements including the addition of "Import_Type" support and corrections delivered against bugs 2502991 and 2441049 for both XML and non-XML import paths.

Key Procedures and Functions

The ETRM metadata documents a single procedure, CREATE_MAPPING. It is the entry point for establishing a list source mapping. Its purpose is to allocate or retrieve a list source type identifier, create the corresponding list source field records, and record the column-level mapping between the supplied source fields and the intended target fields for a given import list header. The procedure works against caller-supplied collections of source and target field names, and it returns the newly created source type identifier to the caller through an OUT NOCOPY parameter.

Internally the procedure declares the API name and version constants as create_mapping and 1.0. It obtains sequence values from AMS_LIST_SRC_TYPES_S and AMS_LIST_SRC_FIELDS_S, and it uses internal cursors to resolve the source column name from AMS_LIST_SRC_FIELDS_VL ordered by LIST_SOURCE_FIELD_ID, the source type code from AMS_LIST_SRC_TYPES_VL, and the import type from the import list header. No other documented procedures or functions are exposed by this package body.

Tables Accessed

The package reads and writes a focused set of AMS base and translation tables through APPS synonyms:

• AMS_LIST_SRC_TYPES, AMS_LIST_SRC_TYPES_S, and AMS_LIST_SRC_TYPES_TL — the source type definition, its surrogate key sequence, and its translated (language) descriptions.
• AMS_LIST_SRC_FIELDS, AMS_LIST_SRC_FIELDS_S, and AMS_LIST_SRC_FIELDS_TL — the source field definition, its sequence, and translated field text; the view AMS_LIST_SRC_FIELDS_VL supplies source column names.
• AMS_IMP_LIST_HEADERS_ALL — the import list header that identifies the import context, including the import type flag consumed by the procedure.
• AMS_IMP_COL_MAPPING — the column mapping table where the resolved source-to-target associations are persisted.
• FND_LANGUAGES, DUAL, DBMS_UTILITY, and PLITBLM — supporting access to installed languages, sequence selection, message formatting/stack utilities, and PL/SQL table (index-by table) handling.

Usage Notes

AMS_LIST_SRC_MAPPING.CREATE_MAPPING is typically invoked from Oracle Marketing setup or import flows rather than called directly by end users. It is reached from the list import setup forms and from the concurrent processing that prepares import mappings, and it is referenced by one other package in the documented call graph, indicating it occupies an inner layer of the import infrastructure. Callers should pass a valid import list header identifier, the source and table names, and collections of source and target fields, and should honor the standard API contract by checking x_return_status and inspecting x_msg_data on failure. Because the procedure can allocate new source type and field identifiers, it should be invoked within a controlled transaction where the mapping records and the returned source type identifier are committed together, using p_commit as appropriate. Custom integrations requiring only read access to existing mappings should query the underlying views directly rather than invoking this creation routine.