How To Fix AU068 - No closing check required for company code &1 and year &2


SAP Error Message - Details

  • Message type: E = Error

  • Message class: AU - FI-AA utility program error messages

  • Message number: 068

  • Message text: No closing check required for company code &1 and year &2

  • Show details Hide details
  • What causes this issue?

    Company code &V1& has no open depreciation area in fiscal year &V2&
    that is relevant for the check for the year-end closing.
    A depreciation area is relevant for the year-end closing if it posts
    depreciation or asset balance sheet values to the general ledger.
    Not having any relevant, open depreciation areas is justified if you
    have carried out a complete year-end closing, and then took back the
    year-end closing for certain selected depreciation areas that do not
    automatically post to the general ledger.

    System Response

    Company code &V1& is closed for fiscal year &V2&.

    How to fix this error?

    Check to make sure that all relevant depreciation areas are defined so
    that they automatically post their depreciation and/or asset balance
    sheet values to the general ledger.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message AU068 - No closing check required for company code &1 and year &2 ?

    The SAP error message AU068 "No closing check required for company code &1 and year &2" typically occurs in the context of financial closing processes, particularly when you are trying to execute a closing operation for a specific company code and fiscal year. Here’s a breakdown of the cause, potential solutions, and related information:

    Cause:

    1. No Closing Check Configuration: The error indicates that there is no closing check configured for the specified company code and fiscal year. This could mean that the system is set up in such a way that it does not require a closing check for that particular combination.

    2. Company Code Settings: The company code may not have been set up to require a closing check, or the fiscal year may not be defined correctly in the system.

    3. Incorrect Transaction: The transaction you are trying to execute may not be applicable for the specified company code and year.

    Solution:

    1. Check Configuration:

      • Go to the configuration settings in SAP (Transaction SPRO) and navigate to the Financial Accounting (FI) module.
      • Check the settings for the closing process under "Financial Accounting" -> "General Ledger" -> "Closing" -> "Define Closing Check".
    2. Review Company Code Settings:

      • Ensure that the company code is correctly configured to require a closing check. You can check this in the company code settings (Transaction OX02).
      • Verify that the fiscal year is correctly defined and that the closing check is applicable for that year.
    3. Adjust the Transaction:

      • If you are using a specific transaction code, ensure that it is the correct one for the operation you are trying to perform. Sometimes, using the wrong transaction can lead to such errors.
    4. Consult Documentation:

      • Review SAP documentation or help files related to the closing process for additional insights on how to configure and troubleshoot closing checks.
    5. Contact SAP Support:

      • If the issue persists after checking the configuration and settings, consider reaching out to SAP support for further assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (to maintain posting periods) and OX02 (to maintain company codes).
    • SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or updates.
    • User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.

    By following these steps, you should be able to identify the cause of the AU068 error and implement the necessary changes to resolve it.

    • 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