How To Fix /SAPAPO/DMRES122 - Resource & planning version & not found in SAP liveCache

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/DMRES -

• Message number: 122

• Message text: Resource & planning version & not found in SAP liveCache

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/DMRES122 - Resource & planning version & not found in SAP liveCache ?

  The SAP error message /SAPAPO/DMRES122 indicates that a specific resource and planning version combination could not be found in the SAP LiveCache. This error typically occurs in the context of Advanced Planning and Optimization (APO) when trying to access or manipulate data related to resources in the planning process.
  Cause:
  
  Missing Resource or Planning Version: The specified resource or planning version does not exist in the LiveCache. This could be due to incorrect configuration or data entry.
  Data Synchronization Issues: There may be a delay or failure in the synchronization of data between the SAP ERP system and the LiveCache.
  Incorrect Planning Area: The planning area being referenced may not be correctly set up or may not include the specified resource.
  Authorization Issues: The user may not have the necessary authorizations to access the resource or planning version.
  
  Solution:
  
  
  Verify Resource and Planning Version:
  
  Check if the resource and planning version specified in the transaction or report actually exist in the LiveCache.
  Use transaction /SAPAPO/RES01 to view resources and ensure that the correct planning version is being used.
  
  
  
  Check Planning Area Configuration:
  
  Ensure that the planning area is correctly configured and includes the resource in question. You can check this in the planning area settings.
  
  
  
  Data Consistency Check:
  
  Run consistency checks to ensure that the data in the SAP ERP and LiveCache are synchronized. You can use transaction /SAPAPO/LC10 to check the consistency of LiveCache data.
  
  
  
  Reinitialize LiveCache:
  
  If there are significant discrepancies, consider reinitializing the LiveCache. This can be done through transaction /SAPAPO/LC10 or by using the appropriate background jobs.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the resource and planning version. Check the user roles and authorizations in the SAP system.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  SAP LiveCache: A high-performance database used in SAP APO for storing and processing planning data.
  APO Planning Areas: These are defined in the system to manage different planning scenarios and resources.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/RES01, /SAPAPO/LC10, and others for managing resources and LiveCache.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or APO support team for further investigation.