|
| What are Input Sets? | Input Sets offer the possibility of storing whole sets of predefined input values so that they can be called up with the mouse. You can define several Input Sets per screen.
You can define individual Input Sets for particular users and other Input Sets for groups of users. Input Sets will be shown on the right end of the pushbutton bar in R/3 window: they will be represented by the initial of their title. Individual Input Sets will be represented in blue, shared Input Sets in yellow, e.g.:
A click on the right key of mouse will show the name of the Input Set and the field names and values:
|
| How are Input Sets defined ? | You define Input Sets by choosing the option Edit->History in GuiXT window, where you can set the values. Each Input Set definition starts with a title put into squared brackets, followed by field designation and value separated by “:”. You specify each field : value in a separate line:
[Receipt] The initial letter of the title, i.e.: “R” will be shown by GuiXT in the pusbutton bar of the R/3 window. The name of the file for shared Input Sets is the same as for individual Input Sets. You can just copy the file in the directory you specified as “Shared Input Sets” in GuiXT profile. |
| Field designation | Following designations are possible:
|
| Execution of Enter-key | After specifying values of fields you can simulate an action on “Enter”-key of the user by specifying “OK” at the end of the Input Set, i.e.:
Company code: 0012 You can also specify a function code (Transaction code, internal code or Function key), i.e.: Company code: 0012 Please refer to documentation of Pushbutton-command for possible function codes. It is also possible to fill other fields on the following screen after an ok code. The difference between this solution and an execution of an InputScript (Pushbutton-command, process=) is that screens are processed in a visible manner here. So it does not really make sense to have a long screen combination. |
| Positionning input cursor | By inputting a value in a field you also position the cursor there. After processing the Input Set the cursor will be in the last field specified in the Input Set. You can also position the cursor on an explicite postion without entering a value. To do this you specify the field name and the value “@Cursor“, i.e.:
Password: @Cursor |
| Calling local value help | Using the value “@History“, you can display the input history and local value help for a field. For example, you can combine this with the “Image” command and its “Start=…” parameter. You display a small icon near an input field (standard entry field or your “InputField”), allowing the user to click on it to display local value help:
Image (..,..) “valuehelp.gif” Input=”Department:@History” |
| Cursor-con trolled table input | For table input it makes sense to enter the data into the table row where the cursor points to, instead of using a fixed row number. To achieve this, please use the following notation:
cell[All Items,Material,*]: 10007684 If the cursor is outside of the table, GuiXT chooses the first table row. A further option is the notation “*+” as table row. In this case, GuiXT will use the next table row for the next input. Please note that if there are of several columns this notation should be used for the last column only. Example: cell[All items,Material,*]: 10007684 cell[All items,Material,*+1]: 10007685 cell[All items,Material,*+1]: 10007686 At the end you can also put the cursor into a new row: cell[All items,Material,*+1]: @Cursor |
| Pictures instead of first letter of designation | You can also specify a small image file when defining an Input Set. This image file will then be displayed instead of the letter. Example :
[Travel Document] Image=C:\GuiXT\Images\travel.gif Size must be 18×18 pixel. The border (3D-effect), if desired, must be contained in the image.
|
|
Shared input sets | The GuiXT profile containes an additional directory: “Shared input sets”. Here you can define input sets that are shared by all users, or groups of users. The icons for the shared input sets are displayed in a different color (yellow instead of blue).
Shared input sets can be organized language dependent or language independent for each screen. GuiXT always first looks for an .inp file with language key included in the file name; the structure of the filename is the same as for GuiXT scripts. If this file is not found, a language independent file is searched, deleting the language key from the file name. |
| Commands | Image and View commands. Input data can also be stored with an image or an html file; please refer to GuiXT commands Image and View. |
| External applications | Input data can also be sent to GuiXT from external applications, using a simple command type interface. The input is always done in the active SAP session. If no session is active, no action is performed. The external application can first start a session, if necessary, via an SAP shortcut (.sap file). GuiXT Version 2003 Q2 3 (or later) is required for this functionality.
In order to send the input data, call GuiXT with the parameter guixt input=”inputstring” where the inputstring is exactly as described in the input= parameter of the Image command. You can set field values, perform actions, and process InputScripts. Example 1: guixt input=”Customer:1000;OK” You set the value “1000″ into the field “Customer” and press Enter. Example 2: guixt input=”U[CUST]:1000;OK:/NVD03,process=vd03.txt” You switch to transaction VD03, processing the InputScript “vd03.txt”, passing a value “1000″ as parameter “CUST” for the InputScript. Example 3: Create a file “showcustomer.bat” containing the line guixt input=”U[CUST]:%1;OK:/NVD03,process=vd03.txt” Now you can type showcustomer 1000 to get the input and actions shown in Example 2. |
