cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

AW01N - values for ordinary depreciation have changed in depreciation area 02 and 32

bose_gourav
Explorer
0 Likes
676

Hi Experts,

We went live on January 2025 for our India local company code that belongs to Group company located in USA. So typically we have set-up two FYV i.e. 0L- Jan to Dec and L1- Apr to March. But in S/4 2021 on prem in-order to use AA module your FYV periods should same further we have created additional ledger with R1 and assign same FYV (Jan to Dec) and done the required system set-up.

We followed year-end approach where-in the transfer date was 12.31.2024 (FAA_CMP) in which Highest FY is 2025 and Closed FY is 2024 for 0L and R1 ledger. Now, currently what we have observe after AA legacy data load of APC and Accumulated depreciation values through migration cockpit is whenever we are executing AW01N report system is showing message 'values for ordinary depreciation have changed in depreciation area 02 and 32' (India local-GAAP depreciation areas) SAP message AU390. Post which system is looking for AFAR not sure why? And not sure what went wrong and how to proceed further. Please note: Till now we haven't run any depreciation for the new company code

Best Regards,

Gourav Bose

Accepted Solutions (0)

Answers (1)

Answers (1)

JaquelineF
Explorer
0 Likes

I had this situation with a customer that system required AFAR because previous FY has not been properly closed in legacy system. Have the users executed sucessfuly all AFAR, all AFAB runs as well as AJAB for 2024?

Another points which system might be asking recalculation of depreciation are differences in rounding settings or posting control (compare T093 and T093B tables). If this is the case, if you test AFAR it will show which assets have planned values not yet corrected in 2024.

bose_gourav
Explorer
0 Likes
Hi Jaqueline, Thank you so much for your response.
bose_gourav
Explorer
0 Likes
In continuation to your reponse
bose_gourav
Explorer
0 Likes
System required AFAR because previous FY has not been properly closed in legacy system  You mean to say FY-2024 within SAP if yes you are correct we haven’t yet close the FY-2024 because we went live on January which is still period 10 for L1 ledger (FYV- Apr to March). But when I try reproducing the same message in test environment after loading the legacy asset values this message is not showing even when I do the roll forward of 0L ledger (FAGLGVTR) still we are not getting the message in AW01N however the moment we carry forward the roll-forward for L1 ledger (FAGLGVTR) system is showing the message when we again open AW01N. But since we haven’t posted yet anything in Asset sub-ledger G/L account’s only balance carry forward happens for retained earnings account but not sure what it reason behind it and what SAP is expecting now in test environment. Have the users executed successfully all AFAR, all AFAB runs as well as AJAB for 2024?  In prod system yes they have firstly executed dep. run (AFAB) followed by (AFAR) and again run (AJAB). No changes happens in dep. areas with US-GAAP (dep. area 01,05,13,20,30) in posted value fields it’s showing posted in FY-2025 however for local-GAAP India depreciation books (dep. areas 02, 32) if we change to FY-2025 in AW01N for same asset system is not showing any values for local dep. area complete blank