Do you have any question about this error?
Message type: E = Error
Message class: /SAPAPO/ATP -
Message number: 135
Message text: Selection not found in liveCache
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.
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.
/SAPAPO/ATP135
- Selection not found in liveCache ?The SAP error message
/SAPAPO/ATP135 Selection not found in liveCache
typically occurs in the context of Advanced Planning and Optimization (APO) when the system is unable to find the requested data in the liveCache. This can happen for various reasons, and understanding the cause and potential solutions is essential for troubleshooting.Causes:
Data Not Available: The requested data (e.g., stock levels, planned orders) may not be present in the liveCache due to various reasons, such as:
- The data has not been loaded into liveCache.
- The data has been deleted or is not relevant for the current selection criteria.
Incorrect Selection Criteria: The selection criteria used in the ATP (Available to Promise) check may be too restrictive or incorrect, leading to no matching records in liveCache.
LiveCache Issues: There may be issues with the liveCache itself, such as:
- The liveCache is not running or is in an inconsistent state.
- There are connectivity issues between the SAP system and liveCache.
Configuration Issues: Incorrect configuration settings in APO or liveCache can lead to data not being available as expected.
Solutions:
Check Data Availability:
- Ensure that the relevant data has been loaded into liveCache. You can use transaction
/SAPAPO/LC10
to check the contents of liveCache.- If necessary, run the relevant data load jobs to populate liveCache with the required data.
Review Selection Criteria:
- Verify the selection criteria used in the ATP check. Ensure that they are correct and not overly restrictive.
- Adjust the criteria if needed to broaden the search.
Check LiveCache Status:
- Ensure that the liveCache is running properly. You can check the status using transaction
/SAPAPO/LC10
or by checking the liveCache administration tools.- If there are issues, consider restarting the liveCache or checking for any error logs that might indicate the problem.
Configuration Review:
- Review the configuration settings in APO and liveCache to ensure they are set up correctly.
- Consult with your SAP Basis team or system administrator if you suspect configuration issues.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be patches or updates that resolve known issues.
Debugging:
- If the issue persists, consider enabling debugging or logging to capture more detailed information about the error. This can help identify the root cause.
Related Information:
/SAPAPO/LC10
for liveCache monitoring and /SAPAPO/ATP
for ATP checks.By following these steps, you should be able to diagnose and resolve the /SAPAPO/ATP135 Selection not found in liveCache
error effectively.
Get instant SAP help. Start your 7-day free trial now.
/SAPAPO/ATP134
ATP check in system &1 not possible, since liveCache is not active
What causes this issue? An ATP check could not be carried out because liveCache is not active in the APO server.System Response The check is cancele...
/SAPAPO/ATP133
Comparision canceled during data record selection
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPAPO/ATP136
One or more PEGIDs do not exist in liveCache
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPAPO/ATP137
Start immediately is only effective if rules-based ATP is active
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.