ISU_DB_EUITRANS_INT_SINGLE SAP Function module - INTERNAL: Read EUITRANS via Internal Point of Delivery ID

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

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

Pattern for FM ISU_DB_EUITRANS_INT_SINGLE - ISU DB EUITRANS INT SINGLE

CALL FUNCTION 'ISU_DB_EUITRANS_INT_SINGLE' "INTERNAL: Read EUITRANS via Internal Point of Delivery ID
  EXPORTING
    x_int_ui =                  " int_ui        EDM: internal point of delivery
*   x_keydate = SY-DATUM        " e_edmdatefrom  From-Date
*   x_keytime = SY-UZEIT        " e_edmtimefrom  From-Time
*   x_clear_buffer = SPACE      " flag          Clear Buffer
  IMPORTING
    y_euitrans =                " euitrans      Transformation Table: Internal PoD <-> External PoD
  EXCEPTIONS
    NOT_FOUND = 1               "               Object Not Found
    SYSTEM_ERROR = 2            "               Other Error
    .  "  ISU_DB_EUITRANS_INT_SINGLE

ABAP code example for Function Module ISU_DB_EUITRANS_INT_SINGLE

The ABAP code below is a full code listing to execute function module ISU_DB_EUITRANS_INT_SINGLE 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_y_euitrans  
 
 TYPE EUITRANS
.


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

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

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

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

CALL FUNCTION 'ISU_DB_EUITRANS_INT_SINGLE'
  EXPORTING
    x_int_ui =                   ld_x_int_ui
*   x_keydate =                  ld_x_keydate
*   x_keytime =                  ld_x_keytime
*   x_clear_buffer =             ld_x_clear_buffer
  IMPORTING
    y_euitrans =                 ld_y_euitrans
  EXCEPTIONS
    NOT_FOUND =                  1
    SYSTEM_ERROR =               2
    .  "  ISU_DB_EUITRANS_INT_SINGLE

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_y_euitrans
 
 TYPE EUITRANS ,
ld_x_int_ui
 
 TYPE INT_UI ,
ld_x_keydate
 
 TYPE E_EDMDATEFROM ,
ld_x_keytime
 
 TYPE E_EDMTIMEFROM ,
ld_x_clear_buffer
 
 TYPE FLAG .


ld_x_int_ui = 'Check type of data required'.
ld_x_keydate = 'Check type of data required'.
ld_x_keytime = 'Check type of data required'.
ld_x_clear_buffer = 'Check type of data required'.