How To Fix /SAPAPO/DMRES070 - Resource & is still being used in a planning version

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/DMRES -

• Message number: 070

• Message text: Resource & is still being used in a planning version

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/DMRES070 - Resource & is still being used in a planning version ?

  The SAP error message /SAPAPO/DMRES070 indicates that a resource is still being used in a planning version, which prevents certain operations from being performed on that resource. This error typically arises in the context of SAP Advanced Planning and Optimization (APO) when you attempt to delete or change a resource that is still linked to a planning version.
  Cause:
  
  Active Planning Version: The resource is still assigned to an active planning version, which means it is being utilized in planning scenarios.
  Dependencies: There may be dependent objects (like production orders, planned orders, or other planning objects) that are still referencing the resource.
  Resource Locking: The resource might be locked due to ongoing planning activities or processes.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Planning Versions:
  
  Go to the planning version management in SAP APO and check which planning versions are currently active and using the resource.
  You can use transaction /SAPAPO/VER to view and manage planning versions.
  
  
  
  Deactivate or Change Planning Version:
  
  If the resource is linked to a planning version that is no longer needed, consider deactivating that version or changing it to a different version where the resource is not used.
  
  
  
  Review Dependent Objects:
  
  Check for any dependent objects that might be using the resource. This can include production orders, planned orders, or any other planning-related objects.
  You can use transaction codes like /SAPAPO/ORD to view orders and see if they are linked to the resource.
  
  
  
  Resource Usage Analysis:
  
  Use the resource usage analysis tools in SAP APO to identify where the resource is being utilized. This can help you pinpoint the exact objects that are causing the issue.
  
  
  
  Delete or Modify Dependent Objects:
  
  If you find that there are unnecessary dependent objects, consider deleting or modifying them to free up the resource.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed instructions on managing resources and planning versions in SAP APO.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/VER for planning version management and /SAPAPO/ORD for order management.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  User Roles and Permissions: Ensure that you have the necessary permissions to make changes to planning versions and resources.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate actions to resolve it.