How To Fix FDT_WD_INFRA036 - No suitable object types for creating available; check filter

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_WD_INFRA - FDT: Message Class for WD Infrastructure

• Message number: 036

• Message text: No suitable object types for creating available; check filter

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 FDT_WD_INFRA036 - No suitable object types for creating available; check filter ?

  The SAP error message FDT_WD_INFRA036 indicates that there are no suitable object types available for creating a new object in the context of the Fiori Design Time (FDT) or Web Dynpro applications. This error typically arises when the system cannot find any object types that match the criteria specified in the filter settings.
  Causes:
  
  Filter Settings: The filter settings applied in the FDT or Web Dynpro environment may be too restrictive, leading to no available object types being displayed.
  Authorization Issues: The user may not have the necessary authorizations to access certain object types.
  Configuration Issues: There may be configuration issues in the backend that prevent the system from recognizing available object types.
  Missing Object Types: The required object types may not be defined or activated in the system.
  
  Solutions:
  
  
  Check Filter Settings:
  
  Review the filter settings in the FDT or Web Dynpro environment. Ensure that the criteria are not overly restrictive and that they include the object types you are trying to access.
  Try resetting the filters to see if that resolves the issue.
  
  
  
  Verify Authorizations:
  
  Ensure that the user has the necessary authorizations to create or access the object types. Check the roles and authorizations assigned to the user.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the backend system to ensure that the object types are correctly defined and activated.
  Consult with your SAP Basis or technical team to verify that all necessary components are properly configured.
  
  
  
  Check for Missing Object Types:
  
  If specific object types are required, verify that they are defined in the system. If they are missing, you may need to create or activate them.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that may resolve known issues.
  
  
  
  System Logs:
  
  Check the system logs for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for Fiori Design Time and Web Dynpro for more details on object types and configuration.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have already taken.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.