How To Fix /SAPAPO/DMRES168 - Resource type & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/DMRES -

• Message number: 168

• Message text: Resource type & does not exist

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 /SAPAPO/DMRES168 - Resource type & does not exist ?

  The SAP error message /SAPAPO/DMRES168 Resource type & does not exist typically occurs in the context of SAP Advanced Planning and Optimization (APO) when the system is unable to find a specified resource type in the system. This can happen for various reasons, and understanding the cause and finding a solution involves a few steps.
  Cause:
  
  Missing Resource Type: The specified resource type may not have been created or defined in the system.
  Incorrect Configuration: There may be a configuration issue where the resource type is not properly linked to the relevant planning area or master data.
  Authorization Issues: The user may not have the necessary authorizations to access the resource type.
  Data Consistency Issues: There may be inconsistencies in the master data or planning area that prevent the system from recognizing the resource type.
  
  Solution:
  
  
  Check Resource Type Definition:
  
  Go to the transaction code /SAPAPO/RES01 (Resource Overview) and check if the resource type exists.
  If it does not exist, you will need to create it using the appropriate transaction (e.g., /SAPAPO/RES02 for resource creation).
  
  
  
  Verify Configuration:
  
  Ensure that the resource type is correctly configured in the relevant planning area. Check the settings in the transaction /SAPAPO/CPM (Configuration of Planning Area).
  Make sure that the resource type is assigned to the correct planning object structure.
  
  
  
  Check Authorizations:
  
  Verify that the user has the necessary authorizations to access the resource type. This can be done by checking the user roles and authorizations in transaction SU01.
  
  
  
  Data Consistency Check:
  
  Run consistency checks for the master data and planning area to identify any inconsistencies. You can use transaction /SAPAPO/DM (Data Management) for this purpose.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to resource types in APO for any additional configuration steps that may be required.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  /SAPAPO/RES01: Resource Overview
  /SAPAPO/RES02: Create Resource
  /SAPAPO/CPM: Configuration of Planning Area
  /SAPAPO/DM: Data Management
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  Documentation: Refer to the SAP Help Portal for detailed information on resource management in SAP APO.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.