OM_GENERATE_TREE_BEHAVIOUR SAP Function module

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

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

Pattern for FM OM_GENERATE_TREE_BEHAVIOUR - OM GENERATE TREE BEHAVIOUR

CALL FUNCTION 'OM_GENERATE_TREE_BEHAVIOUR' "
  EXPORTING
    pathid =                    " gdstr-wegid
*   int_path_flag =             " hrrhas-77aw_int
*   source =                    " flag
*   target =                    " flag
*   move_flag =                 " flag
*   copy_flag =                 " flag
  IMPORTING
    behaviour_tab =             " ombehav_t
* TABLES
*   i77aw =                     " t77aw         Definition of Evaluation Paths
    .  "  OM_GENERATE_TREE_BEHAVIOUR

ABAP code example for Function Module OM_GENERATE_TREE_BEHAVIOUR

The ABAP code below is a full code listing to execute function module OM_GENERATE_TREE_BEHAVIOUR 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_behaviour_tab  
 
 TYPE OMBEHAV_T
,
it_i77aw  
 
 TYPE STANDARD TABLE OF T77AW,"TABLES PARAM
wa_i77aw
 
 LIKE LINE OF it_i77aw
.



DATA(ld_pathid) = some text here


DATA(ld_int_path_flag) = some text here

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

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

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

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

"populate fields of struture and append to itab
append wa_i77aw to it_i77aw.
.

CALL FUNCTION 'OM_GENERATE_TREE_BEHAVIOUR'
  EXPORTING
    pathid =                     ld_pathid
*   int_path_flag =              ld_int_path_flag
*   source =                     ld_source
*   target =                     ld_target
*   move_flag =                  ld_move_flag
*   copy_flag =                  ld_copy_flag
  IMPORTING
    behaviour_tab =              ld_behaviour_tab
* TABLES
*   i77aw =                      it_i77aw
    .  "  OM_GENERATE_TREE_BEHAVIOUR

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_behaviour_tab
 
 TYPE OMBEHAV_T ,
ld_pathid
 
 TYPE GDSTR-WEGID ,
it_i77aw
 
 TYPE STANDARD TABLE OF T77AW ,
wa_i77aw
 
 LIKE LINE OF it_i77aw,
ld_int_path_flag
 
 TYPE HRRHAS-77AW_INT ,
ld_source
 
 TYPE FLAG ,
ld_target
 
 TYPE FLAG ,
ld_move_flag
 
 TYPE FLAG ,
ld_copy_flag
 
 TYPE FLAG .



ld_pathid = some text here 

"populate fields of struture and append to itab
append wa_i77aw to it_i77aw.

ld_int_path_flag = some text here
ld_source = 'Check type of data required'.
ld_target = 'Check type of data required'.
ld_move_flag = 'Check type of data required'.
ld_copy_flag = 'Check type of data required'.