How To Fix FINS_CFIN_CO_MESSAGE313 - Order &1 is used by controlling document &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_CFIN_CO_MESSAGE - Central Finance Message Class

• Message number: 313

• Message text: Order &1 is used by controlling document &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 FINS_CFIN_CO_MESSAGE313 - Order &1 is used by controlling document &2 ?

  The SAP error message FINS_CFIN_CO_MESSAGE313 indicates that a controlling order (or cost object) is currently being used by a controlling document, which prevents certain operations from being performed on that order. This error typically arises in the context of financial and controlling processes within SAP, particularly when dealing with cost center accounting, internal orders, or similar objects.
  Cause:
  The error occurs when:
  
  An attempt is made to change or delete an internal order or cost object that is currently referenced in a controlling document (e.g., a journal entry, allocation, or settlement).
  The order is locked due to ongoing processes or transactions that are still referencing it.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify the Controlling Document: 
  
  Use transaction codes like KOB1 (for displaying line items for internal orders) or KSB1 (for cost centers) to find out which controlling document is using the order.
  Check the document number mentioned in the error message.
  
  
  
  Review the Document:
  
  Analyze the controlling document to understand why it is still referencing the order. This could be due to open postings, allocations, or settlements.
  
  
  
  Complete or Reverse Transactions:
  
  If the document is still open, you may need to complete the necessary transactions or reverse them if they are no longer needed.
  Ensure that all necessary postings are finalized before attempting to modify or delete the order.
  
  
  
  Check for Locks:
  
  Sometimes, the order may be locked due to ongoing processes. Check if there are any background jobs or transactions that are currently processing and holding a lock on the order.
  
  
  
  Consult with Your Team:
  
  If you are unsure about the implications of changing or deleting the order, consult with your finance or controlling team to ensure that you are not disrupting any critical processes.
  
  
  
  Use Transaction Codes:
  
  You can use transaction codes like KO02 (Change Internal Order) or KO03 (Display Internal Order) to check the status of the order and see if any changes can be made.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for controlling and financial reporting, such as KOB1, KSB1, KO02, KO03, KSV5, etc.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation on internal orders and controlling documents for a better understanding of how they interact.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.