Module PBO_Subscreen

Use

The name of the module is comprised as follows: PBO_<relevant subscreen>. In our example, the module is called PBO_2013.

Sample source text:

MODULE pbo_2013 OUTPUT.

CALL FUNCTION 'BRF_PBO'

EXPORTING

iv_screen = '2013'

iv_program = gc_this_program

IMPORTING

es_screen_structure = sbrf142

eo_instance = go_instance.

ENDMODULE. " pbo_2013 OUTPUT

Description:

Each subscreen that participates in the maintenance environment of the BRF must call function module BRF_PBO in its PBO module. The parameters to be used depend on the case in question.

In our example, the following parameters are used:

  • On the 'EXPORTING' side, the following parameters are transferred:

    • Number of the relevant subscreen (subscreen 2013 in this example)

    • Name of the program (program SAPLBRF_MAINTENANCE in this example)

      In this example, the program name SAPLICL_BRF_MAINTENANCE is transferred in the constant GC_THIS_PROGRAM in a 'hidden' form.

  • On the 'IMPORTING' side, the following values are returned:

    • A structure (SBRF142 in this example)

    Note the following:

    • EO_INSTANCE contains a reference to the instance of the associated maintenance class.

      On the PBO side, you must assign this reference to the GO_INSTANCE variable. Variable go_instance ist is declared in the TOP include.

      Otherwise, you have no access to some methods of the maintenance class.

For its part, the function module that is used calls the following methods: