How To Fix /IWFND/COD035 - Error retrieving roles for GSDO type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /IWFND/COD -

• Message number: 035

• Message text: Error retrieving roles for GSDO type &1

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 /IWFND/COD035 - Error retrieving roles for GSDO type &1 ?

  The SAP error message /IWFND/COD035 Error retrieving roles for GSDO type &1 typically occurs in the context of SAP Gateway and OData services. This error indicates that there is an issue with retrieving roles associated with a specific Generic Service Data Object (GSDO) type.
  
  Cause:
  
  Missing Roles: The roles required for accessing the GSDO type may not be assigned to the user or may not exist in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the GSDO type.
  
  Configuration Issues: There may be a misconfiguration in the OData service or the associated roles.
  System Errors: There could be underlying system issues, such as database connectivity problems or inconsistencies in the role definitions.
  
  
  Solution:
  
  
  Check User Roles:
  
  Verify that the user encountering the error has the necessary roles assigned. You can do this by checking the user’s role assignments in transaction SU01 or PFCG.
  Ensure that the roles include the necessary authorizations for the