Now we are ready to run mass update to material master weights. We are going to use 'MM02' transaction, take material number from column A and weights from column B and C.
However, we have not yet told Process Runner which Excel file to use. We will do that now as you see in screen shot below in step 1, 2 and 3.
We are now ready to do a small test run. We will start from Excel row 2 and stop at row 3. Finally we will click on Run button.
When you click Run – Process Runner will perform following actions:
1.SAP Logon: Select correct system; provide client, user name, password and language to logon.
2.Once logon is successfully, Process Runner will read recorded transaction and mapping instructions we carried out in earlier steps.
3.Process Runner will build data package by merging recorded transaction with mapped Excel and other values and send this package to SAP transaction for processing.
4.Once SAP is finishing executing the transaction, Process Runner will retrieve transaction status and message from SAP and place that next available empty columns in the spreadsheet.
5.Repeats this process for all the Excel rows we selected to run.
6.Finally, log itself off from the SAP system.
This sounds a lot but it is done in amazingly fast speed. Process Runner will report and log exactly how long it took to run given set of transactions.
At the end of the test run, our example Excel spreadsheet should look like this:
Upon this verification in SAP, we successfully completed our 'Test Run'! We are ready for our next and final step. We are now ready to do full blast run. Change End row value to something big and Process Runner will run till it finds data in that sheet. As Process Runner executes all these calls, it posts all the logs from SAP as it runs. You can switch to Excel and see what kinds of messages are returned.
Hint: Process Runner is running; make sure you do not do anything that would lock Excel file. We recommend that you do not touch Excel.
We are done with our Transaction tutorial.
Next |
|