FVER_CREATE SAP Function module - Create Executable Rights

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

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

Pattern for FM FVER_CREATE - FVER CREATE

CALL FUNCTION 'FVER_CREATE' "Create Executable Rights
  EXPORTING
    i_righttype =               " ter_righttype  Type des Rechts (Optionsschein,...)
    i_str_rightinterface =      " tersinterface  Parameter zum Erzeugen den Rechts
  IMPORTING
    e_tab_mesg =                " terymesg      Error Messages Table
    e_referencenumber =         " ter_referencenumber  identifiziert zugehörige Rechte zu einer Gattung
  EXCEPTIONS
    NO_RIGHTTYPE = 1            "               kein Rechtstyp angegeben
    DATA_INCONSISTENCY = 2      "               Dateninkosistenz
    .  "  FVER_CREATE

ABAP code example for Function Module FVER_CREATE

The ABAP code below is a full code listing to execute function module FVER_CREATE 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_e_tab_mesg  
 
 TYPE TERYMESG
,
ld_e_referencenumber  
 
 TYPE TER_REFERENCENUMBER
.


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

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

CALL FUNCTION 'FVER_CREATE'
  EXPORTING
    i_righttype =                ld_i_righttype
    i_str_rightinterface =       ld_i_str_rightinterface
  IMPORTING
    e_tab_mesg =                 ld_e_tab_mesg
    e_referencenumber =          ld_e_referencenumber
  EXCEPTIONS
    NO_RIGHTTYPE =               1
    DATA_INCONSISTENCY =         2
    .  "  FVER_CREATE

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_e_tab_mesg
 
 TYPE TERYMESG ,
ld_i_righttype
 
 TYPE TER_RIGHTTYPE ,
ld_e_referencenumber
 
 TYPE TER_REFERENCENUMBER ,
ld_i_str_rightinterface
 
 TYPE TERSINTERFACE .


ld_i_righttype = 'Check type of data required'.
ld_i_str_rightinterface = 'Check type of data required'.