Transactions Workbench Issue: After Merge a Transaction, Sharing the Same Site of Another Operating Unit, Has Incorrect Operating Unit for the BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID and SOLD_TO_CUSTOMER_ID (Doc ID 1904441.1)

Last updated on OCTOBER 15, 2015

Applies to:

Oracle Receivables - Version 12 and later
Information in this document applies to any platform.

Symptoms

An Account Merge was requested for a specific Operating Unit.
It has moved the BILL_TO_CUSTOMER_ID, on transactions belonging to another Operating Unit (the one that was sharing same site before the merge).

After the customer merge, the BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID and SOLD_TO_CUSTOMER_ID, in the header level, are not updated to the new value.
They are still showing the old value only.

Whereas, the following are populated with the new value (the correct one):

1. RA_CUSTOMER_TRX_LINES_ALL.SHIP_TO_CUSTOMER_ID
2. AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_ID
3. AR_DISTRIBUTIONS_ALL.THIRD_PARTY_ID
4. ZX_LINES_DET_FACTORS.BILL_THIRD_PTY_ACCT_ID
5. ZX_LINES_DET_FACTORS.SHIP_THIRD_PTY_ACCT_ID
6. XLA_AE_LINES.PARTY_ID

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms