You can specify a different FYV by depreciation area. However, the beginning of the FY and the end of the FY must be the same dates as in the FYV assigned to the company code. The individual periods within the FYV can be defined differently but 1st day and last day of the FYV must be the same
Please search the discussion boards and SAP notes. There is much written about this topic.
Look at SAP note: 844029 as a start. If you are using "new" asset accounting there are differences.
Thanks for sharing the Tip.
Hi,
Our SAP system only use special purpose ledger not use New GL. (We use SAP for a long time for other entities, all new entities still need to rollout with SPL)
Component version EHP7 for SAP ERP 6.0
The reason I set up 1st period from Sept. 29th to Sept. 30th, 2011 is that I'd like system to calculate the depreciation amount. Then user can use AR03 report to know total amount (by cost center) and do manual adjustment for yearly legal reporting purpose.
I know notes 1175751 with MCC solution but it's not user wanted and the solution even have to post unplanned depreciation manually in MCC.
Actually before I raise the discussion, I've already searched SAP notes several days but still can't find related answer. Maybe it's because I searched for the wrong direction.
It would be appreciated any other feedback.
Thanks
Where did you see that you can use a FYV at a depreciation area level that has a beginning and ending date different than the FYV that is assigned to the co code?
SAP addresses that in Note 1175751. You don't want to use that. Note 1951069 also addresses the use of different FYV (but you're not using different ledgers).
Hi Lidia,
Actually, I set the same start date and end date for FYV Z1 and ZZ. The only difference is the date range in P1 and P2, 2011.
Based on above link, SAP help did mention that period 1 end date can be different.
However, even if I set dep. area 40 for ZZ the system still use Z1 to calculated dep. amount in Z1.
Hi all,
Conclusion:
Change ANLB-PERFY=X with a small ABAP or per debugging.
Explanation:
In note 1795678 I have described that the settings on Asset level and on depreciation key level have to be the same. Either "daily" or "no daily" depreciation. If not you will get the AA 662.
So far it is clear and you have already described in your first question.
The problem is that on asset level you can not change the setting ("daily" or "no daily"). It is set when you create a asset and cannot be changed in the standard. On depreciation key level you can change the setting whenever you want.
But from technical point of view, in 99% it is not problem. Therefore please check carefully on a testsystem.
Furthermore:
Which problem do you have with the new depreciation area? This is not clear for me.
best regards
Bernhard
Hi Bernhard,
Very honestly, I do not understand why this setting, the PERFY one, is on asset level. As an object it seems to have a very strange behavior. I will have to go deep in debugging to understand how and from where it gets its values and I will not do it now since I found this workaround with the AS02 and LSM. In my view the Attributes of this object should clearly be on dep. area and asset level not asset only.
Now, the second one with the AFBN and the OAYZ again I do not get it. Why it does not get the defaults from OAYZ for the already posted assets?!? When the business asks for a new depreciation area apparently they come to this requirement based on the existing assets and a new need for different calcuation formula. A group reporting change request or new acquisions etc etc. If you cannot pick the new calculation formulas ( dep. keys) whats the added value of having this program, AFBN?!?. I am not a huge fan of copying std programs and deactivating lines of coding to do my job, especially for Fixed assets. Just to catch your possible reply here. I have tried all possible combinations of selection parameters in the AFBN program as well as the AFAR program and nothing seems to be working. I ,also, debugged the AFBN and I found that it first checks 01 area and if this is not empty/blank then the programs skips the OAYZ defaults.
IF P_ANLKL = CON_X ." AND
* XANLB-AFABG IS INITIAL AND
* ANLA-ZUGDT IS INITIAL.
READ TABLE YANKB WITH KEY ANLKL = ANLA-ANLKL
AFAPL = X093C-AFAPL
AFABE = P_AFABE.
Also, on dep. key level is not possible to change the XDAILY setting once this dep. key has already been posted.
A restructuring of the programs and logic on adding a new Depreciation area is required. I really believe that.
Hi all,
I am having this problem and seem to not be able to fix it. When running report S_ALR_87011990 or AR01, with depreciation posted flag, if we select a specific asset, the depreciation for the year is correctly displayed.
| Asset | SNo. CoCode Asset description | Cap.date | Class | Accnt: APC Cost Ctr WBS Element -Costs | APC FY start Dep. FY start Bk.val.FY strt | Acquisi Dep. for yea |
| 100000013 0 | XX01 | VR 4000173 | 1700110010 870096 | 170,000.00 | 56,666.64- | 113,333.36 | 0.00 | 9,444.45- |
If we run the same report, with Depreciation posted flag, but with no specific asset selected, the depreciation for the year is higher. It seems the report adds up the accumulated depreciation for the year and the ordinary depreciation for the period before the legacy data transfer but that makes no sense since in table ANLC, the accumulated depreciation already includes the depreciation for the year before the legacy data transfer.
| Asset | SNo. CoCode Asset description | Cap.date | Class | Accnt: APC Cost Ctr WBS Element -Costs | APC FY start Dep. FY start Bk.val.FY strt | Acquisi Dep. for yea |
| 100000013 0 | XX01 | VR 4000173 | 1700110010 870096 | 170,000.00 | 56,666.64- | 113,333.36 | 0.00 | 14,166.68- |
Is there something I'm missing or an SNOTE that I might have overlooked (I have checked lots of notes and none have been successful).
Thank you in advance,
A restructuring of the programs and logic on adding a new Depreciation area is required. I really believe that.
This program is the most often copied/changed program in all of FI-AA. Copy it and insert your own logic for your own needs.
This worked. Thanks!
The write up recognizes the Forecast which is exactly what we wanted. The forecast recalculates once the write up is posted. So, this is resolves the issue.
Thanks!
Hi,
Have you checked on same reporting date for both the views?
Regards,
Mukthar
Of course, the date was always the same: 29.02.2016, the only thing that changed was the selection on asset number 100000013 or free selection, including all assets.
I have to mention that the transfer date for the migration was 31.01.2016 and when I transferred, I also put in the takeover value section the Ordinary Depreciation Posted for the month of January. But when I look at it now, it has added up even the depreciation for February, which I run with AFAB.
The value now is 9,444.45 while at the moment of transfer was 4,722.23.
When the report is run selection-free, the value for asset 100000013 from ANLC-NAFAG (9,444.45) is added with ANLP-NAFAZ (4,722.22) and that's why it shows wrong amount.
When the report is run with selection for the asset 1000000013, only the ANLC-NAFAG value is retrieved.
That is most surprising: why when running with selection on asset it shows correct depreciation posted for year but when I erase selection, the value for the depreciation is higher?
Hi,
Good afternoon.
Could you please help with a question about correct transaction type? We are disposing of non capital assets that were posted in a prior year, and would like to transfer the current net book value of these disposed assets to another asset. Should we use non capital transfer prior year, or non capital transfer current year? Our confusion has to do with using the current net book value, hence we wonder if current year might be more appropriate.
Thank you.
Hi Tanya,
If you are transferring the values in the current year, then you have to chose prior- year else you have to chose as current year.
Regards,
Mukthar
Hi Farhan,
Since EHP 5 there can be a separate field for the Profit Center in asset master data. In that case it will not depend on the Cost Center anymore. So check if you have Profit Center field in asset master. If yes, check if you have maintained the "Agreement" indicator for the Profit Center in FI-AA customizing for additional account assignment. If this indicator is set, it's not possible to maintain Profit Center during the posting and the field is grayed out (like you described).
If you want the Cost Center set in the line items during posting (not just to derive the Profit Center), in addition to account field status and FI-AA customizing, you also have to disable error message KI098 and set the accounts as statistical cost elements.
Have a look at note 684659 for additional information on settings that affect account assignment objects in FI-AA.
If none of this helps you have to provide more info, like screenshots of the posting transaction where Profit Center is read-only, and screenshots of customizing you did.
Best regards, Michael
Hi,
Adding points to Michael,
Check the following
SPRO/IMG/FA/AA/integration to the GL/Additional account assignment objects/activate account assignment objects--- here account assignment object cost center must be activated.
SPRO/IMG/FA/AA/master data/screen layout/Define Screen Layout for Asset Master Data->Define Screen Layout for Asset Master Data....
select required screen layout rules and click on logical field groups and select logical field group3
Regards,
Pavan Kumar Arvapally
Hi
We are in EHP 7. Activated segment reporting Also. In asset master profit center is derived from cost center. But in posting, profit center field is blank..When we try to post, it gives error.
Kind regards
Farhan
Hi
All the settings are already in placed.
regards
Farhan
Hi Farhan
If you have PC assigned in the Asset Master itself, then in ACSET, you must choose "Profit Center" also along with Cost Center, in my opinion (IMG Path mentioned in above reply)
Also ensure APC account is defined as Cost Element (Catg 90)
Ajay M