SAP PVSDBWTY_OR_READ_DB Function Module for NOTRANSL: Lesen die Datenbank für Online-reporting









PVSDBWTY_OR_READ_DB is a standard pvsdbwty or read db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen die Datenbank für Online-reporting 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 pvsdbwty or read db FM, simply by entering the name PVSDBWTY_OR_READ_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function PVSDBWTY_OR_READ_DB 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 'PVSDBWTY_OR_READ_DB'"NOTRANSL: Lesen die Datenbank für Online-reporting
  EXPORTING
   IV_EXTRACTION_TYPE =  "
   IV_SELECTION_TYPE =  "
*  IT_SELECTION_FIELDS =  "Logical DB Field Selection: Field Name
*  IT_WHERE_CLAUSES =  "
*  IT_WA_DESCR =  "
*  IT_FIELD_SELECTION_MATCH =  "
*  IT_SELECT_FIELDS =  "

 IMPORTING
   ET_PNWTYH_DIA =  "Dialog Table Header
   ET_PNWTYV_DIA =  "Dialog Table Version
   ET_PVWTY_DIA =  "Dialog Table Item

EXCEPTIONS
   AUTHORITY_FAILED = 1
.



IMPORTING Parameters details for PVSDBWTY_OR_READ_DB

IV_EXTRACTION_TYPE -

Data type: PWTY_EXTRACTION_TYPE
Optional: No
Call by Reference: Yes

IV_SELECTION_TYPE -

Data type: PWTY_SELECTION_TYPE
Optional: No
Call by Reference: Yes

IT_SELECTION_FIELDS - Logical DB Field Selection: Field Name

Data type: RSFSFIELDST
Optional: Yes
Call by Reference: Yes

IT_WHERE_CLAUSES -

Data type: RSDS_WHERE_TAB
Optional: Yes
Call by Reference: Yes

IT_WA_DESCR -

Data type: PWTY_LD_WA_DESCR_TAB
Optional: Yes
Call by Reference: Yes

IT_FIELD_SELECTION_MATCH -

Data type: PWTY_LD_FLD_SELECT_MATCH_TAB
Optional: Yes
Call by Reference: Yes

IT_SELECT_FIELDS -

Data type: RSFS_FIELDS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PVSDBWTY_OR_READ_DB

ET_PNWTYH_DIA - Dialog Table Header

Data type: WTY_PNWTYH_DIA_TAB
Optional: No
Call by Reference: Yes

ET_PNWTYV_DIA - Dialog Table Version

Data type: WTY_PNWTYV_DIA_TAB
Optional: No
Call by Reference: Yes

ET_PVWTY_DIA - Dialog Table Item

Data type: WTY_PVWTY_DIA_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

AUTHORITY_FAILED - No Authorization

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PVSDBWTY_OR_READ_DB 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_et_pnwtyh_dia  TYPE WTY_PNWTYH_DIA_TAB, "   
lv_authority_failed  TYPE WTY_PNWTYH_DIA_TAB, "   
lv_iv_extraction_type  TYPE PWTY_EXTRACTION_TYPE, "   
lv_et_pnwtyv_dia  TYPE WTY_PNWTYV_DIA_TAB, "   
lv_iv_selection_type  TYPE PWTY_SELECTION_TYPE, "   
lv_et_pvwty_dia  TYPE WTY_PVWTY_DIA_TAB, "   
lv_it_selection_fields  TYPE RSFSFIELDST, "   
lv_it_where_clauses  TYPE RSDS_WHERE_TAB, "   
lv_it_wa_descr  TYPE PWTY_LD_WA_DESCR_TAB, "   
lv_it_field_selection_match  TYPE PWTY_LD_FLD_SELECT_MATCH_TAB, "   
lv_it_select_fields  TYPE RSFS_FIELDS. "   

  CALL FUNCTION 'PVSDBWTY_OR_READ_DB'  "NOTRANSL: Lesen die Datenbank für Online-reporting
    EXPORTING
         IV_EXTRACTION_TYPE = lv_iv_extraction_type
         IV_SELECTION_TYPE = lv_iv_selection_type
         IT_SELECTION_FIELDS = lv_it_selection_fields
         IT_WHERE_CLAUSES = lv_it_where_clauses
         IT_WA_DESCR = lv_it_wa_descr
         IT_FIELD_SELECTION_MATCH = lv_it_field_selection_match
         IT_SELECT_FIELDS = lv_it_select_fields
    IMPORTING
         ET_PNWTYH_DIA = lv_et_pnwtyh_dia
         ET_PNWTYV_DIA = lv_et_pnwtyv_dia
         ET_PVWTY_DIA = lv_et_pvwty_dia
    EXCEPTIONS
        AUTHORITY_FAILED = 1
. " PVSDBWTY_OR_READ_DB




ABAP code using 7.40 inline data declarations to call FM PVSDBWTY_OR_READ_DB

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.

 
 
 
 
 
 
 
 
 
 
 


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!