RS_NAVIGATION_SEML_ENTRY SAP Function module - Navigation Module: Calling the Relationship List Through Monitor

RS_NAVIGATION_SEML_ENTRY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RS_NAVIGATION_SEML_ENTRY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SEML
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RS_NAVIGATION_SEML_ENTRY - RS NAVIGATION SEML ENTRY

CALL FUNCTION 'RS_NAVIGATION_SEML_ENTRY' "Navigation Module: Calling the Relationship List Through Monitor
  EXPORTING
    navtab_entry =              " navtab
*   status_i = SPACE            " nav_status
  IMPORTING
    status_o =                  " nav_status
    exit_o =                    "
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    PARAMETER_ERROR = 2         "
    .  "  RS_NAVIGATION_SEML_ENTRY

ABAP code example for Function Module RS_NAVIGATION_SEML_ENTRY

The ABAP code below is a full code listing to execute function module RS_NAVIGATION_SEML_ENTRY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_status_o  
 
 TYPE NAV_STATUS
,
ld_exit_o  
 
 TYPE STRING
.


DATA(ld_navtab_entry) = 'Check type of data required'.

DATA(ld_status_i) = 'Check type of data required'.
.

CALL FUNCTION 'RS_NAVIGATION_SEML_ENTRY'
  EXPORTING
    navtab_entry =               ld_navtab_entry
*   status_i =                   ld_status_i
  IMPORTING
    status_o =                   ld_status_o
    exit_o =                     ld_exit_o
  EXCEPTIONS
    INTERNAL_ERROR =             1
    PARAMETER_ERROR =            2
    .  "  RS_NAVIGATION_SEML_ENTRY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_status_o
 
 TYPE NAV_STATUS ,
ld_navtab_entry
 
 TYPE NAVTAB ,
ld_exit_o
 
 TYPE STRING ,
ld_status_i
 
 TYPE NAV_STATUS .


ld_navtab_entry = 'Check type of data required'.
ld_status_i = 'Check type of data required'.