In the last dialog step before starting the actual object processing, the user chooses a certain object class at application level (for example, quotations, invoices, documents, master data, plans, programs, tables, or - even more specific - GR/GI document, material master, networks, screens) (see Levels in the SAP System). The application level with its object classes constitutes the focus of navigation for the user: From the logon screen via the main menu level the user jumps directly to the application level and returns to this screen upon completion of an application.

After choosing an object class, the user chooses the required action from a pull-down menu.

The object classes and actions should be geared to the actual work objectives of the user rather than reflect the logical business structure of the application area if this does not correspond with the work processes. Processes such as Transfers or Incoming Payments must also be possible at object class level.

On the following fullscreen initial screen of the task, a particular object of the chosen class is called by entering a number or a name. Additionally required parameters can be entered either on the initial screen or in a separate dialog box.

The actual processing of the object starts after this. The processing of the object is the sum of all the processing actions to the individual object components . The user chooses the required functions primarily from the menu bar.

The object-oriented user interface approach must flexibly support the various learning stages of the users (inexperienced user/expert user), the various workplaces and tasks (routine work/bulk data processing/variable information gathering), and the various input elements (keyboard/mouse). Therefore, the user must have various access and interaction options available to him or her.