|Purpose||Many R/3 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 transaction.
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:
InputField (row1,col1) “Text” (row2,col2) Size=“…” Name=“…” Default=“…”
InputField (10,40) “Material text” (10,48) Size=“3″ Name=“Mt”
|Pushbutton||Pushbutton (row,col) “Text” “fcode“ Process=“…”
Process=“…” relates to the InputScript file. You can omit the “fcode” parameter if only “Enter” is needed in order to continue with the transaction.
Pushbutton (10,40) “Create material” Process=“CreateMaterialSimple.txt”
With using you can set parameters of the InputScript:
Pushbutton (toolbar) “Create material” Process=“CreateMaterialSimple.txt”