Key Features and Benefits Summary
- Use data in a spreadsheet to run virtually any SAP Transaction, on-line or using batch input.
- Record, import, parameterise, prepare your data and then run – that’s it! Five quick and easy steps to running almost any SAP Transaction, any number of times.
- No transports required.
- No ABAP programming, or any programming required.
- No changes to standard SAP are needed, ProCapture is a desktop tool – simply install and run.
- Gives functional consultants independence from ABAP programmers, allowing them to become responsible for, for example, data conversions.
- Releases ABAP resources from these time consuming tasks, allowing them to work on other activities.
- Rapid implementation of data uploads, without programming.
- Invaluable tool for SAP support teams: assisting in activities from population of new fields on existing master data, to reversing documents resulting from interface files being run twice.
On-Line Training and Demonstrations
These demonstrations are intended primarily as training aids, to get new users quickly up-to-speed with the use of our products.
They can also be viewed by people considering a purchase, to receive an appreciation of what out products can do. If you are interested in purchasing our products and require further information please contact prosuite@progresspacific.com
Please note, if viewing these demonstations for training purposes, that they should be viewed in sequence as later demonstrations do not necessarily repeat hints and tips contained in earlier demonstrations.
Pro Capture Demonstrations
The Pro Capture demonstrations focus largely on the SAP related aspects of using Pro Capture, e.g. downloading recordings, uploading and executing a batch input session. It is these topics that our users ask about most.
The first two demonstrations are applicable whether preparing for batch input or a direct run, as is the first part of the third demonstration.
Demo 1
This is a short demonstration intended to assist those that are not familiar with downloading recordings from SAP. It does not show the making of the recording, only how to download a previously made recording
Demo 2 Import a Recording & Parameterise
This demonstration shows the basic steps required to import a downloaded recording into Pro Capture. The steps shown are:- importing a recording;
- using the parameterisation wizard;
- creating an excel template.
Demo 3
Prepare, Upload and Run a Batch Input File This demonstrations has several distinct parts:- preparing a data file in Excel (note: also applicable to ‘Direct Run');
- creating a file for use in batch input;
- uploading a batch input file to SAP;
- executing the batch input file.
ProCapture Troubleshooting Advice
Parameterisation
The most common reasons for ProCapture runs to fail are incorrect parameterisation and/or data in the spreadsheet columns not matching the parameter sequence.
Almost all ProCapture 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 - butchoosing 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 ProCapture will not be able to run it.
Step2:
If step 1 didn’t help then you could try the following.
- If you didn’t save the recording in SHDB, when you originally made the recording, it is recommended that you record it again and save it.
- From inside SHDB you can run the recording directly (click “Process”, F8) and step through screen-by-screen (choose Processing Mode “A” “Display all Screens”).
- Verify that the original recording will run correctly in SAP – if it does not run in SAP it will not run from Transact.
- If it does run, try downloading again and re-importing to Transact.
- When parameterising, try not using the Wizard. Use the edit/change recording screen (set to show the full recording) and take great care during the edit. Chances are you’ll notice something important that you deleted the first time around
‘Batch Input’ Versus ‘Direct Run’
If you can wait, ‘Direct Run’ will usually be the best choice. This is not only because of the internal audit trail that Transact maintains of files that have been run, but, primarily, because it is so much easier to identify, separate, fix and re-run failed records with Transact than it is with Batch Input. In all cases, we would alwaysrecommend running at least a percentage of your transactions using ‘Direct Run’, so that you get an appreciation of the quality of your data before committing larger volumes to the batch input queue.
For larger volumes, batch input may be the best choice. The problem with using large volumes through Direct Run is that it runs on your PC and prevents you from using Transact for anything else whilst running the file. However, you could split your datainto smaller, more practical, files that can be more comfortably put through a Direct Run.
Being precise about what constitutes a ‘large volume’ is difficult as the time taken to run an SAP transaction is highly dependent upon the number of screens in the transaction – this can have a greater impact than the number of records to be run to the overall run-time.
In general, we would recommend not using Direct Run for a single data file containing more than 2,000 to 3,000 records. This is not because it can’t handle more, but because it is usually more convenient to put larger runs on a batch input queue and let them run.
If you have 10,000 records, or so, we would recommend splitting this into 3 or 4 smaller file sizes and doing several direct runs. Alternatively, you could do a single batch input for the whole 10,000. The choice is yours, but keep in mind the advantages with using direct run – you should really only choose batch input if you arevery confident that your data will run okay.
Even using batch input, for very large data volumes it is still more practical to split your files. Just from the perspective of managing problems and monitoring, we would recommend putting no more than 20,000 to 30,000 records through a single data file/batch input session. Additionally, for example, if you have 100,000 records to load, splitting into blocks of 20,000 also means that you can run 5 batch inputs in parallel – getting your data in faster.
ProCapture Frequently Asked Questions
Why do I keep getting password errors?
Newer versions of SAP allow the use of long passwords, previously only 8 character long passwords were allowed (and were case insensitive).
What SAP authorisations do I need for ProCapture?
In general, for any WinR3 product, you need the authorisations to run any transaction that you wish to record or run/replay.
For ProCapture to connect to SAP correctly your authorisations should include:
Authorisation object: S_RFC
with the following fields:
RFC_TYPE: FUGR
RFC_NAME : *
ACTVT: 16 or *
Is ProCapture compatible with older versions of SAP?
A special version of WinR3 Professional (not ProCapture), that is compatible with 3.x versions of SAP, can be provided. This requires a simple RFC function module to be implemented in your SAP system.
This version of WinR3 Professional, along with the function module, are available at the standard price of Transact and include a free upgrade to Transact at any time. However, only limited support will be provided for this version.
What reports are available to analyse my runs and run results?
There are no standard reports available. However, the Transact database is a simple, open, MS Access database which you can use to build your own reports.
Why do my Sales Order document numbers have an extra ‘2′?
When creating sales orders, the SAP RFC interface sometimes (often!) appends a 2 to the document number. Please take care and pay close attention to the document numbers created for any of your recordings that create sales orders.
