SAP PPEDBFILT_EXPL_MAINTAIN Function Module for NOTRANSL: ändert/anlegen Auflösungsparameter des Filters
PPEDBFILT_EXPL_MAINTAIN is a standard ppedbfilt expl maintain 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: ändert/anlegen Auflösungsparameter des Filters 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 expl maintain FM, simply by entering the name PPEDBFILT_EXPL_MAINTAIN 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_EXPL_MAINTAIN 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_EXPL_MAINTAIN'"NOTRANSL: ändert/anlegen Auflösungsparameter des Filters.
EXPORTING
IM_EXPL = "Filter for Explosion Parameters
IM_COMMIT_FLG = "Checkbox
* IM_CREATE_IF_NOT_EXIST = "Checkbox
* IM_CUOBJ_TEMP = 'X' "Checkbox
* IM_INDX_ID = "INDX ID
IMPORTING
EX_EXPL_GUID = "Internal Identification for PVS Objects
EX_EXPL_CUOBJ = "Configuration (Internal Object Number)
TABLES
* T_FILT_EFF = "Table of Effectivity Parameters
* T_CUOBJ_VALUES = "Interface for Value of a Characteristic (Internal Format)
EXCEPTIONS
ERROR = 1 NOT_FOUND = 2 CUOBJ_ERROR = 3 TECHS_ERROR = 4
IMPORTING Parameters details for PPEDBFILT_EXPL_MAINTAIN
IM_EXPL - Filter for Explosion Parameters
Data type: FILT_EXPLOptional: No
Call by Reference: No ( called with pass by value option)
IM_COMMIT_FLG - Checkbox
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
IM_CREATE_IF_NOT_EXIST - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_CUOBJ_TEMP - Checkbox
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_INDX_ID - INDX ID
Data type: PPE_INDX_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PPEDBFILT_EXPL_MAINTAIN
EX_EXPL_GUID - Internal Identification for PVS Objects
Data type: PVS_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EX_EXPL_CUOBJ - Configuration (Internal Object Number)
Data type: PPE_CUOBJOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PPEDBFILT_EXPL_MAINTAIN
T_FILT_EFF - Table of Effectivity Parameters
Data type: TFILT_EFFOptional: Yes
Call by Reference: Yes
T_CUOBJ_VALUES - Interface for Value of a Characteristic (Internal Format)
Data type: PPE_API_VALIOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR - General Error
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)
CUOBJ_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
TECHS_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPEDBFILT_EXPL_MAINTAIN 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, " | |||
| lv_im_expl | TYPE FILT_EXPL, " | |||
| lt_t_filt_eff | TYPE STANDARD TABLE OF TFILT_EFF, " | |||
| lv_ex_expl_guid | TYPE PVS_GUID, " | |||
| lv_not_found | TYPE PVS_GUID, " | |||
| lv_ex_expl_cuobj | TYPE PPE_CUOBJ, " | |||
| lv_im_commit_flg | TYPE XFELD, " | |||
| lt_t_cuobj_values | TYPE STANDARD TABLE OF PPE_API_VALI, " | |||
| lv_cuobj_error | TYPE PPE_API_VALI, " | |||
| lv_im_create_if_not_exist | TYPE XFELD, " | |||
| lv_techs_error | TYPE XFELD, " | |||
| lv_im_cuobj_temp | TYPE XFELD, " 'X' | |||
| lv_im_indx_id | TYPE PPE_INDX_ID. " |
|   CALL FUNCTION 'PPEDBFILT_EXPL_MAINTAIN' "NOTRANSL: ändert/anlegen Auflösungsparameter des Filters |
| EXPORTING | ||
| IM_EXPL | = lv_im_expl | |
| IM_COMMIT_FLG | = lv_im_commit_flg | |
| IM_CREATE_IF_NOT_EXIST | = lv_im_create_if_not_exist | |
| IM_CUOBJ_TEMP | = lv_im_cuobj_temp | |
| IM_INDX_ID | = lv_im_indx_id | |
| IMPORTING | ||
| EX_EXPL_GUID | = lv_ex_expl_guid | |
| EX_EXPL_CUOBJ | = lv_ex_expl_cuobj | |
| TABLES | ||
| T_FILT_EFF | = lt_t_filt_eff | |
| T_CUOBJ_VALUES | = lt_t_cuobj_values | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| NOT_FOUND = 2 | ||
| CUOBJ_ERROR = 3 | ||
| TECHS_ERROR = 4 | ||
| . " PPEDBFILT_EXPL_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM PPEDBFILT_EXPL_MAINTAIN
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_im_cuobj_temp) | = 'X'. | |||
Search for further information about these or an SAP related objects