|
| Which files are necessary for displaying local value help? | The following files are necessary for displaying local value help:
All files can be generated automatically in the R/3 system (APAB programs ZGUIXT12 and ZGUIXT16). You can also maintain the value help files manually in order to adapt them to your specific needs (i.e. to display only a certain part of the values). For domains with a very large spread of values, R/3 typically offers a matchcode search (i.e. for the material number). Here you can create a value help file by yourself (manually or automatically) with the most common values. |
| How you generate your own value help files | Start the ABAP program ZGUIXT16 in the R/3 system:
Choose one or several domains. The parameter Maximum number of values lets you select only those value help files which contain less than the specified amount of values. The typical run time for one domain is short (approx. 1 second). The size of a value help file is usually between 1 and 10 kB. It takes around 30 minutes to generate all value help files. The total disk space required for all files (with parameter 400, IDES system) is less than 10 MB. ZGUIXT16 program generates values only for domains for which a value table is specified in the Data Dictionary (SE11). You can download the ZGUIXT16 utility from our download page. |
| How you generate the domain files | Start ABAP program ZGUIXT12 in R/3 system:
The selection criteria program, dynpro and domain are just for testing purposes. You should run the program without restrictions for a productive application. The global size of the two files (created for an IDES system) is about 0.5 Megabyte. The run time for all screens of R/3 system is about 30 minutes. You can download the ZGUIXT12 utility from our download page. |
| Structure of value help files | The structure of the value help files is similar to the F4 value help display of R/3. You have one line for each value; it starts with the value itself, followed by one or more columns (usually associated text) that are separated from each other by //. Examples (domains WAERS and BUKRS):
ADP //Andoran peseta 1000 //IDES AG //Frankfurt //DEM |
| Structure of domain files | The file domText.E.txt contains the most frequently used domain for each field text.
Format of each line: Field Text: Domain Examples: Currency: WAERS The file domTextScreen.E.txt contains all exceptions, i.e. all fields with a domain that differs from the domain contained in domText.D.txt. Each line contains the program and dynpro name, followed by the field text. Example: SAPMF05A.0110.Account:KTO16 |
| When do you need to regenerate the local files? | The value help files have to be regenerated after changes in the customizing tables; for instance after a new material type or a new document type has been added.
The domain files need to be regenerated after dynpro modifications or for a new R/3 release, since some field texts could be changed or new domains could be added. |
| Buffering of local files | The domain files domText.E.txt and domTextScreen.E.txt are kept in memory by GuiXT. The value help files are read each time they are requested. This means that modifications in domText.E.txt or domTextScreen.E.txt only take effect after you log out of your R/3 session, quit GuiXT, start GuiXT and log on to R/3 again. |
| Creating your own specific local value help | It is a simple matter to create your own specific local value help for individual fields, even where there is no standard-F4- help available in the R/3 System.
Proceed as follows:
A number of options are open to you:
|
| Checklist | Please look at our Checklist in case of any problems. |
