Show TOC

Read-Only Data Based on RecordingsLocate this document in the navigation structure


You can record a transaction for the purposes of displaying the data from a specific SAP backend system, using the Read operation.


Make sure that the transaction you record is for reading data, for example, XD03.

Controls: Tables and Fields

Recordings that include the read operation can contain data about controls and fields within a screen, such as, text controls, and table controls.

When you expand the recorded screen, you can display the fields in the screen, as well as, the field names as they exist in your SAP system.

If you want the recording to read data within a table, make sure that your table has some content, and that the transaction provides functionality such as, buttons, and function keys that enable you to page through the table.


If you record an empty table control at design-time, you cannot add data to it at runtime.

If Screen Scraping does not identify table paging functionality in the recording, it provides a warning message. At runtime, it will display only the number of lines that were visible during the recording.

General Guidelines for Recording a Table Control with Content

Record paging through the table by placing the cursor on the same table entry and click twice the page down button, Table paging control.

To record all the entries in a table, make sure that you position the cursor on the same entry while clicking the page down button twice.

Assigning Constant Values During the Recording

In Screen Scraping, you assign one or more fields as constant data objects during the recording. You assign a field as a constant data object by selecting it or entering a value.

In addition, the value you specify during the recording, is captured and made available in the recorded value column. You can then set this value as a constant value.

The constant you assign at design-time help in the flow of the operation during the runtime of your Data Model.

Fields designated as constants contain initial recorded values. Do not set constant values for an attribute that has already been mapped to the key Property.


Using a Data Model based on the transaction, XD03, you can set and specify the constants as in the example below.

When the recording begins, select the checkboxes in the initial screen for Address and Marketing. Your selection designates them as constants.

In order to have the data about the tabs, Address and Marketing available at runtime, set constant values for them in the mapping screen.

To set the constant value, select the relevant attribute in the Map Operation dialog screen, and then choose Set Constant Value. Enter the same value as displayed in the column, Recorded Value, in this case 'X' (include the single quotes), and close the Map Operation dialog screen.

More Information

For more information about recordings, see Recording a transaction code, its screens and its fields.