How To Fix CO359 - The cost log is empty

SAP Error Message - Details

• Message type: E = Error

• Message class: CO - PPC order processing messages

• Message number: 359

• Message text: The cost log is empty

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 CO359 - The cost log is empty ?

  The SAP error message CO359 ("The cost log is empty") typically occurs in the context of controlling (CO) when you are trying to analyze or display cost information for a particular cost object, such as a production order, internal order, or project. This error indicates that there are no cost entries available for the specified object, which can be due to several reasons.
  Causes of CO359 Error
  
  
  No Cost Entries: The most straightforward reason is that there are no cost entries recorded for the specified cost object. This can happen if the object has not yet incurred any costs.
  
  
  Cost Object Not Released: If the cost object (like a production order) has not been released, it may not have any associated costs.
  
  
  Incorrect Period: The costs may be recorded in a different period than the one you are currently viewing. If you are looking at a closed period, you may not see the costs.
  
  
  Data Not Posted: Costs may not have been posted yet due to delays in processing or errors in the posting process.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the cost data, leading to an empty log.
  
  
  Configuration Issues: There may be configuration issues in the controlling module that prevent costs from being recorded or displayed correctly.
  
  
  Solutions to CO359 Error
  
  
  Check Cost Entries: Verify if there are any cost entries for the cost object in question. You can do this by checking the relevant transaction (e.g., CO03 for production orders) to see if costs have been posted.
  
  
  Release the Cost Object: If the cost object is not released, release it to allow costs to be recorded.
  
  
  Review Posting Period: Ensure that you are looking at the correct posting period. If necessary, change the period to one where costs are expected to be recorded.
  
  
  Post Costs: If costs have not been posted, ensure that all necessary transactions (like goods movements, confirmations, etc.) are completed to generate costs.
  
  
  Check Authorizations: Ensure that you have the necessary authorizations to view cost data. Consult with your SAP security team if needed.
  
  
  Configuration Review: If you suspect configuration issues, consult with your SAP CO configuration team to ensure that everything is set up correctly.
  
  
  Use Transaction Codes: Utilize relevant transaction codes to check for costs:
  
  KSB1: Display actual line items for cost centers.
  CJI3: Display actual costs for projects.
  CO03: Display production orders.
  
  
  
  Related Information
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for controlling (CO) to understand how costs are recorded and displayed.
  Community Forums: Engage with SAP community forums or user groups for additional insights and solutions from other users who may have encountered the same issue.
  
  By following these steps, you should be able to diagnose and resolve the CO359 error in SAP.