SAP UA_RFC_PDCE_TREE_LOAD_ID Function Module for









UA_RFC_PDCE_TREE_LOAD_ID is a standard ua rfc pdce tree load id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ua rfc pdce tree load id FM, simply by entering the name UA_RFC_PDCE_TREE_LOAD_ID into the relevant SAP transaction such as SE37 or SE38.

Function Group: UA_RFC_PDCE
Program Name: SAPLUA_RFC_PDCE
Main Program: SAPLUA_RFC_PDCE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function UA_RFC_PDCE_TREE_LOAD_ID pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'UA_RFC_PDCE_TREE_LOAD_ID'"
  EXPORTING
   ID_DATABASIS =  "Data Basis
   ID_ROOT_OBJ_ID =  "
   ID_ROOT_OBJ_TYPENAME =  "
*  ID_CALCULATE =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
*  ID_DISPLAY = 'X' "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

 IMPORTING
   ED_DISPLAY_ONLY =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
   ED_CODE =  "

TABLES
   ET_OBJECT =  "
   ET_NODE =  "
   ET_EDGE =  "
   ET_TNODE =  "
   ET_HIER =  "Edges for Data Basis 1PDCE
   BAPIRET2 =  "Return Parameters
.



IMPORTING Parameters details for UA_RFC_PDCE_TREE_LOAD_ID

ID_DATABASIS - Data Basis

Data type: ACC_DATABASIS
Optional: No
Call by Reference: No ( called with pass by value option)

ID_ROOT_OBJ_ID -

Data type: FOBJ_OBJECT_ID
Optional: No
Call by Reference: No ( called with pass by value option)

ID_ROOT_OBJ_TYPENAME -

Data type: FINB_TYPE_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

ID_CALCULATE - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_DISPLAY - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UA_RFC_PDCE_TREE_LOAD_ID

ED_DISPLAY_ONLY - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: No
Call by Reference: No ( called with pass by value option)

ED_CODE -

Data type: SYSUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for UA_RFC_PDCE_TREE_LOAD_ID

ET_OBJECT -

Data type: UAB_T_RFC_OBJECT_PDCE
Optional: No
Call by Reference: No ( called with pass by value option)

ET_NODE -

Data type: UAB_T_RFC_NODE_PDCE
Optional: No
Call by Reference: No ( called with pass by value option)

ET_EDGE -

Data type: UAB_T_RFC_EDGE_PDCE
Optional: No
Call by Reference: No ( called with pass by value option)

ET_TNODE -

Data type: UAB_T_RFC_TNODE_PDCE
Optional: No
Call by Reference: Yes

ET_HIER - Edges for Data Basis 1PDCE

Data type: UAB_T_RFC_TREE_PDCE
Optional: No
Call by Reference: Yes

BAPIRET2 - Return Parameters

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for UA_RFC_PDCE_TREE_LOAD_ID Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_et_object  TYPE STANDARD TABLE OF UAB_T_RFC_OBJECT_PDCE, "   
lv_id_databasis  TYPE ACC_DATABASIS, "   
lv_ed_display_only  TYPE BOOLE_D, "   
lv_ed_code  TYPE SYSUBRC, "   
lt_et_node  TYPE STANDARD TABLE OF UAB_T_RFC_NODE_PDCE, "   
lv_id_root_obj_id  TYPE FOBJ_OBJECT_ID, "   
lt_et_edge  TYPE STANDARD TABLE OF UAB_T_RFC_EDGE_PDCE, "   
lv_id_root_obj_typename  TYPE FINB_TYPE_NAME, "   
lt_et_tnode  TYPE STANDARD TABLE OF UAB_T_RFC_TNODE_PDCE, "   
lv_id_calculate  TYPE BOOLE_D, "   
lt_et_hier  TYPE STANDARD TABLE OF UAB_T_RFC_TREE_PDCE, "   
lv_id_display  TYPE BOOLE_D, "   'X'
lt_bapiret2  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'UA_RFC_PDCE_TREE_LOAD_ID'  "
    EXPORTING
         ID_DATABASIS = lv_id_databasis
         ID_ROOT_OBJ_ID = lv_id_root_obj_id
         ID_ROOT_OBJ_TYPENAME = lv_id_root_obj_typename
         ID_CALCULATE = lv_id_calculate
         ID_DISPLAY = lv_id_display
    IMPORTING
         ED_DISPLAY_ONLY = lv_ed_display_only
         ED_CODE = lv_ed_code
    TABLES
         ET_OBJECT = lt_et_object
         ET_NODE = lt_et_node
         ET_EDGE = lt_et_edge
         ET_TNODE = lt_et_tnode
         ET_HIER = lt_et_hier
         BAPIRET2 = lt_bapiret2
. " UA_RFC_PDCE_TREE_LOAD_ID




ABAP code using 7.40 inline data declarations to call FM UA_RFC_PDCE_TREE_LOAD_ID

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
DATA(ld_id_display) = 'X'.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!