SAP SX_NODE_ID_DETERMINE Function Module for SAPconnect: Routing Module (Determination of Outbound Node)
SX_NODE_ID_DETERMINE is a standard sx node id determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPconnect: Routing Module (Determination of Outbound Node) processing and below is the pattern details for this FM, 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 sx node id determine FM, simply by entering the name SX_NODE_ID_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SX01
Program Name: SAPLSX01
Main Program: SAPLSX01
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SX_NODE_ID_DETERMINE 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 'SX_NODE_ID_DETERMINE'"SAPconnect: Routing Module (Determination of Outbound Node).
EXPORTING
RECIPIENT = "Any type of recipient address
SENDER = "Sender address in RML type (system:cl:sapusername)
* EXPLAIN = "If true, determination is explained (WRITE)
* IGNORE_CDG = ' ' "If true, CDG of sender is ignored
* APPLOG = "
* IS_NORMAL = "
IMPORTING
NODE_ID = "Outbound node
EXCEPTIONS
ERR_NODE_NOT_FOUND = 1 ERR_REC_ADDR_INVALID = 2 ERR_SND_ADDR_INVALID = 3
IMPORTING Parameters details for SX_NODE_ID_DETERMINE
RECIPIENT - Any type of recipient address
Data type: SX_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
SENDER - Sender address in RML type (system:cl:sapusername)
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPLAIN - If true, determination is explained (WRITE)
Data type: SX_BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
IGNORE_CDG - If true, CDG of sender is ignored
Data type: SX_BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
APPLOG -
Data type: BALLOGHNDLOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_NORMAL -
Data type: SX_BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SX_NODE_ID_DETERMINE
NODE_ID - Outbound node
Data type: SX_NODE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERR_NODE_NOT_FOUND - No node for this sender/recipient combination
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_REC_ADDR_INVALID - Invalid recipient address
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_SND_ADDR_INVALID - Sender address not RML type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SX_NODE_ID_DETERMINE 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_id | TYPE SX_NODE_ID, " | |||
| lv_recipient | TYPE SX_ADDRESS, " | |||
| lv_err_node_not_found | TYPE SX_ADDRESS, " | |||
| lv_sender | TYPE SY-UNAME, " | |||
| lv_err_rec_addr_invalid | TYPE SY, " | |||
| lv_explain | TYPE SX_BOOLEAN, " | |||
| lv_err_snd_addr_invalid | TYPE SX_BOOLEAN, " | |||
| lv_ignore_cdg | TYPE SX_BOOLEAN, " SPACE | |||
| lv_applog | TYPE BALLOGHNDL, " | |||
| lv_is_normal | TYPE SX_BOOLEAN. " |
|   CALL FUNCTION 'SX_NODE_ID_DETERMINE' "SAPconnect: Routing Module (Determination of Outbound Node) |
| EXPORTING | ||
| RECIPIENT | = lv_recipient | |
| SENDER | = lv_sender | |
| EXPLAIN | = lv_explain | |
| IGNORE_CDG | = lv_ignore_cdg | |
| APPLOG | = lv_applog | |
| IS_NORMAL | = lv_is_normal | |
| IMPORTING | ||
| NODE_ID | = lv_node_id | |
| EXCEPTIONS | ||
| ERR_NODE_NOT_FOUND = 1 | ||
| ERR_REC_ADDR_INVALID = 2 | ||
| ERR_SND_ADDR_INVALID = 3 | ||
| . " SX_NODE_ID_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM SX_NODE_ID_DETERMINE
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_sender). | ||||
| DATA(ld_ignore_cdg) | = ' '. | |||
Search for further information about these or an SAP related objects