SAP KBPV_POST_DATA Function Module for Call update budgeting/planning









KBPV_POST_DATA is a standard kbpv post data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call update budgeting/planning 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 kbpv post data FM, simply by entering the name KBPV_POST_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: KBPV
Program Name: SAPLKBPV
Main Program: SAPLKBPV
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function KBPV_POST_DATA 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 'KBPV_POST_DATA'"Call update budgeting/planning
EXPORTING
* DELTA_UPDATE = 'X' "Delta values are transferred
* DIALOG_UPDATE = ' ' "Update online
* BUFFER_UPDATE = ' ' "
* MODIFY_INSERT = ' ' "
* IM_BELNR = ' ' "
* IM_BPBK = ' ' "
IM_BPIN = "

IMPORTING
EX_BELNR = "
EX_BPBK = "

TABLES
* TAB_BPCH = "
* TAB_BPGE = "
* TAB_BPHI = "
* TAB_BPIG = "
* TAB_BPIJ = "
* TAB_BPJA = "
* TAB_BPPE = "
* TAB_BPTR = "
.




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_SAPLKBPV_003 User Exit for Budget Document Posting Time

IMPORTING Parameters details for KBPV_POST_DATA

DELTA_UPDATE - Delta values are transferred

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

DIALOG_UPDATE - Update online

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

BUFFER_UPDATE -

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

MODIFY_INSERT -

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

IM_BELNR -

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

IM_BPBK -

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

IM_BPIN -

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

EXPORTING Parameters details for KBPV_POST_DATA

EX_BELNR -

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

EX_BPBK -

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

TABLES Parameters details for KBPV_POST_DATA

TAB_BPCH -

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

TAB_BPGE -

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

TAB_BPHI -

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

TAB_BPIG -

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

TAB_BPIJ -

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

TAB_BPJA -

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

TAB_BPPE -

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

TAB_BPTR -

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

Copy and paste ABAP code example for KBPV_POST_DATA 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_ex_belnr  TYPE BPBK-BELNR, "   
lt_tab_bpch  TYPE STANDARD TABLE OF BPBK, "   
lv_delta_update  TYPE BPBK, "   'X'
lv_ex_bpbk  TYPE BPBK, "   
lt_tab_bpge  TYPE STANDARD TABLE OF BPBK, "   
lv_dialog_update  TYPE BPBK, "   SPACE
lt_tab_bphi  TYPE STANDARD TABLE OF BPBK, "   
lv_buffer_update  TYPE BPBK, "   SPACE
lt_tab_bpig  TYPE STANDARD TABLE OF BPBK, "   
lv_modify_insert  TYPE BPBK, "   SPACE
lv_im_belnr  TYPE BPBK-BELNR, "   SPACE
lt_tab_bpij  TYPE STANDARD TABLE OF BPBK, "   
lv_im_bpbk  TYPE BPBK, "   SPACE
lt_tab_bpja  TYPE STANDARD TABLE OF BPBK, "   
lv_im_bpin  TYPE BPIN, "   
lt_tab_bppe  TYPE STANDARD TABLE OF BPIN, "   
lt_tab_bptr  TYPE STANDARD TABLE OF BPIN. "   

  CALL FUNCTION 'KBPV_POST_DATA'  "Call update budgeting/planning
    EXPORTING
         DELTA_UPDATE = lv_delta_update
         DIALOG_UPDATE = lv_dialog_update
         BUFFER_UPDATE = lv_buffer_update
         MODIFY_INSERT = lv_modify_insert
         IM_BELNR = lv_im_belnr
         IM_BPBK = lv_im_bpbk
         IM_BPIN = lv_im_bpin
    IMPORTING
         EX_BELNR = lv_ex_belnr
         EX_BPBK = lv_ex_bpbk
    TABLES
         TAB_BPCH = lt_tab_bpch
         TAB_BPGE = lt_tab_bpge
         TAB_BPHI = lt_tab_bphi
         TAB_BPIG = lt_tab_bpig
         TAB_BPIJ = lt_tab_bpij
         TAB_BPJA = lt_tab_bpja
         TAB_BPPE = lt_tab_bppe
         TAB_BPTR = lt_tab_bptr
. " KBPV_POST_DATA




ABAP code using 7.40 inline data declarations to call FM KBPV_POST_DATA

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 BELNR FROM BPBK INTO @DATA(ld_ex_belnr).
 
 
DATA(ld_delta_update) = 'X'.
 
 
 
DATA(ld_dialog_update) = ' '.
 
 
DATA(ld_buffer_update) = ' '.
 
 
DATA(ld_modify_insert) = ' '.
 
"SELECT single BELNR FROM BPBK INTO @DATA(ld_im_belnr).
DATA(ld_im_belnr) = ' '.
 
 
DATA(ld_im_bpbk) = ' '.
 
 
 
 
 


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!