Transact Troubleshooting Advice

Parameterisation

The most common reasons for Transact runs to fail are incorrect parameterisation and/or data in the spreadsheet columns not matching the parameter sequence.

Almost all Transact problems fall into this category!

Try creating an Excel template (from Transact's main screen) and comparing the columns in this sheet to the columns in your data file.

ActiveX

Some SAP transactions contain “ActiveX” controls on their screens. An example of this would be the ‘Purchase Order Text' view on a material master.

Batch input is unable to process screens which contain ActiveX controls, therefore, Transact is also unable to process these screens. This is because the ActiveX controls require an active SAP GUI. QuickScript does not have such limitations and will happily run any SAP transaction.

Note that, sometimes, older versions of SAP transactions may be fine whilst newer versions may fail (e.g. try MB01 instead of MIGO – incidentally, we've never had any reported problems with MIGO, this is just an example!).

“Commands”

Surprisingly (or maybe not, given the size of SAP) some transactions have in-built inconsistencies in that the “command” they send to the processor for key-presses, menu selections, or button-clicks, may differ.

For example, we have had reports from users recording classification transactions that clicking a button on the toolbar produces a recording that will not re-play - but choosing the same option from the menu produces a recording that will replay!

So, our advice, if a recording does not run, and alternative methods of input are available (e.g. an F key or menu option) try recording using the alternative.

This is an unusual (rather than common) problem but is still worth having in your ‘trouble-shooting armoury'!

Diagnostic Procedure

If you are still experiencing problems, the following ‘diagnostic procedure' might be helpful.

Step 1:
If the recording does not run using “Direct Run” try (with a smaller data set) creating a batch input file.

Upload the created batch input in SM35 and run in foreground, stepping through each screen. This should help you identify the problem. Remember, Transact simply re-runs what has already been recorded.

If there are problems with the recording then Transact will not be able to run it.

Step2:
If step 1 didn't help then you could try the following.