Use of Event Handling

Use

Event handling of appointment management is based on the link between appointment types and exit function modules. This assignment can be made in transaction OSC1. If no exit function module is specified for an appointment type, appointments of this type are not involved in event handling.

Every appointment has an appointment type and the corresponding exit function module is called with a specific event, depending on the scenario. The appointment structures (for example, APPOINTMENT) also contain the field EXIT_INFO, which the applications can use to store local technical information, such as a customer number, for each appointment generated. This field is not evaluated in appointment management, but is forwarded to the exists using event handling.

Events can be used, on the one hand, to display additional information about an appointment within the appointment processing dialog, for example the customer contact person or telephone number. On the other hand, they can also be used to control the behavior of the appointment calendar.

Besides an exit function module, appointment types also have other attributes that can be maintained using the above transaction. When actions are executed on an appointment of the type concerned, these attributes influence the behavior of the interface of a user calendar.

Activities

To influence the behavior of the appointment calendar according to the appointment type, make settings for the appointment type attributes in transaction OSC1.

To integrate application-related functions, create an exit function module and assign this to the required appointment type in transaction OSC1. Various appointment-related events are available. You can react to these using the function modules. For an example of an exit function module, see Jump to an Application Transaction or Calling a Search for Customer Master Data.