Search Results process_element_success

Overview

APPS.AMS_LIST_IMPORT_PUB is a public PL/SQL package in the Oracle E-Business Suite marketing (AMS) and Trading Community Architecture (TCA) product family. Its purpose is to import external list and customer data — sourced from flat files, XML documents, or third-party data providers — and to materialize that data as TCA customer records in the HZ schema. The package header comment states that it creates organization, person, party relationship, organization contact, location, party site, email, and phone records for both B2B and B2C customer types by calling TCA APIs.

For B2B customers the package orchestrates creation of an organization, a person, a party relationship, the party for that relationship, an organization contact, a location, a party site, and contact points. For B2C customers it creates a person, a location, a party site, and contact points. The package is declared AUTHID CURRENT_USER, so it executes under the privileges of the invoking session rather than the definer. The packaged header carries the revision marker amspimls.pls 115.13 2003/12/23, indicating that the procedural logic is stable and predates the 12.1.1 and 12.2.2 releases; both releases inherit essentially identical behavior.

Key Procedures and Functions

• CREATE_CUSTOMER — The primary entry point, and the object most often sought by name. It creates a new customer together with the associated entities described above. Its documented parameters include p_api_version, p_init_msg_list, and record-type inputs for the party (p_party_rec), organization (p_org_rec), person (p_person_rec), location (p_location_rec), party site (p_psite_rec), contact point (p_cpoint_rec), email (p_email_rec), phone (p_phone_rec), and organization contact (p_ocon_rec). It returns x_party_id for the created party and x_new_party to indicate whether the party was newly created or matched an existing record.
• UPDATE_RENTED_LIST_PARTY — Updates party records that originate from rented or third-party lists, reconciling imported attributes with existing TCA data.
• ERROR_CAPTURE — Records import failures and validation errors for later review and reprocessing.
• PROCESS_ELEMENT_SUCCESS — Processes an imported element that was validated and loaded successfully.
• PROCESS_ELEMENT_DUPLICATE — Handles imported elements identified as duplicates of existing parties, supporting deduplication logic.

Tables Accessed

The package reads staging and control tables via APPS synonyms: AMS_IMP_DOCUMENTS, AMS_IMP_LIST_HEADERS_ALL, AMS_IMP_SOURCE_LINES, and AMS_IMP_XML_ELEMENTS hold the inbound import payload. AMS_LIST_IMPORT_ERRORS and AMS_LIST_IMPORT_ERRORS_S store captured errors, while AMS_PARTY_SOURCES and AMS_PARTY_SOURCES_S track the source list attribution for each party. On the TCA side it writes HZ_PARTIES, HZ_PARTIES_S, HZ_LOCATIONS, HZ_CONTACT_POINTS, HZ_CONTACT_NUMBERS_S, HZ_ORG_CONTACTS, and HZ_ORG_CONTACTS_S.

Usage Notes

AMS_LIST_IMPORT_PUB is invoked during list import processing, typically from the Oracle Marketing list import concurrent programs and related list management forms, and it is referenced by five other packages in the instance. Because CREATE_CUSTOMER wraps TCA APIs, custom integrations should follow the standard API conventions: pass p_api_version, respect p_init_msg_list, check x_return_status and the message stack, and commit only after successful completion. Direct DML against the underlying HZ tables should be avoided in favor of this package so that TCA integrity rules and source attribution are preserved.