SAP SEGMENT_FOR_RUNTIME_READ Function Module for
SEGMENT_FOR_RUNTIME_READ is a standard segment for runtime read 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 segment for runtime read FM, simply by entering the name SEGMENT_FOR_RUNTIME_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDIJ
Program Name: SAPLEDIJ
Main Program: SAPLEDIJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SEGMENT_FOR_RUNTIME_READ 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 'SEGMENT_FOR_RUNTIME_READ'".
EXPORTING
SEGMENTTYP = "Segment Type
TABLES
SEGMENTSTRUCTURE = "EDI: IDoc Segment Application Structure
EXCEPTIONS
SEGMENT_DOES_NOT_EXIST = 1
IMPORTING Parameters details for SEGMENT_FOR_RUNTIME_READ
SEGMENTTYP - Segment Type
Data type: EDISEGMHD-SEGTYPOptional: No
Call by Reference: Yes
TABLES Parameters details for SEGMENT_FOR_RUNTIME_READ
SEGMENTSTRUCTURE - EDI: IDoc Segment Application Structure
Data type: EDSAPPLOptional: No
Call by Reference: Yes
EXCEPTIONS details
SEGMENT_DOES_NOT_EXIST - Segment Does Not Exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SEGMENT_FOR_RUNTIME_READ 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_segmenttyp | TYPE EDISEGMHD-SEGTYP, " | |||
| lt_segmentstructure | TYPE STANDARD TABLE OF EDSAPPL, " | |||
| lv_segment_does_not_exist | TYPE EDSAPPL. " |
|   CALL FUNCTION 'SEGMENT_FOR_RUNTIME_READ' " |
| EXPORTING | ||
| SEGMENTTYP | = lv_segmenttyp | |
| TABLES | ||
| SEGMENTSTRUCTURE | = lt_segmentstructure | |
| EXCEPTIONS | ||
| SEGMENT_DOES_NOT_EXIST = 1 | ||
| . " SEGMENT_FOR_RUNTIME_READ | ||
ABAP code using 7.40 inline data declarations to call FM SEGMENT_FOR_RUNTIME_READ
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 SEGTYP FROM EDISEGMHD INTO @DATA(ld_segmenttyp). | ||||
Search for further information about these or an SAP related objects