Jump to an Application Transaction

Use

In the following example, a sales activity and the corresponding appointments for the sales representative responsible and the participating sales executives are to be changed at the same time. This change can be made via the application SD-CAS itself. The prerequisite is that the appointments have already been created via this application by simply calling the appointment management interface.

SD-CAS reacts to the events with subroutines, which are to process not only the sales activity but also the appointments. These subroutines are not specified in more detail here. The field EXIT_INFO is used to store and change technical information during appointment management and to evaluate it before it is displayed. This information helps the application to identify the customer for whom the sales activity is taking place.

A jump to the application transaction takes place within the form routine TO_MODIFY. This application transaction changes not only its own sales activity but also the corresponding appointments via the interface. The control variable ERROR_MESSAGE-VAR1 is immediately set to 'EXIT' so that the change dialog of the calendar does not continue to be displayed after the change has been made.

The appointments cannot be moved. Instead, an application-specific error message is output and further appointment processing, which would move the appointment, is suppressed again. Alternatively, a different transaction could be used to move the appointment, as is the case when appointments are changed.