Maintenance Interface

Use

This section describes how the data gets onto the screen and then back to the database.

The basic problem with the maintenance interface is that there are no 'instance-specific' subscreens. This means that there is no natural connection between a class (or its instance at runtime) and a GUI element (like a subscreen). You therefore have to use a function group that accepts subscreens and their modules. Suitable function modules can be used to create communication with the instance of a maintenance class.

It makes no difference which function group the subscreens are in. SAP delivers the subscreens that belong to the BRF in function group BRF_MAINTENANCE. You as a BRF user do not have any possibility of adding other subscreens to this function group, or changing subscreens, without having to make modifications.

For this reason, an application that uses the BRF and has own BRF maintenance objects must provide an own function group. You can implement the required subscreens and their modules in this function group. When doing so, consider the namespaces in the BRF.

The following description of the maintenance interface is split as follows:

• DDIC Declarations

• Global Declarations in the Function Group

• Flow Logic of Subscreen

Subscreen 2013 from the function group ICL_BRF_MAINTAIN serves as an example.

Subscreen 2013 of the function group BRF_MAINTENANCE has the following appearance:

• It has simple fields

  These fields are part of the structure SBRF142 defined in the DDIC.

• It has an SAP List Viewer that is shown in a Custom Control.

  This SAP List Viewer displays data in accordance with structure SBRF144.

  In general, you can orient yourself on function group BRF_MAINTENANCE and the subscreens contained therein, its modules, and subprograms.