How To Fix CD173 - Filling of control table started

SAP Error Message - Details

• Message type: E = Error

• Message class: CD - Change Documents

• Message number: 173

• Message text: Filling of control table 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 CD173 - Filling of control table started ?

  The SAP error message CD173, which states "Filling of control table started," typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with the allocation of costs or the execution of certain controlling functions. This message is not necessarily an error but rather an informational message indicating that a process related to filling a control table has begun.
  Cause:
  
  Process Initialization: The message indicates that a process, such as a cost allocation or assessment run, has been initiated. This is part of the normal operation of SAP when it is preparing to execute a task that involves data processing.
  Long-Running Processes: If the process takes a long time to complete, users may see this message for an extended period, which can lead to confusion.
  System Performance: If the system is under heavy load or if there are performance issues, the filling of the control table may take longer than expected.
  
  Solution:
  
  Wait for Completion: Since this message is informational, the first step is to wait for the process to complete. Monitor the job status in transaction codes like SM37 (Job Monitoring) to see if it finishes successfully.
  Check for Errors: If the process does not complete or if you encounter subsequent error messages, check the job logs for any errors that may have occurred during execution.
  Performance Tuning: If the process consistently takes too long, consider reviewing system performance. This may involve checking for:
  
  Database performance issues
  System resource utilization (CPU, memory, etc.)
  Lock contention or other bottlenecks
  
  
  Review Configuration: Ensure that the configuration settings for the controlling processes are optimized for your business needs. This may involve adjusting parameters related to cost allocation or assessment cycles.
  Consult Documentation: Refer to SAP documentation or notes related to the specific transaction or process you are executing for any additional guidance or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  KSU5: For executing assessments.
  KSV5: For executing distributions.
  SM37: For monitoring background jobs.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific version of SAP you are using.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar messages.
  
  If the issue persists or if you encounter specific errors following this message, it may be beneficial to involve your SAP Basis team or consult with SAP support for further assistance.