In the S/4 HANA client system, check whether there is an (active) BAdI implementation called MDG_BS_KEY_MAP_HANDLER_CUSTOM for the enhancement implementation MDG_BS_CUSTOM_SI_ERP of the enhancement spot MDG_BS_SUPPLIER_SI.Standard BADI Availability in SAP S/4 HANA and SAP CRM (ID Matching API is called internally from the BADI Code) Detailed view of Service Flow and Service call between SAP MDG, SAP S/4 HANA and SAP CRM A CRM System is connected in the Landscape with SAP S/4 HANA and SAP MDG for Master Data (BP) replications.Ī typical Business Partner flow looks like below with all the SOA based services in place.If message fails in target systems the CRM Tables will not be updated. SAP S/4 HANA and SAP CRM should also have the required Value Mappings to consume the service and create BP/Customers successfully. All Service based configurations/derivations/validations to trigger a BP SOA service should be in place in MDG.No use of CRM middleware for BP replication.This blog covers all steps to enable Approach-1.įollowing are the pre-requisites to enable the scenario: Build a Custom Web Service/RFC Program using Mapping API’s.Using Standard BADI Activation and additional configurations. ![]() There are 2 different approaches to implement the solution: This is also part of the concept used in SOA based Web Services where each message has a unique identity while processing in the system.)ĬRMKUNNR & CRMM_BUT_CONTNO – These tables store the Client #, CRM GUID ID and BP IDĬRMPARNR & CRMM_BUT_CUSTNO – These tables store the CRM GUID ID, SAP S/4 HANA Partner GUID ID and SAP S/4 HANA Partner IDĬRM and SAP S/4 HANA uses the above tables to validate or verify Customer information during transactional data interfacing. (GUID ID is a uniquely generated 32 digit alpha numberic number used to identify the Source and receiver systems. A typical SAP S/4 HANA system does not receive a CRM GUID ID during BP replication from MDG ![]() Similarly, when CRM sends Sales Quotes to SAP S/4 HANA, CRM sends CRM GUID ID as a Primary key to uniquely identify the Quote information. In such scenarios the SAP S/4 HANA Partner Number (Contact Person/User) is different than the MDG Contact Person number and this information is required in CRM to process any Orders sent from SAP S/4HANA through Order interfaces. SAP S/4 HANA and CRM generates separate BP Numbers based on the defined Number ranges. The replication involves sending Customer & Contact BP details created in MDG to CRM and SAP S/4 HANA system. CRM Side: CRMM_BUT_CONTNO & CRMM_BUT_CUSTNOīusiness Partners (Customer & Contacts) replicated from MDG to CRM and SAP S/4 HANA are utilized in CRM and SAP S/4 HANA to enable Procurement activities (Order creation, Sales Quote generation, Price information, etc).To enable the exchange of transactional data as quotations and price lists between CRM and S/4, four tables need be in synchronization: MDG create the Business Partners through Change Request followed by compliance approval process (Organization & Contact) and replicate to SAP S/4 HANA/CRM system using DRF Framework. Business Scenario/Use CaseĬRM Prospect are send to MDG to convert to Sold-To. ![]() This blog is to all those who needs assistance into a smooth journey to perform Synchronization of Mapping Tables (CRM Tables) between SAP MDG, SAP S/4 HANA and SAP CRM Systems for Business Partners. ![]() In most of the implementations, there are Business Scenarios where SAP MDG needs to be implemented as a Standalone system (Acting as a Hub) to perform Master Data Creations, Change and Replications.
0 Comments
Leave a Reply. |