SAP PRELIMINARY_POSTING_POST_ALL Function Module for









PRELIMINARY_POSTING_POST_ALL is a standard preliminary posting post all SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 post all FM, simply by entering the name PRELIMINARY_POSTING_POST_ALL into the relevant SAP transaction such as SE37 or SE38.

Function Group: F040
Program Name: SAPLF040
Main Program: SAPLF040
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PRELIMINARY_POSTING_POST_ALL 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_POST_ALL'"
EXPORTING
* BUPBI = ' ' "Generate batch input
* NOMSG = ' ' "
* SYNCH = ' ' "
* NOCHECK = ' ' "
* APPL_LOG = ' ' "

IMPORTING
E_LOG_HANDLE = "Application Log: Log Handle
ES_DISPLAY_PROFILE = "Application Log: Log Output Format Profile

TABLES
T_VBKPF = "Table with documents to be posted
* T_MSG = "
* T_MSG_TAB = "Line Structure for Table of Errors from FBVB
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLF040_001 WF: Amount Release by Person with Release Authorization
EXIT_SAPLF040_002 WF: Account Assignment Approval by Person with Release Authorization
EXIT_SAPLF040_003 WF: Operater after Refusal of Release
EXIT_SAPLF040_004 User Exit: Payment Release by Person with Release Authorization

IMPORTING Parameters details for PRELIMINARY_POSTING_POST_ALL

BUPBI - Generate batch input

Data type: VBSEG-XSKRL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOMSG -

Data type: VBSEG-XSKRL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SYNCH -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOCHECK -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPL_LOG -

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

EXPORTING Parameters details for PRELIMINARY_POSTING_POST_ALL

E_LOG_HANDLE - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: No
Call by Reference: Yes

ES_DISPLAY_PROFILE - Application Log: Log Output Format Profile

Data type: BAL_S_PROF
Optional: No
Call by Reference: Yes

TABLES Parameters details for PRELIMINARY_POSTING_POST_ALL

T_VBKPF - Table with documents to be posted

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

T_MSG -

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

T_MSG_TAB - Line Structure for Table of Errors from FBVB

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

Copy and paste ABAP code example for PRELIMINARY_POSTING_POST_ALL 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_bupbi  TYPE VBSEG-XSKRL, "   SPACE
lt_t_vbkpf  TYPE STANDARD TABLE OF VBKPF, "   
lv_e_log_handle  TYPE BALLOGHNDL, "   
lv_nomsg  TYPE VBSEG-XSKRL, "   SPACE
lt_t_msg  TYPE STANDARD TABLE OF FIMSG1, "   
lv_es_display_profile  TYPE BAL_S_PROF, "   
lv_synch  TYPE BOOLE-BOOLE, "   SPACE
lt_t_msg_tab  TYPE STANDARD TABLE OF MSG_TAB_LINE, "   
lv_nocheck  TYPE BOOLE-BOOLE, "   SPACE
lv_appl_log  TYPE XFELD. "   SPACE

  CALL FUNCTION 'PRELIMINARY_POSTING_POST_ALL'  "
    EXPORTING
         BUPBI = lv_bupbi
         NOMSG = lv_nomsg
         SYNCH = lv_synch
         NOCHECK = lv_nocheck
         APPL_LOG = lv_appl_log
    IMPORTING
         E_LOG_HANDLE = lv_e_log_handle
         ES_DISPLAY_PROFILE = lv_es_display_profile
    TABLES
         T_VBKPF = lt_t_vbkpf
         T_MSG = lt_t_msg
         T_MSG_TAB = lt_t_msg_tab
. " PRELIMINARY_POSTING_POST_ALL




ABAP code using 7.40 inline data declarations to call FM PRELIMINARY_POSTING_POST_ALL

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 XSKRL FROM VBSEG INTO @DATA(ld_bupbi).
DATA(ld_bupbi) = ' '.
 
 
 
"SELECT single XSKRL FROM VBSEG INTO @DATA(ld_nomsg).
DATA(ld_nomsg) = ' '.
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_synch).
DATA(ld_synch) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_nocheck).
DATA(ld_nocheck) = ' '.
 
DATA(ld_appl_log) = ' '.
 


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!