Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

1.

Required Actions in SAP ERP


A Business Add-In (BadI) implementation has been provided to ensure that the mass
synchronization does not generate new GUIDs instead of using the existing GUIDs from the
CRM mapping tables. The BAdI is contained in SAP Note 2283695.
It is imperative that SAP Note 2283695 is implemented before the Customer Vendor
Integration (CVI) is activated and the mass synchronization of customer master or customer
vendor data for the generation of business partners is started. If you start the
synchronization before SAP Note 2283695 has been implemented, the mapping between
business partners that is used in an integration scenario with SAP CRM is irretrievably lost.
A check report has been provided to examine whether the BAdI implementation is available
in your system. In addition, a check report is available that identifies any existing
inconsistencies (if you have been using an active CVI already) or any inconsistencies that
appear after mass synchronization. For more information about the check reports, see SAP
Note 2304337.
2. Required actions in SAP S/4HANA, on-premise edition Simplification List for SAP
S/4HANA 1610 FPS1
Page | 30
Settings for integration of SAP CRM with SAP S/4HANA, on premise-edition 1511 Feature
Package Stack 01
If you want to integrate your SAP CRM system with SAP S/4HANA, on premise-edition
1511 FPS 01, several limitations apply to the exchange of business partner data. For more
information, see SAP Note 2231667. Most of the limitations are resolved with SAP
S/4HANA, on premise-edition 1511 FPS 02.
In the integration scenario with SAP S/4HANA, on premise-edition 1511 FPS 01, you must
make the settings described in SAP Notes 1968132 and 2070408.
Settings for integration of SAP CRM with SAP S/4HANA, on premise-edition 1511 FPS 02,
or a higher FPS
You need to adjust the settings in transaction COM_BUPA_CALL_FU according to SAP Note
2283810.

You might also like