Graphics Proxy


A graphics proxy is an object representing a frontend component. It defines and implements the programming interface for application development so that the latter can program the graphical objects (encapsulation). The graphics proxy determines what the graphic looks like and deals with interaction with the front end. The data to be displayed is taken from the data container.


A graphics proxy is used by the application that wants to display a graphic. The application has to interact with the graphics proxy in several ways:

Creating and Destroying the Graphics Proxy)

Initializing the Graphics Proxy)

Setting Parameters)

Making customizing settings - that is - assigning customizing objects to the graphics proxy (see Customizing Settings)

Activating/Deactivating the Graphics Proxy)

Processing events

All graphics proxies support the global interface IF_GRAPHIC_PROXY. SAP provides a graphics proxy for each graphic type. You can find some special hints on these graphics proxies (such as the class name) in sections on the programming interfaces for the relevant graphic type (for example, business graphics).

A graphics proxy requires a data container to provide the data. For more information on other basic objects in the Graphical Framework, see Interaction of Basic Objects.

See also:

Notifying Changes to Data or Customizing Objects

Graphic Type-Specific Method Calls


A graphics proxy has an ABAP Objects interface which the application uses to access the graphic. The proxy can also collect method calls in the form of a flush and can also contain parts of the application logic that are relevant to graphics. The graphics proxy controls the front end independently of how the graphic is implemented in the front end.


Once the application has generated the graphics proxy the latter subscribes to the data container. The proxy subscribes to selected columns and, if necessary, with a data filter. After this, changes to data are sent from the data container to the graphics proxy automatically. The graphics proxy must also subscribe to the multiplexer to synchronize events.

In keeping with object-oriented programming the graphics proxy manages local object data as instance variables (member variables).

There are two global interfaces for the graphics proxy: one for the application and the multiplexer (IF_GRAPHIC_PROXY) and one for the notify mechanism for the data container (IF_GP_NOTIFICATION).