Retrieving Long Text for Document Line Item in SAP: A Step-by-Step Guide

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

Introduction

    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.

Solution

• 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 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.

Steps for Retrieving Long Text

The long texts associated with document line items are stored in two primary tables: STXH (Header) and STXL (Lines). To retrieve these texts, the READ_TEXT function module is employed. The following is a step-by-step guide for retrieving long text by identifying and using the appropriate parameters.

1. Identifying the Parameters from Table STXH: First, the STXH table must be used to identify the necessary parameters for the READ_TEXT function module. Specifically, the STXH-TDNAME field must be constructed by concatenating the company code, document number, fiscal year, and document item.

2. Executing the READ_TEXT Function Module: Long texts are retrieved from the database using the READ_TEXT function module. The function requires the input of four key parameters, which can be obtained from the STXH table. To execute the function module:

ID: Text ID(from STXH)

LANGUAGE: Language Key(from STXH)

NAME: Text Name(from STXH)

OBJECT: Text Object(from STXH)

3. Retrieving and Displaying the Long Text After executing the READ_TEXT function module, the long text associated with the document line item will be displayed on the screen. The four parameters previously identified must be correctly entered to ensure the proper retrieval of the text.

References

1.      SAP Help Portal.(n.d.). Long Text Fields – Tips. Retrieved from Long Text Fields - Tips | SAP Help Portal

2.      SAP Community. (2023). FI Document Line Item Long Text – Store in Which Table? Retrieved from https://community.sap.com/t5/application-development-discussions/fi-document-line-item-long-text-store-in-which-table/td-p/3341779