Add Own Button

Adding your own button is slightly more effort, but there may be situations where you need further application-specific buttons, or your button cannot really be described as Display.

Procedure

Go to your OVP component configuration in change mode.

In your feeder class, create a global constant GC_EVENT_RESET_DEFAULTS (type STRING) and give it the initial value RESET_DEFAULTS.

To make this available to use in the configuration (but it works without this step) you can declare your event (also known as actions) in your method GET_DEFINITION:

Syntax Syntax

	DATA ls_action           TYPE fpmgb_s_actiondef.

* supply actions as available for configuration

```
* Button 'Reset Defaults'
```

	ls_action-id        = GC_EVENT_ RESET_DEFAULTS.

```
	ls_action-text      = text-e01.
```
```
	ls_action-enabled   = abap_true.
```
```
	ls_action-exposable = abap_true.
```

	APPEND ls_action TO et_action_definition.

End of the code.

Choose Content Area: MAIN_SCREEN in the hierarchy on the left.
Choose Add Toolbar Element followed by menu point to content area.
A dialog box is displayed.
In this dialog box, choose Button (don't press OK instead).
In the field Text, enter the text for your button, for example, Reset Defaults.
In filed FPM Event ID, enter the name of the event you will program for the event in your feeder class, for example RESET_DEFAULTS.
Choose Save.

Add the following code (or similar) to your method GET_DATA:

Syntax Syntax

```
case io_event->mv_event_id.
```
```
	when  gc_event_reset_defaults.
```

		<your handling of event, e.g retrieve default values>

```
	when others.
```
```
		endcase.
```

End of the code.

Activate your feeder class, place an external break point at this point in the code and test your application. Use the link at the top of the same screen to go to the application configuration and choose Test. Choose your new button and the debugger should stop at your code.