FAQs CRM / ERP Integration with SAP Hybris Cloud for Customer SAP Hybris Cloud for Customer PUBLIC

Transcription

1 FAQs CRM / ERP Integration with SAP Hybris Cloud for Customer SAP Hybris Cloud for Customer PUBLIC

2 TABLE OF CONTENTS 1. Error: No IDoc saved in target system (SOAP HTTP) Error: ID mapping for external value <value> of Product Category Key in CRM Suite missing Error: Conversion between UoM missing Error: Conversion between <UoM1> and <UoM2> already exists Error Text: Assigned employee <EMP_NAME> is not valid from <DATE> to <DATE> Error: ID Mapping for External Value ABC of ERP Customer Number Missing Error "Solve Configuration Issue in Code List Mapping for field XYZ with value ABC" Account team employees are removed from account team facet when replicating accounts from ERP to C4C An Account is not replicating from C4C to ERP and no web service message is being generated I have scoped my C4C tenant to block prospects from replicating to ERP, however message ID xxxxxxxxxx shows a prospect leaving C4C Action Create ERP Sales Quote and / or Create ERP Sales Order options are missing in the Opportunity document Action Request External Pricing is missing on a Sales Quote Action Print Preview is not available for a sales quote created in C4C Error while replicating Business Partner from ERP to C4C "Changing the field not possible; field does not match partner category" Error on incoming messages to C4C Exception: Error in message header mapping; agent class is ****"(Applicable to all interfaces) Error while replicating Materials to C4C "Quantity Conversion Change : The Product is used in one or more sales documents"

3 1. Error: No IDoc saved in target system (SOAP HTTP). While replicating from ERP to Cloud for Customer using HCI system, all outbound idocs in ERP are failing with the following error No IDoc saved in target system (SOAP HTTP) Above error means SOAP application processing was started in the target system i.e. in HCI. However, errors occurred in the target system due to unknown reason, which means that IDocs cannot be saved in ERP. Hence for more details about failure please check in target systems error log i.e. HCI 2. Error: ID mapping for external value <value> of Product Category Key in CRM Suite missing. Product category must be replicated first before starting with product replication. 3. Error: Conversion between UoM missing. All UoM available in the payload as part of sales UoM should have a conversion maintained to the base UoM where, in addition, the code list mapping should also be maintained uniquely for these UoM. 4. Error: Conversion between <UoM1> and <UoM2> already exists. This can be due to two causes: 1. The code list mapping for more than 1 UoM in the message is done to the same external UoM code. 2. Code list mapping is missing for one of the UoM 5. Error Text: Assigned employee <EMP_NAME> is not valid from <DATE> to <DATE>. You have scoped the question Can we use business partner service interface to replicate employees from CRM to Cloud for Customer? BP service interface should not be used to replicate employees. Instead, use Employee replication service to replicate employees from ERP/CRM. 6. Error: ID Mapping for External Value ABC of ERP Customer Number Missing This occurs when replicating an account to C4C and the payload contains partner functions which do not exist in C4C yet, the partner function needs to be replicated first then the account. Please review KBA and

4 7. Error "Solve Configuration Issue in Code List Mapping for field XYZ with value ABC". This is due to missing code ABC coming in the payload in the tag XYZ, ABC needs to be mapped to its C4C corresponding value in Business configuration activity Code List Mapping for Integration with External Applications and Solutions. 8. Account team employees are removed from account team facet when replicating accounts from ERP to C4C. This is due to the employees added manually in the account team facet do not exist in ERP then when the next update come from ERP these employees are removed from account team. If you want to keep these employees in the account team you need to perform a mapping change in middleware as described in this blog: 9. An Account is not replicating from C4C to ERP and no web service message is being generated. You need to check if the account is a prospect, if it is, check the tenant's scoping to check to see if prospects are being blocked. If the Account in question is not a prospect, check to see if you have implemented a BADI of type CheckBusinessObjectInstanceProcessIntegrationRelevance and check the filter conditions here. 10. I have scoped my C4C tenant to block prospects from replicating to ERP, however message ID xxxxxxxxxx shows a prospect leaving C4C. If a prospect has ever been replicated to ERP or CRM it will continue to replicate to that system regardless of the scoping options or BADI implementation of CheckBusinessObjectInstanceProcessIntegrationRelevance present on the system, as the system primary goal is to keep all data consistent. 11. Action Create ERP Sales Quote and / or Create ERP Sales Order options are missing in the Opportunity document. You need to scope the relevant question, Ensure that for a particular document type you have enabled these two options under the Custom Status activity of Business Configuration activity Opportunities Ensure that you have created relevant communication arrangement 4

5 12. Action Request External Pricing is missing on a Sales Quote. You need to enable the external pricing for relevant document type under Document Types activity of Sales Quote activity. Ensure that the document affected was created with same document type for which the above option is enabled. 13. Action Print Preview is not available for a sales quote created in C4C. You need to uncheck the flag Direct Customer Acceptance for relevant document type under Document Types activity of Sales Quote activity. 14. Error while replicating Business Partner from ERP to C4C "Changing the field not possible; field does not match partner category" You have created a Business Partner in C4C with Category Code as 2 [Organization/Account] and the incoming message you are sending the category code as 1[Natural Person] or vice versa This is expected behavior in C4C system. Once a business partner is created with Category Code as 1 or 2 - It cannot be changed again. 15. Error on incoming messages to C4C Exception: Error in message header mapping; agent class is ****"(Applicable to all interfaces). You need to check the Sender System and Receiver System available in the incoming message are same as System Instance ID in Communication System and My System ID in Communication Arrangement 16. Error while replicating Materials to C4C "Quantity Conversion Change : The Product is used in one or more sales documents" You are trying to update the quantity conversion on a product - but the product with existing quantity conversion is already used in sales documents. If you still want to change the quantity for this material, you can follow the below mentioned steps after which you can restart the message and it became successful (If the severity is changed to Warning or Information). => Go to Business Configuration work center => Search for and Edit fine tuning activity "Materials" => Select "Message Severity Configuration" link 5

6 2017 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. 6