ICL_BCUST_ITEM_COV_BENTREE_GET SAP Function module - Determine the benefit type tree for a claimed item

ICL_BCUST_ITEM_COV_BENTREE_GET 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 ICL_BCUST_ITEM_COV_BENTREE_GET into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ICL_BCUST_ITEM_COV_BENTREE_GET - ICL BCUST ITEM COV BENTREE GET

CALL FUNCTION 'ICL_BCUST_ITEM_COV_BENTREE_GET' "Determine the benefit type tree for a claimed item
  EXPORTING
    is_item =                   " icl_itemlist  ICL: GUI Structure for Claim Item List (Screen 301)
*   is_subcl =                  " icl_iclsubcl  ICL: Subclaim Information: Fields on Screen
  IMPORTING
    es_ticl161 =                " ticl161       Version of Benefit Type Tree
  EXCEPTIONS
    INVALID_ITEM_DATA = 1       "
    NO_BENTREE_DEFINED = 2      "               no_bentree_defined
    NO_BENTREE_VERSION = 3      "               no_bentree_version
    NOT_FOUND = 4               "               NOT_FOUND
    INVALID_COVTYPE = 5         "
    .  "  ICL_BCUST_ITEM_COV_BENTREE_GET

ABAP code example for Function Module ICL_BCUST_ITEM_COV_BENTREE_GET

The ABAP code below is a full code listing to execute function module ICL_BCUST_ITEM_COV_BENTREE_GET 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_es_ticl161  
 
 TYPE TICL161
.


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

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

CALL FUNCTION 'ICL_BCUST_ITEM_COV_BENTREE_GET'
  EXPORTING
    is_item =                    ld_is_item
*   is_subcl =                   ld_is_subcl
  IMPORTING
    es_ticl161 =                 ld_es_ticl161
  EXCEPTIONS
    INVALID_ITEM_DATA =          1
    NO_BENTREE_DEFINED =         2
    NO_BENTREE_VERSION =         3
    NOT_FOUND =                  4
    INVALID_COVTYPE =            5
    .  "  ICL_BCUST_ITEM_COV_BENTREE_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
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_es_ticl161
 
 TYPE TICL161 ,
ld_is_item
 
 TYPE ICL_ITEMLIST ,
ld_is_subcl
 
 TYPE ICL_ICLSUBCL .


ld_is_item = 'Check type of data required'.
ld_is_subcl = 'Check type of data required'.