SAP PRELIMINARY_POSTING_DOC_WRITE Function Module for Write a parked document
PRELIMINARY_POSTING_DOC_WRITE is a standard preliminary posting doc write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write a parked document 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 posting doc write FM, simply by entering the name PRELIMINARY_POSTING_DOC_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: F042
Program Name: SAPLF042
Main Program: SAPLF042
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1
Function PRELIMINARY_POSTING_DOC_WRITE 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_POSTING_DOC_WRITE'"Write a parked document.
EXPORTING
* I_UF05A = "
* I_BSTAT = "
TABLES
T_VBKPF = "Document headers
T_VBSEC = "One-time account data
T_VBSEG = "Line items
T_VBSET = "
* T_VACSPLT = "Carrier for Split Information re: Current Account Line Items
* T_VSPLTWT = "FI Document Parking (Enjoy): W/Tax Data Amount Split
EXCEPTIONS
ABNORMAL_TERMINATION = 1 INSERT_ERROR = 2 UPDATE_ERROR = 3 READ_ERROR = 4
IMPORTING Parameters details for PRELIMINARY_POSTING_DOC_WRITE
I_UF05A -
Data type: UF05AOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BSTAT -
Data type: BKPF-BSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PRELIMINARY_POSTING_DOC_WRITE
T_VBKPF - Document headers
Data type: FVBKPFOptional: No
Call by Reference: No ( called with pass by value option)
T_VBSEC - One-time account data
Data type: FVBSECOptional: No
Call by Reference: No ( called with pass by value option)
T_VBSEG - Line items
Data type: FVBSEGOptional: No
Call by Reference: No ( called with pass by value option)
T_VBSET -
Data type: FVBSETOptional: No
Call by Reference: No ( called with pass by value option)
T_VACSPLT - Carrier for Split Information re: Current Account Line Items
Data type: FVACSPLTOptional: Yes
Call by Reference: Yes
T_VSPLTWT - FI Document Parking (Enjoy): W/Tax Data Amount Split
Data type: VSPLTWTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ABNORMAL_TERMINATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INSERT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
READ_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PRELIMINARY_POSTING_DOC_WRITE 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_i_uf05a | TYPE UF05A, " | |||
lt_t_vbkpf | TYPE STANDARD TABLE OF FVBKPF, " | |||
lv_abnormal_termination | TYPE FVBKPF, " | |||
lv_i_bstat | TYPE BKPF-BSTAT, " | |||
lt_t_vbsec | TYPE STANDARD TABLE OF FVBSEC, " | |||
lv_insert_error | TYPE FVBSEC, " | |||
lt_t_vbseg | TYPE STANDARD TABLE OF FVBSEG, " | |||
lv_update_error | TYPE FVBSEG, " | |||
lt_t_vbset | TYPE STANDARD TABLE OF FVBSET, " | |||
lv_read_error | TYPE FVBSET, " | |||
lt_t_vacsplt | TYPE STANDARD TABLE OF FVACSPLT, " | |||
lt_t_vspltwt | TYPE STANDARD TABLE OF VSPLTWT. " |
  CALL FUNCTION 'PRELIMINARY_POSTING_DOC_WRITE' "Write a parked document |
EXPORTING | ||
I_UF05A | = lv_i_uf05a | |
I_BSTAT | = lv_i_bstat | |
TABLES | ||
T_VBKPF | = lt_t_vbkpf | |
T_VBSEC | = lt_t_vbsec | |
T_VBSEG | = lt_t_vbseg | |
T_VBSET | = lt_t_vbset | |
T_VACSPLT | = lt_t_vacsplt | |
T_VSPLTWT | = lt_t_vspltwt | |
EXCEPTIONS | ||
ABNORMAL_TERMINATION = 1 | ||
INSERT_ERROR = 2 | ||
UPDATE_ERROR = 3 | ||
READ_ERROR = 4 | ||
. " PRELIMINARY_POSTING_DOC_WRITE |
ABAP code using 7.40 inline data declarations to call FM PRELIMINARY_POSTING_DOC_WRITE
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 BSTAT FROM BKPF INTO @DATA(ld_i_bstat). | ||||
Search for further information about these or an SAP related objects