|Purpose||Many SAP transactions are
multi-screen transactions, i.e. they consist of several
screens. A typical transaction begins with a relatively
empty first screen with some key data; this is followed by one or
several more complex screens that describe the
business case being dealt with.
Commonly one needs to fill in only a few fields on each of these screens. This means that
With GuiXT+InputAssistant you can now transform these multi-screen transactions into single-screen transactions. The user stays on one screen where he can enter all relevant data directly.
Internally the original transaction is processed with all its screens. The application logic and all integrity checks are performed in exactly the same way.
|How to proceed||
|General||Single-screen transactions can
be defined either on the first screen of a transaction or
on one of the menu screens. It is also possible to call a
different transaction (or a series of transactions) via
an InputScript. A third possibility is to process only
some screens internally and to let the user complete the
You can also add your own integrity checks and set values depending on the value of input data.
|Input fields||Normal input fields as well as
checkbuttons and radiobuttons are supported:
"Text" (row2,col2) Size="..."
"Material text" (10,48) Size="3"
"Text" "fcode" Process="..."
Process="..." relates to the
InputScript file. You can omit the "fcode"
prameter if only "Enter" is needed in
order to continue with the transaction.
With using you can set parameters of the InputScript:
An InputScript is a textfile with a name of your choice, e.g.. C:\GuiXT\Scripts\CreateMaterialSimple.txt. It contains the names of the screens that you want to process (Screen-command), Set-commands to fill in the values, and Enter-commands that define the navigation from one screen to the next one. If no path is specified in the Process= parameter the InputScript is searched in the current GuiXT Script directory.
Set [Amount] &[Amount2]
While the InputAssistant processes the transactions internally, it looks for the next matching Screen command and then executes the corresponding commands. If no matching Screen command is found, the internal processing is terminated, the screen is displayed and the user can complete the transaction. The same happens if no Enter command is specified for this screen.
Error messages are displayed on the first screen, where the user can correct the input data.
Warnings are ignored.
It is a good idea to work with parameters in InputScripts. The InputScripts can then be used in a more flexible way, and in addition you are able to use the parameter values in if-commands in order to set values or to navigate in different ways.
The names are not case-sensitive.
The value of a parameter (specified with the using command or as default value) can be used in if-expression:
if U[Language=E] and U[Stdname=X]
is fulfilled if the parameter has a non-space value.
You can also define your own integrity checks. Use the Return command in order to return to the basic screen with an error message. Example:
if not U[cc]
if U[CC=0001] and not U[currency=USD]