How To Fix GX316 - Company code -fiscal year combination not allowed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: GX - Archiving/Reorganization

  • Message number: 316

  • Message text: Company code -fiscal year combination not allowed

  • Show details Hide details
  • What causes this issue?

    At least one company code (&V1&) was found for a fiscal year (&V2&)
    with data that is less than two years old.
    More specifically, the system checks the current system date and
    calculates 2 years back for all fiscal years of the company codes
    concerned. Based on the selection criteria, data would be archived that
    is less the 2 fiscal years old.

    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?

    Check your entries again.

    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 GX316 - Company code -fiscal year combination not allowed ?

    The SAP error message GX316 ("Company code - fiscal year combination not allowed") typically occurs when there is an attempt to post a transaction in a company code that is not valid for the specified fiscal year. This can happen in various scenarios, such as during the posting of financial documents, creating new entries, or executing certain reports.

    Causes:

    1. Invalid Fiscal Year Configuration: The fiscal year for the company code may not be set up correctly in the system.
    2. Fiscal Year Not Open: The fiscal year you are trying to post to may not be open for posting. This can happen if the year has been closed in the system.
    3. Company Code Not Assigned: The company code may not be assigned to the fiscal year variant in the configuration settings.
    4. Posting Periods: The posting period for the transaction may be closed or restricted.

    Solutions:

    1. Check Fiscal Year Variant:

      • Go to the configuration settings in SAP (Transaction Code: OB29).
      • Verify that the fiscal year variant is correctly assigned to the company code in question.
    2. Open the Fiscal Year:

      • If the fiscal year is closed, you may need to open it for posting. This can be done in the configuration settings (Transaction Code: OB52).
      • Ensure that the relevant posting periods are open for the transactions you are trying to execute.
    3. Review Posting Periods:

      • Check the posting periods for the company code (Transaction Code: OB52).
      • Make sure that the posting period you are trying to use is open and not restricted.
    4. Check Company Code Settings:

      • Ensure that the company code is correctly configured and that it is assigned to the correct fiscal year variant.
    5. Consult with Finance Team:

      • If you are unsure about making changes to the configuration, consult with your finance or SAP configuration team to ensure compliance with accounting policies.

    Related Information:

    • Transaction Codes:

      • OB29: Configure fiscal year variants.
      • OB52: Open or close posting periods.
      • OBA7: Assign company code to fiscal year variant.
    • Documentation: Refer to SAP Help documentation for detailed steps on configuring fiscal year variants and posting periods.

    • User Roles: Ensure that you have the necessary authorizations to make changes to the configuration settings.

    By following these steps, you should be able to resolve the GX316 error and successfully post transactions in the desired fiscal year for the specified company code.

    • 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