FM_FMDERIVE_CALL_CUSTOMER_EXIT SAP Function module - CALL FMDERIVE USER-EXIT

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

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

Pattern for FM FM_FMDERIVE_CALL_CUSTOMER_EXIT - FM FMDERIVE CALL CUSTOMER EXIT

CALL FUNCTION 'FM_FMDERIVE_CALL_CUSTOMER_EXIT' "CALL FMDERIVE  USER-EXIT
  EXPORTING
    i_env =                     " tabadrs-abadrenv  Environment for strategy
    i_date =                    " sy-datum      Date and time, current (application server) date
    i_step_id =                 " tabadrs-stepid  Strucutre used by the FM Derivation Tool with COBL
    i_fmderive_source =         " fmderive      FM Derivation Structure
  IMPORTING
    e_fmderive_target =         " fmderive      FM Derivation Structure
    e_exit_is_active =          "
    e_failed =                  "
  EXCEPTIONS
    DERIVATION_FAILED = 1       "
    .  "  FM_FMDERIVE_CALL_CUSTOMER_EXIT

ABAP code example for Function Module FM_FMDERIVE_CALL_CUSTOMER_EXIT

The ABAP code below is a full code listing to execute function module FM_FMDERIVE_CALL_CUSTOMER_EXIT 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_fmderive_target  
 
 TYPE FMDERIVE
,
ld_e_exit_is_active  
 
 TYPE STRING
,
ld_e_failed  
 
 TYPE STRING
.

 

SELECT single ABADRENV 
  FROM TABADRS 
  INTO @DATA(ld_i_env).


DATA(ld_i_date) = '20210129'.
 

SELECT single STEPID 
  FROM TABADRS 
  INTO @DATA(ld_i_step_id).


DATA(ld_i_fmderive_source) = '20210129'.
.

CALL FUNCTION 'FM_FMDERIVE_CALL_CUSTOMER_EXIT'
  EXPORTING
    i_env =                      ld_i_env
    i_date =                     ld_i_date
    i_step_id =                  ld_i_step_id
    i_fmderive_source =          ld_i_fmderive_source
  IMPORTING
    e_fmderive_target =          ld_e_fmderive_target
    e_exit_is_active =           ld_e_exit_is_active
    e_failed =                   ld_e_failed
  EXCEPTIONS
    DERIVATION_FAILED =          1
    .  "  FM_FMDERIVE_CALL_CUSTOMER_EXIT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_e_fmderive_target
 
 TYPE FMDERIVE ,
ld_i_env
 
 TYPE TABADRS-ABADRENV ,
ld_e_exit_is_active
 
 TYPE STRING ,
ld_i_date
 
 TYPE SY-DATUM ,
ld_e_failed
 
 TYPE STRING ,
ld_i_step_id
 
 TYPE TABADRS-STEPID ,
ld_i_fmderive_source
 
 TYPE FMDERIVE .



SELECT single ABADRENV 
  FROM TABADRS 
  INTO ld_i_env.

ld_i_date = '20210129'.

SELECT single STEPID 
  FROM TABADRS 
  INTO ld_i_step_id.

ld_i_fmderive_source = '20210129'.