Special Depreciation Error when Scrapping an Asset #COE #MODPIZZA

[former_member95896]

Hello,

With the new s/4hana cloud 2102 release we're encountering an error that I've never seen before when we try to scrap some fully depreciated legacy assets as part of our period close. These assets are in an equipment asset class which has only ordinary depreciation for the book area (01), but special depreciation in the tax areas (90-92) which follows the SAP delivered setup for these classes. The error we're getting is below:

Symbolic Account KTSAFB isn't in our account determination at all (including the SAP delivered), and the special depreciation postings are only tax relevant. We don't have gl accounts for special depreciation because they aren't gl/book relevant (tax postings have been statistical).

I know that changes were made in the backend with regards to asset accounting tax areas as part of the 2102 release (KBA: https://launchpad.support.sap.com/#/notes/3001115), and per the KBA the system should fallback to an applicable account.

Can anyone shed some light on what's going on here, and how this should work?

Thanks,

Ryan

[Mark_W]

Hi Ryan,
With the upgrade postings now go to GL rather than the asset accounting specific tables which are now obsolete as documented in note 3001115 you already know, with these changes the statistical items are now recorded in table ACDOCA, and with that change there maybe adjustments that are required to the accounts determination to ensure these are posted. You will need to maintain the account so the posting can be made to the technical ledger, once the posting is made you can see these are posting with the prefix G.
Kind regards
Mark

[former_member95896]

Hi Mark,

There are a few things I find unclear about this and the impact to our config and chart of accounts. First is the note discusses fallback logic but that doesn't seem to apply to these cases, why? In the release notes and documentation, it needs to be clearer on impact and what we as administrators/users need to change in our system (in plain language). It reads (to me at least) that the migration is just in the backend and there should be no effect and that there is fallback logic to catch anything that does change. Based on my experience this isn't the case with assets/asset classes with have Special Depreciation keys in the their tax areas or Tax Area only assets.

Second, with regards to those Tax Only Assets, there is limited account determination considering they are statistical postings (book area is expensed) and there aren't GL accounts associated with the asset classes. Is it best practice to add GL accounts to your chart of accounts which will not have financial/book postings? The tax only assets now require account determination for acquisition balances, accumulated depreciation, depreciation expense, etc.

Thanks,

Ryan