Search Results hz_mixnm_conc_dynamic_pkg

Overview

The APPS.HZ_MIXNM_CONC_DYNAMIC_PKG package is a component of the Oracle E-Business Suite Trading Community Architecture (TCA) and Customer Data Management (CDM) infrastructure. Its name reflects its role as a dynamic processing package for the Mix 'n' Match (MIXNM) name and address cleansing and matching feature, invoked in a concurrent (batch) context. The package provides the dynamic SQL and bulk-processing abstraction layer that supports the loading of party, organization, and person records during import, deduplication, and merge operations performed by the TCA party import framework.

In Oracle EBS 12.1.1 and 12.2.2, the HZ schema hosts TCA entities. The HZ_MIXNM_CONC_DYNAMIC_PKG is classified in ETRM as an OTHER API, meaning it is an internal, implementation-support package rather than a public or documented extension API. It is marked VALID and owned by the APPS schema, which is the standard convention for TCA runtime packages exposed via APPS synonyms.

Key Procedures and Functions

ETRM documents eight procedures within the package. All eight share a common naming pattern built from two dimensions: the entity type (Organization or Person) and the operation mode (Bulk versus Import, with Create and Update variants):

• BULKCREATEORGSST — Handles bulk creation of organization party records (such as in the Mix 'n' Match staging/transform step) for set-based processing.
• BULKUPDATEORGSST — Performs bulk updates against existing organization records during set-based match/merge processing.
• BULKCREATEPERSONSST — Performs bulk creation of person party records in the same set-based context.
• BULKUPDATEPERSONSST — Performs bulk updates of existing person records.
• IMPORTCREATEORGSST — Handles creation of organization records through the import path, typically driven by the party import concurrent program.
• IMPORTUPDATEORGSST — Handles update of organization records during import.
• IMPORTCREATEPERSONSST — Handles creation of person records during import.
• IMPORTUPDATEPERSONSST — Handles update of person records during import.

The "SST" suffix is consistent with set-based (SST = set-based staging table) processing, indicating that these routines operate against collections rather than single-row record operations. The pairing of Bulk and Import variants suggests the package abstracts two distinct invocation paths through a common dynamic execution model.

Tables Accessed

The ETRM metadata for this object does not enumerate referenced tables via APPS synonyms. However, the package's dependency metadata establishes that it is referenced by HZ_IMP_LOAD_CODE_ASSIGNMENTS, HZ_IMP_LOAD_PARTIES_PKG, and HZ_MIXNM_UTILITY. These referencing packages operate over the standard TCA import interface and staging tables (for example, the HZ_IMP_* interface tables and the HZ_PARTIES, HZ_ORGANIZATION_PROFILES, and HZ_PERSON_PROFILES base tables). Because procedures are named for both Create and Update against Organizations and Persons, the package is designed to read from interface/staging structures and write to the corresponding base TCA party tables through dynamic SQL.

The only explicit external dependency recorded is on SYS.STANDARD, which is the standard Oracle PL/SQL package present in every database and does not imply application data access.

Usage Notes

HZ_MIXNM_CONC_DYNAMIC_PKG is an internal implementation package and is not intended for direct customer invocation. It is typically called indirectly from the TCA party import and Mix 'n' Match cleansing flows, notably when the user submits concurrent programs such as "Import Party" or the batch deduplication and merge processes. The "CONC" in the name indicates the package is designed for the concurrent (multi-row, set-based) execution path rather than online single-record processing.

Because it is referenced by HZ_MIXNM_UTILITY and the HZ import loader packages, its procedures are invoked as part of a broader orchestration sequence: utility routines identify candidate records, then the dynamic package executes the appropriate Bulk or Import Create/Update procedure. Customizations should never call these procedures directly; any extension of TCA import behavior should use the documented public TCA APIs and DQM matching rules instead. The package should be treated as read-only infrastructure that is subject to change during patching or upgrade between 12.1.1 and 12.2.2.