After mapping SAP fields in the Mapper to the columns in the data file, you enter the data and run the script. Each row of data in the data file is uploaded to SAP.
You can upload the data from the Run tab in Studio, or you can use the Excel Add-in.
Click the Run tab to view commands for validating and running the script.
The Run tab displays details about the GUI for HTML App script and data file that are being used.
Validate the data
For more details, see Validate before the run.
Run the script
- Click the Run tab.
- Click the top of the Run button, or click the arrow and choose an
option.
If prompted, save the script file.
If errors occur while the script is running, Studio continues to upload data for any remaining records. In Excel, any success and error messages returned from SAP are logged into the log result column, with one log per record.
If you are unable to connect to SAP, update the Shuttlerule file with the AdvancedUITypeGUIHTMLApps configuration. Add the comma-separated T-Codes to this property to run Advanced GUI for HTML apps.
Fix errors
- Correct the values.
- Click the arrow on the Run button, and then click Run Only Error Rows.
Studio Transaction uploads only the corrected records.
Validation and Error Handling
- Unsupported Apps: Validation is not supported for certain apps like "Manage Global Accounting Hierarchies," "Manage Bank," and "Manage Flexible Hierarchies." This is indicated by messages stating "Validation is not supported."
- Incorrect Error Messages: An invalid debit/credit indicator might display an incorrect error message. These messages originate from SAP.
- Recording Limitations: For apps like Bill Of Material, recording single deletions captures valid data. Errors such as You must enter material/plant/usage reflect SAP's messages and are not altered by Automate Studio.
- Session Expiry: Users might see an error message for session expiration while still appearing connected to SAP system. Re-login might be necessary.
-
If Underlying connection was closed error appears on running script with large number of records, the <ReloginWebGUIConnectionValue> key has been implemented in the Shuttle Rule file with the default value set as 100.
Run options for script developers and runners
These options can be chosen by the script developer or the script runner when the script is run.
- Run Specified Range: To upload only some of the rows in your data file. Use the Start Row and End Row boxes to specify the range.
- Run First 5 Transactions: To test the data by running the first five rows, or the first five header plus line item transactions, in the data file. This is helpful before you start a large run.
- Run Error Rows and Unprocessed Rows in a single step: To process Error Rows (rows in which you have fixed the data) AND Unprocessed Rows (rows which have been added or were not processed because the run stopped) in a single step.
- Run Only Error Rows: To process rows after you have fixed the data in them.
- Run Only Unprocessed Rows: To run rows that have been added or were not processed because the run stopped. This option can be set by the person running the script.
The following options can be set only by the script developer:
- Require Run Reason: To open the Run reason box when the script is run. Studio adds some basic information about the script, but the person who starts the run can provide more details.
- Run Only Unprocessed: To run rows that have been added or were not processed because the run stopped. This check box can be selected only by the script developer.
For troubleshooting specific situations, see Automate Support.