Redesigning Entry into Applications
Omitting Selection of the Processing Object in a Single-Screen Application
There are applications in which the enduser sees no explicit difference between selection and processing of the object. In such cases, the screen should be designed in accordance with the enduser's workflow. This means that any required key appears on the screen in the location demanded by the workflow. No differentiation between the different processing types is necessary before processing is started.
In the example below, however, there are four different options for completing processing of the object (parking, flagging, posting). The corresponding functions have been placed in the application toolbar.
Figure 1: Example for separation between initial area and data input area omitted; key: vendor; select templates from a left-hand object selection area (this diagram has been modified for the recommendations)
Click image to enlarge it!
"Saving" the Processing Object and Changing the Processing Type
The processing object is saved through an explicit trigger of the "Save" function, as before. The contents of the data fields and - where sensible - the fields for selecting the processing object remain. The data fields are initially set to read-only, while any fields for entering the processing object are released (R/W). The application remains on the screen. The user can then enter a different processing object and has to select
Source: SAP R/3 Style Guide