SAP SAMPLE_PROCESS_CRM0_200 Function Module for
SAMPLE_PROCESS_CRM0_200 is a standard sample process crm0 200 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 sample process crm0 200 FM, simply by entering the name SAMPLE_PROCESS_CRM0_200 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM0
Program Name: SAPLCRM0
Main Program: SAPLCRM0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SAMPLE_PROCESS_CRM0_200 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 'SAMPLE_PROCESS_CRM0_200'".
EXPORTING
I_OBJ_CLASS = "
I_OBJ_NAME = "
* I_BAPICRMDH2 = "
I_KEYWORD_IN = "
* I_CRMRFCPAR = "
IMPORTING
E_DO_NOT_SEND = "
CHANGING
C_BAPICRMDH2 = "
C_RFCDEST = "
C_OBJNAME = "
TABLES
T_INT_TABLES = "
T_BAPISTRUCT = "
T_MESSAGES = "
T_KEY_INFO = "
T_OTHER_INFO = "
T_BAPIIDLIST = "
IMPORTING Parameters details for SAMPLE_PROCESS_CRM0_200
I_OBJ_CLASS -
Data type: BAPICRMOBJ-OBJCLASSOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJ_NAME -
Data type: BAPICRMOBJ-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_BAPICRMDH2 -
Data type: BAPICRMDH2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KEYWORD_IN -
Data type: CRM_PARA-KEYWORD_INOptional: No
Call by Reference: No ( called with pass by value option)
I_CRMRFCPAR -
Data type: CRMRFCPAROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SAMPLE_PROCESS_CRM0_200
E_DO_NOT_SEND -
Data type: CRM_PARA-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SAMPLE_PROCESS_CRM0_200
C_BAPICRMDH2 -
Data type: BAPICRMDH2Optional: No
Call by Reference: No ( called with pass by value option)
C_RFCDEST -
Data type: CRMRFCPAROptional: No
Call by Reference: No ( called with pass by value option)
C_OBJNAME -
Data type: BAPICRMOBJ-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SAMPLE_PROCESS_CRM0_200
T_INT_TABLES -
Data type: BAPIMTCSOptional: No
Call by Reference: No ( called with pass by value option)
T_BAPISTRUCT -
Data type: BAPIMTCSOptional: No
Call by Reference: No ( called with pass by value option)
T_MESSAGES -
Data type: BAPICRMMSGOptional: No
Call by Reference: No ( called with pass by value option)
T_KEY_INFO -
Data type: BAPICRMKEYOptional: No
Call by Reference: No ( called with pass by value option)
T_OTHER_INFO -
Data type: BAPIEXTCOptional: No
Call by Reference: No ( called with pass by value option)
T_BAPIIDLIST -
Data type: BAPIIDLISTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SAMPLE_PROCESS_CRM0_200 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_i_obj_class | TYPE BAPICRMOBJ-OBJCLASS, " | |||
| lv_c_bapicrmdh2 | TYPE BAPICRMDH2, " | |||
| lt_t_int_tables | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lv_e_do_not_send | TYPE CRM_PARA-XFELD, " | |||
| lv_c_rfcdest | TYPE CRMRFCPAR, " | |||
| lv_i_obj_name | TYPE BAPICRMOBJ-OBJ_NAME, " | |||
| lt_t_bapistruct | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lv_c_objname | TYPE BAPICRMOBJ-OBJ_NAME, " | |||
| lt_t_messages | TYPE STANDARD TABLE OF BAPICRMMSG, " | |||
| lv_i_bapicrmdh2 | TYPE BAPICRMDH2, " | |||
| lt_t_key_info | TYPE STANDARD TABLE OF BAPICRMKEY, " | |||
| lv_i_keyword_in | TYPE CRM_PARA-KEYWORD_IN, " | |||
| lv_i_crmrfcpar | TYPE CRMRFCPAR, " | |||
| lt_t_other_info | TYPE STANDARD TABLE OF BAPIEXTC, " | |||
| lt_t_bapiidlist | TYPE STANDARD TABLE OF BAPIIDLIST. " |
|   CALL FUNCTION 'SAMPLE_PROCESS_CRM0_200' " |
| EXPORTING | ||
| I_OBJ_CLASS | = lv_i_obj_class | |
| I_OBJ_NAME | = lv_i_obj_name | |
| I_BAPICRMDH2 | = lv_i_bapicrmdh2 | |
| I_KEYWORD_IN | = lv_i_keyword_in | |
| I_CRMRFCPAR | = lv_i_crmrfcpar | |
| IMPORTING | ||
| E_DO_NOT_SEND | = lv_e_do_not_send | |
| CHANGING | ||
| C_BAPICRMDH2 | = lv_c_bapicrmdh2 | |
| C_RFCDEST | = lv_c_rfcdest | |
| C_OBJNAME | = lv_c_objname | |
| TABLES | ||
| T_INT_TABLES | = lt_t_int_tables | |
| T_BAPISTRUCT | = lt_t_bapistruct | |
| T_MESSAGES | = lt_t_messages | |
| T_KEY_INFO | = lt_t_key_info | |
| T_OTHER_INFO | = lt_t_other_info | |
| T_BAPIIDLIST | = lt_t_bapiidlist | |
| . " SAMPLE_PROCESS_CRM0_200 | ||
ABAP code using 7.40 inline data declarations to call FM SAMPLE_PROCESS_CRM0_200
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 OBJCLASS FROM BAPICRMOBJ INTO @DATA(ld_i_obj_class). | ||||
| "SELECT single XFELD FROM CRM_PARA INTO @DATA(ld_e_do_not_send). | ||||
| "SELECT single OBJ_NAME FROM BAPICRMOBJ INTO @DATA(ld_i_obj_name). | ||||
| "SELECT single OBJ_NAME FROM BAPICRMOBJ INTO @DATA(ld_c_objname). | ||||
| "SELECT single KEYWORD_IN FROM CRM_PARA INTO @DATA(ld_i_keyword_in). | ||||
Search for further information about these or an SAP related objects