SAP BBP_PDH_BID_TREE_DELETE_NODE Function Module for









BBP_PDH_BID_TREE_DELETE_NODE is a standard bbp pdh bid tree delete node 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 bbp pdh bid tree delete node FM, simply by entering the name BBP_PDH_BID_TREE_DELETE_NODE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PDH_TREE_UI
Program Name: SAPLBBP_PDH_TREE_UI
Main Program: SAPLBBP_PDH_TREE_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_PDH_BID_TREE_DELETE_NODE 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 'BBP_PDH_BID_TREE_DELETE_NODE'"
EXPORTING
IS_OUTLINE = "

CHANGING
CT_TREE_UI = "

EXCEPTIONS
NOT_AN_OUTLINE = 1 PARENT_DOES_NOT_EXIST = 2 NODE_DOES_NOT_EXIST = 3 HEADER_NOT_ERASABLE = 4 NODE_HAS_SONS = 5
.



IMPORTING Parameters details for BBP_PDH_BID_TREE_DELETE_NODE

IS_OUTLINE -

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

CHANGING Parameters details for BBP_PDH_BID_TREE_DELETE_NODE

CT_TREE_UI -

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

EXCEPTIONS details

NOT_AN_OUTLINE -

Data type:
Optional: No
Call by Reference: Yes

PARENT_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

NODE_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

HEADER_NOT_ERASABLE -

Data type:
Optional: No
Call by Reference: Yes

NODE_HAS_SONS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PDH_BID_TREE_DELETE_NODE 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:
lv_ct_tree_ui  TYPE BBPT_TREE_UI, "   
lv_is_outline  TYPE BBP_PDS_BID_ITEM_D, "   
lv_not_an_outline  TYPE BBP_PDS_BID_ITEM_D, "   
lv_parent_does_not_exist  TYPE BBP_PDS_BID_ITEM_D, "   
lv_node_does_not_exist  TYPE BBP_PDS_BID_ITEM_D, "   
lv_header_not_erasable  TYPE BBP_PDS_BID_ITEM_D, "   
lv_node_has_sons  TYPE BBP_PDS_BID_ITEM_D. "   

  CALL FUNCTION 'BBP_PDH_BID_TREE_DELETE_NODE'  "
    EXPORTING
         IS_OUTLINE = lv_is_outline
    CHANGING
         CT_TREE_UI = lv_ct_tree_ui
    EXCEPTIONS
        NOT_AN_OUTLINE = 1
        PARENT_DOES_NOT_EXIST = 2
        NODE_DOES_NOT_EXIST = 3
        HEADER_NOT_ERASABLE = 4
        NODE_HAS_SONS = 5
. " BBP_PDH_BID_TREE_DELETE_NODE




ABAP code using 7.40 inline data declarations to call FM BBP_PDH_BID_TREE_DELETE_NODE

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.

 
 
 
 
 
 
 


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!