How To Fix 29126 - G/L account & not defined in company code & (plant &)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: 29 - Bills of Material

  • Message number: 126

  • Message text: G/L account & not defined in company code & (plant &)

  • Show details Hide details
  • What causes this issue?

    You want to enter G/L account &V1& for the non-stock item.
    The system determines the valuation area on the base of the plant
    entered on the initial screen. A valuation area corresponds either to
    one plant or to all the plants in a company code.
    If the BOM (variant or alternative) is allocated to more than one
    plant, the system checks the G/L account for all the plants.
    The G/L account entered is not maintained in the determined company
    code.

    How to fix this error?

    Contact the department responsible for maintaining G/L accounts.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message 29126 - G/L account & not defined in company code & (plant &) ?

    The SAP error message 29126 indicates that a General Ledger (G/L) account is not defined for a specific company code and plant combination. This error typically occurs during transactions that involve financial postings, such as goods movements, invoice postings, or other financial activities where a G/L account is required.

    Cause:

    1. Missing G/L Account Configuration: The G/L account has not been assigned to the specified company code and plant in the system.
    2. Incorrect Account Assignment: The account being used in the transaction is not valid for the specified company code or plant.
    3. Data Entry Errors: There may be a typo or incorrect entry in the transaction that is causing the system to look for a non-existent account.

    Solution:

    1. Check G/L Account Configuration:

      • Go to the transaction code OBY6 (or FS00) to check the G/L account settings.
      • Ensure that the G/L account is defined for the relevant company code.
      • If the account is not defined, you will need to create or modify the account to include the necessary company code and plant.
    2. Assign G/L Account to Company Code and Plant:

      • If the G/L account is missing for the specific company code and plant, you can assign it by navigating to the appropriate configuration settings in the SAP system.
      • Use transaction code OBYC to check the account determination settings for the relevant transaction type (e.g., inventory postings, goods movements).
    3. Review Transaction Data:

      • Double-check the transaction data for any errors or inconsistencies.
      • Ensure that the correct G/L account is being used and that it is valid for the specified company code and plant.
    4. Consult with Finance Team:

      • If you are unsure about the correct G/L account to use, consult with your finance or accounting team to ensure compliance with accounting practices.

    Related Information:

    • Transaction Codes:
      • FS00: Create/Change G/L Account
      • OBY6: Define G/L Account for Company Code
      • OBYC: Automatic Account Determination
    • Documentation: Refer to SAP Help documentation for detailed steps on configuring G/L accounts and account determination.
    • User Roles: Ensure that you have the necessary authorizations to make changes to G/L account settings.

    By following these steps, you should be able to resolve the error message 29126 and ensure that the G/L account is properly defined for the company code and plant in question.

    • 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
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author