How To Fix /SRMSMC/CMN_BL141 - Contact Person &1 (&2) is blocked centrally and cannot be assigned

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/CMN_BL -

• Message number: 141

• Message text: Contact Person &1 (&2) is blocked centrally and cannot be assigned

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 /SRMSMC/CMN_BL141 - Contact Person &1 (&2) is blocked centrally and cannot be assigned ?

  The SAP error message /SRMSMC/CMN_BL141 Contact Person &1 (&2) is blocked centrally and cannot be assigned typically indicates that the contact person you are trying to assign in the SAP system is blocked at a central level. This can happen for various reasons, such as compliance issues, data integrity concerns, or administrative decisions.
  Cause:
  
  Central Blocking: The contact person has been marked as blocked in the central system, which prevents any assignments or transactions involving that contact.
  Data Integrity Issues: The contact person may have incomplete or incorrect data that has led to their being blocked.
  Compliance or Policy Reasons: The organization may have policies that require certain contacts to be blocked due to compliance, security, or other administrative reasons.
  
  Solution:
  
  
  Check Contact Person Status: 
  
  Go to the relevant transaction (e.g., transaction code BP for Business Partner) and check the status of the contact person. Look for any indicators that show the contact is blocked.
  
  
  
  Unblock the Contact Person:
  
  If you have the necessary permissions, you can unblock the contact person by navigating to the Business Partner transaction and changing the status from blocked to active.
  Ensure that all required data for the contact person is complete and correct before unblocking.
  
  
  
  Consult with Administration:
  
  If you do not have the necessary permissions to unblock the contact, consult with your system administrator or the relevant department (e.g., compliance, HR) to understand why the contact is blocked and whether it can be unblocked.
  
  
  
  Review Configuration Settings:
  
  Check if there are any configuration settings in the system that might be causing the contact to be blocked. This may involve reviewing the settings in the SAP system related to business partners or contact management.
  
  
  
  Documentation and Compliance:
  
  Ensure that any changes made to the contact person’s status are documented and comply with your organization’s policies.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP (Business Partner), SU01 (User Maintenance), or any other relevant transactions that may help in managing contact persons.
  User Roles and Permissions: Ensure that you have the appropriate roles and permissions to view and modify contact person data.
  SAP Notes and Documentation: Check SAP Notes for any known issues or updates related to this error message. SAP’s support portal may have additional information or patches that could be relevant.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.