Search Results merge_account

Overview

OKC_HZ_MERGE_PUB is a public PL/SQL API in the Oracle E-Business Suite 12.1.1 and 12.2.2 releases that manages the merge of customers and parties across the Oracle Contracts (OKC) and Oracle Trading Community Architecture (HZ) data models. Its stated purpose in the package header is "Manage customer and party merges." When two duplicate customer records, party records, or customer accounts are consolidated into a single surviving entity, the contracts schema must be updated so that references to the surrendered entity are re-pointed to the surviving entity. This package provides the contracts-side logic for that re-pointing operation.

The package is owned by APPS and is classified as a Public API, meaning it is intended for external invocation by Oracle Applications code, concurrent programs, and customer extensions. It is not a private helper package.

Key Procedures and Functions

The documented package specification exposes exactly one public procedure:

• MERGE_ACCOUNT — The single entry point of the package. It performs the contracts-side processing associated with merging customer accounts and parties. Based on the documented parameter names in the specification (req_id, set_number, and process_mode), the procedure is designed to be driven by a concurrent request identifier, a merge set number that identifies the batch of records being merged, and a processing mode indicator. The parameter list is drawn from the package specification only; callers should not assume additional optional parameters exist.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• HZ_PARTIES, HZ_CUST_ACCOUNTS — the TCA party and customer account entities whose merge is being propagated into contracts.
• HZ_CUSTOMER_MERGE_LOG, HZ_CUSTOMER_MERGE_LOG_S — the TCA customer merge log and its sequence, used to track the merge transaction and its result set.
• RA_CUSTOMER_MERGES — the Receivables customer merge staging table that defines the set of source and target accounts for a merge run.
• OKC_K_HEADERS_B, OKC_K_LINES_B, OKC_K_ITEMS, OKC_K_VERS_NUMBERS, OKC_K_VERS_NUMBERS_H — the contracts header, line, item, and version entities that carry party and account references requiring update.
• OKC_K_PARTY_ROLES_B — contracts party role assignments, the primary touchpoint where a merged party must be replaced by its surviving party.
• OKC_RULES_B — contracts rules that may reference the affected party or account.
• OKE_K_HEADERS — the Oracle Procurement Contracts (OKE) header table, indicating the merge also propagates into procurement contract records.
• JTF_OBJECTS_B, JTF_OBJECT_USAGES — the CRM Foundation object registry and usage tables, used for object-level bookkeeping associated with the merged entities.

Usage Notes

MERGE_ACCOUNT is invoked as part of the customer merge workflow rather than directly by end users. In a typical EBS implementation it is called from the concurrent program that orchestrates the customer/party merge after the TCA and Receivables portions of the merge have staged their data in RA_CUSTOMER_MERGES and the HZ customer merge log tables. The req_id parameter ties the invocation to a specific concurrent request for logging and restartability, set_number identifies the batch of merge records under processing, and process_mode controls the behavior of the run.

Because the package is classified as PUB and is referenced by zero other PL/SQL packages in the documented metadata, it is an integration surface rather than an internal utility. Custom code and extensions that need to synchronize contracts data during a customer merge should call this procedure, supplying a valid concurrent request identifier and the correct merge set number. Calling it independently of the standard merge workflow, or with an incorrect set_number, risks leaving contracts party roles and version records out of synchronization with TCA. As with all public EBS APIs, the procedure should be invoked within the transaction and error-handling framework expected by the merge process, and the merge log tables should be reviewed afterward to confirm the outcome.