before the run
Validation checks the data row-by-row, but it does not check the document as a whole. To check the entire document, click Simulate.
Note: Validate will not check upload fields in the last screen of the recording. Any errors in those fields will be returned during the run.
When data validation is turned on, you do not need a separate validation sheet.
Turn on data validation
Important: Before you turn validation on, be sure that the script contains only one commit code and that the commit code appears at the end of the script.
A commit code represents any kind of save action. Example commit code values include =BU and =SICH.
If a transaction script contains more than one commit code, some of the data might be committed to SAP during validation in Studio v11 and v11.0.1. This has been fixed in Studio v11.0.2.
Exception: PA30 and PA40 are supported if Winshuttle Function Module v11.1 or later is installed and the script contains only one commit code.
- On the Map tab, click Allow Validation.
Studio automatically adds the Validate Log field to the Mapper and maps it to the data file.
Validate the data against the script's rules
Click Check Data to check that the data meets all the script's requirements for required fields and allowed values. You do not need to be logged on to SAP.
Validate the data against SAP
Validate checks the fields in each line item against both the script's requirements and the requirements in SAP. Errors are returned against the individual line items, and the results are written back to the data file against each line item. Validate does not check the document as a whole. Validate is not supported for HR t-codes except PA30 and PA40.
You must be logged on to SAP. You can log on from the lower left area of the status bar on the Run tab.
Next, validate the line items against SAP.
- On the Run tab, click Validate.
When you validate, the data is uploaded to SAP but it is not committed to SAP, as long as there is only one commit code and it is at the end of the script.
- Correct any errors or make changes.
- Click Run to upload the data.
Studio gives you additional validation options. Click the arrow below the Validate button to do any of the following:
- Validate Specified Range
- Validate First 5 Transactions
- Validate Only Error Rows
- Validate Only Unprocessed Rows
Note: When you click Validate Only Unprocessed Rows, the setting can be changed only by you, the script developer. Runners cannot change this setting.
Validating data in loops
In an Excel data file, validation checks all line items, and the validation log messages appear next to the individual line items.
Winshuttle Function Module does not support validation of multiple Do-While loops at the same level in a transaction script. Nested loops are supported.
Validation is not supported for Access data files that contain loops.
Validating linked scripts
You can run validation on linked scripts in the following configurations:
- Column-based mapping and cell-based mapping in Excel forms
- Column-based mapping in Access forms
- Column-based files linked to cell-based files and vice versa
- Linked scripts with different types of data files
Validation for cell-based mapping
When you turn on validation for the script, Studio automatically maps the Validate Log column to the first empty row. In the Mapper, the Validate Log row appears below the Log row.
Simulate checks the fields in each line item against the script's requirements and checks the entire document against the requirements in SAP. Click Simulate, or click the arrow for the following options:
- Simulate Specified Range
- Simulate First 5 Transactions
- Simulate Only Error Rows
- Simulate Only Unprocessed Rows
In Studio v11.0, Simulate is available for these t-codes: FB50, FB60, FB70, ME21N, ME22N, ME51N, PA30, PA40, VA01, VA02.
Studio 11.1.0 also supports FB01, FBD1, and FBS1.
Studio 11.3.0 provides support for these additional t-codes: F-02, F-05, F-22, F-43, F-65, FB01L, FB50L, FB65, FB75, FBB1, FBV1, FV50, FV50L, FV60, FV65, FV70, FV75.