How To Fix /SRMSMC/FND_MD_PARTY002 - Employee &1 does not exist or is not authorized as purchaser responsible

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/FND_MD_PARTY -

• Message number: 002

• Message text: Employee &1 does not exist or is not authorized as purchaser responsible

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/FND_MD_PARTY002 - Employee &1 does not exist or is not authorized as purchaser responsible ?

  The SAP error message /SRMSMC/FND_MD_PARTY002 indicates that the system cannot find the employee specified (denoted by &1) or that the employee is not authorized to act as a purchaser responsible in the context of the SAP Supplier Relationship Management (SRM) module. This error typically arises in scenarios where a user is trying to perform actions related to purchasing or procurement, but the system cannot validate the user's credentials or role.
  Causes:
  
  Employee Not Found: The employee ID provided does not exist in the system.
  Authorization Issues: The employee exists but does not have the necessary authorizations or roles assigned to act as a purchaser.
  Data Synchronization Issues: There may be a delay or issue in the synchronization of employee data between different systems (e.g., between SAP ERP and SAP SRM).
  Incorrect Configuration: The configuration settings for the purchasing organization or the employee's role may not be set up correctly.
  
  Solutions:
  
  
  Verify Employee ID:
  
  Check if the employee ID entered is correct and exists in the system. You can do this by searching for the employee in the relevant HR or user management transaction (e.g., PA20 or SU01).
  
  
  
  Check Authorizations:
  
  Ensure that the employee has the necessary roles and authorizations to act as a purchaser. This can be done by reviewing the user's role assignments in transaction SU01 or by using transaction PFCG to check the role definitions.
  
  
  
  Update Employee Data:
  
  If the employee is new or has recently changed roles, ensure that their data is up to date in the system. This may involve updating their purchasing group or other relevant fields.
  
  
  
  Synchronize Data:
  
  If there are multiple systems involved (e.g., SAP ERP and SAP SRM), ensure that the data synchronization process is functioning correctly. You may need to run a synchronization job or check for any errors in the data transfer.
  
  
  
  Consult with Security Team:
  
  If you are not able to resolve the authorization issue, consult with your SAP security team to review the authorization objects and ensure that the employee has the correct permissions.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the purchasing organization and ensure that they are correctly set up to recognize the employee as a purchaser.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  PA20 - Display HR Master Data
  
  
  Authorization Objects: Check for relevant authorization objects related to purchasing, such as M_BEST_BSA (Purchasing Group) and M_BEST_EKG (Purchasing Document).
  Documentation: Refer to SAP Help documentation for SRM and user management for more detailed guidance on roles and authorizations.
  
  If the issue persists after following these steps, it may be necessary to engage with SAP support or your internal SAP support team for further investigation.