DGREL_LB02_WRITE_TO_DB SAP Function module

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

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

Pattern for FM DGREL_LB02_WRITE_TO_DB - DGREL LB02 WRITE TO DB

CALL FUNCTION 'DGREL_LB02_WRITE_TO_DB' "
* EXPORTING
*   i_call_status = 'D'         " dgpd1_call_status
*   i_valdat = SY-DATUM         " rcgaddinf-valdat
*   i_aennr =                   " eseaennr
  IMPORTING
    e_flg_error =               " eseboole
    e_error_wa =                " balmi
  CHANGING
    x_dgrel_tab =               " ehs_rcbduapidgrelappl_t
    x_dgrel_del_tab =           " ehs_rcbduapidgrelappl_t
    .  "  DGREL_LB02_WRITE_TO_DB

ABAP code example for Function Module DGREL_LB02_WRITE_TO_DB

The ABAP code below is a full code listing to execute function module DGREL_LB02_WRITE_TO_DB 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_flg_error  
 
 TYPE ESEBOOLE
,
ld_e_error_wa  
 
 TYPE BALMI
.


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

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

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


DATA(ld_i_valdat) = 20210129

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

CALL FUNCTION 'DGREL_LB02_WRITE_TO_DB'
* EXPORTING
*   i_call_status =              ld_i_call_status
*   i_valdat =                   ld_i_valdat
*   i_aennr =                    ld_i_aennr
  IMPORTING
    e_flg_error =                ld_e_flg_error
    e_error_wa =                 ld_e_error_wa
  CHANGING
    x_dgrel_tab =                ld_x_dgrel_tab
    x_dgrel_del_tab =            ld_x_dgrel_del_tab
    .  "  DGREL_LB02_WRITE_TO_DB

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_x_dgrel_tab
 
 TYPE EHS_RCBDUAPIDGRELAPPL_T ,
ld_e_flg_error
 
 TYPE ESEBOOLE ,
ld_i_call_status
 
 TYPE DGPD1_CALL_STATUS ,
ld_x_dgrel_del_tab
 
 TYPE EHS_RCBDUAPIDGRELAPPL_T ,
ld_e_error_wa
 
 TYPE BALMI ,
ld_i_valdat
 
 TYPE RCGADDINF-VALDAT ,
ld_i_aennr
 
 TYPE ESEAENNR .


ld_x_dgrel_tab = 'Check type of data required'.
ld_i_call_status = 'Check type of data required'.
ld_x_dgrel_del_tab = 'Check type of data required'.

ld_i_valdat = 20210129
ld_i_aennr = 'Check type of data required'.