CMS_API_INS_CHECK SAP Function module - Business checks for Insurance - Obj layer

CMS_API_INS_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CMS_API_INS_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CMS_API_INS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CMS_API_INS_CHECK - CMS API INS CHECK

CALL FUNCTION 'CMS_API_INS_CHECK' "Business checks for Insurance - Obj layer
  EXPORTING
    i_ins_guid =                " cms_dte_ins_guid  Insurance GUID
*   i_ast_objsysid =            " cms_dte_obj_sysid  Object System Reference ID
    i_tab_related_guid =        " cms_tab_pcn_object_id  Object IDs
    i_tab_chk =                 " cms_tab_pcn_actvt_pl  Plausibility checks for an activity
  IMPORTING
    e_tab_msg =                 " cms_tab_msg_col_message  Return Code and corresponding Message
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_API_INS_CHECK

ABAP code example for Function Module CMS_API_INS_CHECK

The ABAP code below is a full code listing to execute function module CMS_API_INS_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_tab_msg  
 
 TYPE CMS_TAB_MSG_COL_MESSAGE
,
ld_e_tab_rc  
 
 TYPE CMS_TAB_MSG_COL_MESSAGE
.


DATA(ld_i_ins_guid) = 'Check type of data required'.

DATA(ld_i_ast_objsysid) = '20210129'.

DATA(ld_i_tab_related_guid) = 'some text here'.

DATA(ld_i_tab_chk) = 'some text here'.
.

CALL FUNCTION 'CMS_API_INS_CHECK'
  EXPORTING
    i_ins_guid =                 ld_i_ins_guid
*   i_ast_objsysid =             ld_i_ast_objsysid
    i_tab_related_guid =         ld_i_tab_related_guid
    i_tab_chk =                  ld_i_tab_chk
  IMPORTING
    e_tab_msg =                  ld_e_tab_msg
    e_tab_rc =                   ld_e_tab_rc
    .  "  CMS_API_INS_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_tab_msg
 
 TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_ins_guid
 
 TYPE CMS_DTE_INS_GUID ,
ld_e_tab_rc
 
 TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_ast_objsysid
 
 TYPE CMS_DTE_OBJ_SYSID ,
ld_i_tab_related_guid
 
 TYPE CMS_TAB_PCN_OBJECT_ID ,
ld_i_tab_chk
 
 TYPE CMS_TAB_PCN_ACTVT_PL .


ld_i_ins_guid = 'some text here'.
ld_i_ast_objsysid = '20210129'.
ld_i_tab_related_guid = 'some text here'.
ld_i_tab_chk = 'some text here'.