How To Fix MDG_BS_CUS_CHECK132 - Customer &1 is marked for deletion in company code &2

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: 132

• Message text: Customer &1 is marked for deletion in company code &2

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 132 of message class F2.

System Response

If the severity of message F2 ? 132 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 company code being marked for deletion can only be
unmarked. All other company codes not being marked for deletion can be
maintained as usual on all attributes.
If the severity of F2 ? 132 is anything other than an error (such as
?Warning? or ?Information?), then the corresponding data can still 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 ? 132 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

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

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_CHECK132 - Customer &1 is marked for deletion in company code &2 ?

  The SAP error message MDG_BS_CUS_CHECK132 indicates that a customer record (identified by the customer number &1) is marked for deletion in the specified company code (&2). This typically occurs in the context of Master Data Governance (MDG) when trying to perform operations on a customer that has been flagged for deletion.
  Cause:
  
  Customer Marked for Deletion: The customer record has been marked for deletion in the company code. This means that the customer is no longer active and cannot be used for transactions.
  Data Governance Rules: The MDG system enforces data governance rules that prevent the use of customers that are marked for deletion to maintain data integrity.
  
  Solution:
  
  
  Unmark the Customer for Deletion:
  
  If the customer should still be active, you need to unmark the deletion flag. This can typically be done in the customer master data transaction (e.g., using transaction code XD02 for changes).
  Navigate to the customer record in the relevant company code and remove the deletion flag.
  
  
  
  Check the Status:
  
  Ensure that the customer is not in a state that prevents it from being used. You may need to check other statuses or flags that could affect the customer's usability.
  
  
  
  Consult with Business Users:
  
  If the customer is indeed meant to be deleted, consult with relevant business users to confirm that the deletion is appropriate and that no further transactions should be processed for this customer.
  
  
  
  Review MDG Configuration:
  
  If this error occurs frequently, review the MDG configuration and data governance rules to ensure they align with business processes.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  XD02: Change Customer (General Data)
  XD03: Display Customer (General Data)
  FD32: Change Customer Credit Management
  
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional insights or solutions related to this error.
  Documentation: Review SAP documentation on customer master data management and MDG processes for best practices and guidelines.
  
  Additional Considerations:
  
  If the customer is marked for deletion due to business processes (e.g., customer no longer exists), ensure that all necessary data is archived or handled according to your organization's data retention policies.
  Always perform such changes in a test environment before applying them in production to avoid unintended consequences.