SAP POINTER_PROCESSED_DELETE Function Module for Delete processed change pointers
POINTER_PROCESSED_DELETE is a standard pointer processed delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete processed change pointers 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 pointer processed delete FM, simply by entering the name POINTER_PROCESSED_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRE_MD_SOS_OUT
Program Name: SAPLFRE_MD_SOS_OUT
Main Program: SAPLFRE_MD_SOS_OUT
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function POINTER_PROCESSED_DELETE 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 'POINTER_PROCESSED_DELETE'"Delete processed change pointers.
EXPORTING
* PI_TEST = "
I_MESSAGE_TYPE = "Message type
I_CREATION_DATE_HIGH = "Date and time, current (application server) date
I_CREATION_TIME_HIGH = "Dat and time, current application server time
I_CREATION_DATE_LOW = "Date and time, current (application server) date
I_CREATION_TIME_LOW = "Dat and time, current application server time
* PI_COMMIT_COUNT = "Number of deleted data records for Commit
* PI_WRITE_LIST = 'X' "New input values
IMPORTING
PE_DELETET_BDCP = "
PE_DELETET_BDCPS = "
IMPORTING Parameters details for POINTER_PROCESSED_DELETE
PI_TEST -
Data type: EDIDOC1-SYNTAXOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MESSAGE_TYPE - Message type
Data type: TBDME-MESTYPOptional: No
Call by Reference: Yes
I_CREATION_DATE_HIGH - Date and time, current (application server) date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_CREATION_TIME_HIGH - Dat and time, current application server time
Data type: SY-UZEITOptional: No
Call by Reference: Yes
I_CREATION_DATE_LOW - Date and time, current (application server) date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_CREATION_TIME_LOW - Dat and time, current application server time
Data type: SY-UZEITOptional: No
Call by Reference: Yes
PI_COMMIT_COUNT - Number of deleted data records for Commit
Data type: SY-TABIXOptional: Yes
Call by Reference: Yes
PI_WRITE_LIST - New input values
Data type: XFLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for POINTER_PROCESSED_DELETE
PE_DELETET_BDCP -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
PE_DELETET_BDCPS -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for POINTER_PROCESSED_DELETE 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_pi_test | TYPE EDIDOC1-SYNTAX, " | |||
| lv_pe_deletet_bdcp | TYPE SY-TABIX, " | |||
| lv_i_message_type | TYPE TBDME-MESTYP, " | |||
| lv_pe_deletet_bdcps | TYPE SY-TABIX, " | |||
| lv_i_creation_date_high | TYPE SY-DATUM, " | |||
| lv_i_creation_time_high | TYPE SY-UZEIT, " | |||
| lv_i_creation_date_low | TYPE SY-DATUM, " | |||
| lv_i_creation_time_low | TYPE SY-UZEIT, " | |||
| lv_pi_commit_count | TYPE SY-TABIX, " | |||
| lv_pi_write_list | TYPE XFLAG. " 'X' |
| CALL FUNCTION 'POINTER_PROCESSED_DELETE' "Delete processed change pointers |
| EXPORTING | ||
| PI_TEST | = lv_pi_test | |
| I_MESSAGE_TYPE | = lv_i_message_type | |
| I_CREATION_DATE_HIGH | = lv_i_creation_date_high | |
| I_CREATION_TIME_HIGH | = lv_i_creation_time_high | |
| I_CREATION_DATE_LOW | = lv_i_creation_date_low | |
| I_CREATION_TIME_LOW | = lv_i_creation_time_low | |
| PI_COMMIT_COUNT | = lv_pi_commit_count | |
| PI_WRITE_LIST | = lv_pi_write_list | |
| IMPORTING | ||
| PE_DELETET_BDCP | = lv_pe_deletet_bdcp | |
| PE_DELETET_BDCPS | = lv_pe_deletet_bdcps | |
| . " POINTER_PROCESSED_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM POINTER_PROCESSED_DELETE
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.| "SELECT single SYNTAX FROM EDIDOC1 INTO @DATA(ld_pi_test). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_pe_deletet_bdcp). | ||||
| "SELECT single MESTYP FROM TBDME INTO @DATA(ld_i_message_type). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_pe_deletet_bdcps). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_creation_date_high). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_i_creation_time_high). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_creation_date_low). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_i_creation_time_low). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_pi_commit_count). | ||||
| DATA(ld_pi_write_list) | = 'X'. | |||
Search for further information about these or an SAP related objects