SAP TOE_NOE_DISPLAY Function Module for Calls the proper Screen
TOE_NOE_DISPLAY is a standard toe noe display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls the proper Screen 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 toe noe display FM, simply by entering the name TOE_NOE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: TOE_UI
Program Name: SAPLTOE_UI
Main Program: SAPLTOE_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TOE_NOE_DISPLAY 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 'TOE_NOE_DISPLAY'"Calls the proper Screen.
EXPORTING
IV_SCREEN_NUMBER = "Screen Number
* IV_POP_UP_START_X = "
* IV_POP_UP_START_Y = "
* IV_POP_UP_END_X = "
* IV_POP_UP_END_Y = "
IMPORTING Parameters details for TOE_NOE_DISPLAY
IV_SCREEN_NUMBER - Screen Number
Data type: SY-DYNNROptional: No
Call by Reference: Yes
IV_POP_UP_START_X -
Data type: IOptional: Yes
Call by Reference: Yes
IV_POP_UP_START_Y -
Data type: IOptional: Yes
Call by Reference: Yes
IV_POP_UP_END_X -
Data type: IOptional: Yes
Call by Reference: Yes
IV_POP_UP_END_Y -
Data type: IOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for TOE_NOE_DISPLAY 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_iv_screen_number | TYPE SY-DYNNR, " | |||
| lv_iv_pop_up_start_x | TYPE I, " | |||
| lv_iv_pop_up_start_y | TYPE I, " | |||
| lv_iv_pop_up_end_x | TYPE I, " | |||
| lv_iv_pop_up_end_y | TYPE I. " |
|   CALL FUNCTION 'TOE_NOE_DISPLAY' "Calls the proper Screen |
| EXPORTING | ||
| IV_SCREEN_NUMBER | = lv_iv_screen_number | |
| IV_POP_UP_START_X | = lv_iv_pop_up_start_x | |
| IV_POP_UP_START_Y | = lv_iv_pop_up_start_y | |
| IV_POP_UP_END_X | = lv_iv_pop_up_end_x | |
| IV_POP_UP_END_Y | = lv_iv_pop_up_end_y | |
| . " TOE_NOE_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM TOE_NOE_DISPLAY
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 DYNNR FROM SY INTO @DATA(ld_iv_screen_number). | ||||
Search for further information about these or an SAP related objects