SAP ISU_NAVIGATOR Function Module for INTERNAL: IS-U Navigator









ISU_NAVIGATOR is a standard isu navigator SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Navigator 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 isu navigator FM, simply by entering the name ISU_NAVIGATOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: ECN1
Program Name: SAPLECN1
Main Program: SAPLECN1
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_NAVIGATOR 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 'ISU_NAVIGATOR'"INTERNAL: IS-U Navigator
  EXPORTING
*  X_OBJREF =  "
*  X_ACTUAL = ' ' "
*  X_NOSCREEN = ' ' "
*  X_OBJTYPE =  "
*  X_OBJKEY =  "
*  X_CONFIG = ' ' "Navigator configuration
*  X_PRGCONTEXT = ' ' "
*  X_SUBCONTEXT = ' ' "Call context - subcontext
*  X_FROM = SY-DATUM "
*  X_TO = SY-DATUM "End of the Period of Examination
*  X_FILTER = ' ' "

 IMPORTING
   T_OBJECT =  "
   T_HLIST =  "

EXCEPTIONS
   CONFIG_NOT_FOUND = 1    OBJECT_INVALID = 2    CONFIG_INVALID = 3    CANCELLED = 4
.



IMPORTING Parameters details for ISU_NAVIGATOR

X_OBJREF -

Data type: OBJ_RECORD
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_ACTUAL -

Data type: EBAGEN-KENNZX
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_NOSCREEN -

Data type: EBAGEN-KENNZX
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_OBJTYPE -

Data type: EBAGEN-OBJTYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_OBJKEY -

Data type: EBAGEN-OBJKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_CONFIG - Navigator configuration

Data type: ECNCONF-CONFIG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PRGCONTEXT -

Data type: ECNFIND-PRGCONTEXT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_SUBCONTEXT - Call context - subcontext

Data type: ECNFIND-SUBCONTEXT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_FROM -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_TO - End of the Period of Examination

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_FILTER -

Data type: EBAGEN-KENNZX
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_NAVIGATOR

T_OBJECT -

Data type: ECNOBJECTTAB
Optional: No
Call by Reference: Yes

T_HLIST -

Data type: SNODETAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CONFIG_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_INVALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CONFIG_INVALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCELLED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_NAVIGATOR 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_t_object  TYPE ECNOBJECTTAB, "   
lv_x_objref  TYPE OBJ_RECORD, "   
lv_config_not_found  TYPE OBJ_RECORD, "   
lv_x_actual  TYPE EBAGEN-KENNZX, "   SPACE
lv_x_noscreen  TYPE EBAGEN-KENNZX, "   SPACE
lv_t_hlist  TYPE SNODETAB, "   
lv_x_objtype  TYPE EBAGEN-OBJTYPE, "   
lv_object_invalid  TYPE EBAGEN, "   
lv_x_objkey  TYPE EBAGEN-OBJKEY, "   
lv_config_invalid  TYPE EBAGEN, "   
lv_x_config  TYPE ECNCONF-CONFIG, "   SPACE
lv_cancelled  TYPE ECNCONF, "   
lv_x_prgcontext  TYPE ECNFIND-PRGCONTEXT, "   SPACE
lv_x_subcontext  TYPE ECNFIND-SUBCONTEXT, "   SPACE
lv_x_from  TYPE SY-DATUM, "   SY-DATUM
lv_x_to  TYPE SY-DATUM, "   SY-DATUM
lv_x_filter  TYPE EBAGEN-KENNZX. "   SPACE

  CALL FUNCTION 'ISU_NAVIGATOR'  "INTERNAL: IS-U Navigator
    EXPORTING
         X_OBJREF = lv_x_objref
         X_ACTUAL = lv_x_actual
         X_NOSCREEN = lv_x_noscreen
         X_OBJTYPE = lv_x_objtype
         X_OBJKEY = lv_x_objkey
         X_CONFIG = lv_x_config
         X_PRGCONTEXT = lv_x_prgcontext
         X_SUBCONTEXT = lv_x_subcontext
         X_FROM = lv_x_from
         X_TO = lv_x_to
         X_FILTER = lv_x_filter
    IMPORTING
         T_OBJECT = lv_t_object
         T_HLIST = lv_t_hlist
    EXCEPTIONS
        CONFIG_NOT_FOUND = 1
        OBJECT_INVALID = 2
        CONFIG_INVALID = 3
        CANCELLED = 4
. " ISU_NAVIGATOR




ABAP code using 7.40 inline data declarations to call FM ISU_NAVIGATOR

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 KENNZX FROM EBAGEN INTO @DATA(ld_x_actual).
DATA(ld_x_actual) = ' '.
 
"SELECT single KENNZX FROM EBAGEN INTO @DATA(ld_x_noscreen).
DATA(ld_x_noscreen) = ' '.
 
 
"SELECT single OBJTYPE FROM EBAGEN INTO @DATA(ld_x_objtype).
 
 
"SELECT single OBJKEY FROM EBAGEN INTO @DATA(ld_x_objkey).
 
 
"SELECT single CONFIG FROM ECNCONF INTO @DATA(ld_x_config).
DATA(ld_x_config) = ' '.
 
 
"SELECT single PRGCONTEXT FROM ECNFIND INTO @DATA(ld_x_prgcontext).
DATA(ld_x_prgcontext) = ' '.
 
"SELECT single SUBCONTEXT FROM ECNFIND INTO @DATA(ld_x_subcontext).
DATA(ld_x_subcontext) = ' '.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_x_from).
DATA(ld_x_from) = SY-DATUM.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_x_to).
DATA(ld_x_to) = SY-DATUM.
 
"SELECT single KENNZX FROM EBAGEN INTO @DATA(ld_x_filter).
DATA(ld_x_filter) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!