FM2BL_DERIVATION_TEST SAP Function module - FM2BL - Derivation Test

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

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

Pattern for FM FM2BL_DERIVATION_TEST - FM2BL DERIVATION TEST

CALL FUNCTION 'FM2BL_DERIVATION_TEST' "FM2BL - Derivation Test
  EXPORTING
    i_subclass =                " abadrsubclass  Subgroup by Application Class
    i_env =                     " abadrenv      Environment for strategy
    i_strategy_id =             " abadrstratid  Strategy ID
*   i_display_only = SPACE      " flag          Only Display
* CHANGING
*   c_record_1 =                "
*   c_record_2 =                "
    .  "  FM2BL_DERIVATION_TEST

ABAP code example for Function Module FM2BL_DERIVATION_TEST

The ABAP code below is a full code listing to execute function module FM2BL_DERIVATION_TEST 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_c_record_1) = 'some text here'.

DATA(ld_c_record_2) = 'some text here'.

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

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

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

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

CALL FUNCTION 'FM2BL_DERIVATION_TEST'
  EXPORTING
    i_subclass =                 ld_i_subclass
    i_env =                      ld_i_env
    i_strategy_id =              ld_i_strategy_id
*   i_display_only =             ld_i_display_only
* CHANGING
*   c_record_1 =                 ld_c_record_1
*   c_record_2 =                 ld_c_record_2
    .  "  FM2BL_DERIVATION_TEST

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_c_record_1
 
 TYPE STRING ,
ld_i_subclass
 
 TYPE ABADRSUBCLASS ,
ld_c_record_2
 
 TYPE STRING ,
ld_i_env
 
 TYPE ABADRENV ,
ld_i_strategy_id
 
 TYPE ABADRSTRATID ,
ld_i_display_only
 
 TYPE FLAG .


ld_c_record_1 = 'some text here'.
ld_i_subclass = 'Check type of data required'.
ld_c_record_2 = 'some text here'.
ld_i_env = 'Check type of data required'.
ld_i_strategy_id = 'Check type of data required'.
ld_i_display_only = 'Check type of data required'.