How To Fix /SAPCND/CUSTOMIZING103 - Restructuring of cache for &1 and usage &2 was started

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUSTOMIZING -

• Message number: 103

• Message text: Restructuring of cache for &1 and usage &2 was started

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/CUSTOMIZING103 - Restructuring of cache for &1 and usage &2 was started ?

  The SAP error message /SAPCND/CUSTOMIZING103 indicates that the system is restructuring the cache for a specific customizing object and usage. This message is typically informational and not necessarily indicative of an error that requires immediate action. However, it can be associated with performance issues or changes in customizing settings.
  Cause:
  
  
  Cache Restructuring: The message is triggered when the system detects that the cache for a specific customizing object (like condition records, pricing, etc.) needs to be restructured. This can happen due to:
  
  Changes in customizing settings.
  Updates to condition records or other related data.
  System upgrades or changes in configuration.
  
  
  
  Performance Optimization: The system may be optimizing the cache to improve performance, especially if there have been significant changes in the underlying data.
  
  
  Solution:
  
  
  Wait for Completion: Since this message is often informational, the first step is to wait for the cache restructuring process to complete. This process is usually handled automatically by the system.
  
  
  Monitor Performance: After the restructuring is complete, monitor the system's performance. If you notice any performance degradation or issues, consider the following:
  
  Check for any recent changes in customizing or data that might have triggered the cache restructuring.
  Review system logs for any related errors or warnings.
  
  
  
  Clear Cache Manually: If the system seems to be stuck or if performance issues persist, you may consider manually clearing the cache. This can be done using transaction codes like SICF or SICF for specific services, but be cautious as this can impact system performance temporarily.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address specific issues related to this message. There may be patches or updates that can help resolve underlying issues.
  
  
  System Configuration Review: If this message occurs frequently, it may be worth reviewing the system configuration and customizing settings to ensure they are optimized for performance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to cache management, such as SICF, SICF, and SE11 for data dictionary objects.
  SAP Community: Engage with the SAP Community forums to see if other users have experienced similar issues and what solutions they have found.
  Performance Monitoring Tools: Utilize SAP's performance monitoring tools to analyze system performance and identify bottlenecks.
  
  If the issue persists or if you encounter additional error messages, it may be necessary to involve your SAP Basis team or consult with SAP support for further assistance.