ICL_SUBCL_SALVAGE_POTENTIAL SAP Function module - Maintain salvage status to potential

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

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

Pattern for FM ICL_SUBCL_SALVAGE_POTENTIAL - ICL SUBCL SALVAGE POTENTIAL

CALL FUNCTION 'ICL_SUBCL_SALVAGE_POTENTIAL' "Maintain salvage status to potential
  EXPORTING
    is_iclsubcl =               " icl_iclsubcl  ICL: Subclaim Information: Fields on Screen
*   iv_dobj =                   " icl_damobj
*   iv_from_subcl =             " xfeld         Checkbox
*   iv_from_dobj =              " boole_d
*   iv_from_assign =            " boole_d
  EXCEPTIONS
    NO_DAMAGEDOBJ = 1           "
    MULTIPLE_DAMOBJ_IN_SUBCL = 2  "
    .  "  ICL_SUBCL_SALVAGE_POTENTIAL

ABAP code example for Function Module ICL_SUBCL_SALVAGE_POTENTIAL

The ABAP code below is a full code listing to execute function module ICL_SUBCL_SALVAGE_POTENTIAL 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_is_iclsubcl) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'ICL_SUBCL_SALVAGE_POTENTIAL'
  EXPORTING
    is_iclsubcl =                ld_is_iclsubcl
*   iv_dobj =                    ld_iv_dobj
*   iv_from_subcl =              ld_iv_from_subcl
*   iv_from_dobj =               ld_iv_from_dobj
*   iv_from_assign =             ld_iv_from_assign
  EXCEPTIONS
    NO_DAMAGEDOBJ =              1
    MULTIPLE_DAMOBJ_IN_SUBCL =    2
    .  "  ICL_SUBCL_SALVAGE_POTENTIAL

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
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_is_iclsubcl
 
 TYPE ICL_ICLSUBCL ,
ld_iv_dobj
 
 TYPE ICL_DAMOBJ ,
ld_iv_from_subcl
 
 TYPE XFELD ,
ld_iv_from_dobj
 
 TYPE BOOLE_D ,
ld_iv_from_assign
 
 TYPE BOOLE_D .


ld_is_iclsubcl = 'Check type of data required'.
ld_iv_dobj = 'Check type of data required'.
ld_iv_from_subcl = 'Check type of data required'.
ld_iv_from_dobj = 'Check type of data required'.
ld_iv_from_assign = 'Check type of data required'.