How To Fix FAGL_COFI120 - KSTAR field is not filled in company code &1; see long text


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FAGL_COFI - Messages for Real-Time Integration CO->FI

  • Message number: 120

  • Message text: KSTAR field is not filled in company code &1; see long text

  • Show details Hide details
  • What causes this issue?

    The real-time integration of Controlling with Financial Accounting is
    active for company code &V1& of the controlling area.
    However, there are postings for which the <LS>Cost Element</> (<AB>KSTAR
    </>) field is <ZH>not</> filled.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    Implement SAP Note 1036248.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FAGL_COFI120 - KSTAR field is not filled in company code &1; see long text ?

    The SAP error message FAGL_COFI120 indicates that the KSTAR (cost element) field is not filled in the specified company code. This error typically occurs during the posting of financial documents, particularly in the context of the New General Ledger (New GL) accounting.

    Cause:

    The error is usually caused by one of the following reasons:

    1. Missing Cost Element: The cost element (KSTAR) is not defined or not assigned in the system for the specified company code.
    2. Configuration Issues: There may be configuration issues in the controlling area or company code settings that prevent the system from recognizing the cost element.
    3. Document Type Restrictions: The document type being used may not allow for the posting of certain cost elements.
    4. Data Entry Error: The user may have inadvertently left the KSTAR field blank during data entry.

    Solution:

    To resolve the FAGL_COFI120 error, you can take the following steps:

    1. Check Cost Element Configuration:

      • Go to the transaction code KA01 (Create Cost Element) or KA02 (Change Cost Element) to verify if the cost element exists for the specified company code.
      • Ensure that the cost element is properly defined and active.
    2. Assign Cost Element to Company Code:

      • If the cost element is missing, create it or assign it to the relevant company code.
      • Ensure that the cost element is assigned to the correct controlling area.
    3. Review Document Type Settings:

      • Check the document type settings in transaction code OBY6 to ensure that the document type allows for the posting of the relevant cost elements.
    4. Data Entry Verification:

      • Review the document being posted to ensure that all required fields, including KSTAR, are filled in correctly.
      • If you are using a custom program or interface, ensure that it is populating the KSTAR field correctly.
    5. Consult Long Text:

      • The error message suggests checking the long text for additional details. You can do this by clicking on the message or using transaction code SE91 to view the message class and long text associated with the error.
    6. Testing:

      • After making the necessary changes, attempt to post the document again to see if the error persists.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL1N (Vendor Line Items), FB03 (Display Document), and F-02 (General Posting) for further investigation.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • User Authorization: Ensure that the user has the necessary authorizations to create or modify cost elements and perform postings.

    If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in Financial Accounting (FI) and Controlling (CO) modules.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant