SAP BUS_OP_SAVE_POST_PREPARE Function Module for Prepare to Post a Business Transaction









BUS_OP_SAVE_POST_PREPARE is a standard bus op save post prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prepare to Post a Business Transaction 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 bus op save post prepare FM, simply by entering the name BUS_OP_SAVE_POST_PREPARE into the relevant SAP transaction such as SE37 or SE38.

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



Function BUS_OP_SAVE_POST_PREPARE 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 'BUS_OP_SAVE_POST_PREPARE'"Prepare to Post a Business Transaction
  EXPORTING
   I_ACTION =  "
   IT_VDBOHEAD =  "
   IS_VDARL =  "

CHANGING
   CT_VDBOBEPP_NEW =  "
*  CT_PAYMENT_KEY =  "Table Type for VDAUSZ_KEY

TABLES
   CT_IVDBEPP =  "
   IT_ZITIBEPP =  "
   CT_VDBEPP_NEW =  "
*  IT_VDBEPP_OLD =  "Transaction Data - Plan Item

EXCEPTIONS
   POSTING_IMPOSSIBLE = 1    ACTIVATE_IMPOSSIBLE = 2
.



IMPORTING Parameters details for BUS_OP_SAVE_POST_PREPARE

I_ACTION -

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

IT_VDBOHEAD -

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

IS_VDARL -

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

CHANGING Parameters details for BUS_OP_SAVE_POST_PREPARE

CT_VDBOBEPP_NEW -

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

CT_PAYMENT_KEY - Table Type for VDAUSZ_KEY

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

TABLES Parameters details for BUS_OP_SAVE_POST_PREPARE

CT_IVDBEPP -

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

IT_ZITIBEPP -

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

CT_VDBEPP_NEW -

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

IT_VDBEPP_OLD - Transaction Data - Plan Item

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

EXCEPTIONS details

POSTING_IMPOSSIBLE -

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

ACTIVATE_IMPOSSIBLE -

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

Copy and paste ABAP code example for BUS_OP_SAVE_POST_PREPARE 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_action  TYPE STRING, "   
lt_ct_ivdbepp  TYPE STANDARD TABLE OF VDBEPP, "   
lv_ct_vdbobepp_new  TYPE TRTY_VDBOBEPP, "   
lv_posting_impossible  TYPE TRTY_VDBOBEPP, "   
lv_it_vdbohead  TYPE TRTY_SCR_VDBOHEAD, "   
lt_it_zitibepp  TYPE STANDARD TABLE OF VZZBEPP, "   
lv_ct_payment_key  TYPE TRTY_VDAUSZ_KEY, "   
lv_activate_impossible  TYPE TRTY_VDAUSZ_KEY, "   
lv_is_vdarl  TYPE VDARL, "   
lt_ct_vdbepp_new  TYPE STANDARD TABLE OF VDBEPP, "   
lt_it_vdbepp_old  TYPE STANDARD TABLE OF VDBEPP. "   

  CALL FUNCTION 'BUS_OP_SAVE_POST_PREPARE'  "Prepare to Post a Business Transaction
    EXPORTING
         I_ACTION = lv_i_action
         IT_VDBOHEAD = lv_it_vdbohead
         IS_VDARL = lv_is_vdarl
    CHANGING
         CT_VDBOBEPP_NEW = lv_ct_vdbobepp_new
         CT_PAYMENT_KEY = lv_ct_payment_key
    TABLES
         CT_IVDBEPP = lt_ct_ivdbepp
         IT_ZITIBEPP = lt_it_zitibepp
         CT_VDBEPP_NEW = lt_ct_vdbepp_new
         IT_VDBEPP_OLD = lt_it_vdbepp_old
    EXCEPTIONS
        POSTING_IMPOSSIBLE = 1
        ACTIVATE_IMPOSSIBLE = 2
. " BUS_OP_SAVE_POST_PREPARE




ABAP code using 7.40 inline data declarations to call FM BUS_OP_SAVE_POST_PREPARE

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.

 
 
 
 
 
 
 
 
 
 
 


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!