SAP Function Modules

STREE_NODE_CREATE_BMO2 SAP Function module







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

Associated Function Group: SFTX_NODE
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM STREE_NODE_CREATE_BMO2 - STREE NODE CREATE BMO2





CALL FUNCTION 'STREE_NODE_CREATE_BMO2' "
  EXPORTING
    structure_id =              " hier_iface-tree_id
*   filter_id =                 " hier_iface-tree_id
    extension =                 " hier_iface-extension
*   language =                  " sy-langu
*   predecessor_title =         " hier_texts-text
  IMPORTING
    message =                   " hier_mess
    action =                    " sy-ucomm
  TABLES
    possible_node_types =       " hier_ntype
    list_of_nodes =             " hier_iface
    list_of_references =        " hier_ref
    list_of_texts =             " hier_texts
    user_parameters =           " streeprop
    .  "  STREE_NODE_CREATE_BMO2

ABAP code example for Function Module STREE_NODE_CREATE_BMO2





The ABAP code below is a full code listing to execute function module STREE_NODE_CREATE_BMO2 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_message  TYPE HIER_MESS ,
ld_action  TYPE SY-UCOMM ,
it_possible_node_types  TYPE STANDARD TABLE OF HIER_NTYPE,"TABLES PARAM
wa_possible_node_types  LIKE LINE OF it_possible_node_types ,
it_list_of_nodes  TYPE STANDARD TABLE OF HIER_IFACE,"TABLES PARAM
wa_list_of_nodes  LIKE LINE OF it_list_of_nodes ,
it_list_of_references  TYPE STANDARD TABLE OF HIER_REF,"TABLES PARAM
wa_list_of_references  LIKE LINE OF it_list_of_references ,
it_list_of_texts  TYPE STANDARD TABLE OF HIER_TEXTS,"TABLES PARAM
wa_list_of_texts  LIKE LINE OF it_list_of_texts ,
it_user_parameters  TYPE STANDARD TABLE OF STREEPROP,"TABLES PARAM
wa_user_parameters  LIKE LINE OF it_user_parameters .


DATA(ld_structure_id) = some text here

DATA(ld_filter_id) = some text here

DATA(ld_extension) = some text here
DATA(ld_language) = 'Check type of data required'.

DATA(ld_predecessor_title) = some text here

"populate fields of struture and append to itab
append wa_possible_node_types to it_possible_node_types.

"populate fields of struture and append to itab
append wa_list_of_nodes to it_list_of_nodes.

"populate fields of struture and append to itab
append wa_list_of_references to it_list_of_references.

"populate fields of struture and append to itab
append wa_list_of_texts to it_list_of_texts.

"populate fields of struture and append to itab
append wa_user_parameters to it_user_parameters. . CALL FUNCTION 'STREE_NODE_CREATE_BMO2' EXPORTING structure_id = ld_structure_id * filter_id = ld_filter_id extension = ld_extension * language = ld_language * predecessor_title = ld_predecessor_title IMPORTING message = ld_message action = ld_action TABLES possible_node_types = it_possible_node_types list_of_nodes = it_list_of_nodes list_of_references = it_list_of_references list_of_texts = it_list_of_texts user_parameters = it_user_parameters . " STREE_NODE_CREATE_BMO2
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_message  TYPE HIER_MESS ,
ld_structure_id  TYPE HIER_IFACE-TREE_ID ,
it_possible_node_types  TYPE STANDARD TABLE OF HIER_NTYPE ,
wa_possible_node_types  LIKE LINE OF it_possible_node_types,
ld_action  TYPE SY-UCOMM ,
ld_filter_id  TYPE HIER_IFACE-TREE_ID ,
it_list_of_nodes  TYPE STANDARD TABLE OF HIER_IFACE ,
wa_list_of_nodes  LIKE LINE OF it_list_of_nodes,
ld_extension  TYPE HIER_IFACE-EXTENSION ,
it_list_of_references  TYPE STANDARD TABLE OF HIER_REF ,
wa_list_of_references  LIKE LINE OF it_list_of_references,
ld_language  TYPE SY-LANGU ,
it_list_of_texts  TYPE STANDARD TABLE OF HIER_TEXTS ,
wa_list_of_texts  LIKE LINE OF it_list_of_texts,
ld_predecessor_title  TYPE HIER_TEXTS-TEXT ,
it_user_parameters  TYPE STANDARD TABLE OF STREEPROP ,
wa_user_parameters  LIKE LINE OF it_user_parameters.


ld_structure_id = some text here

"populate fields of struture and append to itab
append wa_possible_node_types to it_possible_node_types.

ld_filter_id = some text here

"populate fields of struture and append to itab
append wa_list_of_nodes to it_list_of_nodes.

ld_extension = some text here

"populate fields of struture and append to itab
append wa_list_of_references to it_list_of_references.
ld_language = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_list_of_texts to it_list_of_texts.

ld_predecessor_title = some text here

"populate fields of struture and append to itab
append wa_user_parameters to it_user_parameters.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name STREE_NODE_CREATE_BMO2 or its description.