How To Fix MDG_BS_ECC_CUSTOMER035 - No customer IDOC (DEBMAS) was sent; check Customizing settings

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_ECC_CUSTOMER - Messages for Customer

• Message number: 035

• Message text: No customer IDOC (DEBMAS) was sent; check Customizing settings

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_BS_ECC_CUSTOMER035 - No customer IDOC (DEBMAS) was sent; check Customizing settings ?

  The SAP error message MDG_BS_ECC_CUSTOMER035 indicates that no customer IDOC (DEBMAS) was sent during the process of data transfer from SAP Master Data Governance (MDG) to the SAP ERP system. This error typically arises due to issues in the configuration or customizing settings related to IDOC processing.
  Causes:
  
  Missing Configuration: The IDOC type DEBMAS may not be properly configured in the MDG system or the target ECC system.
  Incorrect Mapping: The mapping between MDG and ECC for customer data might not be set up correctly.
  Inconsistent Data: The data being processed may not meet the required criteria for IDOC generation, leading to no IDOC being created.
  IDOC Processing Settings: The settings for IDOC processing in the MDG system may not be correctly defined.
  Error in the MDG Workflow: If there are issues in the workflow or process chain that handles the data transfer, it may prevent IDOC creation.
  
  Solutions:
  
  
  Check Customizing Settings:
  
  Go to the transaction SPRO and navigate to the relevant customizing settings for MDG and IDOC processing.
  Ensure that the IDOC type DEBMAS is correctly configured and that the necessary settings for customer data transfer are in place.
  
  
  
  Review Data Mapping:
  
  Verify that the mapping between MDG and ECC for customer data is correctly defined. This includes checking the field mappings and ensuring that all required fields are populated.
  
  
  
  Validate Data:
  
  Check the data being processed to ensure it meets the criteria for IDOC generation. Look for any missing or incorrect data that could prevent IDOC creation.
  
  
  
  Check IDOC Processing Settings:
  
  Review the IDOC processing settings in the MDG system. Ensure that the relevant settings for IDOC generation and processing are correctly defined.
  
  
  
  Monitor Workflow:
  
  Check the workflow or process chain that handles the data transfer. Look for any errors or issues that may be preventing the IDOC from being created.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify where the IDOC generation is failing. This may involve looking at the relevant function modules or classes involved in the IDOC creation process.
  
  
  
  Related Information:
  
  Transaction Codes: Use transaction codes like WE02 or WE05 to monitor IDOC processing and check for any related errors.
  MDG Configuration: Familiarize yourself with the MDG configuration guide specific to customer data to ensure all necessary steps have been followed.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on configuring IDOC processing for MDG.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.