SAP CRM_GET_EXTENSION_PROCESS_TYPE Function Module for Get SC document guid from extension
CRM_GET_EXTENSION_PROCESS_TYPE is a standard crm get extension process type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get SC document guid from extension 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 get extension process type FM, simply by entering the name CRM_GET_EXTENSION_PROCESS_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_PROVIDER_TOOLS
Program Name: SAPLCRM_PROVIDER_TOOLS
Main Program: SAPLCRM_PROVIDER_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_GET_EXTENSION_PROCESS_TYPE 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_GET_EXTENSION_PROCESS_TYPE'"Get SC document guid from extension.
EXPORTING
IV_ITEM_GUID = "
IMPORTING
EV_PROCESS_TYPE = "Process Type
IMPORTING Parameters details for CRM_GET_EXTENSION_PROCESS_TYPE
IV_ITEM_GUID -
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_GET_EXTENSION_PROCESS_TYPE
EV_PROCESS_TYPE - Process Type
Data type: IST_ITEM_PROCESSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_GET_EXTENSION_PROCESS_TYPE 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_item_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_ev_process_type | TYPE IST_ITEM_PROCESS. " |
|   CALL FUNCTION 'CRM_GET_EXTENSION_PROCESS_TYPE' "Get SC document guid from extension |
| EXPORTING | ||
| IV_ITEM_GUID | = lv_iv_item_guid | |
| IMPORTING | ||
| EV_PROCESS_TYPE | = lv_ev_process_type | |
| . " CRM_GET_EXTENSION_PROCESS_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM CRM_GET_EXTENSION_PROCESS_TYPE
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