WB_TREE_GET_OBJECT_POSITION SAP Function module

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

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

Pattern for FM WB_TREE_GET_OBJECT_POSITION - WB TREE GET OBJECT POSITION

CALL FUNCTION 'WB_TREE_GET_OBJECT_POSITION' "
  EXPORTING
    object_type =               " seu_objtyp
    object_name =               " seu_objkey    WB Request: Key for an object in the ABAP Workbench
  IMPORTING
    node_id =                   " treev_nkey    Tree control (CNT4): Structure of node key table
  TABLES
    expand =                    " treev_nkey    Tree control (CNT4): Structure of node key table
  EXCEPTIONS
    PARAMETER_ERROR = 1         "               Incorrect parameter value
    NOT_FOUND = 2               "               Object Not Found
    .  "  WB_TREE_GET_OBJECT_POSITION

ABAP code example for Function Module WB_TREE_GET_OBJECT_POSITION

The ABAP code below is a full code listing to execute function module WB_TREE_GET_OBJECT_POSITION 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_node_id  
 
 TYPE TREEV_NKEY
,
it_expand  
 
 TYPE STANDARD TABLE OF TREEV_NKEY,"TABLES PARAM
wa_expand
 
 LIKE LINE OF it_expand
.


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

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

"populate fields of struture and append to itab
append wa_expand to it_expand.
.

CALL FUNCTION 'WB_TREE_GET_OBJECT_POSITION'
  EXPORTING
    object_type =                ld_object_type
    object_name =                ld_object_name
  IMPORTING
    node_id =                    ld_node_id
  TABLES
    expand =                     it_expand
  EXCEPTIONS
    PARAMETER_ERROR =            1
    NOT_FOUND =                  2
    .  "  WB_TREE_GET_OBJECT_POSITION

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_node_id
 
 TYPE TREEV_NKEY ,
ld_object_type
 
 TYPE SEU_OBJTYP ,
it_expand
 
 TYPE STANDARD TABLE OF TREEV_NKEY ,
wa_expand
 
 LIKE LINE OF it_expand,
ld_object_name
 
 TYPE SEU_OBJKEY .


ld_object_type = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_expand to it_expand.
ld_object_name = 'Check type of data required'.