SAP VIEWPROC_JDVGENER Function Module for Extended Table Maintenance: Lower Level
VIEWPROC_JDVGENER is a standard viewproc jdvgener SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extended Table Maintenance: Lower Level 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 viewproc jdvgener FM, simply by entering the name VIEWPROC_JDVGENER into the relevant SAP transaction such as SE37 or SE38.
Function Group: 0JDL
Program Name: SAPL0JDL
Main Program: SAPL0JDL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function VIEWPROC_JDVGENER 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 'VIEWPROC_JDVGENER'"Extended Table Maintenance: Lower Level.
EXPORTING
* FCODE = 'RDED' "
* VIEW_ACTION = 'S' "
VIEW_NAME = "
* CORR_NUMBER = ' ' "
IMPORTING
LAST_ACT_ENTRY = "
UCOMM = "
UPDATE_REQUIRED = "
TABLES
CORR_KEYTAB = "
DBA_SELLIST = "
DPL_SELLIST = "
EXCL_CUA_FUNCT = "
EXTRACT = "
TOTAL = "
X_HEADER = "
X_NAMTAB = "
EXCEPTIONS
NO_VALUE_FOR_SUBSET_IDENT = 1 MISSING_CORR_NUMBER = 2 SAVING_CORRECTION_FAILED = 3
IMPORTING Parameters details for VIEWPROC_JDVGENER
FCODE -
Data type:Default: 'RDED'
Optional: No
Call by Reference: No ( called with pass by value option)
VIEW_ACTION -
Data type:Default: 'S'
Optional: No
Call by Reference: No ( called with pass by value option)
VIEW_NAME -
Data type: DD02V-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
CORR_NUMBER -
Data type: E070-TRKORRDefault: ' '
Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VIEWPROC_JDVGENER
LAST_ACT_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UCOMM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_REQUIRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for VIEWPROC_JDVGENER
CORR_KEYTAB -
Data type: E071KOptional: No
Call by Reference: No ( called with pass by value option)
DBA_SELLIST -
Data type: VIMSELLISTOptional: No
Call by Reference: No ( called with pass by value option)
DPL_SELLIST -
Data type: VIMSELLISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCL_CUA_FUNCT -
Data type: VIMEXCLFUNOptional: No
Call by Reference: No ( called with pass by value option)
EXTRACT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOTAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_HEADER -
Data type: VIMDESCOptional: No
Call by Reference: No ( called with pass by value option)
X_NAMTAB -
Data type: VIMNAMTABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_VALUE_FOR_SUBSET_IDENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_CORR_NUMBER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SAVING_CORRECTION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VIEWPROC_JDVGENER 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_fcode | TYPE STRING, " 'RDED' | |||
lt_corr_keytab | TYPE STANDARD TABLE OF E071K, " | |||
lv_last_act_entry | TYPE E071K, " | |||
lv_no_value_for_subset_ident | TYPE E071K, " | |||
lv_ucomm | TYPE E071K, " | |||
lt_dba_sellist | TYPE STANDARD TABLE OF VIMSELLIST, " | |||
lv_view_action | TYPE VIMSELLIST, " 'S' | |||
lv_missing_corr_number | TYPE VIMSELLIST, " | |||
lv_view_name | TYPE DD02V-TABNAME, " | |||
lt_dpl_sellist | TYPE STANDARD TABLE OF VIMSELLIST, " | |||
lv_update_required | TYPE VIMSELLIST, " | |||
lv_saving_correction_failed | TYPE VIMSELLIST, " | |||
lv_corr_number | TYPE E070-TRKORR, " ' ' | |||
lt_excl_cua_funct | TYPE STANDARD TABLE OF VIMEXCLFUN, " | |||
lt_extract | TYPE STANDARD TABLE OF VIMEXCLFUN, " | |||
lt_total | TYPE STANDARD TABLE OF VIMEXCLFUN, " | |||
lt_x_header | TYPE STANDARD TABLE OF VIMDESC, " | |||
lt_x_namtab | TYPE STANDARD TABLE OF VIMNAMTAB. " |
  CALL FUNCTION 'VIEWPROC_JDVGENER' "Extended Table Maintenance: Lower Level |
EXPORTING | ||
FCODE | = lv_fcode | |
VIEW_ACTION | = lv_view_action | |
VIEW_NAME | = lv_view_name | |
CORR_NUMBER | = lv_corr_number | |
IMPORTING | ||
LAST_ACT_ENTRY | = lv_last_act_entry | |
UCOMM | = lv_ucomm | |
UPDATE_REQUIRED | = lv_update_required | |
TABLES | ||
CORR_KEYTAB | = lt_corr_keytab | |
DBA_SELLIST | = lt_dba_sellist | |
DPL_SELLIST | = lt_dpl_sellist | |
EXCL_CUA_FUNCT | = lt_excl_cua_funct | |
EXTRACT | = lt_extract | |
TOTAL | = lt_total | |
X_HEADER | = lt_x_header | |
X_NAMTAB | = lt_x_namtab | |
EXCEPTIONS | ||
NO_VALUE_FOR_SUBSET_IDENT = 1 | ||
MISSING_CORR_NUMBER = 2 | ||
SAVING_CORRECTION_FAILED = 3 | ||
. " VIEWPROC_JDVGENER |
ABAP code using 7.40 inline data declarations to call FM VIEWPROC_JDVGENER
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_fcode) | = 'RDED'. | |||
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