Customizing: From Database to Graphic

Purpose

A group of display attributes for the graphic is created and then transferred to the graphic.

Process Flow

The graphic shows what happens when customizing data is transferred from the database to the graphic. The order of events can be read vertically down the graphic:

  1. The application creates the customizing object. In this example it has the ID 4711.

  2. CREATE OBJECT <drawing area> EXPORTING

    INSTANCE_ID = "4711".

  3. The application loads the attribute values from the database.

  4. Start of the navigation pathCALL METHOD <drawing area  Next navigation step >  Next navigation step IF_CUSTOMIZING~LOAD.End of the navigation path

  5. Data is read from the database.

  6. Using the method ADD_CU_BUNDLE the application notifies the graphics proxy about the customizing object and at which port it is to be used.

  7. Start of the navigation pathCALL METHOD <graphics proxy  Next navigation step >  Next navigation step IF_GRAPHIC_PROXY~ADD_CU_BUNDLEEnd of the navigation path

    EXPORTING PORT = IF_GRAPHIC_PROXY => CO_PORT…

    BUNDLE = <drawing area>

    IMPORTING RETVAL = <return value>.

  8. After all the customizing steps have been completed the graphics proxy has to be activated.

  9. Start of the navigation pathCALL METHOD <graphics proxy  Next navigation step >  Next navigation step ACTIVATEEnd of the navigation path

    IMPORTING RETVAL = <return value>.

  10. The graphic is displayed with the display attributes specified in the customizing object. The label 6:#§&:-) is to indicate that the method call to the graphic is product-specific .