Search Results oe_merge_headers

Overview

APPS.OE_CUST_MERGE_DATA_FIX is a data-fix package that participates in the Oracle Customer Merge (Customer Merge / Party Merge) process for Oracle Order Management in EBS 12.1.1 and 12.2.2. When duplicate customers or customer sites are merged, the surviving record (the merge target) replaces the duplicate across all transaction tables in the E-Business Suite. Order Management stores ship-to, invoice-to, deliver-to and sold-to customer references directly on order headers and lines, so those references must be repointed from the duplicate to the surviving customer or site. OE_CUST_MERGE_DATA_FIX performs that repointing for the OM tables that the generic Customer Merge process does not automatically update.

The package reads its work list from RA_CUSTOMER_MERGES, the staging table populated by the Customer Merge concurrent programs. Rows marked with PROCESS_FLAG = 'Y' for a specific REQUEST_ID and SET_NUMBER identify the duplicate customer or site identifiers that must be replaced. The package body shown in the ETRM excerpt contains a private routine, OE_MERGE_HEADERS, which selects and locks order headers by SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID and SOLD_TO_ORG_ID before applying the updates. The public entry point MERGE drives this and the remaining sub-routines.

Key Procedures and Functions

• MERGE — the public driver routine that coordinates the full data-fix pass for a given Customer Merge request.
• OE_ORDER_MERGE — performs the core update of order header and line customer/site references to point at the surviving entity.
• OE_ATTACHMENT_MERGE — repoints order attachment rule element references from the duplicate to the merge target.
• OE_DEFAULTING_MERGE — updates defaulting attribute and condition rule definitions whose customer or site criteria reference the duplicate.
• OE_CONSTRAINTS_MERGE — realigns order constraints and validation rules that reference the merged customer or site.
• OE_SETS_MERGE — updates customer item set definitions (OE_SETS, OE_CUST_ITEM_SETTINGS) so item/customer mappings follow the surviving customer.
• OE_DROP_SHIP_MERGE — repoints drop-ship sourcing records to the merge target.
• OE_SHIP_TOLERANCE_MERGE — updates shipping tolerance and preference data keyed to the customer or site.
• OE_HOLD_MERGE — repoints order hold source references from the duplicate to the surviving customer or site.
• OE_WORKFLOW_MERGE — updates workflow and order acknowledgment references that carry customer identifiers.

Tables Accessed

Order data is read and written in OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL; OE_ORDER_LINES_HISTORY preserves the audit trail of line changes. Acknowledgment references are maintained in OE_HEADER_ACKS and OE_LINE_ACKS. Configuration and rule tables include OE_ATTACHMENT_RULE_ELEMENTS, OE_DEF_ATTR_DEF_RULES, OE_DEF_CONDN_ELEMS, OE_PC_VTMPLT_COLS and OE_CONSTRAINTS-related structures. Customer item setup is held in OE_SETS and OE_CUST_ITEM_SETTINGS, drop-ship sourcing in OE_DROP_SHIP_SOURCES, and hold sourcing in OE_HOLD_SOURCES. RA_CUSTOMER_MERGES supplies the duplicate-to-target mapping and the PROCESS_FLAG, REQUEST_ID and SET_NUMBER control columns that scope each run.

Usage Notes

The package is not intended to be called interactively. In normal operation it is invoked from the Customer Merge concurrent program flow, either directly or through the Customer Merge PL/SQL driver, using the request ID and set number of the active merge request. The code uses FOR UPDATE NOWAIT on order headers, so conflicting locks on open orders must be resolved before running the merge; otherwise the routine returns an error. The debug facility (OE_DEBUG_PUB) is controlled by the standard OM debug profile option. Users searching for the related term "ar_updating_table" are typically troubleshooting the Receivables side of Customer Merge; in that context, OE_CUST_MERGE_DATA_FIX is the Order Management counterpart that keeps the om tables synchronized with the AR merge, and it should be run in the same request scope so that order and receivables customer references remain consistent. The ETRM metadata records no packages that reference this package, confirming it is a terminal utility invoked only by the merge infrastructure.