24/11/11

Example: FB01 as single-screen

transaction

Example:

FBOl

as single-screen

transaction

You can transform complex, multiple-screen SAP 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 SAP standard transaction, our simplified transaction, and the necessary scripts.

1 A short example:

GIL Posting with

FBOl

We have chosen a simple example: implementing fast GIL postings in the SAP posting transaction FB01. The SAP standard already contains a similar function (click on "GIL item fast entry"), so in reality it would not be necessary to use GuiXT here. But in the SAP standard system the "fast and easy" variants of SAP 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 SAP users a lot.

Screen 3 .24/11/11 Example: FB01 as single-screen transaction On the second screen he enters the amount second account. for the first line item and the posting information for the 3 FBOl standard.

5 FBOl simplified .24/11/11 Example: FB01 as single-screen transaction The system then returns to the initial screen and displays the posting message.

The user can enter all values here. With GuiXT we place all necessary input fields on the first screen. 6 FBOl simplified: Error messages If I BRP (l) BOt} . then he presses the lip 0 s til button. I SYIl<lctr.re12 I ...24/11/11 Example: FB01 as single-screen transaction Let us assume for this example that some SAP users enter GIL postings of the above type quite often.. The users stays on this screen and gets the final posting message right there.

'9» size=2 tl1. fields del F [TrSi. (3. . 48} size=H:i name=" aJm/ountl" (12.":1:8) size=16 "P 0. It refers to the Input Script below.40) "AJill0unt" (8. 6.1} "Pstky" [11.ccount2·' !laIile="aroount 2 " txt" size= (6 .ding pBI. even if they occur on screens processed later on. and the Process= parameter in the Pushbutton command. are also displayed on the initial 7 GuiXT Script pas GIFirst line item] (7. BA] del F [SGL Ind] del F [TType] The relevant commands in the GuiXT script are the definition of additional input fields (command InputField).lO} Fu.rt. 6":1:} "Second line item.tField InputField (8.65) InputField Box (10.ot needed herel / / hide some standall:'Cl.040} "Amount" (11.sRIlbuttm]. 12} "ACCOffi"lt [11. name= "ps t ky2 or nane=" Bi. 81nputScript ." [11. O} InputField InpiJI. n.3} s t" process="glentl!:'Y.24/11/11 Example: FB01 as single-screen transaction Error messages that might be issued by the SAP standard transaction screen.0) BoxSize G[First line item] (3.20} size=17 or (11.

2 ]" " &V[accDllllt..2Jr! F[Acc:aunt] Screen SAPllI:F05A .. and the necessary navigation commands.&V[amount1 j'r! ":&VfpstKl.24/11/11 Example: FB01 as single-screen transaction Screen Set Set Set [riter SAPMF05A .0300 Set E:nter '"BU''' "&V [amount. . 2 j nr The InputScript defines the mapping of the input values to the fields of the SAP multiple-screen transaction.0300 F[Amo·unt] F[PstKy] ".

Sign up to vote on this title
UsefulNot useful