Recalculate Depreciation
Recalculate Depreciation
Recalculate Depreciation
Overview
To ensure depreciation is recalculated correctly for all assets, usually we execute depreciation recalculation in background first and remove all errors
occurred in test run of depreciation recalculation. afterwards, we execute real run of depreciation recalculation in background.
2, Go to menu: Program -> Execute in background to execute depreciation calculation in background mode.
8, Check the status of Test Run. if the status is red light, then go to next step to check the details of error messages
11, Check error messages one by one and correct those errors completely
12, After all errors are solved, you need to repeat all of above steps again to check if there is still any error message recorded in the spool of test run of
depreciation recalculation
13, If the status for test run of depreciation recalculation in step 8 is green light like below screen, you can move to section 2 to execute real run of
depreciation recalculation
9, In below screen, click on button 'Spool' to check there is no error message recorded in the bottom of the spool
<Section 3: Scenarios for Depreciation Recalculation>
1, Before Month / Year end closing
FI T-Codes
Skip to end of metadata
Created by Prasanna Ramachandran, last modified by Nathan Genez on May 06, 2009
Go to start of metadata
T Code Description
ABNA Post-capitalization
ABNAN Post-Capitalization
ABZU Write-up
ASEM My assets
AUN1 FI-AA Asset Summary - Analysis of an asset and its environment: Postings
AUN10 FI-AA Asset Summary - Analysis of an asset and its environment: Fiscal Year Variant
AUN11 FI-AA Asset Summary - Analysis of an asset and its environment: Transfer/Line Item Schema
AUN2 FI-AA Asset Summary - Analysis of an asset and its environment: Value Determination
AUN3 FI-AA Asset Summary - Analysis of an asset and its environment: Posted Values
AUN4 FI-AA Asset Summary - Analysis of an asset and its environment: Legacy Data
AUN5 FI-AA Asset Summary - Analysis of an asset and its environment: Account Assignment
AUN6 FI-AA Asset Summary - Analysis of an asset and its environment: Insurance
AUN7 FI-AA Asset Summary - Analysis of an asset and its environment: Leasing
AUN8 FI-AA Asset Summary - Analysis of an asset and its environment: Investment Support
AUN9 FI-AA Asset Summary - Analysis of an asset and its environment: Screen Layout
Will do some basic configuration in the S4 HANA FINANCE system, without many bells and whistles; I have not activated document splitting
nor additional local currencies, will configure the following:
1. Chart of Depreciation
a. Account Determination
f. Create GL account (for eg: Vehicle(Recon), Accumulated depreciation account(Liability) Sale of asset( Profit on sale GL
account/loss on sale GL account) , Loss due to scrap, Deprecation.
k. Define screen layout for asset master data (eg: Default capitalization date.)
l. l. Screen layout for Depreciation area (eg: Dep Key, useful life, start date)
3. Depreciation configuration
c. Base method
f. Do some postings like create asset, sale, scrap, run Dep etc.
Created company code AB10 and the following are the bare minimum settings:
AB10 has local currency as USD and Fiscal year variant K4. (also activated parallel GL accts for account based approach )
Chart of Dep:
Nothing fancy, we are going to us only Book Depreciation, what is new here is Assignment of accounting Principle
Assign Chart of Depreciation to Company code.
Double click on Depreciation Enter Depreciation and accumulate dep GL accounts as shown below.
Maintain the document type number range OBA7
Specify the Posting rules OAYR
Making Dep key, usefully life and dep start date required.
Create asset
Now the depreciation values will post from period 2 from the transferred asset
Asset sub number 1 is closed
1. If Non-leading ledgers are activated, you need to create additional depreciation areas for each non leading ledger. And also for additional
local currencies
3. Posting will be done in real time to Non-leading ledgers, so no delta postings required anymore.
6. Instead of vendor to asset, postings in new asset accounting will be to Technical clearing accounts..
If time permits will do one more demo with document splitting and non leading ledgers.
Thanks
Akbar
Purpose
The purpose of this page is to help users to verify system log after run periodic posting or depreciation posting in test mode.
Overview
When we run periodic posting or depreciation posting, as best practice, we should run them as test mode first and verify the system log to ensure that
posting will occur without errors.
The most used transaction codes to verify periodic and depreciation posting logs are SCMO and ARMO.
Module Sr. No. Process Description T Code / Menu- Periodicity(D/W/M) Person Responsible / Location
path
SD 5 Check Billing Due List for the VF04 - Monthly Logtistics/Sales Admin.
last days in the month * *Logistics >
Sales and
Distribution >
Billing > Billing
Document >
Process Billing
Due List
MM 13 Open next MM Period MMPV Logistics Monthly Manual orAutomated back ground
> Material job
Managements >
Material Master >
Other > Close
Period
FI 20 Post Recurring Entries F.14 Depends on Nature of entry and Corporate Accounts
Accounting -> target accrual dates
Financial
Accounting->
General Ledger ->
Periodic
Processing ->
Recurring Entries
-> F.14 - Execute
Module Sr. Process T Code / Menu- Preceding Subsequent Process Periodicity(D/W/ Person Responsible /
No. Description path Dependency Impacted M) Location
FI 1 Open FI OB52 Accounting -> Open period 13 Allows all specific Annual Corporate Accounts
Posting Financial close Normal en year postings
Periods Accounting-> periods 1 to 12
General Ledger -> initially.
Environment -> Open Special
Current Settings -> Period 13 , only
S_ALR_87003642 - for non sales
Open and Close accounts
Posting Periods ( exclude
accounts 7*)
FI 2 End year FB50 Accounting -> All specific postings Annual Corporate Accounts
Manual FI Financial for regularisation
Postings Accounting-> involving generation
General Ledger -> of and FI and non
Document Entry -> sales imapct
FB50 - Enter G/L -commissions on
Account Document sales
FI 3 Fiscal Year AJRW Accounting None 1/Calcul evaluation Annual Corporate Accounts
Change for -> Financial on next period
Fixed Assets Accounting-> Fixed 2/Posting to Assets
Assets -> Periodic Accounting in next
Processing -> AJRW Fiscal Year
- Fiscal Year Change 3/reporting Budget
FI 4 Open FI OB52 Accounting -> Close Special All processing Annual Corporate Accounts
Posting Financial Period 13 to 16 to involving generation
Periods Accounting-> be closed after of and FI Document
General Ledger -> full & complete not allowed in next
Environment -> finalisation. of posting period.
Current Settings -> trial balance.
S_ALR_87003642 -
Open and Close
Posting Periods
FI 5 Fixed AJAB Accounting After END Posting to Previous Annual Corporate Accounts
Assets Year- -> Financial closing period 13 Fiscal Year can not
End Closing Accounting-> Fixed =>Completion of be continued after
Assets -> Periodic Capitalization the year- end closing
Processing -> Year- Activities and
End Closing -> Posting of Final
AJAB - Execute Depreciation Run
for the Fiscal
Year.
FI 7 Vendors & F.07 Accounting -> Scrutiny and Annual Corporate Accounts
Customers Financial closing of all
Accounting-> Vendor &
Accounts Payable -> Customer
Periodic Processing accounts
-> Closing ->
Carrying Forward ->
F.07 - Balance Carry
Forward
FI 9 P & L Items F.16 Accounting -> Scrutiny and Annual Corporate Accounts
Financial closing of all GL
Accounting-> P & L accounts
General Ledger ->
Periodic Processing
-> Closing ->
Carrying Forward ->
F.16 - Balance Carry
Forward
FI 13 Review and S_ALR_87012284 Scrutinise & Year end Annual Corporate Accounts
download Ledger - Reporting Download P& L
the p& l and -> Information and Balance Sheet
balance System -> General
sheet Ledger Reports >
Balance Sheet/ Profit
and Loss Statement /
Cash Flow ->General
> Actual/Actual
Comparisons
->S_ALR_87012284
The Fiscal Year change can only be carried out (even in test mode) for the new Fiscal Year. The earliest that one can carry out a Fiscal Year change is
in the last month of the old Fiscal Year. One can choose any point in the new Fiscal Year for carrying out the Fiscal Year change. One can have a
maximum of two Fiscal years open for postings at any given point in time. Before one changes to Fiscal Year 9999, it is important and must to close
Fiscal Year 9999 - 2 (Reference: Year-end Closing Transaction AJAB).
One should not post any business transactions in a new Fiscal Year before the Fiscal Year change is taken up. Posting in the old Fiscal Year can be
continued, even after the Fiscal year Change, as already mentioned above. The system automatically corrects any values which are affected by
postings in the past
Let's see an example here. Let's take a scenario where there are two open Fiscal Yea(s) for Assets are 2016 and 2017. Now, if Fiscal Year 2018 need
to be opened, then one should consider closing Fiscal Year 2016. To congurate this situation, one need to access Transaction Code OAAQ (Change
View "Remove Year-End Closing for Company Code": Overview).
Now, consider closing Fiscal Year in Asset Accounting with Transaction Code AJAB (Refer Screenshot above).
As a next step, consider opening a Fiscal Year in Asset Accounting with Transaction Code: AJRW (Refer Screenshot Above)
Later, consider copying a Document Number Range Interval for the next Fiscal Year with Transaction OBH2.
Later open posting periods for the next Fiscal Year with Transaction Code OB52.
Cross Company Code Depreciation Postings
Skip to end of metadata
Common Abbreviations
CoD = Chart of Depreciation
CC = Company Code
Occuring Issues
Customer upgrades from release prior to R/3 Enterprise (4.70) and detects differences between cross-company postings done by the old
depreciation program (RABUCH00) vs. the new depreciation program (RAPOST2000).
Often the Cost Center has a different company code assigned, RABUCH00 did not post the depreciation to this foreign company code (=
cross-company), but RAPOST2000 ends with error message KI 223 (Cost center &/& can only be assigned to in company code &).
In some cases customer complains that other G/L transactions (FB01, etc.) allow posting to TCODE used in this transaction without errors,
even if the cost center has a different company code assigned, but RAPOST2000 ends with error message KI 223 (Cost center &/& can only be
assigned to in company code &).
In seldom cases the customer does not know the document number determination for these postings, because it changed also from
RABUCH00 to RAPOST2000
Basic Functionality
IMG
Asset Accounting
Master Data
cost accounting extends across company codes (several company codes belong to one controlling area) and
account assignment of cost accounting depreciation from Asset Accounting to cost centers that are in different company codes than the
asset.
When you enter a cost center in the asset master record, the standard system checks if this cost center exists in the same company code as the asset.
You are not allowed to enter a cost center in a different company code.
In this step, you can make this check less strict. The system then only checks whether the cost center exists in the given controlling area.
Example
Asset: 30051 -> Company code of the asset: 0001 -> Cost center in the asset: SAP-DUMMY -> Company code of cost center SAP-DUMMY: 1000
Excursus CO
Company Code Maintenance in Cost Center Master Record only when Cross-Company Code Cost Accounting is active in Controlling Area (OX06)
This is the first pitfall when upgrading to RAPOST2000. New depreciation report initially uses cost center information. As additional check T093C-
BKRAKT is checked. If inconsistent information is determined, RAPOST2000 will end with errors
Important note:
Deactivating the company code check has an effect on all postings in external FI since CO objects from other company codes can generally be
assigned to an account as a result. A reconciliation between G/L and cost accounting is no longer possible.
Deactivate the company code check is only possible if the reconciliation ledger is not active (Deactivate Reconciliation Ledger: Transaction KALB).
Basic Intention
If depreciation is posted in company code X for the cost-accounting depreciation area "fixed assets" that points at a cost center K in another company
code Y, two documents are created (one for each account assignment):
Document 2:
============================
Debits/credits Account Company code Cost center
D clearing acc. X -
C depr. clearing acc. X -
All company codes "X1, X2 ..." with fixed assets use same doc type for depreciation posting (e.g. AF). Corresponding number ranges over company
codes "X1, X2 ..." may have no overlaps. In addition, the number range for document type AF must be maintained in company code Y of the cost
centers and all number ranges for document type AF must be across company codes "X1, X2 ..." or chosen internally.
If fixed assets are also contained in company code Y, then in Y a document type other than the AF document type for the "X1, X2, ..." company codes
(e.g. AG) must be chosen as document type for the depreciation posting runs. The number range of document type AG across company code Y may
not overlap with the number ranges of document type AF across company codes "X1, X2, ...".
Document type for cross-company code depreciation posting must meet the following conditions:
Enhancement: only 2 document types needed, AF used for depreciation postings in all company codes, AZ will always be used for cross-
company postings!
Document type for cross-company code depreciation posting must meet the following conditions:
It needs not to be different from AF, can be the same as the regular depr. document type
Many customers do not want to use open item managed accounts in their local GAAP for postings from the CO-only depreciation area (e.g. area 20) ...
this is a conflict, because is only one IMG step for any purposes
Assumption: Accounting Interface creates automated cross-company postings only if balance per document per company code is not balancing.
Solution: Asset Accounting line item generator enriches created document, so that in each affected company code balance zero is given before
passing the document to Accounting Interface.
Use of method ADD_DOC_LINES in Business Add-In BADI_FIAA_DOCLINES for Asset Accounting line item generator.
Coding Template released in note 723611 (RAPOST2000: Cross-company code postings in calc. Area)
Functionality: take depreciation line item for sending company code (offset account) and
Duplicate entry with twisted posting indicator and twisted posting amount in sending company code to identical account
Duplicate entry with an identical posting in receiving company code to identical account
-> G/L document balances in all company codes before passing the document to Accounting Interface
51860 Cross company code depreciat. posting runs > F5152 (> for RABUCH00)
https://help.sap.com/doc/saphelp_glossary/latest/en-US/35/2cd77bd7705394e10000009b387c12/frameset.htm
0 Likes
Helpful Answer
by
Sarma tadikonda
Not what you were looking for? View more on this topic or Ask a question
6 replies
Hi,
Following is the difference
ASKB:
You can post the values of depreciation areas to the general ledger directly, without having to
generate a batch-input session, using a new periodic APC posting run. In addition, you can directly
update the values of depreciation areas to a ledger during the posting transaction. This direct
update is similar to online posting used for the master depreciation area.
Following is the procedure
1. ASKB
2. Enter the required dataThe update run of the report has to be executed in the background, in
order to improve system performance. Therefore, start the report in the background Report
selection screen: Program >Execute in Background
3. Check the log of the APC posting run
4. Generate an asset history sheet for the depreciation areas posted
5. Compare the asset history sheet values with the balances of the corresponding reconciliation
accounts in the general ledger.
AFAB
Posting of Depreciation.
The calculation and scheduling of depreciation, interest and revaluation are automatically
controlled by keys in the system, or you can control them manually using a special posting
transaction. In both cases, planned depreciation from Asset Accounting has to be periodically
posted to the corresponding asset and expense accounts of the general ledger. In addition to the
various depreciation types, interest and revaluation, this posting run also posts the allocation and
write-off of special reserves.
Ihope this found useful to you.
Regards,
Jigar
0 likes
Hi,
AFAB is used to post only the dep at the end of the period generally.
whereas ASKB is used to post any APC values for an asset at any period of time...
Hope you are clear..
Cheers
Raghu
0 likes
Helpful Answer
We specify how depreciation areas should post to the general ledger as below using transaction
code OABX.
o no values (0)
o APC transactions online and depreciation in periodic processing (1)
o APC transactions in periodic processing and depreciation in periodic processing (2)
o only depreciation in periodic processing.(3)
Normally we use Option (APC online and depreciation in Periodic) for book depreciation area (01)
The depreciation areas for which APC transactions in periodic processing and depreciation in
periodic processing is specified, to post to general ledger for those depreciation areas we use
ASKB transaction.
AFAB is used for periodic depreciation posting.
0 likes
Helpful Answer
solved
0 likes
sap_erp_financials
enterprise_resource_planning
mysap query
0 Likes
Not what you were looking for? View more on this topic or Ask a question
10 replies
Hi Rekha,
ASKBN or ASKB : Periodic asset posting will update acquisition and depreciation in depreciation
area other than area 01 which are maintained as post "APC and depreciation on periodic basis" by
using ASKB or ASKBN
Separate set of GL accounts will be used for ASKBN. You can run ASKBN or ASKB as and when
you need it and not necessarily Month end
AFAB : To post a book depreciation at every period and this activity usually every month end
which posts depreciation 01 Book Depreciation and other areas maintained as real time at OADB.
Regards
Eugene
0 likes
Hi,
If you want to post different APC values in different ledger, you have to use ASKB
e.g. area 01: IGAAP
e.g. area 50: IFRS
AFAB - It will post dep as per respective depreciation area
ASKB - It will post difference in APC values (area 01 - 50) on asset sale during the year
Hope this helps
Thank You
Nishu
0 likes
Hi,
According to me, ASKBN is to be used periodically after month end activity of Depreciation
posting through AFAB is done. The purpose is to rectify the difference between the ledgers due to
parallel depreciation area. By this the amount will be posted in the other depreciation area in
which the Asset Values are not taken like Revaluation Depreciation Area.
Regards,
Malhar.
0 likes
Can you please let me know what tcode can i use to see the document posted through ASKB.The
document posted in non leading ledger.But i cant see it in fagll03 against the GL or asset.
Please advice.
0 likes
Hi,
ASKB is used for having the depreciation areas to be updated for values of asset related postings.
This is basically used for having the update in depreciation areas other than the main
depreciation area.
For example if the client requires reporting as per USGAAP and also IFRS then if we say the basic
depreciation area is USGAAP and then for the values to be updated for assets posting in IFRS you
need to use ASKB.
Hope it helps
Regards
Venkat
0 likes
Hi,
this is a "safety" feature of the general periodic posting functionality which becomes necessary in
case a "direct" update fails.
The "direct" posting functionality (posting indicator 4) does not update the FI documents realtime
(like posting indicator 1). When using posting indicator 4 the system tries to post the document
"directly" after the realtime postings, but in an asynchronous way. That implies that errors during
the posting will NOT be propagated to the user in dialog, it will simply cause a failure in document
posting.
That also means the user does not get any notification about the failure in posting. There is only a
possibility in transaction ARAL to check if direct postings failed.
However, to avoid now data inconsistencies ASKB has to be run - at least once before fiscal year
closure -, as ASKB is capable to "pick up" these failed direct postings and posts it to G/L.
In case no direct posting failed, ASKB will not post anything but update the log tables that way
that you can close the fiscal year. In this case it just operates as a failsafe check to ensure all
items have been posted before closing the year.
Kind Regards,
Markus
0 likes
Srinivasa CT replied
Jam000 Jam000
0 Likes
Not what you were looking for? View more on this topic or Ask a question
3 replies
P. Annotee replied
In the 6.0 version you have to assign s document type for periodical postings, go to the part
Intergration with FI in config.
From now the numberrange assigned to should be internal and no longer external!
0 likes
Hi,
Go to IMG and assign the document type in the Path:
Asset Accounting - Integration with General Ledger - Post APC values periodically to the General
Ledger - Specify Document type for peridical Posting of Asset Values.
Thanks,
Raja.
ASKBN will be used when you want to post values to two real depreciation areas.
As SAP cannot post to two real depreication areas on real time, you need to post values to the other areas usign ASKBN.
This useful when you have 2 ledgers and each ledger is used for one depreciation area lets say Local GAAP and US GAAP
where the APC values and the rates of depreciations are different.
y ASKBN system arrives the differential values between APC, Dpereciation for different depreciation areas which AFABN doesn't
do.
More Over ASKBN checks thoroughly than AFABN.
Reports
Bureau Asset Accountant
OMF Asset Accountant
Reports
S_ALR_87010175 Display Posted Depreciation by Cost Center
S_ALR_87011963 Display Export Annual Inventory (Balances)
S_ALR_87011979 Display Physical Inventory List
S_ALR_87011990 Display Asset History
S_ALR_87012037 Display Changes to Asset Master Records
S_ALR_87012050 Display Asset Acquisitions
S_ALR_87012052 Display Asset Retirements
S_ALR_87012054 Display Asset Transfers
S_ALR_87012056 Display Directory of Unposted Assets
S_ALR_87012066 Display Analysis of Retirement Revenue
S_P99_41000192 Display Posted Depreciation by Asset-Period
Update 5 August 2013
Bureau accountants are responsible for creating/maintaining Asset Master Records and posting fixed
asset transactions.
Job Aid
Processing Trade-In Value
Work Instructions
AB08 Reverse Asset Transaction
ABAON Asset Retirement by Sale
ABAVN Retire Asset by Trade-In and Scrapping
ABNE Add Subsequent Revenue to Asset Retirement
ABNK Post Subsequent Costs to Scrapped Asset
ABUMN Post Asset Transfer
ABZON Post Asset Donation
AS01 Create Main Asset
AS11 Create Sub-Asset
CJ20N Create Settlement Rules and Set TECO Status
CJ88 Capitalize Final Depreciating Asset (FDA) from AUCs
Change Documentation
The OMF Asset Accountant is responsible for transactions related to month-end and year-end
processes, including depreciation posting and maintaining full accrual accounts.
Work Instructions