SAP KBPP_EXTERN_UPDATE Function Module for









KBPP_EXTERN_UPDATE is a standard kbpp extern update 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 kbpp extern update FM, simply by entering the name KBPP_EXTERN_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function KBPP_EXTERN_UPDATE 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 'KBPP_EXTERN_UPDATE'"
  EXPORTING
*  IMP_CARRY_OVER = ' ' "Changing of fiscal year
*  IMP_CHECK = ' ' "'X' check without posting
*  IMP_COMMIT = ' ' "COMMIT WORK after each IMP_BPAK line
*  IMP_FCODE = ' ' "
*  IMP_SUPRESS_AVA_CHECK = ' ' "
*  IMP_TCODE = ' ' "Transaction code
*  IMP_UNAME = ' ' "

TABLES
   IMP_BPAK =  "Transfer structure of values
*  IMP_BPAK_PER =  "
*  RETURN =  "Return Parameter(s)
.



IMPORTING Parameters details for KBPP_EXTERN_UPDATE

IMP_CARRY_OVER - Changing of fiscal year

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

IMP_CHECK - 'X' check without posting

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

IMP_COMMIT - COMMIT WORK after each IMP_BPAK line

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

IMP_FCODE -

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

IMP_SUPRESS_AVA_CHECK -

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

IMP_TCODE - Transaction code

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

IMP_UNAME -

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

TABLES Parameters details for KBPP_EXTERN_UPDATE

IMP_BPAK - Transfer structure of values

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

IMP_BPAK_PER -

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

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for KBPP_EXTERN_UPDATE 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:
lt_imp_bpak  TYPE STANDARD TABLE OF BPAK, "   
lv_imp_carry_over  TYPE BPAK, "   SPACE
lv_imp_check  TYPE BPAK, "   SPACE
lt_imp_bpak_per  TYPE STANDARD TABLE OF BPBU_T_BPAK_PER, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_imp_commit  TYPE BAPIRET2, "   SPACE
lv_imp_fcode  TYPE BAPIRET2, "   SPACE
lv_imp_supress_ava_check  TYPE BAPIRET2, "   SPACE
lv_imp_tcode  TYPE BAPIRET2, "   SPACE
lv_imp_uname  TYPE BAPIRET2. "   SPACE

  CALL FUNCTION 'KBPP_EXTERN_UPDATE'  "
    EXPORTING
         IMP_CARRY_OVER = lv_imp_carry_over
         IMP_CHECK = lv_imp_check
         IMP_COMMIT = lv_imp_commit
         IMP_FCODE = lv_imp_fcode
         IMP_SUPRESS_AVA_CHECK = lv_imp_supress_ava_check
         IMP_TCODE = lv_imp_tcode
         IMP_UNAME = lv_imp_uname
    TABLES
         IMP_BPAK = lt_imp_bpak
         IMP_BPAK_PER = lt_imp_bpak_per
         RETURN = lt_return
. " KBPP_EXTERN_UPDATE




ABAP code using 7.40 inline data declarations to call FM KBPP_EXTERN_UPDATE

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.

 
DATA(ld_imp_carry_over) = ' '.
 
DATA(ld_imp_check) = ' '.
 
 
 
DATA(ld_imp_commit) = ' '.
 
DATA(ld_imp_fcode) = ' '.
 
DATA(ld_imp_supress_ava_check) = ' '.
 
DATA(ld_imp_tcode) = ' '.
 
DATA(ld_imp_uname) = ' '.
 


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!