Results for “oks_party_merge_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKS_PARTY_MERGE_PKG is a service-oriented PL/SQL package that implements the Oracle E-Business Suite (EBS) party merge integration for the Service (OKS) module. It is registered against the Trading Community Architecture (TCA) party merge framework so that Order Capture / Service authoring data remains consistent when two trading community parties are merged in the Customer relationship management (CRM) layer. Concretely, the package substitutes the "from" party identifier with the "to" party identifier in the OKS-owned columns that hold a party foreign key, thereby preserving billing profile, defaulting rule, service availability exception, and qualifier associations after a merge.

The header comment ($Header: OKSPYMGB.pls 120.0 … noship $) and the use of arp_standard.profile values for user and login auditing reflect the standard EBS API and audit conventions. The package body begins with constants for the API name (OKS_PARTY_MERGE_PKG), user identifier (g_user_id), and login identifier (g_login_id), and each callback procedure returns a status compliant with FND_API, namely FND_API.G_RET_STS_SUCCESS on completion.

Key Procedures and Functions

The body exposes four documented callback procedures, each corresponding to a single registrable entity in the HZ_MERGE_DICTIONARY.

• OKS_BILLING_PROFILES — Handles the merge of the OKS_BILLING_PROFILES_B billing profile entity. If the merge is a site merge (p_from_fk_id = p_to_fk_id) the procedure returns the identifier unchanged and performs no work. Otherwise it updates OKS rows where owned_party_id1 matches the old party, setting it to the new party and stamping audit columns and an incremented object_version_number. It uses arp_message to record the name and row count of the update.
• OKS_DEFAULTS — Performs the analogous merge for OKS_K_DEFAULTS, repointing party-keyed defaulting records from the source party to the target party.
• OKS_SERVICE_EXCEPTS — Performs the merge for OKS_SERV_AVAIL_EXCEPTS, repointing service availability exception rows to the surviving party.
• OKS_QUALIFIERS — Performs the merge for OKS qualifier records, repointing the qualifying party reference to the surviving party.

All four procedures accept the standard HZ_MERGE_DICTIONARY signature used by TCA merge callbacks: p_entity_name, p_from_id, x_to_id (in out), p_from_fk_id, p_to_fk_id, p_parent_entity_name, p_batch_id, p_batch_party_id, and x_return_status (out). Parameter lists are not reproduced here beyond what the source excerpt documents.

Tables Accessed

The package operates against a small, well-defined set of objects accessed through APPS synonyms.

• OKS_BILLING_PROFILES_B — Reads and updates the preferred billing profile rows; the owned_party_id1 column carries the merged party key. Audit and version columns (last_update_date, last_updated_by, last_update_login, object_version_number) are maintained during the update.
• OKS_K_DEFAULTS — The target of OKS_DEFAULTS; holds party-scoped defaulting information.
• OKS_SERV_AVAIL_EXCEPTS — The target of OKS_SERVICE_EXCEPTS; holds party-scoped service availability exceptions.
• HZ_MERGE_DICTIONARY, HZ_MERGE_PARTIES, HZ_MERGE_BATCH, HZ_MERGE_PARTY_DETAILS — TCA framework tables that supply merge metadata and parameter types, and that record the merge batch and party detail context in which these callbacks run.

Usage Notes

OKS_PARTY_MERGE_PKG is not called directly by users. It is invoked by the TCA party merge engine when a party merge is executed from the Customers form or through the party merge concurrent programs, which consult HZ_MERGE_DICTIONARY to locate the OKS-owned entities and then call the registered procedure for each. The package is referenced by zero other packages, confirming its role purely as a merge handler rather than a shared utility.

Because the callbacks run inside a merge batch, they participate in that transaction and honour the framework's commit and rollback boundaries. The site-merge short-circuit in OKS_BILLING_PROFILES means no updates occur when the from and to party identifiers are equal. Customisations should not call these procedures directly; any party-keyed OKS data added by extensions must be registered through the merge dictionary and handled by a callback that mirrors this package's update pattern, including audit column maintenance and FND_API status returns. The package is compatible with both EBS 12.1.1 and 12.2.2, where the underlying OKS and HZ schemas are unchanged.