How To Fix CO860 - G/L account & is invalid

SAP Error Message - Details

• Message type: E = Error

• Message class: CO - PPC order processing messages

• Message number: 860

• Message text: G/L account & is invalid

What causes this issue?

The G/L account that you have entered is invalid.

How to fix this error?

Check whether you have entered the G/L account correctly. If necessary,
correct your entry.
If you have entered the correct G/L account, check
the validity period of the G/L account,
the cost element type of the G/L account.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CO860 - G/L account & is invalid ?

  The SAP error message CO860 indicates that a General Ledger (G/L) account is invalid for the context in which it is being used. This error typically arises in the context of controlling (CO) or financial accounting (FI) when trying to post a transaction that references a G/L account that is not valid for the specified criteria.
  Causes of CO860 Error
  
  Inactive G/L Account: The G/L account may be inactive or not allowed for the specific company code or controlling area.
  Account Type Restrictions: The G/L account may not be of the correct type for the transaction being processed (e.g., expense accounts for certain types of postings).
  Missing Master Data: The G/L account may not have been set up correctly in the system, or it may be missing required master data.
  Company Code/Controlling Area Issues: The G/L account may not be assigned to the company code or controlling area being used in the transaction.
  Posting Period Issues: The posting period may be closed, preventing postings to that G/L account.
  
  Solutions to CO860 Error
  
  
  Check G/L Account Status:
  
  Go to the G/L account master data (transaction code FS00) and verify that the account is active and correctly configured for the relevant company code and controlling area.
  
  
  
  Verify Account Type:
  
  Ensure that the G/L account type is appropriate for the transaction. For example, if you are trying to post an expense, make sure the account is set up as an expense account.
  
  
  
  Review Master Data:
  
  Check if all necessary master data for the G/L account is complete. This includes ensuring that the account is assigned to the correct cost element category if applicable.
  
  
  
  Check Company Code/Controlling Area Assignment:
  
  Ensure that the G/L account is assigned to the correct company code and controlling area. This can be checked in the G/L account master data.
  
  
  
  Posting Period:
  
  Verify that the posting period is open for the G/L account. You can check this in the transaction code OB52 to see if the period is open for the relevant company code.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the configuration or the reason for the error, consult with your finance or accounting team to ensure that the G/L account is set up correctly.
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  FS00: G/L Account Master Data
  OB52: Open and Close Posting Periods
  KSB1: Cost Centers: Actual Line Items
  FBL3N: G/L Account Line Items
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on G/L account configuration and controlling area settings.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the CO860 error.
  
  
  By following these steps, you should be able to identify the cause of the CO860 error and implement the necessary solutions to resolve it.