Search Results hz_imp_load_ssm_matching_pkg




Overview
Explore in AI Chat

Overview

HZ_IMP_LOAD_SSM_MATCHING_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Trading Community Architecture (TCA) bulk import and batch matching infrastructure. Its primary responsibility is to orchestrate the matching phase of the Supplier/Student/Party (SSM) import load process, in which staged interface records are compared against existing master records in the TCA registry in order to detect and resolve duplicates before the records are committed to the production tables.

During a batch import, entity data such as parties, addresses, contact points, contacts, contact roles, credit ratings, code assignments, financial reports, financial numbers, relationships, and address uses are loaded into staging interface tables. Before these staged rows can be promoted to their destination tables, the import process must determine whether each incoming entity already exists in the registry. This package performs that matching logic, evaluating each staged record against the matching rules and scoring attributes defined for the relevant entity type, and recording the outcome so that the calling load process can apply the appropriate create or update decision.

Key Procedures and Functions

The package exposes a set of matching procedures, each dedicated to a specific TCA entity type, and each sharing a common invocation pattern driven by batch and operating unit context along with rerun and batch mode controls.

  • MATCH_PARTIES — Processes party (the root entity) matching first. Because the party is the root entity from which the other entities descend, it is the first entity processed in the matching sequence.
  • MATCH_ADDRESSES — Processes the address entity, the second entity to be processed in the sequence.
  • MATCH_CONTACT_POINTS — Performs matching on contact point records associated with the staged parties.
  • MATCH_CREDIT_RATINGS — Matches credit rating records. This procedure includes a definition start time parameter in addition to the standard batch and rerun controls.
  • MATCH_CODE_ASSIGNMENTS — Matches code assignment records held in the classification and code assignment staging area.
  • MATCH_FINANCIAL_REPORTS — Matches financial report records for the staged parties.
  • MATCH_FINANCIAL_NUMBERS — Matches financial number records associated with the staged parties.
  • MATCH_RELATIONSHIPS — Matches party relationship records between the staged entities and existing parties.
  • MATCH_CONTACTS — Matches contact records. This is the procedure most directly associated with the search term "match_contacts" and is the entry point invoked when contact-level deduplication is required during the batch load.
  • MATCH_CONTACTROLES — Matches the roles assigned to contacts, ensuring role assignments are reconciled against existing contact role data.
  • MATCH_ADDRUSES — Matches address use records, linking staged addresses to their intended usage context.

Each procedure accepts a batch identifier, an operating unit indicator, a from/to operating system range, actual content source, rerun flag, and batch mode flag, allowing the process to be scoped to a specific batch and to be safely re-executed.

Tables Accessed

The package reads and writes the TCA staging and master tables through APPS synonyms. The staging side includes HZ_IMP_ADDRESSES_INT, HZ_IMP_ADDRESSES_SG, HZ_IMP_ADDRESSUSES_INT, HZ_IMP_ADDRESSUSES_SG, and HZ_IMP_CLASSIFICS_INT, which hold the imported records awaiting matching. The master side includes HZ_CONTACT_POINTS and HZ_CONTACT_POINTS_S, HZ_CREDIT_RATINGS and HZ_CREDIT_RATINGS_S, HZ_CODE_ASSIGNMENTS and HZ_CODE_ASSIGNMENTS_S, HZ_FINANCIAL_NUMBERS and HZ_FINANCIAL_NUMBERS_S, and HZ_FINANCIAL_REPORTS and HZ_FINANCIAL_REPORTS_S. The _S synonyms reference the TCA secure (multi-org) versions of these objects, reflecting that matching must respect operating unit security context passed into each procedure.

Usage Notes

HZ_IMP_LOAD_SSM_MATCHING_PKG is not typically called directly by end users. It is invoked as part of the batch import load flow, generally from concurrent programs or from other packages that drive the TCA bulk import process. The metadata records three other packages that reference this package, confirming that it sits within a layered import framework in which a controlling load program calls the matching procedures in sequence — beginning with parties, then addresses, and proceeding through the dependent entities. The common parameter convention (batch identifier, operating unit, from/to OSR, rerun flag, batch mode flag) allows the process to be restarted safely after failure and to be limited to a defined range of operating system references. Customizations that require contact-level or party-level deduplication during import should invoke the appropriate matching procedure through the standard batch driver rather than calling the package directly, to preserve the ordering and transactional integrity of the import.