Ready to enhance your SAP AR01 report? Check out the guide for step-by-step instructions on adding custom fields and maximizing your asset insights!
Meryem Gizem Ersen
gizem.ersen@revola.com.tr
SAP FICO Consultant, Revola Consulting
The AR01 report is a key tool used to display detailed information about assets within a specific depreciation area. This report provides crucial insights into the financial status of fixed assets for a given fiscal year. Here's what the AR01 report typically includes for each asset:
Cumulative Acquisition Value at the Beginning of the Fiscal Year: This represents the total acquisition cost of the asset at the start of the fiscal year.
Accumulated Depreciation: This shows the total depreciation calculated for the asset, including the planned depreciation for the current fiscal year.
Planned Book Value at the End of the Reporting Year: This indicates the expected book value of the asset at the end of the fiscal year.
In addition to these details, the AR01 report offers various standard versions that allow for primary selection and the creation of totals according to different criteria, such as asset class, business area, cost center, and more.
While the report displays depreciation area values using the standard fields of Asset Accounting, there are cases where adding new custom fields to the report is necessary.
This document provides a step-by-step guide for incorporating a new field into the AR01 report and explains when additional steps are required to ensure the new field is populated correctly.
Call the transaction SE11 and enter the Data Type ‘FIAA_SALVTAV_RABEST’.
Click on “Include” to access the CI_REPRABEST structure.
Figure 1.FIAA_SALVTAB_RABEST Structure
Add the new field to the CI_REPRABEST structure. This action will integrate the new field into the report's data structures.
Figure 2.Structure View with Newly Added Field
Since the field definition was initially created in Turkish, it was necessary to ensure that the definitions appear in English when logging in with the 'EN' language setting. Therefore, the data elements of the newly added fields can be translated from Turkish to English using SE63 or by double-clicking on the data element and navigating to Goto ⇒ Translation.
Figure 3.Data Element – Translation
Figure 4.From TR to EN Translation
When returning to the structure, it is confirmed that the definition of the newly added field in the 'EN' language is visible within the structure.
Figure 5.Field Definition After Translation
If the new field does not populate automatically after updating the CI_REPRABEST structure, an explicit enhancement must be implemented to manage custom data retrieval and processing.
Example enhancement location: The FILL_OUTTAB_LINE form. This is where you will specify how the new field acquires its value.
Figure 6.Example Location for Enhancement
Figure 7.Changing Layout
Figure 8.Making Hidden Field Visible
Figure 9.New Field Display in Report
References