In tests, when you record with the Auto-parameterize table and grid controls option and you perform an operation that sends data to the SAP server after setting table or grid cell values, UFT:
Creates a new data sheet to represent the table or grid. Each data sheet is a sub-sheet of the action in which the table or grid operations were recorded. The data sheet name is always the action name followed by a period (.) and the internal name of the table or grid. For example: Action1.FLIGHT_TABLE
Adds a column to the data sheet for each table or grid column in which you record. (Columns in which you did not set any cell data are not added to the data sheet.) The name of the column in the data sheet is generally the same as the name of the column in your application.
If a column in the application does not have a header, or more than one column header has the same name, UFT inserts a column with a name in the format: _ _<index>, where <index> represents the column number according to its location when you record the Input step.
Inserts the values you set during the recording session into the appropriate cells in the data sheet. Each row in which you entered data is represented by a row in the data sheet. Place-holder (empty) rows are added for rows above the rows in which you recorded. For example, if you set data in rows 2, 4, and 7, seven rows are added to the data sheet. The cells in rows 1, 3, 5, and 6 do not contain any data.
Inserts an additional end row where the value of the first cell in the row is .END.
Inserts an Input <DataSheetName> statement (followed by a SelectCell statement) into your test.
The Input statement instructs UFT to enter values from the data sheet into the table or grid corresponding to the data sheet name, similar to an automatically parameterized statement referring to a special sheet in the Data pane.
Example: Suppose you update values in a table control containing airline flight information. You update some airline codes, add state and country names to some of the departure and destination cities, update one of the destination airport codes, and update some of the departure times. The edited table in your application may look something like this:
UFT inserts the following Input statement in your test to represent the data input:
SAPGuiSession("Session").SAPGuiWindow("SAP R/3").SAPGuiTable("SPFLI").Input "Action1.SPFLI"
If you record on a table or grid that scrolls using the ENTER key rather than the PAGEDOWN key, you may need to manually add the ScrollMethod optional argument. For details, see Data in rows that require scrolling.
The corresponding data sheet in your Data pane looks like this:
There are three rows in the data sheet, because data was modified in the first three rows of the table or grid in the application. Note that the data sheet does not contain columns for the Airfare and Plane Type columns, because no values were modified in those columns during the recording session.