Results for “amw_party_merge_pkg”

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

Overview

AMW_PARTY_MERGE_PKG is an Oracle Applications (APPS) schema PL/SQL package that participates in the Oracle E-Business Suite party merge process. It belongs to the ETRM (Enterprise Tax and Regulatory Management / Oracle Fusion Tax and party-related) grouping of AMW modules, and its principal responsibility is to synchronize the AMW regulatory data model when two TCA (Trading Community Architecture) parties are merged. In a party merge, records belonging to a source (or duplicate) party are re-pointed or consolidated into a target (or surviving) party using a defined set of merge rules. AMW_PARTY_MERGE_PKG serves as the AMW-side handler for that event, ensuring that assessments, certifications, constraints, violations, and execution records associated with the losing party are correctly updated or reconciled to the surviving party so that regulatory reporting and compliance history remain intact after the merge. The package is classified as OTHER in the ETRM documentation, indicating it is an internal processing routine rather than a published open interface or a formal public API.

Key Procedures and Functions

The documented package exposes a single procedure, PARTY_MERGE. Its purpose is to carry out the AMW-specific party merge logic. When invoked, it identifies the AMW records tied to the source party and applies the merge rules to move or reconcile them against the target party, updating the affected AMW entities and their associated child rows. The procedure is the sole entry point documented for this package, meaning all AMW party merge handling is centralized in this single call. No parameter lists, overloads, or additional private helpers are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

AMW_PARTY_MERGE_PKG interacts directly with several AMW base tables (referenced through APPS synonyms):

• AMW_AP_EXECUTIONS — stores assessment program execution records; the procedure updates these to reflect the surviving party after a merge.
• AMW_ASSESSMENTS_B — the base table for AMW assessments (regulatory evaluations); affected rows are redirected to the target party.
• AMW_CERTIFICATION_B — the base table for certifications held by a party; these are migrated to the surviving entity during merge.
• AMW_CONSTRAINTS_B — the base table for regulatory constraints attached to a party; requirements are preserved and reassigned.
• AMW_VIOLATIONS — records of regulatory violations; the procedure maintains the compliance audit trail by associating violations with the surviving party.

These tables form the core of the AMW regulatory profile, and the package’s role is to keep them consistent with the TCA party merge outcome.

Usage Notes

AMW_PARTY_MERGE_PKG is not typically invoked directly by end users. It is called as part of the wider Oracle EBS party merge framework, which is driven from the Trading Community Architecture party maintenance forms (for example, the Party Merge concurrent program or the merge region in the party management forms) or by custom code that executes the TCA merge APIs. Because the package is an internal handler, it is invoked indirectly when a merge that affects AMW data is submitted. The metadata notes that AMW_PARTY_MERGE_PKG is referenced by no other packages (0 dependencies), so it does not expose a public surface for reuse; any call should come from the merge orchestration layer. In EBS 12.1.1 and 12.2.2, the package is VALID in the APPS schema and depends only on SYS and STANDARD, meaning it relies on core PL/SQL built-ins rather than other application packages. Developers extending AMW merge behavior should be cautious, since modifying this package can affect data integrity across all five AMW tables it maintains.