How To Fix ACEPS105 - Carrying forward to fiscal year &1 not possible in company code &2


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ACEPS - Fehlermeldungen Abgrenzungsbuchungen

  • Message number: 105

  • Message text: Carrying forward to fiscal year &1 not possible in company code &2

  • Show details Hide details
  • trados = docu -> fi -> figl

    What causes this issue?

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

    System Response

    You cannot carry forward year values to fiscal year &V1& in company code
    &V2&.

    How to fix this error?

    Check your entries or the <DS:SIMG.FIGL_ACE_V_ACE001_DC> settings for
    the current fiscal year</> in the Customizing of the Accrual Engine for
    the company code.
    It is only possible to carry forward annual values under the following
    conditions:
    The new fiscal year must be in the future, that is, it must be after the
    last fiscal year closed and after or the same as the last fiscal year
    carried forward.
    The new fiscal year must be no more than one year after the last fiscal
    year carried forward otherwise years would be skipped.
    The new fiscal year must be no more than one year after the fiscal year
    determined from the current date. This prevents values being carried
    forward prematurely. If the company code has been set to productive, the
    carryforward cannot be peformed until the last posting period of the
    current fiscal year.

    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 ACEPS105 - Carrying forward to fiscal year &1 not possible in company code &2 ?

    The SAP error message ACEPS105, which states "Carrying forward to fiscal year &1 not possible in company code &2," typically occurs during the year-end closing process when the system is unable to carry forward balances to the new fiscal year for a specific company code. This can happen for several reasons, and understanding the cause is essential for resolving the issue.

    Causes:

    1. Open Items: There may be open items in the accounts that need to be cleared before the carryforward can occur.
    2. Incomplete Year-End Closing: The previous fiscal year may not have been closed properly, or there may be pending tasks that need to be completed.
    3. Configuration Issues: There may be configuration settings in the financial accounting module that are preventing the carryforward.
    4. Missing Authorizations: The user attempting to perform the carryforward may not have the necessary authorizations.
    5. Locked Periods: The fiscal periods may be locked, preventing any changes or carryforward actions.
    6. Incorrect Settings in Financial Statement Versions: If the financial statement versions are not set up correctly, it can lead to issues during the carryforward process.

    Solutions:

    1. Clear Open Items: Review and clear any open items in the accounts that may be preventing the carryforward.
    2. Complete Year-End Closing Activities: Ensure that all year-end closing activities for the previous fiscal year are completed. This includes running necessary reports and closing all relevant periods.
    3. Check Configuration: Review the configuration settings in the financial accounting module to ensure they are set up correctly for year-end closing and carryforward.
    4. Verify Authorizations: Ensure that the user has the necessary authorizations to perform the carryforward. This may involve checking user roles and permissions.
    5. Unlock Periods: If fiscal periods are locked, unlock them temporarily to allow the carryforward process to complete.
    6. Review Financial Statement Versions: Check the financial statement versions to ensure they are correctly configured and do not have any discrepancies.

    Related Information:

    • Transaction Codes: You may need to use transaction codes such as OB52 (to open/close posting periods) or F.01 (to run financial statements) to assist in resolving the issue.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
    • Documentation: Refer to SAP documentation on year-end closing procedures for detailed steps and best practices.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a financial consultant who specializes in SAP to further investigate the problem.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker