Key Features and Benefits Summary
- Automate any SAP transaction, for whatever reason, e.g. data correction, data load, new sales orders, financial document postings - in fact, anything at all that you have a lot of and don’t want to enter manually!
- Fast and efficient creation of SAP test scripts for automating unit, system and regression tests.
- Record yourself running a transaction and all your actions and data are recorded in a spreadsheet. Just add more data rows and then sit back and watch it run!
- Runs directly from within Microsoft Excel, no other applications or programs are needed.
- Records, and runs, not just single transactions, but sequences of transactions, enabling automatic end-to-end process testing.
- Includes a Data Wizard for assisting you in specifying outputs of a transaction to be used as inputs to another, subsequent, transaction.
- No transports.
- No ABAP programming, or any programming, is required.
- No additional programs need to be installed to SAP, in fact the only change usually needed to SAP is to enable scripting – a simple task.
- Easily regression test programs, transactions and end-to-end processes.
- Test scripts can be loaded into the test case tab of the configuration transaction in solution manager as test documents.
- Test scripts can then be planned into test packages for execution by testers from their assigned worklist.
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.
Demo 1 – Single Transaction
- making a ProScript recording
- entering data for a ‘run' of the script;
- running a script.
Demo 2 – Recording a Multi-Transaction Script
- creating a material master using MM01 (basic data view only);
- deleting the newly created material using MM06.
Demo 3 – Using the Wizard
The demonstration takes the recording made in the previous demonstration and uses the Wizard to set the input of the delete material transaction (MM06) to be the material number created in the first transaction (MM01).
Demo 4 – Running a Multi-Transaction Script
- adding data to the spreadsheet;
- running the script;
- reviewing the run results.
Frequently Asked Questions
What SAP authorisations do I need for ProScript?
How can I make my scripts use “today” for input data, instead of a fivxed date?
Can I rely on SAP’s parameter ID (PID) to carry forward data from one transaction to the next?
Can I make the script ‘Run’ faster?
Can I share scripts?
What SAP authorisations do I need for ProScript?
In general, for any ProSuite product, you need the authorisations to run any transaction that you wish to record or run/replay.
There is a comperhensive description of the additional SAP set-up required to run ProScript in the User Guide.
How can I make my scripts use “today” for input data, instead of a fixed date?
Very often, when a date is recorded, what you really need in your script is not a fixed date (the actual date that was recorded) but a relative date – e.g. “today” or “today + 1 week”. For example, when creating a Purchase Order you may want the delivery date to be in the future (e.g. today + 2 days), it is very unlikely that you would always want it to be the exact date you recorded.
This is very easy to do and a useful general technique to remember when working with ProScript. Remember, you are using Excel and all of Excel’s functions and formulas are available to you. All you have to do is replace the date recorded in the sheet with a formula – for example, to use “today” just use the formula:
=TEXT(TODAY(), “mm.dd.yyyy”)
Note the conversion to text, this is to ensure that ProScript uses exactly the value you see in the cell. Note also the specification of date format, this is critical. The format must be exactly the same as the format you have specified in your SAP user profile (you can see your SAP format by running transaction SU3 and looking at the ‘Defaults’ tab
Can I rely on SAP’s parameter ID (PID) to carry forward data from one transaction to the next?
Very often, SAP ‘remembers’ what it has just done and carries it forward in a parameter ID which it defaults into subsequent transactions. For example, if you create a Sales Order (VA01) then run the Change Sales Order transaction (VA02) the sales document number will be automatically carried forward from VA01 to VA02.
You can, if you wish, rely on this behaviour rather than using the Data Wizard in ProScript. However, you must be very careful when making the recording. Continuing with the example, you must not record the input of the sales document number to the VA02 transaction, that is the recording must be made using the default value and not entering the data yourself. If you make the recording and input the data, the entry of the data will be recorded and put into the script – there will also be a column for the data in the spreadsheet. If you see the column in the spreadsheet, you must use the Data Wizard – if it is in the script as an input field, QuickScript will always use the spreadsheet as the source of data.
It is recommended, at least until you become more familiar with ProScript, that you do not rely on parameter ID’s. This will make your scripts more predictable.
Can I share scripts?
Yes! All QuickScript spreadsheets are completely self-contained and can be used on any PC that has QuickScript installed.
Can I make the script ‘Run’ faster?
QuickScript’s ‘Run’ speed can be increased by turning ‘Off’ local data history, as follows.
- From inside an SAP session click the button and choose ‘Options …’ from the drop-down menu.
- Go to the ‘Local data’ tab and click the ‘Off’ radio-button
