Search Results party_merge




Overview
Explore in AI Chat

Overview

AMW_PARTY_MERGE_PKG is an Oracle E-Business Suite package body in the APPS schema that participates in the TCA (Trading Community Architecture) party merge process. It is classified in the ETRM repository as an "OTHER" API and is associated with the Oracle Advanced Managed Warehouse (AMW) product family. Its role is to re-point foreign key references held by AMW tables whenever two party records are merged, so that transactional and reference data owned by the "from" party is reassigned to the surviving "to" party without breaking referential integrity.

Party merge is initiated from the standard TCA party merge infrastructure, which walks the registry of registered entities and invokes each subscribing package's merge handler. AMW_PARTY_MERGE_PKG registers itself as one such handler. When the merge engine reaches an AMW entity, the package is called through its single documented procedure, PARTY_MERGE, and performs the necessary UPDATE statements against the AMW tables that carry party, party site, or user identifiers.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure for this package, PARTY_MERGE. It is the entry point invoked by the TCA merge framework rather than by application code directly. Its documented parameters include the entity name, the "from" primary key, an outbound "to" primary key, the "from" and "to" foreign key identifiers, the parent entity (HZ) name, the batch identifier, the batch party identifier, and an outbound return status.

The procedure returns status through the standard FND_API convention, initialising the return status to FND_API.G_RET_STS_SUCCESS and raising failure only when an error occurs. No other procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

The package performs targeted UPDATE statements against five AMW base tables, keyed by the entity name passed in by the merge engine:

Each branch is conditioned on the p_entity_name value, so the procedure updates only the table corresponding to the entity currently being merged. The referenced objects are resolved through APPS synonyms.

Usage Notes

AMW_PARTY_MERGE_PKG is not a general-purpose API. It is invoked internally by the TCA party merge concurrent program and its associated merge orchestration logic, which supplies the entity name, batch identifiers, and from/to key values. It is referenced by zero other packages, confirming its role as a leaf subscriber rather than a shared utility.

Custom code should not call PARTY_MERGE directly; instead, AMW entities should be registered with the TCA party merge registry so the framework invokes this package automatically. Administrators should treat it as part of the standard AMW/TCA merge surface and validate AMW assessment, constraint, certification, violation, and AP execution data after any party merge run to confirm that ownership references were reassigned correctly.