You can transform complex, multiple-screen R/3 transactions into single-screen transactions, thus increasing both ease of use and data entry speed. On this page we will show you a typical example, including the R/3 standard transaction, our simplified transaction, and the necessary scripts.

1 A short example: G/L Posting with FB01 (Screen 1)

We have chosen a simple example: implementing fast G/L postings in the R/3 posting transaction FB01. The SAP standard already contains a similar function (click on "G/L item fast entry"), so in reality it would not be necessary to use GuiXT here. But in the R/3 standard system the "fast and easy" variants of R/3 transactions are only available for a few business cases.

With our new approach you can select the most often used processes of your company, and with a relatively small amount of work you can help your R/3 users a lot.

First we look at the standard data entry in FB01 for our special case (entering 2 G/L line items).

The user starts with the header data; he enters the posting key and account for the first line item.

2 FB01 standard, Screen 2

On the second screen he enters the amount for the first line item and the posting information for the second account.

3 FB01 standard, Screen 3

The third and last screen is only necessary for entering the amount of the second line item.

4 FB01 standard, Screen 4

The system then returns to the initial screen and displays the posting message.

5 FB01 simplified

Let us assume for this example that some R/3 users enter G/L postings of the above type quite often.

With GuiXT we place all necessary input fields on the first screen. The user can enter all values here, then presses the "P o s t" button.

6 FB01 simplified

The user stays on the first screen and gets the final posting message right there.

7 FB01 simplified

Error messages that might be issued by the R/3 standard transaction are also displayed on the initial screen. All fields can be re-entered by the user.

8 FB01 simplified

In this case the R/3 standard transaction would only allow to re-enter the company code, the posting key and the second account. In the simplified transaction, these fields are highlighted, but the user can change any other fields as well.

9 GuiXT Script

The relevant new commands in the GuiXT script are the definition of additional input fields (command InputField), and the Process= parameter in the Pushbutton command. This refers to the Input Script below.

10 Input Script

The Input Script defines the mapping of the input values to the fields of the R/3 multiple-screen transaction, and the necessary navigation commands.

It would be quite easy to add some more input fields here, if necesssary.

11 An Input Script for 3 line items

Input Scripts can be re-used from several different screens. They can be parameterized in order to become independent of the environment from which they had been called.

Complex transactions sometimes require a small amount of logic within the Input Script. Here you see a script which allows us to enter 2 or 3 line items.

12 Scripts for download

GuiXT script: sapmf05a.e0100.txt

Input script: glentry.txt