SOTR_API_WB_ALIAS_NAVIGATE SAP Function module

SOTR_API_WB_ALIAS_NAVIGATE 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 SOTR_API_WB_ALIAS_NAVIGATE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM SOTR_API_WB_ALIAS_NAVIGATE - SOTR API WB ALIAS NAVIGATE

CALL FUNCTION 'SOTR_API_WB_ALIAS_NAVIGATE' "
  EXPORTING
    langu = SY-LANGU            " sylangu       SAP R/3 System, Current Language
    alias =                     " string        Unique Alias Name for OTR Concept
    paket =                     " sotr_pack     Package
    object =                    " trobjtype     Object Type
*   mode = 'M'                  " c
*   flag_correction_entry =     " as4flag       Flag (X or blank)
  IMPORTING
    new_alias =                 " string        Unique Alias Name for OTR Concept
  EXCEPTIONS
    NO_ENTRY_FOUND = 1          "
    USER_CANCELLED = 2          "
    .  "  SOTR_API_WB_ALIAS_NAVIGATE

ABAP code example for Function Module SOTR_API_WB_ALIAS_NAVIGATE

The ABAP code below is a full code listing to execute function module SOTR_API_WB_ALIAS_NAVIGATE 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_new_alias  
 
 TYPE STRING
.


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

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

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

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

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

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

CALL FUNCTION 'SOTR_API_WB_ALIAS_NAVIGATE'
  EXPORTING
    langu =                      ld_langu
    alias =                      ld_alias
    paket =                      ld_paket
    object =                     ld_object
*   mode =                       ld_mode
*   flag_correction_entry =      ld_flag_correction_entry
  IMPORTING
    new_alias =                  ld_new_alias
  EXCEPTIONS
    NO_ENTRY_FOUND =             1
    USER_CANCELLED =             2
    .  "  SOTR_API_WB_ALIAS_NAVIGATE

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_new_alias
 
 TYPE STRING ,
ld_langu
 
 TYPE SYLANGU ,
ld_alias
 
 TYPE STRING ,
ld_paket
 
 TYPE SOTR_PACK ,
ld_object
 
 TYPE TROBJTYPE ,
ld_mode
 
 TYPE C ,
ld_flag_correction_entry
 
 TYPE AS4FLAG .


ld_langu = 'Check type of data required'.
ld_alias = 'Check type of data required'.
ld_paket = 'Check type of data required'.
ld_object = 'Check type of data required'.
ld_mode = 'Check type of data required'.
ld_flag_correction_entry = 'Check type of data required'.