You can change display attributes in the graphic interactively and these changes can then be saved to the database.

The graphic shows the order of events from when the user changes the graphic to when the change is saved on the database.

1. A change takes place in the graphic and the graphic sends a GUI event to the graphics proxy. The label #§&:-) is to indicate that the event is product-specific. It is not a standard ABAP event.

2. The graphics proxy writes the changes to the customizing objects.

3. The graphics proxy sends an ABAP event to the application to inform it of the change.

There are two options for saving customizing changes:

4 + 5: The application can save customizing settings directly to the database by individually saving all the customizing objects.

4a + 4b + 5: Alternatively, the application can use the method SAVE_CUSTOMIZING in IF_GRAPHIC_PROXY (4a) to tell the graphics proxy to save on the database all the customizing objects it is aware of.