Generating single screen transactions
When analyzing the user actions in SAP transactions, one
often finds that navigation through numerous screens and
tabs is necessary, which costs time and concentration. For
this reason, GuiXT projects often develop single-screen
transactions for frequently used SAP processes, in which all
input fields and information are grouped together on a
single screen without any further navigation steps.
You can generate such GuiXT single screen transactions
largely automatically with UI Log. To do this, UI Log
analyzes the recorded processes and compiles all the
required fields from them. A GuiXT script that contains only
the required fields is generated. In addition, the
navigation steps of the recorded processes are analyzed and
a suitable InputScript is created for reading the data and
for the "Save" function.
With this you often have a
finished application at the push of a button. Even in cases
where the complexity of the SAP user interface is too high
for the UI Log Generator, it creates a good starting point
for your own development. In particular, if you are familiar
with the various control options for generation, you can get
quite close to the desired end result even for complex
transactions and continue on this basis.
We show the
procedure using a simple example, for which we carry out the
following steps:
Define a project The first thing we
do is create a project we call "VA02EASY":
Use recorded user actions or make targeted
recordings yourself Then we record a very simple
VA02 sequence ourselves:
It is even better if we have records of the actual usage for
the transaction in question, as the generation can then take
into account the correct selection of fields, input values
and navigation steps. To get to know the generation function
and even if we ourselves already know exactly which fields
and functions are used, it is a good idea to record typical
processes ourselves.
Generate the Single Screen Transaction
In the transaction overview, we now click on "GuiXT
Single Screen":
An intermediate screen appears for entering some options,
which we will discuss later. With "Start generation"
or F8 we start the generation of the scripts:
UI Log, in connection with the GuiXT Script Editor
Pro, now generates the single screen transaction in
the directory specified during project configuration.
Testing the single screen transaction We
can start the newly generated single screen transaction from
the generated menu. For later productive use, it is also
conceivable to offer the transaction as an alternative in the
standard VA02 initial screen, or to create a separate
transaction code for it.
For testing, please make
sure that you specify the directory in which the scripts
were generated as script directory in the GuiXT profile.
We enter the order number and click on "Continue":
In the generated single screen transaction,the very same
fields from our VA02 recording are now available:
To test the change we remove the "Delivery block" and save
our changes with F11:
Adding further fields
Next, we record a second transaction call that includes
other fields. Note the following for "targeted" recording:
-
It is not necessary to enter a new value to record an
input field, but you must overwrite at least one
character of the existing value, otherwise the field
will not be recorded.
-
You can include pure output fields in the recording by
moving the mouse to the field and pressing the + key.
The field is then generated as an output field in the
single screen transaction. The same applies to output
columns of tables.
When executing VA02, we marked the output fields "Net
value" and "Document currency" with + so that they are also
displayed in the single screen transaction. In addition, we
went to another VA02 screen via the menu Goto -> Header ->
Order data and entered name, character and telephone number.
We regenerate the single screen transaction and tickk the
box in the intermediate screen that the sold-to party and
ship-to party cannot be changed:
Now the transaction looks like this:
In
the "Save" InputScript, the additional navigation steps for
entering name/your character/telephone number are
automatically included in the generation.
Template management for "create" type transactions
For "create" type transactions, e.g. VA01, a small template
administration is automatically generated, in which a user
can store frequently used data entry values:
Click
here for full screen display
In "create" type transactions, the pure output fields, for
example, the net amount in VA01, are filled when you execute
"Check".
Explanation of the generation options
Click
here for full screen display
-
Default value
Useful for "create"
type transactions: For input fields or dropdown lists,
this value is proposed initially. If you select one
or more rows and then press the "Propose default
values" button, the value entered most
frequently according to the records is entered as the
default value. Always enter the value in external
format; it is automatically stored in internal format.
For date fields, you can have the current date suggested
by entering TODAY.
-
Required entry
The input field is
displayed as a mandatory entry. With "Check"
we make sure that a value has been entered.
-
Ignore
The field is not included in
the generation.
-
InputField instead of Dropdown
By default, entries that refer to SAP customizing tables
are automatically generated as a dropdown list. Instead,
you can explicitly select the display as InputField.
Dropdown lists are normally generated only once per session. The
exception to this occurs with interdependent dropdown lists,
such as country and region. Here, the appropriate
dependent value list (regions) is automatically created
when the parent value (country) changes.
-
Output only
The field is generated
as an output field.
-
Key field
Some "display" and
"change" type transactions require additional values to
read the object, for example, the plant if you want to
display plant data in the material. In this case, please
select all key fields, for example, material number and
plant.
-
Value list for dropdown
List of
single values, separated by commas. Only the specified
values appear in the dropdown list. If you press
"Propose value list", all the values contained in the
recordings are used as a list.
Example:
You enter the order types AA, CR,CS and RE:
The selection for the user is then
When generating for several languages, the texts and
the language-dependent conversion of the order type are
automatically taken into account:
You can use the "Check values" button to
check the "Default value" and the "Value list for DropDown":
Further notes on generation
In
our "Tips, Tricks and Samples" section you will find further
hints and examples for the generation and customization of
the generated transactions.
|