Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Former Member
  1. Introduction to Worklist Functionality in SAP

On numerous instances an entity might want to carry out mass retirements, mass transfers or mass changes to asset master data. For example, an organization might dispose a major portion of its Fixed Account and might have to account for the retirement of the same in its books.

This document explains the usage of worklist functionality in asset accounting. This functionality enables the us to carry out mass transactions like retirement, transfers etc. without having to develop an LSMW for the same. The worklist functionality can be used to:

  • Carrying out mass retirement of asset without revenue or with revenue.
  • Mass inter-company asset transfer.
  • Making mass changes to asset master data

The usage of worklist functionality for each of these instances is explained subsequently. Basically this functionality would involve two steps:

a) Grouping assets for which similar processing has to be done-this is achieved by creation of worklist. b) Releasing the worklist so created which would complete the processing on the assets(i.e. transfer, changes or retirement).

This document would describe the usage of worklist functionality to carry out mass retirement with revenue and without revenue and mass intercompany asset transfer The other instances i.e. mass changes to asset master involves some additional steps and are described in Part II of the document.


2.1  Retirement of Assets (without Revenue)

The retirement of assets can be carried out using the transaction code ABAVN. However when an entity desires to retire more than one asset
at a time it can use the worklist functionality to post the mass retirement of assets. This will enable the entity to post the retirement of all assets at a time.

For creation of worklist, following is the path:

Easy Access Path:
Accounting - Financial accounting - Fixed assets - Environment - Worklist –Generate. (T-code is AR01)

At this stage we enter the company code, asset number and asset sub number of the assets which have to be retired. There is possibility of giving additional selection options like asset class, cost center, plant also as given in the screenshot below:


Thereafter we proceed to create the Worklist by clicking on the ‘Worklist’ tab in the following screen that appears on execution:

We give the name of the worklist (any task- name to be input by the user) and the retirement option (in this case Retirement without

In addition, we enter various other parameters like the posting date, document date, asset value date and transaction type for posting the mass retirement. The text that has to be populated during the retirement also has to be entered.

On doing so a work queue gets added. All the selected assets which we need to be retired get added to this work queue.

The next step is to release the worklist. The easy access path for the same is Accounting - Financial accounting - Fixed assets -
Environment - Worklist – Edit (T-code for the same is AR31)

In the screen that appears, we give the work queue number and execute the same. Then we release the work queue as shown below:

  Once released, the following screen appears:

Check the error log for errors if any:

The entry that gets passed is given below. The accumulated depreciation account is debited and the corresponding asset account is
credited. The text given at the time of creation of worklist gets populated here as shown below:

2.2  Retirement of Assets (with Revenue)

The retirement of assets with revenue is similar to the retirement of assets without revenue except for the accounting treatment that has to be followed in case of the resultant revenue derived from the sale of asset and the proportion of distribution of the same to the various assets.

The assets that have to be retired are added to a worklist by using transaction AR01:

An additional step that has to be followed in case of retirement with revenue is to determine the sale proceeds that will be realized from the assets and the proportion in which the same will be distributed amongst various assets.

The manner of distribution of sale proceeds can be either of the following:

  • As per Acquisition costs
  • As per net value
  • Or any manner defined by the user

Once the same is determined, a work Queue gets added:

  The same is then released in transaction AR31 for release of worklist:

The status changes to completed when the processing is complete

The accounting entry that gets generated on retirement is described below:

Since the asset was fully depreciated,  accumulated depreciation and asset account is fully reversed. The entire proceeds from sales is  taken as revenue. Revenue of100 EUR is distributed in proportion to the acquisition cost amongst the three assets that have been retired.

2.3  Mass Inter Company Asset transfer

Assets Transfer from one company code to another mainly happens in case of restructuring of an organization when a change in company code is necessitated. The standard transaction for executing this is ABT1N.  However when an enterprise desires to do a mass Inter company asset transfer in SAP,  the same can be made using the worklist functionality. Like retirement of assets, this involves creation of worklist and release of the same.

A worklist as described above is created using the transaction code AR01. All assets that have to be transferred are given in the selection criteria as shown below:

These assets are then added to the worklist as shown below:

In the selection screen that appears subsequently, the target assets to which the transfer has to be made is given. The transfer variants have to be selected based on the options available in the dropdown The transfer variant specifies the valuation method and the transaction type for posting an asset transfer:

As described above in retirement, a work queue gets added and the same has to be released in the transaction code AR31 as below:

Once the transfer is successful, acquisition cost and accumulated depreciation value becomes 0 in the books of the transferor company:

The entry that is passed at the time of retirement is as follows:

In the books of transferor company, Asset Account is credited and the accumulated depreciation account is debited.

In the books of the transferee company the reverse entry takes place.

The usage of worklist functionality for mass changes to asset master would involve an additional step, i.e. creation of Substitution Rule. These are described in Part II of this document-the link for which I shall update shortly

Labels in this area