SAP STPB3_EXTENT_NODE_IDS Function Module for NOTRANSL: liest die langen STEP Namen und den Typen für einen Knoten
STPB3_EXTENT_NODE_IDS is a standard stpb3 extent node ids SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: liest die langen STEP Namen und den Typen für einen Knoten 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 stpb3 extent node ids FM, simply by entering the name STPB3_EXTENT_NODE_IDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: STPB3
Program Name: SAPLSTPB3
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STPB3_EXTENT_NODE_IDS 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 'STPB3_EXTENT_NODE_IDS'"NOTRANSL: liest die langen STEP Namen und den Typen für einen Knoten.
EXPORTING
NODE_ID = "
TABLES
EXTENT_NODE_IDS = "
IMPORTING Parameters details for STPB3_EXTENT_NODE_IDS
NODE_ID -
Data type: SNODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for STPB3_EXTENT_NODE_IDS
EXTENT_NODE_IDS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STPB3_EXTENT_NODE_IDS 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 SNODE-ID, " | |||
| lt_extent_node_ids | TYPE STANDARD TABLE OF SNODE. " |
|   CALL FUNCTION 'STPB3_EXTENT_NODE_IDS' "NOTRANSL: liest die langen STEP Namen und den Typen für einen Knoten |
| EXPORTING | ||
| NODE_ID | = lv_node_id | |
| TABLES | ||
| EXTENT_NODE_IDS | = lt_extent_node_ids | |
| . " STPB3_EXTENT_NODE_IDS | ||
ABAP code using 7.40 inline data declarations to call FM STPB3_EXTENT_NODE_IDS
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 ID FROM SNODE INTO @DATA(ld_node_id). | ||||
Search for further information about these or an SAP related objects