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

Function RULE_RESULT_NODE_CREATE 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 'RULE_RESULT_NODE_CREATE'".
EXPORTING
NODE_NAME = "
NODE_TYPE = "
NODE_MTECLASS = "
* REAL_MTE_TID = "
TID_TO_PROPAGATE = "
* PARAMS_TO_PROPAGATE = "
F1_XMI_MSGCLASS = "
F1_XMI_MSGID = "
IMPORTING
RESULT_NODE = "
IMPORTING Parameters details for RULE_RESULT_NODE_CREATE
NODE_NAME -
Data type: ALTMPLNNAMOptional: No
Call by Reference: Yes
NODE_TYPE -
Data type: ALTMPLNTYPOptional: No
Call by Reference: Yes
NODE_MTECLASS -
Data type: ALCUSGROUPOptional: No
Call by Reference: Yes
REAL_MTE_TID -
Data type: ALGLOBTIDOptional: Yes
Call by Reference: Yes
TID_TO_PROPAGATE -
Data type: ALGLOBTIDOptional: No
Call by Reference: Yes
PARAMS_TO_PROPAGATE -
Data type: ALRLPARTBLOptional: Yes
Call by Reference: Yes
F1_XMI_MSGCLASS -
Data type: XMILOGCOMPOptional: No
Call by Reference: Yes
F1_XMI_MSGID -
Data type: XMILOGMIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RULE_RESULT_NODE_CREATE
RESULT_NODE -
Data type: ALRLRSNODEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RULE_RESULT_NODE_CREATE 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_node_name | TYPE ALTMPLNNAM, " | |||
| lv_result_node | TYPE ALRLRSNODE, " | |||
| lv_node_type | TYPE ALTMPLNTYP, " | |||
| lv_node_mteclass | TYPE ALCUSGROUP, " | |||
| lv_real_mte_tid | TYPE ALGLOBTID, " | |||
| lv_tid_to_propagate | TYPE ALGLOBTID, " | |||
| lv_params_to_propagate | TYPE ALRLPARTBL, " | |||
| lv_f1_xmi_msgclass | TYPE XMILOGCOMP, " | |||
| lv_f1_xmi_msgid | TYPE XMILOGMID. " |
|   CALL FUNCTION 'RULE_RESULT_NODE_CREATE' " |
| EXPORTING | ||
| NODE_NAME | = lv_node_name | |
| NODE_TYPE | = lv_node_type | |
| NODE_MTECLASS | = lv_node_mteclass | |
| REAL_MTE_TID | = lv_real_mte_tid | |
| TID_TO_PROPAGATE | = lv_tid_to_propagate | |
| PARAMS_TO_PROPAGATE | = lv_params_to_propagate | |
| F1_XMI_MSGCLASS | = lv_f1_xmi_msgclass | |
| F1_XMI_MSGID | = lv_f1_xmi_msgid | |
| IMPORTING | ||
| RESULT_NODE | = lv_result_node | |
| . " RULE_RESULT_NODE_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM RULE_RESULT_NODE_CREATE
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