SAP CRM_EI_RFC_INSERT_DOCS_CLU Function Module for Insert into feature cluster table









CRM_EI_RFC_INSERT_DOCS_CLU is a standard crm ei rfc insert docs clu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Insert into feature cluster table 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 ei rfc insert docs clu FM, simply by entering the name CRM_EI_RFC_INSERT_DOCS_CLU into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_EI_RFCL
Program Name: SAPLCRM_EI_RFCL
Main Program: SAPLCRM_EI_RFCL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CRM_EI_RFC_INSERT_DOCS_CLU 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_EI_RFC_INSERT_DOCS_CLU'"Insert into feature cluster table
EXPORTING
IT_DOC_KEY = "EI - Document Key table
IV_CLUSTER_ID = "data type for cluster id
IV_KB_NAME = "KB name
IV_LANG_ISO = "Language Key
* IV_CLIENT = SY-MANDT "Client
.



IMPORTING Parameters details for CRM_EI_RFC_INSERT_DOCS_CLU

IT_DOC_KEY - EI - Document Key table

Data type: CRMT_EI_DOC_KEY_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CLUSTER_ID - data type for cluster id

Data type: CRMT_EI_CLUSTER_ID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_KB_NAME - KB name

Data type: CRMT_EI_KB_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

IV_LANG_ISO - Language Key

Data type: CRMT_SAF_LANGU_ISO
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CLIENT - Client

Data type: MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CRM_EI_RFC_INSERT_DOCS_CLU 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_it_doc_key  TYPE CRMT_EI_DOC_KEY_TAB, "   
lv_iv_cluster_id  TYPE CRMT_EI_CLUSTER_ID, "   
lv_iv_kb_name  TYPE CRMT_EI_KB_NAME, "   
lv_iv_lang_iso  TYPE CRMT_SAF_LANGU_ISO, "   
lv_iv_client  TYPE MANDT. "   SY-MANDT

  CALL FUNCTION 'CRM_EI_RFC_INSERT_DOCS_CLU'  "Insert into feature cluster table
    EXPORTING
         IT_DOC_KEY = lv_it_doc_key
         IV_CLUSTER_ID = lv_iv_cluster_id
         IV_KB_NAME = lv_iv_kb_name
         IV_LANG_ISO = lv_iv_lang_iso
         IV_CLIENT = lv_iv_client
. " CRM_EI_RFC_INSERT_DOCS_CLU




ABAP code using 7.40 inline data declarations to call FM CRM_EI_RFC_INSERT_DOCS_CLU

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_iv_client) = SY-MANDT.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!