How To Fix COCM185 - Old log was converted

SAP Error Message - Details

• Message type: E = Error

• Message class: COCM - Order Change Management

• Message number: 185

• Message text: Old log was converted

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 COCM185 - Old log was converted ?

  The SAP error message COCM185 ("Old log was converted") typically occurs in the context of the Controlling (CO) module, particularly when dealing with the conversion of old log data during the execution of certain transactions or reports. This message indicates that the system has converted an old log format to a new one, which may be part of a system upgrade or a change in the logging mechanism.
  Cause:
  
  System Upgrade: The error often arises after an upgrade of the SAP system where the logging format has changed.
  Data Migration: If data has been migrated from an older version of SAP to a newer one, the logs may need to be converted to be compatible with the new system.
  Configuration Changes: Changes in the configuration of the Controlling module or related settings can also trigger this message.
  
  Solution:
  
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates. Sometimes, SAP releases notes or patches that address specific issues related to log conversions.
  Review Logs: Check the logs for any additional error messages or warnings that may provide more context about the conversion process.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version you are using. SAP Notes can provide insights into known issues and their resolutions.
  Data Consistency Check: Run consistency checks on your data to ensure that there are no underlying issues that could be causing the conversion message.
  Contact SAP Support: If the issue persists and affects your operations, consider reaching out to SAP support for assistance. They can provide specific guidance based on your system configuration and version.
  
  Related Information:
  
  SAP Notes: Look for relevant SAP Notes that discuss the COCM185 message or related log conversion issues. These notes often contain troubleshooting steps or patches.
  Transaction Codes: Familiarize yourself with transaction codes related to Controlling and logging, such as COSS (CO Object: Secondary Costs) or COSS (CO Object: Primary Costs), which may help in diagnosing the issue.
  System Logs: Use transaction codes like SLG1 (Application Log) to view application logs that may provide more details about the error.
  
  By following these steps, you should be able to address the COCM185 error message effectively.