SAP CRM_ISU_CANCEL_APPOINTMENT_EC Function Module for Handle changes of the appointment set
CRM_ISU_CANCEL_APPOINTMENT_EC is a standard crm isu cancel appointment ec SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Handle changes of the appointment set processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for crm isu cancel appointment ec FM, simply by entering the name CRM_ISU_CANCEL_APPOINTMENT_EC into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECRM_ISU_EC
Program Name: SAPLECRM_ISU_EC
Main Program: SAPLCRM_EVENT_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISU_CANCEL_APPOINTMENT_EC pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CRM_ISU_CANCEL_APPOINTMENT_EC'"Handle changes of the appointment set.
EXPORTING
IV_HEADER_GUID = "GUID of a CRM Order Object
* IV_STRUC_NAME = "Table Name
IV_OBJECT_GUID = "GUID of a CRM Order Object
IV_OBJECT_NAME = "Name of Object to be Processed
IV_EVENT_EXETIME = "CRM Call Time of Functions
IV_EVENT = "CRM Event - Event / Time in Program Run
* IV_ATTRIBUT = "CRM Event - Event / Time in Program Run
* IV_STRVAL_OLD = "
* IV_STRVAL_NEW = "
* IV_RCODE_STATUS = "Return Value, Return Value After ABAP Statements
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CRM_ISU_CANCEL_APPOINTMENT_EC
IV_HEADER_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_STRUC_NAME - Table Name
Data type: CRMC_EVENT_STRUC-STRUCOptional: Yes
Call by Reference: Yes
IV_OBJECT_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_OBJECT_NAME - Name of Object to be Processed
Data type: CRMT_OBJECT_NAMEOptional: No
Call by Reference: Yes
IV_EVENT_EXETIME - CRM Call Time of Functions
Data type: CRMT_EVENT_EXETIMEOptional: No
Call by Reference: Yes
IV_EVENT - CRM Event - Event / Time in Program Run
Data type: CRMT_EVENTOptional: No
Call by Reference: Yes
IV_ATTRIBUT - CRM Event - Event / Time in Program Run
Data type: CRMT_EVENTOptional: Yes
Call by Reference: Yes
IV_STRVAL_OLD -
Data type: ANYOptional: Yes
Call by Reference: Yes
IV_STRVAL_NEW -
Data type: ANYOptional: Yes
Call by Reference: Yes
IV_RCODE_STATUS - Return Value, Return Value After ABAP Statements
Data type: SY-SUBRCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ISU_CANCEL_APPOINTMENT_EC Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_error_occurred | TYPE STRING, " | |||
lv_iv_header_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_struc_name | TYPE CRMC_EVENT_STRUC-STRUC, " | |||
lv_iv_object_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_object_name | TYPE CRMT_OBJECT_NAME, " | |||
lv_iv_event_exetime | TYPE CRMT_EVENT_EXETIME, " | |||
lv_iv_event | TYPE CRMT_EVENT, " | |||
lv_iv_attribut | TYPE CRMT_EVENT, " | |||
lv_iv_strval_old | TYPE ANY, " | |||
lv_iv_strval_new | TYPE ANY, " | |||
lv_iv_rcode_status | TYPE SY-SUBRC. " |
  CALL FUNCTION 'CRM_ISU_CANCEL_APPOINTMENT_EC' "Handle changes of the appointment set |
EXPORTING | ||
IV_HEADER_GUID | = lv_iv_header_guid | |
IV_STRUC_NAME | = lv_iv_struc_name | |
IV_OBJECT_GUID | = lv_iv_object_guid | |
IV_OBJECT_NAME | = lv_iv_object_name | |
IV_EVENT_EXETIME | = lv_iv_event_exetime | |
IV_EVENT | = lv_iv_event | |
IV_ATTRIBUT | = lv_iv_attribut | |
IV_STRVAL_OLD | = lv_iv_strval_old | |
IV_STRVAL_NEW | = lv_iv_strval_new | |
IV_RCODE_STATUS | = lv_iv_rcode_status | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " CRM_ISU_CANCEL_APPOINTMENT_EC |
ABAP code using 7.40 inline data declarations to call FM CRM_ISU_CANCEL_APPOINTMENT_EC
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single STRUC FROM CRMC_EVENT_STRUC INTO @DATA(ld_iv_struc_name). | ||||
"SELECT single SUBRC FROM SY INTO @DATA(ld_iv_rcode_status). | ||||
Search for further information about these or an SAP related objects