SAP CMS_API_CLM_SET_SNG Function Module for Set Claim Data - Single
CMS_API_CLM_SET_SNG is a standard cms api clm set sng SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Claim Data - Single 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 cms api clm set sng FM, simply by entering the name CMS_API_CLM_SET_SNG into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_API_CLM
Program Name: SAPLCMS_API_CLM
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_API_CLM_SET_SNG 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 'CMS_API_CLM_SET_SNG'"Set Claim Data - Single.
EXPORTING
I_CLM_GUID = "Movables Primary key
I_STR_CLM_DATA = "Claims SET data API
* I_TAB_CLM_BP_DATA = "Business Partner Link (Set data)
* I_TAB_CLM_DOC_DATA = "Documents Service Link (Set data)
* I_TAB_CLM_VAL_DATA = "Value service link (Set data)
* I_STR_CLM_ADDR_DATA = "Address data for movables (Std tab)
* I_TAB_CLM_INS_DATA = "Insurance Data - SET
IMPORTING
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_API_CLM_SET_SNG
I_CLM_GUID - Movables Primary key
Data type: CMS_DTE_RIG_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
I_STR_CLM_DATA - Claims SET data API
Data type: CMS_STR_CLM_DATA_SETOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_CLM_BP_DATA - Business Partner Link (Set data)
Data type: CMS_TAB_OMS_BP_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_CLM_DOC_DATA - Documents Service Link (Set data)
Data type: CMS_TAB_OMS_DOC_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_CLM_VAL_DATA - Value service link (Set data)
Data type: CMS_TAB_OMS_VAL_LNK_SET_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STR_CLM_ADDR_DATA - Address data for movables (Std tab)
Data type: CMS_STR_RIG_ADDROptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_CLM_INS_DATA - Insurance Data - SET
Data type: CMS_TAB_OMS_INS_DATA_SETOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CMS_API_CLM_SET_SNG
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_API_CLM_SET_SNG 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_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_clm_guid | TYPE CMS_DTE_RIG_GUID, " | |||
| lv_i_str_clm_data | TYPE CMS_STR_CLM_DATA_SET, " | |||
| lv_i_tab_clm_bp_data | TYPE CMS_TAB_OMS_BP_LNK_SET_DATA, " | |||
| lv_i_tab_clm_doc_data | TYPE CMS_TAB_OMS_DOC_LNK_SET_DATA, " | |||
| lv_i_tab_clm_val_data | TYPE CMS_TAB_OMS_VAL_LNK_SET_DATA, " | |||
| lv_i_str_clm_addr_data | TYPE CMS_STR_RIG_ADDR, " | |||
| lv_i_tab_clm_ins_data | TYPE CMS_TAB_OMS_INS_DATA_SET. " |
|   CALL FUNCTION 'CMS_API_CLM_SET_SNG' "Set Claim Data - Single |
| EXPORTING | ||
| I_CLM_GUID | = lv_i_clm_guid | |
| I_STR_CLM_DATA | = lv_i_str_clm_data | |
| I_TAB_CLM_BP_DATA | = lv_i_tab_clm_bp_data | |
| I_TAB_CLM_DOC_DATA | = lv_i_tab_clm_doc_data | |
| I_TAB_CLM_VAL_DATA | = lv_i_tab_clm_val_data | |
| I_STR_CLM_ADDR_DATA | = lv_i_str_clm_addr_data | |
| I_TAB_CLM_INS_DATA | = lv_i_tab_clm_ins_data | |
| IMPORTING | ||
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_API_CLM_SET_SNG | ||
ABAP code using 7.40 inline data declarations to call FM CMS_API_CLM_SET_SNG
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