This chapter covers the following topics:
Use the Customer Merge feature to consolidate any duplicate customers or transfer site use activity from a customer or site that is no longer active to a new customer or site.
After the merge completes, all activities previously associated with the old customer or site are associated with the new customer or site. Activities include invoices, debit memos, commitments, credits, receipts, adjustments, quotes, orders, and service contracts. You can track the progress of a merge request through its status. For a detailed conceptual explanation of merging customer sites or customers, refer to Merging Customers, Oracle Trading Community Architecture User Guide. Customer Merge in Oracle Customer Data Librarian has the same functionality as Customer Merge in Oracle Trading Community Architecture, plus the additional ability to:
Assign a data steward to an account merge request.
Reject account merge requests.
Data stewards can perform the following functions:
Create account merge requests.
Submit account merge requests.
Reject account merge requests to withdraw the submission of the merge or if the approval to submit the merge is denied.
Search for and view account merge requests.
Assign a data steward to an account merge request.
Use the Customers Online Data Librarian or Customers Online Data Librarian Superuser responsibility to access the Oracle Customer Data Librarian Home page. Select the Data Quality tab, then the Account Merge Requests subtab.
In the Merge Request Queue page, click Create Account Merge.
In the Create Merge Request page, select the following:
Customer Type: the type of customer you are merging, either an organization or person.
Operating Unit: the operating unit in which the customer you want to merge has account sites.
Delete After Merge: select this option to delete the duplicate customer account after merging.
Merge Reason: De-duplication or merger.
Priority: assign a processing priority for the merge process.
Context Value: optionally, enter a descriptive flexfield value at the merge request header level.
In the Duplicate region and then again in the Master region, enter the following:
Customer Name: search for, then select a customer name from the list of values.
Account Number: search for, then select one of the customer's account numbers from the list of values.
Tip: Search for either the Customer Name or Account Number. Once you select one of these field's values, the other field's value defaults.
Click Next .
To map addresses between different accounts
Follow these steps if you selected different account numbers. Otherwise, skip ahead to "To map addresses within the same account".
In the Address Mapping page, all duplicate usage sites associated with the duplicate account number selected appear in the Duplicate table. You can choose to create these duplicate usage sites within the master account number or you can merge the duplicate usage site data to an existing master usage site of the same usage type (for example, merge duplicate Ship To site data into a master Ship To site).
For more information, refer to Merging Different Customers, Oracle Trading Community Architecture User Guide.
In the Address Mapping page, evaluate which duplicate account number usage sites you want to create within the master account number. If you want to merge any duplicate account number usage site data into existing master usage sites, then deselect the Create Same Site check box for that usage site.
The corresponding master Address field clears.
In the master Address field, click the search icon, then search for and select an existing master address with the same usage type.
Optionally, in the DFF field, select a descriptive flexfield value for the address to merge.
Choose one of the following actions:
Cancel: Click Cancel to cancel the customer merge request.
Save: Click Save to save the customer merge request and remain in the Address Mapping page.
Submit Merge: Click Submit Merge to save and submit the customer merge request for immediate processing.
Apply: Click Apply to save the customer merge request and return to the Merge Request Queue page.
To map addresses within the same account
Follow these steps if you selected the same account numbers. For more information, refer to Merging Sites for the Same Customer, Oracle Trading Community Architecture User Guide.
In the Address Mapping page, duplicate Address field, click the Search icon. Search for and select the address you want to merge (the site you plan to close).
In the master Address field, click the Search icon. Search for and select the address to which to merge (the site remaining open).
Action: Add as many duplicate/master address pairs as you want to merge within this account number.
Optionally, in the DFF field, select a descriptive flexfield value for the address to merge.
Choose one of the following actions:
Cancel: Click Cancel to cancel the customer merge request.
Save: Click Save to save the customer merge request and remain in the Address Mapping page.
Submit Merge: Click Submit Merge to save and submit the customer merge request for immediate processing.
Apply: Click Apply to save the customer merge request and return to the Merge Request Queue page.
Use the Customers Online Data Librarian or Customers Online Data Librarian Superuser responsibility to access the Oracle Customer Data Librarian Home page. Select the Data Quality tab, then the Account Merge Requests subtab.
In the Merge Request Queue page, click the Map icon for the merge request.
In the Merge Request Overview page, click the Reject Request button.
A warning message is displayed to confirm the reject action.
To map merge requests
You can update the address mapping for any merge request with a status of Saved.
In the Merge Request Queue page, click the Map icon for the merge request.
In the Merge Request Overview page, click Next.
In the Address Mapping page, you can update the duplicate and master addresses, the DFF, or remove an address mapping.
For detailed address mapping information, refer to To map addresses with different accounts or To map addresses within the same account.
By default, the user creating the merge request is assigned as the data steward. However, the data steward can assign the merge request to another data steward or assign it to a supervisor data steward to ensure correctness of the merge request prior to submission. Optionally, use the HZ: Default Data Librarian profile option to specify a default data steward. Refer to Party Merge Deployment Category, Oracle Trading Community Architecture Administration Guide.
Use the Customers Online Data Librarian or Customers Online Data Librarian Superuser responsibility to access the Oracle Customer Data Librarian Home page. Select the Data Quality tab, then the Account Merge Requests subtab.
In the Merge Requests Queue page, select the merge requests you want to assign to a data steward and click Assign.
Note: You can select only the merge requests for sites having operating units that are accessible to the current user. Merge requests that are not assigned to any user are not displayed.
In the Assign Merge Requests page, select the name of the assignee. Leave the Assignee field blank to merge requests without an assignment.
Optionally, click the Remove from Set icon for a merge request to remove the request from a merge batch.
Click Apply.
To search for and view merge requests
Navigate to the Merge Request Queue page using a Customer Data Librarian responsibility to access the Oracle Customer Data Librarian Home page. Select the Data Quality tab, then the Account Merge Requests subtab.
In the Merge Request Search region, enter a value in one or more of the following search fields:
Merge ID: the merge ID number assigned to the duplicate/merge pair after the completed merge.
Request ID: the concurrent request ID for the merge batch.
Status: the merge request status. Select one of the following statuses:
Failed
In Progress
Pending
Saved
Completed
Rejected
Operating Unit: the operating unit in which the customer has account sites.
Master Customer: the customer who stores the merged data upon completion.
Master Account Number: the account number of the master customer.
Duplicate Customer: all transactional data is removed from this customer upon the merge completion.
Duplicate Account Number: the account number of the duplicate customer.
Assignee: the data steward who ensures correctness of the merge request prior to submission.
Priority: the processing priority when creating merge batches.
Click Go.
A list of merge requests that meet your search criteria appears. You can perform the following actions on merge requests with a Saved status:
For merge requests with any other status, you can only assign a different data steward to the merge requests.