Payment Records Are Getting Orphaned When Merging Contact Records (Doc ID 2922124.1)

Last updated on JANUARY 23, 2023

Applies to:

Symptoms

When merging Contact records, Payment records are getting orphaned if the Payment records were associated to the Contact victim record.

The issue can be reproduced at will with the following steps:

1. Navigate to the 'Contact List View' (Contact > Contact List).

2. Create two Contact records, Contact1 and Contact2. Note the RowIds. In this example, Contact1='1-ROWID1' and Contact2='1-ROWID2'.

3. Navigate to the 'Quote - Payment View' (Quotes > Quote List > Payments).

4. Create a Quote and Payment, and associate Contact1 to the Payment. Do the same for Contact2.

5. Query the database with the following SQL and note similar output:

6. Navigate back to the 'Contact List View' and perform a merge. Select the Contact2 record first (victim record), then press Ctrl and select the Contact1 record (surviving record).

7. Go to application menu: Edit > Merge Records. In the dialog box, click 'OK' to proceed with the merge. Only Contact1 will remains as Contact2 has been merged into the record.

8. Execute the above SQL again and note that the output is still the same. Payment record with ROW_ID '1-PAYID2' is still pointing to CON_ID '1-ROWID2', which is associated with Contact2 but no longer exist.

The expected result is that all child records should be reassociated from the victim to the surviving record. In this case, CON_ID should be updated to '1-ROWID1' for Payment '1-PAYID2'. Expected output is the following:

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.