Run: Upload the mapped data to SAP - Automate_Studio - Latest

Automate Studio with Studio Administrator User Guide
Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio
Version
Latest
Language
English
Product name
Automate Studio
Title
Automate Studio with Studio Administrator User Guide
Copyright
2024
First publish date
2018
Last updated
2024-07-22
Published on
2024-07-22T13:07:07.564657

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 SAP Fiori® script and data file that are being used.

Validate the data

First, check that the data meets all of the script's requirements by clicking Check Data. Click Validate to check each row in the worksheet.

For more details, see Validate before the run.

Run the script

  1. Click the Run tab.
  2. 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 GTIN field is recorded in the Fiori script that creates a Material using “Manage Product Master Data” app, then the script run time would increase for the subsequent runs.

An additional address row might be added due to an already present empty row during recording. To avoid this:
  1. Enter data in the first existing row.
  2. Click create to enter data for the next row.
  3. Delete any extra empty row post-recording.
  4. In the mapper, disable the screen named WIN_HELPER_Q which contains fields BusinessPartner, AddressNumber, and SideEffectsQualifier related to the delete action.

In some apps like, Post General Journal Entries, entering credit amounts for the first line item and both debit and credit amounts for the second line-item results in an unbalanced document. The app does not allow posting of an unbalanced document and sets one of the values to zero. Ensure the document is balanced before posting.

Cost Center Management: On running the script, an error might be logged, but validation shows success. This happens because the Activation call is not replayed during the validate action.

During script execution, SAP is unable to locate the popup control, causing an error. Use the Change Condition Contract - WCOCO app, which offers the same functionality.

Fix errors

  1. Correct the values.
  2. Click the arrow on the Run button, and then click Run Only Error Rows.

Studio 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 the system. Re-login might be necessary.
  • File Drop: Drag and drop of attachments is not supported in the Fiori recording dialog

  • Some apps, like Manage Prices Sales, do not support recording for editing data due to lack of draft functionality.

Note: When you delete a row from the table, data is deleted with incorrect message.

Handling Error Messages in Run Logs

When you encounter an error message in the run logs, please note the following:

  1. Source of Error Messages: Error messages typically originate from the last replayed call, which is a POST call.
  2. Validation Process:
    • During the validation process, we do not replay the POST call since we do not intend to post data to SAP.
    • Instead, we retrieve responses from the previous preparation and simulation calls.
    • If no errors are found in these calls, the validation is considered successful.

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.
  • Upload Delay (ms): To add a slight processing delay (in milliseconds) between each row for transactions that require a delay for commit code processing.

For troubleshooting specific situations, see Automate Support.