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

Function NAVIGATION_READ_START_IMAGE 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 'NAVIGATION_READ_START_IMAGE'".
IMPORTING
START_IMAGE_NAME = "
START_IMAGE_RESIZE = "
EXPORTING Parameters details for NAVIGATION_READ_START_IMAGE
START_IMAGE_NAME -
Data type: W3_QNAMEOptional: No
Call by Reference: No ( called with pass by value option)
START_IMAGE_RESIZE -
Data type: SMENSAPNEW-CUSTOMIZEDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NAVIGATION_READ_START_IMAGE 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_start_image_name | TYPE W3_QNAME, " | |||
| lv_start_image_resize | TYPE SMENSAPNEW-CUSTOMIZED. " |
|   CALL FUNCTION 'NAVIGATION_READ_START_IMAGE' " |
| IMPORTING | ||
| START_IMAGE_NAME | = lv_start_image_name | |
| START_IMAGE_RESIZE | = lv_start_image_resize | |
| . " NAVIGATION_READ_START_IMAGE | ||
ABAP code using 7.40 inline data declarations to call FM NAVIGATION_READ_START_IMAGE
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 CUSTOMIZED FROM SMENSAPNEW INTO @DATA(ld_start_image_resize). | ||||
Search for further information about these or an SAP related objects