BBP_CTR_UI_HIER_ROOT_SAVE SAP Function module - hold the hierarchy root, which is saved on db

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

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

Pattern for FM BBP_CTR_UI_HIER_ROOT_SAVE - BBP CTR UI HIER ROOT SAVE

CALL FUNCTION 'BBP_CTR_UI_HIER_ROOT_SAVE' "hold the hierarchy root, which is saved on db
  EXPORTING
*   iv_set =                    " c
*   iv_get =                    " c
*   iv_header_id =              " crmt_object_id_db  Transaction Number
*   iv_parent_id =              " bbp_hier_parent_objid  Object ID of the parent node
    is_global =                 " bbps_ctr_ui_global  Global Data in Purchase Contract
  IMPORTING
    ev_parent_id =              " bbp_hier_parent_objid  Object ID of the parent node
    ev_parent_id_db =           " bbp_hier_parent_objid  Object ID of the parent node
    .  "  BBP_CTR_UI_HIER_ROOT_SAVE

ABAP code example for Function Module BBP_CTR_UI_HIER_ROOT_SAVE

The ABAP code below is a full code listing to execute function module BBP_CTR_UI_HIER_ROOT_SAVE 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_ev_parent_id  
 
 TYPE BBP_HIER_PARENT_OBJID
,
ld_ev_parent_id_db  
 
 TYPE BBP_HIER_PARENT_OBJID
.


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

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

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

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

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

CALL FUNCTION 'BBP_CTR_UI_HIER_ROOT_SAVE'
  EXPORTING
*   iv_set =                     ld_iv_set
*   iv_get =                     ld_iv_get
*   iv_header_id =               ld_iv_header_id
*   iv_parent_id =               ld_iv_parent_id
    is_global =                  ld_is_global
  IMPORTING
    ev_parent_id =               ld_ev_parent_id
    ev_parent_id_db =            ld_ev_parent_id_db
    .  "  BBP_CTR_UI_HIER_ROOT_SAVE

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_ev_parent_id
 
 TYPE BBP_HIER_PARENT_OBJID ,
ld_iv_set
 
 TYPE C ,
ld_ev_parent_id_db
 
 TYPE BBP_HIER_PARENT_OBJID ,
ld_iv_get
 
 TYPE C ,
ld_iv_header_id
 
 TYPE CRMT_OBJECT_ID_DB ,
ld_iv_parent_id
 
 TYPE BBP_HIER_PARENT_OBJID ,
ld_is_global
 
 TYPE BBPS_CTR_UI_GLOBAL .


ld_iv_set = 'Check type of data required'.
ld_iv_get = 'Check type of data required'.
ld_iv_header_id = 'Check type of data required'.
ld_iv_parent_id = 'Check type of data required'.
ld_is_global = 'Check type of data required'.