SAP CRM_ISU_APPOINTMENT_SPLIT_OW Function Module for Split Appointment Set if necessary
CRM_ISU_APPOINTMENT_SPLIT_OW is a standard crm isu appointment split ow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Split Appointment Set if necessary 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 appointment split ow FM, simply by entering the name CRM_ISU_APPOINTMENT_SPLIT_OW into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECRM_ISU_EC
Program Name: SAPLECRM_ISU_EC
Main Program: SAPLECRM_ISU_EC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISU_APPOINTMENT_SPLIT_OW 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_APPOINTMENT_SPLIT_OW'"Split Appointment Set if necessary.
EXPORTING
IV_REF_GUID = "GUID of a CRM Order Object
IV_REF_KIND = "Object Type
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CRM_ISU_APPOINTMENT_SPLIT_OW
IV_REF_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_REF_KIND - Object Type
Data type: CRMT_OBJECT_KINDOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_ISU_APPOINTMENT_SPLIT_OW 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_iv_ref_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_error_occurred | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_ref_kind | TYPE CRMT_OBJECT_KIND. " |
  CALL FUNCTION 'CRM_ISU_APPOINTMENT_SPLIT_OW' "Split Appointment Set if necessary |
EXPORTING | ||
IV_REF_GUID | = lv_iv_ref_guid | |
IV_REF_KIND | = lv_iv_ref_kind | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " CRM_ISU_APPOINTMENT_SPLIT_OW |
ABAP code using 7.40 inline data declarations to call FM CRM_ISU_APPOINTMENT_SPLIT_OW
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.Search for further information about these or an SAP related objects