SAP PRELIMINARY_DATA_DELETE Function Module for Release Procedure - Delete Posting Transaction from Central Entry Table
PRELIMINARY_DATA_DELETE is a standard preliminary data 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 Release Procedure - Delete Posting Transaction from Central Entry Table 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 preliminary data delete FM, simply by entering the name PRELIMINARY_DATA_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZM
Program Name: SAPLFVZM
Main Program: SAPLFVZM
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRELIMINARY_DATA_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 'PRELIMINARY_DATA_DELETE'"Release Procedure - Delete Posting Transaction from Central Entry Table.
EXPORTING
* BUKRS = ' ' "Company Code
* KEY = ' ' "Key zum Identifizieren der Freigabedatensätze
* SBUAKT = 0 "Buchungsanwendung (Auszahlung, Umbuchung, ..)
* SOBJEKT = ' ' "Internal Key for Object
* SVORGANG = 0 "Vorgangsnummer aus Schwebedatentabelle VZFZE
* UPDATE_TASK = 'X' "Verbuchung in Update Task: TRUE (='X') und FALSE (=' ')
IMPORTING
SFGBEW = "Kennzeichen Schwebedaten vorhanden
EXCEPTIONS
DEL_FAILED = 1 ERROR = 2 NOT_FOUND = 3
IMPORTING Parameters details for PRELIMINARY_DATA_DELETE
BUKRS - Company Code
Data type: T001-BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
KEY - Key zum Identifizieren der Freigabedatensätze
Data type: VZFGD-SKEY1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SBUAKT - Buchungsanwendung (Auszahlung, Umbuchung, ..)
Data type: VZFZE-SBUAKTOptional: Yes
Call by Reference: No ( called with pass by value option)
SOBJEKT - Internal Key for Object
Data type: VZFZE-SOBJEKTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SVORGANG - Vorgangsnummer aus Schwebedatentabelle VZFZE
Data type: VZFZE-SVORGANGOptional: Yes
Call by Reference: No ( called with pass by value option)
UPDATE_TASK - Verbuchung in Update Task: TRUE (='X') und FALSE (=' ')
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PRELIMINARY_DATA_DELETE
SFGBEW - Kennzeichen Schwebedaten vorhanden
Data type: VDARL-SFGBEWOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DEL_FAILED - Delete Incorrect
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR - mehr als ein Vorgang selektiert
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - keinen passenden Satz in VZFZE gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PRELIMINARY_DATA_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_bukrs | TYPE T001-BUKRS, " SPACE | |||
| lv_sfgbew | TYPE VDARL-SFGBEW, " | |||
| lv_del_failed | TYPE VDARL, " | |||
| lv_key | TYPE VZFGD-SKEY1, " SPACE | |||
| lv_error | TYPE VZFGD, " | |||
| lv_sbuakt | TYPE VZFZE-SBUAKT, " 0 | |||
| lv_not_found | TYPE VZFZE, " | |||
| lv_sobjekt | TYPE VZFZE-SOBJEKT, " SPACE | |||
| lv_svorgang | TYPE VZFZE-SVORGANG, " 0 | |||
| lv_update_task | TYPE BOOLE-BOOLE. " 'X' |
|   CALL FUNCTION 'PRELIMINARY_DATA_DELETE' "Release Procedure - Delete Posting Transaction from Central Entry Table |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| KEY | = lv_key | |
| SBUAKT | = lv_sbuakt | |
| SOBJEKT | = lv_sobjekt | |
| SVORGANG | = lv_svorgang | |
| UPDATE_TASK | = lv_update_task | |
| IMPORTING | ||
| SFGBEW | = lv_sfgbew | |
| EXCEPTIONS | ||
| DEL_FAILED = 1 | ||
| ERROR = 2 | ||
| NOT_FOUND = 3 | ||
| . " PRELIMINARY_DATA_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM PRELIMINARY_DATA_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 BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| DATA(ld_bukrs) | = ' '. | |||
| "SELECT single SFGBEW FROM VDARL INTO @DATA(ld_sfgbew). | ||||
| "SELECT single SKEY1 FROM VZFGD INTO @DATA(ld_key). | ||||
| DATA(ld_key) | = ' '. | |||
| "SELECT single SBUAKT FROM VZFZE INTO @DATA(ld_sbuakt). | ||||
| "SELECT single SOBJEKT FROM VZFZE INTO @DATA(ld_sobjekt). | ||||
| DATA(ld_sobjekt) | = ' '. | |||
| "SELECT single SVORGANG FROM VZFZE INTO @DATA(ld_svorgang). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_update_task). | ||||
| DATA(ld_update_task) | = 'X'. | |||
Search for further information about these or an SAP related objects