How To Fix /SRMSMC/ACT007 - Employee &1 does not exist or is not authorized as activity manager

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/ACT -

• Message number: 007

• Message text: Employee &1 does not exist or is not authorized as activity manager

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/ACT007 - Employee &1 does not exist or is not authorized as activity manager ?

  The SAP error message /SRMSMC/ACT007 Employee &1 does not exist or is not authorized as activity manager typically occurs in the context of SAP Supplier Relationship Management (SRM) or similar modules where user roles and authorizations are critical for performing specific activities.
  Cause:
  
  Non-Existent Employee: The employee ID specified in the error message does not exist in the SAP system.
  Authorization Issues: The employee exists, but they do not have the necessary authorizations to act as an activity manager. This could be due to missing roles or authorizations in their user profile.
  Incorrect Configuration: There may be configuration issues in the SRM system that prevent the employee from being recognized as an activity manager.
  Data Inconsistency: There could be inconsistencies in the master data or organizational structure that affect the employee's status.
  
  Solution:
  
  
  Verify Employee Existence:
  
  Check if the employee ID exists in the system. You can do this by using transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data).
  
  
  
  Check Authorizations:
  
  Ensure that the employee has the necessary roles assigned. You can check this using transaction SU01 (User Maintenance) to view the user’s roles and authorizations.
  If the employee does not have the required roles, you may need to assign the appropriate roles that include activity manager authorizations.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the SRM system to ensure that the employee is set up correctly as an activity manager. This may involve reviewing the settings in transaction SPRO (Customizing) related to SRM roles and authorizations.
  
  
  
  Data Consistency Check:
  
  Ensure that there are no inconsistencies in the organizational structure or master data that could affect the employee's status. This may involve checking the organizational assignment of the employee.
  
  
  
  Consult with Basis or Security Team:
  
  If you are unable to resolve the issue, it may be necessary to consult with your SAP Basis or Security team to investigate further. They can help with authorization checks and system configurations.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  PA20 / PA30: HR Master Data Display/Maintenance
  SPRO: Customizing Implementation Guide
  
  
  
  Documentation: Refer to SAP Help documentation for SRM and user authorizations for more detailed information on roles and responsibilities.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.