Now we are ready to run mass update to material master weights. We are going to use MM02 transaction, take material number from column Field1 and weights from Field2 and Field3.
However, we have not yet inform Process Runner DB which database table to use. For elementary transaction learning we will use internal XML Table called iTable
We are now ready to do a small test run. We will start from iTalbe row 1 and stop at row 50. Finally we will click on Run button.
When you click Run – Process Runner DB 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 DB will read recorded transaction and mapping instructions we carried out in earlier steps.
3.Process Runner DB will build data package by merging recorded transaction with mapped iTable and other values and send this package to SAP transaction for processing.
4.Once SAP is finishing executing the transaction, Process Runner DB will retrieve transaction status and message from SAP and place that in first and second columns of iTable.
5.Repeats this process for all the iTable 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 DB will report and log exactly how long it took to run given set of transactions.
At the end of the test run, our example iTable should look like this
Now, we should check weight data in SAP to verify that change actually occurred
…only those fields got changed which you intended and no other. Upon this verification in SAP, we successfully completed our Test Run. You can clearly see the updates in the below screen.
Next: