SAP BM_STREE_NODE_CHANGE_DLVUNIT Function Module for
BM_STREE_NODE_CHANGE_DLVUNIT is a standard bm stree node change dlvunit 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 bm stree node change dlvunit FM, simply by entering the name BM_STREE_NODE_CHANGE_DLVUNIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SFTX
Program Name: SAPLSFTX
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_STREE_NODE_CHANGE_DLVUNIT 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 'BM_STREE_NODE_CHANGE_DLVUNIT'".
EXPORTING
* OBLIGATORY = ' ' "Data element for Flag - Any use
* LANGUAGE = SY-LANGU "SAP R/3 System, Current Language
IMPORTING
MESSAGE = "Transfer structure for messages
ACTION = "Screens, Function Code Triggered by PAI
TABLES
LIST_OF_NODES = "Hierarchy Maintenance Tool Node Transfer Interface
LIST_OF_REFERENCES = "List of References to Structure Items
LIST_OF_TEXTS = "General Structure Repository Node Text
* USER_PARAMETERS = "Hierarchy Maintenance Display Attribute
IMPORTING Parameters details for BM_STREE_NODE_CHANGE_DLVUNIT
OBLIGATORY - Data element for Flag - Any use
Data type: UFFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGE - SAP R/3 System, Current Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BM_STREE_NODE_CHANGE_DLVUNIT
MESSAGE - Transfer structure for messages
Data type: HIER_MESSOptional: No
Call by Reference: No ( called with pass by value option)
ACTION - Screens, Function Code Triggered by PAI
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_STREE_NODE_CHANGE_DLVUNIT
LIST_OF_NODES - Hierarchy Maintenance Tool Node Transfer Interface
Data type: HIER_IFACEOptional: No
Call by Reference: Yes
LIST_OF_REFERENCES - List of References to Structure Items
Data type: HIER_REFOptional: No
Call by Reference: Yes
LIST_OF_TEXTS - General Structure Repository Node Text
Data type: HIER_TEXTSOptional: No
Call by Reference: Yes
USER_PARAMETERS - Hierarchy Maintenance Display Attribute
Data type: STREEPROPOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BM_STREE_NODE_CHANGE_DLVUNIT 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_message | TYPE HIER_MESS, " | |||
| lv_obligatory | TYPE UFFLAG, " SPACE | |||
| lt_list_of_nodes | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lv_action | TYPE SY-UCOMM, " | |||
| lv_language | TYPE SY-LANGU, " SY-LANGU | |||
| lt_list_of_references | TYPE STANDARD TABLE OF HIER_REF, " | |||
| lt_list_of_texts | TYPE STANDARD TABLE OF HIER_TEXTS, " | |||
| lt_user_parameters | TYPE STANDARD TABLE OF STREEPROP. " |
|   CALL FUNCTION 'BM_STREE_NODE_CHANGE_DLVUNIT' " |
| EXPORTING | ||
| OBLIGATORY | = lv_obligatory | |
| LANGUAGE | = lv_language | |
| IMPORTING | ||
| MESSAGE | = lv_message | |
| ACTION | = lv_action | |
| TABLES | ||
| LIST_OF_NODES | = lt_list_of_nodes | |
| LIST_OF_REFERENCES | = lt_list_of_references | |
| LIST_OF_TEXTS | = lt_list_of_texts | |
| USER_PARAMETERS | = lt_user_parameters | |
| . " BM_STREE_NODE_CHANGE_DLVUNIT | ||
ABAP code using 7.40 inline data declarations to call FM BM_STREE_NODE_CHANGE_DLVUNIT
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_obligatory) | = ' '. | |||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_action). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects