TRINT_CHECK_DU_EDIT SAP Function module

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

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

Pattern for FM TRINT_CHECK_DU_EDIT - TRINT CHECK DU EDIT

CALL FUNCTION 'TRINT_CHECK_DU_EDIT' "
* EXPORTING
*   iv_devclass =               " tadir-devclass
*   iv_tdevc_filled =           " trpari-flag
*   iv_insert_devc =            " trpari-flag
  IMPORTING
    et_dlvunits =               " trdlvunits
    es_single_checked_du =      " trdlvunit
* CHANGING
*   cs_tdevc =                  " tdevc
  EXCEPTIONS
    NO_DU_CHANGEABLE = 1        "
    .  "  TRINT_CHECK_DU_EDIT

ABAP code example for Function Module TRINT_CHECK_DU_EDIT

The ABAP code below is a full code listing to execute function module TRINT_CHECK_DU_EDIT 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_et_dlvunits  
 
 TYPE TRDLVUNITS
,
ld_es_single_checked_du  
 
 TYPE TRDLVUNIT
.


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

SELECT single DEVCLASS 
  FROM TADIR 
  INTO @DATA(ld_iv_devclass).



DATA(ld_iv_tdevc_filled) = some text here


DATA(ld_iv_insert_devc) = some text here
.

CALL FUNCTION 'TRINT_CHECK_DU_EDIT'
* EXPORTING
*   iv_devclass =                ld_iv_devclass
*   iv_tdevc_filled =            ld_iv_tdevc_filled
*   iv_insert_devc =             ld_iv_insert_devc
  IMPORTING
    et_dlvunits =                ld_et_dlvunits
    es_single_checked_du =       ld_es_single_checked_du
* CHANGING
*   cs_tdevc =                   ld_cs_tdevc
  EXCEPTIONS
    NO_DU_CHANGEABLE =           1
    .  "  TRINT_CHECK_DU_EDIT

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_cs_tdevc
 
 TYPE TDEVC ,
ld_et_dlvunits
 
 TYPE TRDLVUNITS ,
ld_iv_devclass
 
 TYPE TADIR-DEVCLASS ,
ld_es_single_checked_du
 
 TYPE TRDLVUNIT ,
ld_iv_tdevc_filled
 
 TYPE TRPARI-FLAG ,
ld_iv_insert_devc
 
 TYPE TRPARI-FLAG .


ld_cs_tdevc = 'Check type of data required'.

SELECT single DEVCLASS 
  FROM TADIR 
  INTO ld_iv_devclass.


ld_iv_tdevc_filled = some text here

ld_iv_insert_devc = some text here