UMV_NODE_DRAG_DROP SAP Function module

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

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

Pattern for FM UMV_NODE_DRAG_DROP - UMV NODE DRAG DROP

CALL FUNCTION 'UMV_NODE_DRAG_DROP' "
  EXPORTING
    i_vdtnod =                  " umv_y_vdtnod
    i_from_vdtnodp =            " umv_y_vdtnodp
    i_to_vdtnodp =              " umv_y_vdtnodp
  IMPORTING
    e_pos =                     " umv_y_position
  EXCEPTIONS
    DB_ERROR = 1                "
    NODE_NOT_EXISTING = 2       "
    FROM_VDTNODP_NOT_EXISTING = 3  "
    TO_VDTNODP_NOT_EXISTING = 4  "
    .  "  UMV_NODE_DRAG_DROP

ABAP code example for Function Module UMV_NODE_DRAG_DROP

The ABAP code below is a full code listing to execute function module UMV_NODE_DRAG_DROP 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_pos  
 
 TYPE UMV_Y_POSITION
.


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

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

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

CALL FUNCTION 'UMV_NODE_DRAG_DROP'
  EXPORTING
    i_vdtnod =                   ld_i_vdtnod
    i_from_vdtnodp =             ld_i_from_vdtnodp
    i_to_vdtnodp =               ld_i_to_vdtnodp
  IMPORTING
    e_pos =                      ld_e_pos
  EXCEPTIONS
    DB_ERROR =                   1
    NODE_NOT_EXISTING =          2
    FROM_VDTNODP_NOT_EXISTING =    3
    TO_VDTNODP_NOT_EXISTING =    4
    .  "  UMV_NODE_DRAG_DROP

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_pos
 
 TYPE UMV_Y_POSITION ,
ld_i_vdtnod
 
 TYPE UMV_Y_VDTNOD ,
ld_i_from_vdtnodp
 
 TYPE UMV_Y_VDTNODP ,
ld_i_to_vdtnodp
 
 TYPE UMV_Y_VDTNODP .


ld_i_vdtnod = 'Check type of data required'.
ld_i_from_vdtnodp = 'Check type of data required'.
ld_i_to_vdtnodp = 'Check type of data required'.