How To Fix /SCWM/WB_CORE072 - No authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/WB_CORE -

• Message number: 072

• Message text: No authorization

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 /SCWM/WB_CORE072 - No authorization ?

  The SAP error message /SCWM/WB_CORE072 No authorization typically indicates that the user does not have the necessary authorizations to perform a specific action within the SAP Extended Warehouse Management (EWM) module. This can occur in various scenarios, such as when trying to access certain transactions, reports, or functions within the EWM system.
  Cause:
  
  Missing Authorizations: The user role assigned to the user does not include the necessary authorizations for the action they are trying to perform.
  Role Assignment Issues: The user may not have been assigned the correct role or profile that includes the required authorizations.
  Authorization Object Restrictions: The authorization objects related to the specific action may have restrictions that the user does not meet.
  Profile Changes: Recent changes to user roles or profiles may have inadvertently removed necessary authorizations.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the relevant roles for EWM are included.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after encountering the error to display the last authorization check. This will show which authorization objects failed and why.
  Analyze the output to identify which specific authorizations are missing.
  
  
  
  Modify Roles:
  
  If you have the necessary permissions, you can modify the user roles using transaction PFCG (Role Maintenance) to add the required authorizations.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required changes.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Test the action again to confirm that the authorization issue has been resolved.
  
  
  
  Documentation and Training:
  
  Ensure that users are aware of the roles and authorizations they need for their tasks.
  Provide training or documentation on how to request additional authorizations if needed.
  
  
  
  Related Information:
  
  Authorization Objects: In SAP, authorization checks are performed using authorization objects. Common authorization objects for EWM include S_WB_WB (Warehouse Management) and others specific to the functions being accessed.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide guidance on authorization management in EWM.
  User Groups: Consider using user groups to manage authorizations more effectively, especially in larger organizations.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.