SAP FVVI_AUTHORITY_MESSAGE Function Module for









FVVI_AUTHORITY_MESSAGE is a standard fvvi authority message 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 fvvi authority message FM, simply by entering the name FVVI_AUTHORITY_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVVI
Program Name: SAPLFVVI
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FVVI_AUTHORITY_MESSAGE 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 'FVVI_AUTHORITY_MESSAGE'"
  EXPORTING
   AUTH_ACTVT =  "
*  AUTH_BUKRS = ' ' "
   AUTH_OBJECT =  "
   AUTH_SUBRC =  "
*  AUTH_SWENR = ' ' "
*  AUTH_SKOART = ' ' "

EXCEPTIONS
   AUTHORITY_DESTROYED = 1    NO_AUTHORITY = 2    NO_AUTHORITY_PROFILE = 3    NO_USER_ENTRY = 4    TOO_MUCH_PARAMETER = 5    UNKNOWN_ERROR = 6    WRONG_FIELD_NAME = 7
.



IMPORTING Parameters details for FVVI_AUTHORITY_MESSAGE

AUTH_ACTVT -

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

AUTH_BUKRS -

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

AUTH_OBJECT -

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

AUTH_SUBRC -

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

AUTH_SWENR -

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

AUTH_SKOART -

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

EXCEPTIONS details

AUTHORITY_DESTROYED -

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

NO_AUTHORITY -

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

NO_AUTHORITY_PROFILE -

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

NO_USER_ENTRY -

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

TOO_MUCH_PARAMETER -

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

UNKNOWN_ERROR -

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

WRONG_FIELD_NAME -

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

Copy and paste ABAP code example for FVVI_AUTHORITY_MESSAGE 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_auth_actvt  TYPE RFVZBEROBJ-VVACTVT, "   
lv_authority_destroyed  TYPE RFVZBEROBJ, "   
lv_auth_bukrs  TYPE T001-BUKRS, "   SPACE
lv_no_authority  TYPE T001, "   
lv_auth_object  TYPE T001, "   
lv_no_authority_profile  TYPE T001, "   
lv_auth_subrc  TYPE SY-SUBRC, "   
lv_no_user_entry  TYPE SY, "   
lv_auth_swenr  TYPE VIOB01-SWENR, "   SPACE
lv_too_much_parameter  TYPE VIOB01, "   
lv_auth_skoart  TYPE TZK01-SKOART, "   SPACE
lv_unknown_error  TYPE TZK01, "   
lv_wrong_field_name  TYPE TZK01. "   

  CALL FUNCTION 'FVVI_AUTHORITY_MESSAGE'  "
    EXPORTING
         AUTH_ACTVT = lv_auth_actvt
         AUTH_BUKRS = lv_auth_bukrs
         AUTH_OBJECT = lv_auth_object
         AUTH_SUBRC = lv_auth_subrc
         AUTH_SWENR = lv_auth_swenr
         AUTH_SKOART = lv_auth_skoart
    EXCEPTIONS
        AUTHORITY_DESTROYED = 1
        NO_AUTHORITY = 2
        NO_AUTHORITY_PROFILE = 3
        NO_USER_ENTRY = 4
        TOO_MUCH_PARAMETER = 5
        UNKNOWN_ERROR = 6
        WRONG_FIELD_NAME = 7
. " FVVI_AUTHORITY_MESSAGE




ABAP code using 7.40 inline data declarations to call FM FVVI_AUTHORITY_MESSAGE

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 VVACTVT FROM RFVZBEROBJ INTO @DATA(ld_auth_actvt).
 
 
"SELECT single BUKRS FROM T001 INTO @DATA(ld_auth_bukrs).
DATA(ld_auth_bukrs) = ' '.
 
 
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_auth_subrc).
 
 
"SELECT single SWENR FROM VIOB01 INTO @DATA(ld_auth_swenr).
DATA(ld_auth_swenr) = ' '.
 
 
"SELECT single SKOART FROM TZK01 INTO @DATA(ld_auth_skoart).
DATA(ld_auth_skoart) = ' '.
 
 
 


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!