Hello Experts,
I tried executing AFAR but no data was picked up. Also, I checked the change log for asset and it wasn't shutdown nor deactivated/retired.
I also tried limiting the selection of AFAB to assets that are not picked up and here's the message I've got "No data was found that agrees with the selection made".
Any inputs please?
Thanks.
Dear All,
As there is no other solution, we have proceeded with the cost element creation of AUC asset with 90 category. In this case the WBS balance will become zero after settlement to final asset only.
Thanks to all for your valuable inputs.
Regards,
Rajesh
Dear Cecilia,
Did you set adoption of values from depreciation area OABC ? I think this will work for you.
Best regards,
Gabriel Coleti
Hi Gabriel,
It is not possible to define a transfer value in Tcode OABC. As I explained this is not possible because of the setting required for an inflation area, so the field for entering the value is in grey with '00'. It does not transfer any APC value, the concept is correct, but it is causing problems with the program RAFABNEW.
Thanks,
Cecilia
Hello Cecilia,
I have looked into this program RAFABNEW, and the error message "Define depreciation area correctly" is generated when field WRTAFB of table T093A is empty. This check is done in line 196 of this program.
This table is maintained in OABC.
So I think something is missing in your new area configuration. I checked some OSS notes about program RAFABNEW and there is no SAP changes on this checking condition, to skip this error, OABC must be defined.
I hope this helps you.
Best regards,
Gabriel Coleti
Hi Gabriel,
Unfortunately, I cannot define a transfer value because the inflation area does not manage APC values.
Thanks for your replies,
Cecilia
Dear Cecilia,
The process to opening a new Dep. Area after production startup will required you to run AFBN (program RAFABNEW). According to SAP, values and depreciation terms are adopted without change from the area defined as the reference depreciation area in Customizing.
This means that your new area should have values adopted from an existing area.
As per my understanding, SAP will only allow you to open a new area in the existing assets if APC is being defined for your dep. area.
Best regards,
Gabriel Coleti
Hi all,
Thanks for the support you gave me.
Now the issue is resolved.
Its rootcause was the data inconsistency in asset master data, namely,
the asset has time-dependent depreciation terms in table ANLBZA even though the indicator ANLA-HAS_TDDP is not set, hence when the depreciation terms are changed via AS02, it does not update ANLBZA (time-dependent depreciation terms), hence no recalculating the depreciation. This issue is explained in OSS 1547416 - Inconsistency in time-dependent depreciation terms.
The solution was to
OSS_1839803 - Inconsistent indicator for time-dependent depreciation terms to resolve the inconsinstey
OSS_1773644 - Subnumber Time-dependent depreciation terms not displayed to avoid the recurring such inconsistency at sub asset number level.
Regards
Taro
I am using LSMW to transfer Legacy Asset Data through BAPI FIXEDASSET_CREATEINCLVALUES03.
I need to enter Proportional Values for Transaction Type 200.
The problem is that when I am including the proportional values, the Transaction is not displayed in AS93/AS92 even if it has been created in table ANEP and ANEA for the proportional values.
However if I do not include the Proportional Values, the Transaction can be found in AS92 / AS93 for the Asset created (without any proportional values of course)
Has anyone encountered this problem before and how did you solve it?
Thanks in advance for your reply.
It is quite urgent.
Best Regards,
Pramod.
Hi Cecilia,
Yes this is all right, but in India there are some specifics. Inflation area must be a separate area, with initial values, as this area update it's values with the revaluation program J_AA001 (Tx. J1AI). Could you please give me the code of the error message that you have got?
Is it the AU 008?
best regards
Bernhard
Hi Bernhard,
Do you mean the message number? In this case, the message is the "AU008".
If you are asking for other information please let me know.
Thanks,
Cecilia
Hi Jay,
Thank you! Issue is resolved from my end only that I updated acquistion values specific to statistical dep area(local GAAP) where client is having separate transaction type for this.
Transaction used: ABZO
Thank you,
vinay
Change the depreciation key to your new depreciation key.
Change the UL of the asset
Calculate the expected depreciation of the asset as of the current year (2016).
Post a write-up to the asset to adjust the over depreciated amounts.
Can you give the screenshot of posted values and parameters tab from AW01n of the asset with issue?
I think, you just need to take the Asset which was depreciated and the one which was not picked up in AFAB and compare them both. By doing that, you should be able to find what's missing for the Asset which is not being picked up.
Regards,
Sudhakar*
Hello Jack,
1) At first I might ask you to check in AW01N. Du you get a error message here? Is here a posted or planned depreciation shown, If you go to the tab "posted values", do you se any lines below in "depreciation Posted/Planned? If there is no error and no depreciation planned, please check the depreciation key.
2) Have you got a error in AFABN? (You can check also in SCMO)
3) What happens if you run AFABN with this single asset only?
4) Which posting sign do you have in OADB
regards Bernhard
Hi Expert,
I'd like to use Specify Other Versions on Depreciation Area Level in system. I set FYV Z1 and ZZ with start date and end date. (Ex: FY2011, Sept. 29th 2011 to Sept. 28th 2015 Non-calendar date)
| FV | Year | Month | Calendar Day | Period | FY | FV | Year | Month | Calendar Day | Period |
| Z1 | 2011 | 9 | 28 | 12 | 2011 | ZZ | 2011 | 9 | 28 | 12 |
| Z1 | 2011 | 10 | 28 | 1 | 2012 | ZZ | 2011 | 9 | 30 | 1 |
| Z1 | 2011 | 12 | 2 | 2 | ZZ | 2011 | 12 | 2 | 2 | |
| Z1 | 2011 | 12 | 30 | 3 | ZZ | 2011 | 12 | 30 | 3 | |
| Z1 | 2011 | 12 | 31 | 4 | ZZ | 2011 | 12 | 31 | 4 | |
| Z1 | 2012 | 1 | 27 | 4 | ZZ | 2012 | 1 | 27 | 4 | |
| Z1 | 2012 | 3 | 2 | 5 | ZZ | 2012 | 3 | 2 | 5 | |
| Z1 | 2012 | 3 | 30 | 6 | ZZ | 2012 | 3 | 30 | 6 | |
| Z1 | 2012 | 4 | 27 | 7 | ZZ | 2012 | 4 | 27 | 7 | |
| Z1 | 2012 | 6 | 1 | 8 | ZZ | 2012 | 6 | 1 | 8 | |
| Z1 | 2012 | 6 | 29 | 9 | ZZ | 2012 | 6 | 29 | 9 | |
| Z1 | 2012 | 7 | 27 | 10 | ZZ | 2012 | 7 | 27 | 10 | |
| Z1 | 2012 | 8 | 31 | 11 | ZZ | 2012 | 8 | 31 | 11 | |
| Z1 | 2012 | 9 | 28 | 12 | ZZ | 2012 | 9 | 28 | 12 |
Dep. area 01 use Z1. (Same as FYV in company code. therefore, the setting is blank.)
Dep. area 38 use Z1. (Same as FYV in company code. therefore, the setting is blank.)
Dep. area 40 use ZZ. (For local legal dep.)
Dep. area 38 and 40 use the same dep. key Z005 (dep. to the day).
But the plan dep. amount for P1, FY15 for dep. area 38 and 40 still the same. (from Sept. 29th 2011 to Oct. 28th 2011)
That mean system still use FYV Z1 to calculate plan amount for dep. area 40.
I checked through config. many times, but can't found anything wrong and didn't find any related examples in SDN discussion.
Am I missing any setting?
Thanks
I have created a new Depreciation area following the standard customizing steps and then executed AFBN and AFAR. It has been created as Real dep area that does not post to G/L.
All customizing settings are correct following the bussines requirement. Customizing tcodes/tables have been maintained correctly. OABC, OADB, OABD etc.
Now, the problems that I have faced so far are:
1. AFBN was copying the depreciation keys from Dep Area 01 not from OAYZ. I managed to overcome this issue by copying the RAFABNEW program to a Z one and deactivating a couple of lines. Actually I followed the suggestion from another post here.
2. I could not delete and replicate AFBN in D11. Again, I have found a function module that I picked up from a similar post here. It deletes everything and I can repeat AFBN.
Also minor problems here and there.
The main problem that I face however is the system error message:
Message no. AA662
The source of the problem seems to be the fact that the existing Dep key in Dep area 01 calculates depreciation to date. T090NA-XDAILY is flagged. The same field is not flagged for the Dep Key that I use for the new Dep Area.
This somehow results in setting 365 as the value for T095B-PERFY for the new dep area as well. In my view it should not.
I have tried running AFBN both ways. Meaning option "Leave values Initial" flagged and not flagged and I am always ending up getting the error message in AS02 for the least.
There exist a number of notes addressing this error and a detailed wiki as well:
Error message AA662 You cannot change the depreciation periods - ERP Financials - SCN Wiki
However, none of these seems to be helpfull. Any inputs ideas are welcome!
hi ,
In AFBN did you tick the check box Dep. terms from Asset class . May be that s why First error occur .
Also check OSS 1795678, 912613 and 2275557
Yeap thanks for your reply.
I have tried both options for Dep.terms Asset class and it does not work. It always picks up the Dep key from Dep area 01. Just to catch your possible next comment, OABD is not set to copy dep terms from 01.
I am now thinking to play around with the Layout settings. AO21
At least there is a work around there for the error message. By setting the start of dep, expired life and expired period to 0 in as02 once recalculation happens the PERFY field turns to the correct period setting and the AA662 msg dissapears.