Hello,
well, you stated that the appointment would be deleted in CRM (in your originally request). It looks that this is not the case. Actually when appointment is deleted on client, then it will NOT be deleted on CRM on database. Instead the appointment is changed to status = rejected (user status = E0007 which corresponds to system status I1032).
This is controlled by picklist values for status for appointments. In picklist there are the possible user status for appointment provided from the server to the client. In this status list there is also a field "rejected". If now an appointment is deleted on client then the client sets the status from the picklist which has the value rejected = true. In default delivery this is user status E0007.
So If you want to set another status in case appointment gets deleted, then (from my point of view) you habe to options:
1) you change picklist values so that another user status gets the value rejected = true. In this case the client will then set this user status instead the original one E0007. Picklist for appointments is build in class /CRMGWS/CL_APPT_PICKLIST3.
2) you change UPDATE_ENTITY method where you check on the incomming value for status in the import data structure /CRMGWS/APPOINTMENTMAIN-ACTIVE_STATUS_ID. So you manipulate the incomming value in order to trigger a status change with a different status.
In both cases you have to make sure that the user status you set, does corresponding to the system status you want to be activated.
Regards
Michael