How To Fix /SAPCND/TRANSPORT130 - &1 entries deleted in cache table &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/TRANSPORT -

• Message number: 130

• Message text: &1 entries deleted in cache table &2

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 /SAPCND/TRANSPORT130 - &1 entries deleted in cache table &2 ?

  The SAP error message /SAPCND/TRANSPORT130 &1 entries deleted in cache table &2 typically indicates that there was an issue with the transport of condition records in the SAP system. This message is related to the caching mechanism used for condition records, which are often used in pricing, discounts, and other areas of SAP.
  Cause:
  
  Transport Issues: The error usually occurs when there are inconsistencies or issues during the transport of condition records from one system to another (e.g., from Development to Quality Assurance or Production).
  Cache Invalidation: The cache for condition records may have been invalidated due to changes in the underlying data or configuration, leading to the deletion of entries.
  Missing or Incorrect Transport Requests: If the transport requests do not include the necessary condition records or if they are not properly released, it can lead to this error.
  
  Solution:
  
  Rebuild the Cache: You can manually rebuild the cache for the affected condition records. This can often be done by executing the relevant transaction (e.g., VK11, VK12, or VK13 for pricing conditions) to re-enter or adjust the condition records.
  Check Transport Requests: Ensure that the transport requests containing the condition records are correctly created, released, and imported into the target system.
  Clear Cache: You can clear the cache for the specific condition type using transaction SCC1 or SCC4 to ensure that the system refreshes the cache.
  Use Transaction Codes: Use transaction SDBA to analyze the cache and see if there are any inconsistencies that need to be addressed.
  Check Logs: Review the transport logs and system logs for any additional error messages or warnings that could provide more context on the issue.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to transport issues and caching for condition records. SAP frequently updates its knowledge base with solutions for common issues.
  Documentation: Review the SAP documentation for the specific modules you are working with (e.g., SD, MM) to understand how condition records are managed and transported.
  Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it affects critical business processes.
  
  By following these steps, you should be able to address the error message and restore the functionality of the condition records in your SAP system.