SAP Knowledge Base Article - Public

2747466 - Carry Balance Forward results in error AA709

Symptom

When you run the Carry Forward Balances app for a given company code error AA709 'Target fiscal year specifications 20XX wrong for company code XXXX' is raised.

Environment

  • Financial Accounting (FI)
  • SAP S/4HANA Cloud

Reproducing the Issue

  1. Enter the Carry Forward Balances app.
  2. The error 'Failed to carry foward some items to 20XX. Please view the details and carry forward balances year by year is raised'.
  3. Enter the fiscal year and company code you want to carry forward.
  4. Run the app and the error is raised. 

Cause

While setting up a company code for asset accounting via the app 'Settings for Company Code in Asset Accounting' it is necessary to create at least one legacy data transfer segment, even if you do not want to perform a legacy data transfer. At creation of this first legacy data transfer segment, the system implicitly derives the current fiscal year and the last closed fiscal year from the legacy data transfer date field (if these fields have not yet been filled).

Example: You create a new legacy data transfer segment and specify the legacy transfer date on the last day of fiscal year 2018 which is December 31, 2018.

  • The derived closed fiscal year is 2018.
  • The derived open fiscal year is 2019.

If these steps are not complete then the last closed fiscal year will be set incorrectly and the error will be raised.

Resolution

There are two possible solutions for this situation.

You have to change an entry in the legacy data transfer segment for the company code in order to trigger a new automatic derivation of the current/closed fiscal year from the legacy data transfer date.

Option 1.

  1. Start the application
    (via Current Settings -> 'Make Company Code Settings' tile on your Launchpad; you need to have the business catalog BC: SAP_FIN_BC_AA_CURR_SET_PC included in your user profile or the standard role for an Asset Accountant).
  2. Select the relevant company code.
  3. Switch to edit mode.
  4. Go to section 'Legacy Data Transfer'.
  5. Change the 'Legacy Data Transfer Status' to 'Ongoing' (we will switch it back later).
  6. Save.
    The change from the previous step will trigger the validation of the 'Legacy Data Transfer Segment'. As part of this validation, the current fiscal year will be derived from the legacy data transfer date. 
  7. After successfully saving, change the 'Legacy Data Transfer Status' back to your previous value ('Ongoing (Other Postings Allowed)').
  8. Save again.
  9. Use the balance carry forward to open the fiscal years and the 'Year-End Closing Asset Accounting'-Job to close the fiscal years (if needed) till your desired current fiscal year.

Option 2.

Only possible if no legacy data transfer assets or postings for these assets exist.

If you want a different legacy data transfer date:

  1. Start the application
    (via Current Settings -> 'Make Company Code Settings' tile on your Launchpad; you need to have the business catalog BC: SAP_FIN_BC_AA_CURR_SET_PC included in your user profile or the standard role for an Asset Accountant).
  2. Select the relevant company code.
  3. Switch to edit mode.
  4. Go to section 'Legacy Data Transfer'.
  5. Change the 'Transfer Date' to your desired date.
  6. Save.
    The change from the previous step will trigger the validation of the 'Legacy Data Transfer Segment'. As part of this validation, the current fiscal year will be derived from the legacy data transfer date.
  7. Use the balance carry forward to open the fiscal years and the 'Year-End Closing Asset Accounting'-Job to close the fiscal years (if needed) till your desired current fiscal year.

See Also

Best Practice Guide

KBA 2866041 - Error AA377: Posting not possible in company code (legacy data transfer) in productive system

Keywords

J62 legacy transfer date FAGLGVTR S4_PC , KBA , csg_q , FI-AA-AA-E , Periodic Posting , FI-AA , Asset Accounting , Problem

Product

SAP S/4HANA Cloud all versions