Appointment Types and Event Handling

Use

Appointments in the SAP calendar have an appointment type, which classifies the appointment, for example, "Consultation". Communication between appointment management and the application is controlled in appointment type Customizing (transaction OSC1) using the attributes. As a result, it is possible to influence the behavior of the calendar interface when actions are executed on appointments of a certain type. For example, deleting or copying can be disallowed. These settings only affect the calendar user interface. The interface works independently of this.

Interaction and data exchange with other applications occur using function modules defined in Customizing for each appointment type, function module exits. These function module exits have to suit a specific interface, which is then used for data exchange. Appointment types can also exist for which no function module exit is defined.

In specific situations within a calendar scenario, for example when creating or copying an appointment, the function module exit is called with an event. In this case, the internal application data changes normally occur before appointment management continues its processing after the call, depending on a possible returned control command. For an application example, see Event Handling for the Appointment Type 'Service Order'.

Activities

To integrate event handling in your application, proceed as described in Use of Event Handling.

If you are using the class interface and the appointment calendar is integrated within your application, your application can deal with OO events of the calendar framework class CL_ORGANIZER. Events are currently triggered when appointments are created and changed.