How To Fix MDG_BS_CUS_CHECK131 - Customer & is marked for deletion

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_CUS_CHECK - MDGC: messages for check of customer data, message mapping

• Message number: 131

• Message text: Customer & is marked for deletion

What causes this issue?

Note that although the default severity of this message is ?Warning?,
its impact on whether or not data maintenance is possible within this
user interface depends on the message severity Customizing settings that
are made for message 131 of message class F2.

System Response

If the severity of message F2 ? 131 is defined as an error, a
corresponding information message is shown in MDG (not an error
message). An error would prevent data maintenance in general, which
would be an invalid behavior.
Instead, the customer being marked for deletion can only be unmarked.
All other customers not being marked for deletion can be maintained as
usual on all attributes.
If the severity of F2 ? 131 is anything other than an error (such as
?Warning? or ?Information?), then the corresponding data can be
maintained for the business partner.

How to fix this error?

If you need to change this behavior, contact your system administrator
to configure the severity of system message F2 ? 131 in the SAP
Customizing Implementation Guide under <ZK>Logistics - General ->
Business Partner -> Customers -> Control -> Change Message Control for
Customer Master Data</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_BS_CUS_CHECK131 - Customer & is marked for deletion ?

  The SAP error message MDG_BS_CUS_CHECK131 indicates that a customer record is marked for deletion in the system. This typically occurs in the context of Master Data Governance (MDG) for Customer data. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Marked for Deletion: The customer record has been flagged as "marked for deletion" in the database. This means that the record is not active and cannot be used in transactions or processes.
  Data Governance Process: In the context of MDG, this could be part of a data governance process where certain records are identified for deletion due to various reasons (e.g., business decisions, data quality issues).
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Customer Record:
  
  Use transaction code SE16N or SE11 to access the relevant database table (e.g., KNA1 for general customer data).
  Look for the customer record in question and check the deletion flag (usually a field like LOEVM).
  
  
  
  Remove the Deletion Flag:
  
  If you have the necessary authorizations, you can remove the deletion flag from the customer record. This can typically be done in the customer master data transaction (e.g., XD02 for changing customer data).
  Navigate to the customer record and uncheck the "Marked for Deletion" checkbox.
  
  
  
  Data Governance Workflow:
  
  If the deletion was part of a data governance workflow, you may need to follow the appropriate process to reactivate the customer record. This could involve approval from relevant stakeholders.
  
  
  
  Consult with Your Team:
  
  If you are unsure about the implications of unmarking a customer for deletion, consult with your data governance team or relevant stakeholders to ensure that the action aligns with business policies.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  XD02: Change Customer (General Data)
  SE16N: Data Browser
  SE11: Data Dictionary
  
  
  Tables:
  
  KNA1: General Data in Customer Master
  KNA2: Customer Master (Company Code)
  KNA3: Customer Master (Sales Area)
  
  
  Documentation: Refer to SAP Help documentation for MDG and customer master data management for more detailed processes and guidelines.
  
  Important Note:
  Always ensure that you have the necessary authorizations and that any changes made to master data are in compliance with your organization's data governance policies.