SAP PPEDBFILT_READ Function Module for NOTRANSL: liest Filter









PPEDBFILT_READ is a standard ppedbfilt read 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: liest Filter 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 ppedbfilt read FM, simply by entering the name PPEDBFILT_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: PPEDBFILT
Program Name: SAPLPPEDBFILT
Main Program: SAPLPPEDBFILT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PPEDBFILT_READ 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 'PPEDBFILT_READ'"NOTRANSL: liest Filter
  EXPORTING
*  I_FILTER_GUID =  "Internal Identification for PVS Objects
*  I_FILTER_NAME =  "Filter Name in the iPPE Workbench
   I_USER_ID =  "User Name in User Master Record
*  I_CONTEXT_OTYPE =  "iPPE Workbench Context

TABLES
*  T_FILT_HEAD =  "Header Structure for an iPPE Filter
*  T_TECS =  "Master Effectivity Object
*  T_FILT_OBJ =  "Objects in GUI
*  T_FILT_ATTR =  "Field Catalog Attributes
*  T_FILT_ATTR_SEL =  "Field Catalog Attributes

EXCEPTIONS
   ERROR = 1    INPUT_PARAMETER_INCONSISTENT = 2    NOT_FOUND = 3    NO_ACCESS = 4
.



IMPORTING Parameters details for PPEDBFILT_READ

I_FILTER_GUID - Internal Identification for PVS Objects

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

I_FILTER_NAME - Filter Name in the iPPE Workbench

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

I_USER_ID - User Name in User Master Record

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

I_CONTEXT_OTYPE - iPPE Workbench Context

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

TABLES Parameters details for PPEDBFILT_READ

T_FILT_HEAD - Header Structure for an iPPE Filter

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

T_TECS - Master Effectivity Object

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

T_FILT_OBJ - Objects in GUI

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

T_FILT_ATTR - Field Catalog Attributes

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

T_FILT_ATTR_SEL - Field Catalog Attributes

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

EXCEPTIONS details

ERROR - General Error

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

INPUT_PARAMETER_INCONSISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NOT_FOUND - Not Found

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

NO_ACCESS - No authorization

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPEDBFILT_READ 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_error  TYPE STRING, "   
lt_t_filt_head  TYPE STANDARD TABLE OF FILT_HEAD, "   
lv_i_filter_guid  TYPE PVS_GUID, "   
lt_t_tecs  TYPE STANDARD TABLE OF PPE_TECS, "   
lv_i_filter_name  TYPE PPE_FILTER_NAME, "   
lv_input_parameter_inconsistent  TYPE PPE_FILTER_NAME, "   
lv_i_user_id  TYPE XUBNAME, "   
lv_not_found  TYPE XUBNAME, "   
lt_t_filt_obj  TYPE STANDARD TABLE OF PPEFILTOBJ, "   
lv_no_access  TYPE PPEFILTOBJ, "   
lt_t_filt_attr  TYPE STANDARD TABLE OF PPEFILTATTR, "   
lv_i_context_otype  TYPE PPE_CONTEXT, "   
lt_t_filt_attr_sel  TYPE STANDARD TABLE OF PPEFILTATTRSEL. "   

  CALL FUNCTION 'PPEDBFILT_READ'  "NOTRANSL: liest Filter
    EXPORTING
         I_FILTER_GUID = lv_i_filter_guid
         I_FILTER_NAME = lv_i_filter_name
         I_USER_ID = lv_i_user_id
         I_CONTEXT_OTYPE = lv_i_context_otype
    TABLES
         T_FILT_HEAD = lt_t_filt_head
         T_TECS = lt_t_tecs
         T_FILT_OBJ = lt_t_filt_obj
         T_FILT_ATTR = lt_t_filt_attr
         T_FILT_ATTR_SEL = lt_t_filt_attr_sel
    EXCEPTIONS
        ERROR = 1
        INPUT_PARAMETER_INCONSISTENT = 2
        NOT_FOUND = 3
        NO_ACCESS = 4
. " PPEDBFILT_READ




ABAP code using 7.40 inline data declarations to call FM PPEDBFILT_READ

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!