SAP CRM_IST_CANCEL_MAINTAIN_API Function Module for
CRM_IST_CANCEL_MAINTAIN_API is a standard crm ist cancel maintain api SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ist cancel maintain api FM, simply by entering the name CRM_IST_CANCEL_MAINTAIN_API into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_CANCEL_API
Program Name: SAPLCRM_IST_CANCEL_API
Main Program: SAPLCRM_IST_CANCEL_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CRM_IST_CANCEL_MAINTAIN_API 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_IST_CANCEL_MAINTAIN_API'".
EXPORTING
I_OBJECT_GUID = "
* I_OBJECT_KIND = 'B' "
I_RECEIVE = "
* I_REQUEST = "
I_CANCDATE = "Cancellation date
* I_CANC_REASON = "Cancellation Reason
I_CANC_PARTY = "Cancelling Party
* I_NO_FEE = ' ' "
* I_BUS_TRANS = 'C3CA' "
IMPORTING
E_IP_AMOUNT = "Indemnity Payment Amount
TABLES
* MESSAGELINE = "
IMPORTING Parameters details for CRM_IST_CANCEL_MAINTAIN_API
I_OBJECT_GUID -
Data type: CRMT_OBJECT_GUID_COptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_KIND -
Data type: CRMT_OBJECT_KINDDefault: 'B'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RECEIVE -
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
I_REQUEST -
Data type: DATSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CANCDATE - Cancellation date
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
I_CANC_REASON - Cancellation Reason
Data type: CRMT_SRV_CANCEL_REASONOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CANC_PARTY - Cancelling Party
Data type: CRMT_CANC_PARTYOptional: No
Call by Reference: No ( called with pass by value option)
I_NO_FEE -
Data type: BOOLE_DDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUS_TRANS -
Data type: J_VORGANGDefault: 'C3CA'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CRM_IST_CANCEL_MAINTAIN_API
E_IP_AMOUNT - Indemnity Payment Amount
Data type: CRMT_IST_IP_AMOUNTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CRM_IST_CANCEL_MAINTAIN_API
MESSAGELINE -
Data type: CRMT_ISALES_RETURNOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_CANCEL_MAINTAIN_API 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_e_ip_amount | TYPE CRMT_IST_IP_AMOUNT, " | |||
lt_messageline | TYPE STANDARD TABLE OF CRMT_ISALES_RETURN, " | |||
lv_i_object_guid | TYPE CRMT_OBJECT_GUID_C, " | |||
lv_i_object_kind | TYPE CRMT_OBJECT_KIND, " 'B' | |||
lv_i_receive | TYPE DATS, " | |||
lv_i_request | TYPE DATS, " | |||
lv_i_cancdate | TYPE DATS, " | |||
lv_i_canc_reason | TYPE CRMT_SRV_CANCEL_REASON, " | |||
lv_i_canc_party | TYPE CRMT_CANC_PARTY, " | |||
lv_i_no_fee | TYPE BOOLE_D, " ' ' | |||
lv_i_bus_trans | TYPE J_VORGANG. " 'C3CA' |
  CALL FUNCTION 'CRM_IST_CANCEL_MAINTAIN_API' " |
EXPORTING | ||
I_OBJECT_GUID | = lv_i_object_guid | |
I_OBJECT_KIND | = lv_i_object_kind | |
I_RECEIVE | = lv_i_receive | |
I_REQUEST | = lv_i_request | |
I_CANCDATE | = lv_i_cancdate | |
I_CANC_REASON | = lv_i_canc_reason | |
I_CANC_PARTY | = lv_i_canc_party | |
I_NO_FEE | = lv_i_no_fee | |
I_BUS_TRANS | = lv_i_bus_trans | |
IMPORTING | ||
E_IP_AMOUNT | = lv_e_ip_amount | |
TABLES | ||
MESSAGELINE | = lt_messageline | |
. " CRM_IST_CANCEL_MAINTAIN_API |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_CANCEL_MAINTAIN_API
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.DATA(ld_i_object_kind) | = 'B'. | |||
DATA(ld_i_no_fee) | = ' '. | |||
DATA(ld_i_bus_trans) | = 'C3CA'. | |||
Search for further information about these or an SAP related objects