SAP VIEWFRAME_VRROLETYP Function Module for Upper-level extended table maintenance









VIEWFRAME_VRROLETYP is a standard viewframe vrroletyp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Upper-level extended table maintenance 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 viewframe vrroletyp FM, simply by entering the name VIEWFRAME_VRROLETYP into the relevant SAP transaction such as SE37 or SE38.

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



Function VIEWFRAME_VRROLETYP 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 'VIEWFRAME_VRROLETYP'"Upper-level extended table maintenance
  EXPORTING
*  VIEW_ACTION = 'S' "View action: display/change (S/U)
   VIEW_NAME =  "Name of view
*  CORR_NUMBER = ' ' "Correction Number for Changes Made

TABLES
   DBA_SELLIST =  "Database Access Selection Conditions
   DPL_SELLIST =  "Display Selection Conditions
   EXCL_CUA_FUNCT =  "Table with dynam. CUA funct. to be deactivated
   X_HEADER =  "Control block table for view
   X_NAMTAB =  "View Fields Control Block Table

EXCEPTIONS
   NO_VALUE_FOR_SUBSET_IDENT = 1    MISSING_CORR_NUMBER = 2
.



IMPORTING Parameters details for VIEWFRAME_VRROLETYP

VIEW_ACTION - View action: display/change (S/U)

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

VIEW_NAME - Name of view

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

CORR_NUMBER - Correction Number for Changes Made

Data type: E070-TRKORR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for VIEWFRAME_VRROLETYP

DBA_SELLIST - Database Access Selection Conditions

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

DPL_SELLIST - Display Selection Conditions

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

EXCL_CUA_FUNCT - Table with dynam. CUA funct. to be deactivated

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

X_HEADER - Control block table for view

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

X_NAMTAB - View Fields Control Block Table

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

EXCEPTIONS details

NO_VALUE_FOR_SUBSET_IDENT - No value was specified for 'SUBSET' field

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

MISSING_CORR_NUMBER - Correction Number Missing

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

Copy and paste ABAP code example for VIEWFRAME_VRROLETYP 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:
lt_dba_sellist  TYPE STANDARD TABLE OF VIMSELLIST, "   
lv_view_action  TYPE VIMSELLIST, "   'S'
lv_no_value_for_subset_ident  TYPE VIMSELLIST, "   
lv_view_name  TYPE DD02V-TABNAME, "   
lt_dpl_sellist  TYPE STANDARD TABLE OF VIMSELLIST, "   
lv_missing_corr_number  TYPE VIMSELLIST, "   
lv_corr_number  TYPE E070-TRKORR, "   ' '
lt_excl_cua_funct  TYPE STANDARD TABLE OF VIMEXCLFUN, "   
lt_x_header  TYPE STANDARD TABLE OF VIMDESC, "   
lt_x_namtab  TYPE STANDARD TABLE OF VIMNAMTAB. "   

  CALL FUNCTION 'VIEWFRAME_VRROLETYP'  "Upper-level extended table maintenance
    EXPORTING
         VIEW_ACTION = lv_view_action
         VIEW_NAME = lv_view_name
         CORR_NUMBER = lv_corr_number
    TABLES
         DBA_SELLIST = lt_dba_sellist
         DPL_SELLIST = lt_dpl_sellist
         EXCL_CUA_FUNCT = lt_excl_cua_funct
         X_HEADER = lt_x_header
         X_NAMTAB = lt_x_namtab
    EXCEPTIONS
        NO_VALUE_FOR_SUBSET_IDENT = 1
        MISSING_CORR_NUMBER = 2
. " VIEWFRAME_VRROLETYP




ABAP code using 7.40 inline data declarations to call FM VIEWFRAME_VRROLETYP

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.

 
DATA(ld_view_action) = 'S'.
 
 
"SELECT single TABNAME FROM DD02V INTO @DATA(ld_view_name).
 
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_corr_number).
DATA(ld_corr_number) = ' '.
 
 
 
 


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!