Screen

from Wikipedia, the free encyclopedia

Screen is the abbreviation for a dyn Amish Pro program in SAP ERP .

Overview

Dynpros are one of the main technologies in the interaction between users and the SAP ERP system. The technical implementation is just as unusual as the term itself; it is easiest to understand against the background of the evolutionary development of the SAP ERP user interface. Dynpros consist of two sub-components: the mask definition and the flow logic. In the R / 3 System, screens are interpreted at runtime by a special software component, the screen processor.

In English usage, dynpros are often referred to as screens .

technology

The mask definition describes the positioning and formatting of the input elements ( text fields , checkboxes , radio buttons and pushbuttons ) and design elements (texts and frames). A screen can also contain what are known as container elements. With the help of a subscreen area it is possible to embed a screen in another screen. Another container element allows the control of active components on the front-end computer ( ActiveX controls or Java Beans ). Further container elements are the tabstrip , a kind of index card box with several registers, and the table control , with which tables can be displayed.

In addition to the pure dialog layout, the screen also contains flow logic. The flow logic controls the point in time at which the entry in the fields is transferred to the corresponding ABAP field and when the flow logic of a subscreen is processed. About modules will come off from the flow logic in the ABAP program, where the data is processed. The screen processor processes individual sections of the flow logic at certain times. The flow logic is therefore more time-controlled than purely sequential, even if modules that are assigned to the same point in time are of course executed in the order listed. It is not an event-based control, as it can be found in modern programming environments, but a rather rigid construct that has its roots in the days of text-based mainframe applications. The screen processor prepares the screen and transfers it to the client for display. Processing then rests on the application server until the user triggers a function. This action transfers the content of the screen back to the application server and processes it further by the screen processor.

The most important points in time for dialog processing are PBO ( process before output ) and PAI ( process after input ); There are also special times for the provision of help texts and input help as well as for reacting to certain cancellation commands. The PBO event is triggered before the screen is output and is usually used to supply the screen fields. In the PAI, i.e. immediately after the input has been processed, the data entered is checked and processed; the reaction to commands initiated by the user also takes place here.

The fields on a screen are linked to the associated fields in the associated ABAP program by having the same name . Communication with the ABAP program takes place using special ABAP procedures, so-called modules. The problem here is that the link is only possible with global variables of the ABAP program.

The ABAP command 'MESSAGE' is also closely linked to screen processing.

Successor technologies

In recent years, SAP has begun to supplement the technology of the Dynpro , which is based on the SAP GUI , with web-based technologies:

Individual evidence

  1. ↑ R / 3 History in Screen Shots. In: SAP Design Guild. Retrieved February 23, 2006 .

Web links