How To Fix WB2_ASGT090 - No authority for shadow document type &1 (&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: WB2_ASGT - Shadow items ans assignments

• Message number: 090

• Message text: No authority for shadow document type &1 (&2)

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 WB2_ASGT090 - No authority for shadow document type &1 (&2) ?

  The SAP error message WB2_ASGT090 indicates that a user does not have the necessary authorization to access or work with a specific shadow document type. This error typically arises in the context of document management or workflow processes within SAP, particularly when dealing with shadow documents, which are often used for temporary or intermediate document processing.
  Cause:
  The primary cause of this error is a lack of authorization for the user to access the specified shadow document type. This can happen due to:
  
  Missing Authorization Roles: The user may not have been assigned the appropriate roles that grant access to the shadow document type.
  Authorization Object Restrictions: The authorization objects related to document types may not be configured correctly, preventing access.
  Configuration Issues: There may be issues in the configuration of the document types or the shadow document settings in the system.
  
  Solution:
  To resolve the WB2_ASGT090 error, you can take the following steps:
  
  
  Check User Roles:
  
  Verify that the user has the necessary roles assigned. You can do this by using transaction code SU01 to check the user's profile and roles.
  Ensure that the roles include the necessary authorizations for the specific shadow document type.
  
  
  
  Review Authorization Objects:
  
  Use transaction code SU53 immediately after encountering the error to analyze the authorization check. This will show you which authorization objects failed.
  Check the relevant authorization objects (e.g., S_DOCUMENT, S_TCODE, etc.) to ensure that the user has the required permissions.
  
  
  
  Modify Authorizations:
  
  If the user lacks the necessary authorizations, you may need to modify the roles or create new ones that include the required permissions for the shadow document type.
  Work with your SAP security team to ensure that the roles are correctly configured.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to shadow documents and authorization issues. This can provide additional insights into specific configurations or known issues.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to document types and shadow documents.
  SAP Notes: Check for any SAP Notes related to this error message for additional troubleshooting steps or patches.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further investigation.