Ansicht
Dokumentation

CRMV_BSP_EVENT - Event

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

The display of the People-Centric UI depends on the triggered event. You trigger an event by selecting an interface element (by pressing a button), or by pressing return.

In this activity, you create all events for tab pages, fields and buttons, that is for interface elements of the People-Centric UI that trigger an event.

The start event of an application is INIT.

1. Choose New Entries.
2. Enter the necessary data. The most important fields are listed as follows:

Event
Give the event a unique name.

Usage
Layout-relevant: The triggered event only influences the layout.
Function-relevant:The triggered event only has functional relevance.
Layout-relevant and functional-relevant: The triggered event has both functional relevance as well as influence on the layout.
Example: An event for a tab page is usually only relevant for the layout. Actions like saving data do not usually take place. An event like SAVE on the other hand, only has functional relevance, as here, no new screen areas need to be structured, and existing areas are only refreshed.
Object Type
Use the input help to select an object type for navigation.

Field Name -> Object Type
Specify in which field information about the object type can be found. This can be useful in the case of mixed lists, for example the Interaction History in a list with Activities, Sales Orders and so on.

Method
If necessary, choose a method for the navigation.

Field -> Object ID
This entry defines the fields in which the object key can be found.

Navigation Event
During navigation, the navigation event in the target page can be transferred to the application.

ROGBILLS - Synchronize billing plans   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2241 Date: 20240523 Time: 160741     sap01-206 ( 36 ms )