Select two features regarding the completion of a successful customer merge in Oracle Receivables that support ongoing customer data cleansing efforts after go-live. (Choose two.)

The correct answer is D. Duplicate customers are repointed to the surviving customer after the customer merge process. E. Customer sites associated with the old customer or site are associated with the new customer. In Oracle Receivables, a successful customer merge repoints duplicate customer records to the surviving customer (D) and reassigns customer sites from the old customer or site to the new customer (E) - both actions directly support ongoing data cleansing by consolidating…

Customers

Question

Options

ACustomer merge activity can be reversed after the merge process.
BBank details for the merge-from customer remains available after the merge process.
CDuplicate parties are re pointed to the surviving party after the customer merge process.
DDuplicate customers are repointed to the surviving customer after the customer merge process.
ECustomer sites associated with the old customer or site are associated with the new customer
FCustomer transactions or audit transactions details for the merge-from customer remain available

How the community answered

(38 responses)

A
5% (2)
B
5% (2)
C
3% (1)
D
87% (33)

Explanation

In Oracle Receivables, a successful customer merge repoints duplicate customer records to the surviving customer (D) and reassigns customer sites from the old customer or site to the new customer (E) - both actions directly support ongoing data cleansing by consolidating records rather than deleting them, preserving history while eliminating duplicates.

Why the distractors are wrong:

A is incorrect - customer merges are irreversible once completed; there is no undo/reverse function.
B is incorrect - bank details for the merge-from customer are not retained after the merge; they are handled as part of the merge process.
C is a party-level concept (TCA/HZ schema), not the customer-level merge feature being tested here; the question is specifically about Oracle Receivables customer merge, not party deduplication.
F is a partial distractor - while transaction history is accessible, it is not listed as a core feature of the merge process itself in this context.

Memory tip: Think "Duplicate customers get Directed to the survivor, and Sites get Swapped" - both D and E describe redirection actions (repointing records), which is the core design principle of Oracle's merge: nothing is deleted, everything is consolidated.

Topics

#Customer Merge#Data Cleansing#Customer Consolidation#Duplicate Party Management

Community Discussion

No community discussion yet for this question.

Full 1Z0-518 Practice