SAP ADD_CHILD_NODE Function Module for









ADD_CHILD_NODE is a standard add child 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 add child node FM, simply by entering the name ADD_CHILD_NODE into the relevant SAP transaction such as SE37 or SE38.

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



Function ADD_CHILD_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 'ADD_CHILD_NODE'"
EXPORTING
NAME = "
PARENT = "
L_DOCUMENT = "

CHANGING
NODE = "
.



IMPORTING Parameters details for ADD_CHILD_NODE

NAME -

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

PARENT -

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

L_DOCUMENT -

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

CHANGING Parameters details for ADD_CHILD_NODE

NODE -

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

Copy and paste ABAP code example for ADD_CHILD_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_name  TYPE STRING, "   
lv_node  TYPE IF_IXML_ELEMENT, "   
lv_parent  TYPE IF_IXML_ELEMENT, "   
lv_l_document  TYPE IF_IXML_DOCUMENT. "   

  CALL FUNCTION 'ADD_CHILD_NODE'  "
    EXPORTING
         NAME = lv_name
         PARENT = lv_parent
         L_DOCUMENT = lv_l_document
    CHANGING
         NODE = lv_node
. " ADD_CHILD_NODE




ABAP code using 7.40 inline data declarations to call FM ADD_CHILD_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!