FAQs Data Cleansing SAP Hybris Cloud for Customer PUBLIC

Transcription

1 FAQs Data Cleansing SAP Hybris Cloud for Customer PUBLIC

2 TABLE OF CONTENTS FAQS DATA CLEANSING What is Data Cleansing? How do you scope this activity in your C4C system? Is it possible to delete a merged account? How many Business Partners can you merge at a time? Is it possible to avoid copying relations Account Team (Party Role) after merge? Is it possible to transfer visits with surveys while performing account merge? Why does address of duplicate account is copied with surviving account during account merge? Does Notes and Attachments delete in Slave/Duplicate Account? Can you merge Accounts which belong to same hierarchy? Is it possible to merge obsolete Individual Customer accounts? Is it possible to include Extension Fields in Account Merge? Is there an event that is triggered because of merge account action, that can be caught from SDK? Why is Initiate Merge option is disabled for Duplicate Accounts? What are the different status of Account Merge process? Can you merge Business Partner with role Prospect to role Customer? Is it possible to delete a Merge Instance? Does Odata Service support Account Merge? Which A2X Operations are supported for Account Merge? What is the system behavior for Addresses after Account Merge? Do Account Merge support Notes and Attachments?...6 2

3 FAQS TOPIC NAME 1. What is Data Cleansing? Data Cleansing is also known as Account Merge, where two or three Accounts are merged to create one Master Account. 2. How do you scope this activity in your C4C system? You can scope below Question in Business Configuration: 1. Go to Business Configuration work center. 2. Select Implementation Projects view. 3. Select Edit Project Scope. 4. Go to Questions. a. General Business Partner Data b. Handling of Business Partners c. Check Question: Do you want to enable account merge? 3. Is it possible to delete a merged account? No, we cannot delete a merged account once created in the application. 4. How many Business Partners can you merge at a time? You can merge two or three Business Partners at a time. 5. Is it possible to avoid copying relations Account Team (Party Role) after merge? No, it is not possible to avoid copying relations Account Team (Party Role) after merge. Case1: When there is a Main user for Account Team in surviving account and no Main user in the duplicate account: Ex - When the option Main while adding Account Team (Party Role) in Cust_A is selected and Cust_B is not selected; the system shows Surviving and Duplicate Account Managers details in the merged account. This is expected system behavior. Case2: When there is a Main user in each account: When the option Main while adding Account Team (Party Role) in Cust_A as well as Cust_B is selected. Again, both the Surviving Account Manager and the Duplicate Account Manager details shows in the merged account, keeping Surviving Account Manager as Main. 6. Is it possible to transfer visits with surveys while performing account merge? No, it is not possible to transfer visits with surveys while performing account merge. If you open a visit with a survey added, you will see that it is not possible to change the account. It is not possible to change the account assigned to a visit if the visit has a task or a survey added to it. It is not possible to change the account from the UI as well. 3

4 Once a worklist (Tasks & Surveys) is generated for a Visit, the account for the Visit cannot be changed as the worklist is tied completely to the designated account. This is the expected behavior in C4C and works as designed. 7. Why does address of duplicate account is copied with surviving account during account merge? This is the standard behavior, during the merge process there is a union of addresses of the merged accounts. As a 'Union' operator is used, which behaves as an 'AND' operator hence, both the records are available with surviving account. Though the selected account during merge is the one which appears as a main account. So, both the records will appear in surviving record as per the standard behavior. 8. Does Notes and Attachments delete in Slave/Duplicate Account? No, Notes and Attachments remain available with Duplicate Account after merge. Same holds good for the Account Team of Slave Account. 9. Can you merge Accounts which belong to same hierarchy? No, you cannot merge Corporate Accounts which are in same hierarchy. Merge of Corporate Accounts is allowed only when they belong to different hierarchy. 10. Is it possible to merge obsolete Individual Customer accounts? No, it is not possible to merge the obsolete Individual Customer account. When you create a New merge account, and try to select the obsolete Individual Customer account from the value selection drop down list, obsolete record is not present during selection. 11. Is it possible to include Extension Fields in Account Merge? No, Extension Fields and PDI developed fields are not supported for Account Merge. 12. Is there an event that is triggered because of merge account action, that can be caught from SDK? No event is not triggered because of Account Merge action that could be caught from SDK. 13. Why is Initiate Merge option is disabled for Duplicate Accounts? Select the duplicate accounts and then you can see that the initiate Merge gets enabled. 14. What are the different status of Account Merge process? Below are the statuses for Account Merge: 1. Not Started 2. Merge In Process 3. Merge Failed 4. Merge Completed - Realignment In Process 4

5 5. Merge Completed - Realignment Failed 6. Completed 15. Can you merge Business Partner with role Prospect to role Customer? Yes, BP of role customer can be merged with BP of role prospect. But prospect cannot be the surviving record. 16. Is it possible to delete a Merge Instance? It s possible to delete a merge instance if it s in status Not Started 17. Does OData Service Support Account Merge? Yes, OData service for the creation of Account Merge Instance. However, this OData cannot be used to initiate the merge Service Name: businesspartnermerge Service Metadata Link: Following features are supported by the OData service: It allows to create merge instances with 1 master BP and up to 2 slave BPs. It is possible to create merge instances by providing External ID of BPs. The status of the merge instance is automatically set to "Not Started" and it is not possible to change the status. The BPs can be of the 3 types we support - Account, Individual Customer and Contact person. Action "Initiate merge" is not supported. 18. Which A2X Operations are supported for Account Merge? Communication Scenario: External Business Partner Merge. Below are the Operations: 1. A2X ManageBusinessPartnerMergeIn operation MaintainBundle is used to create an instance of merge 2. A2X ManageBusinessPartnerMergeIn operation Initiate is used to schedule the merge 3. A2X QueryBusinessPartnerMergeIn operation FindByIdentification is used to check progress/status of merge process 19. What is the system behavior for Addresses after Account Merge? Address of slave account will not be deleted. If the UI is used for Merge, then user will see the main address of all the BPs and choose which one should be main address of master account. All other addresses of the slave account will be copied to the master account. 5

6 If the A2X is being used for merge, then the main address in the master account will remain the main address post merge. In case no address information is maintained in the master account, the main address of the slave account will be marked as the main address in the master account post merge. Example of merge: Assume BP1 has addresses - BP1_Add_1 (main) & BP1_Add_2 Assume BP2 has addresses - BP2_Add_1 (main) & BP2_Add_2 Assume BP3 has addresses - BP3_Add_1 (main) & BP3_Add_2 During merge user chooses BP1 as master but BP2_Add_1 as main address from UI. Then after merge BP1 will have following addresses BP2_Add_1 (main), BP1_Add_2, BP2_Add_1, BP2_Add_2, BP3_Add_1, BP3_Add_2. As you can see the same address appears twice. This happens because first the contents of address BP2_Add_1 is copied into BP1_Add_1 and then all the addresses are merged. 20. Do Account Merge Support Notes and Attachments? All the attachments and notes of the slave account will be copied to master account. They will not be deleted in the slave account. 6

7 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See for additional trademark information and notices.