SAP BBP_PD_INV_UPDATE Function Module for









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

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



Function BBP_PD_INV_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 'BBP_PD_INV_UPDATE'"
  EXPORTING
*  I_PARK =  "
*  I_SAVE =  "
*  IV_REJECT =  "
   I_HEADER =  "
*  IT_ATTACH =  "
*  IV_MSG_SCENARIO =  "

 IMPORTING
   E_CHANGED =  "

TABLES
*  I_ITEM =  "
*  IT_EXCHRATE =  "
*  I_HCF =  "
*  I_ICF =  "
*  E_MESSAGES =  "
*  I_ACCOUNT =  "
*  I_PARTNER =  "
*  I_LONGTEXT =  "
*  I_FREIGHT =  "
*  I_MSGI =  "
*  I_ORGDATA =  "
*  I_TAX =  "
*  IT_HUB_IREL =  "
.



IMPORTING Parameters details for BBP_PD_INV_UPDATE

I_PARK -

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

I_SAVE -

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

IV_REJECT -

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

I_HEADER -

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

IT_ATTACH -

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

IV_MSG_SCENARIO -

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

EXPORTING Parameters details for BBP_PD_INV_UPDATE

E_CHANGED -

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

TABLES Parameters details for BBP_PD_INV_UPDATE

I_ITEM -

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

IT_EXCHRATE -

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

I_HCF -

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

I_ICF -

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

E_MESSAGES -

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

I_ACCOUNT -

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

I_PARTNER -

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

I_LONGTEXT -

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

I_FREIGHT -

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

I_MSGI -

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

I_ORGDATA -

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

I_TAX -

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

IT_HUB_IREL -

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

Copy and paste ABAP code example for BBP_PD_INV_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_i_item  TYPE STANDARD TABLE OF BBP_PDS_INV_ITEM_ICU, "   
lv_i_park  TYPE XFELD, "   
lv_e_changed  TYPE XFELD, "   
lt_it_exchrate  TYPE STANDARD TABLE OF BBP_PDS_EXR, "   
lt_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_INV, "   
lt_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_INV, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_save  TYPE XFELD, "   
lt_i_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lv_iv_reject  TYPE XFELD, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_i_header  TYPE BBP_PDS_INV_HEADER_U, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_i_freight  TYPE STANDARD TABLE OF BBP_PDS_FREIGHT, "   
lt_i_msgi  TYPE STANDARD TABLE OF BBP_PDS_MSGI, "   
lv_iv_msg_scenario  TYPE BBP_MSG_SCENARIO, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lt_i_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX, "   
lt_it_hub_irel  TYPE STANDARD TABLE OF BBP_IV_ITEM_REL. "   

  CALL FUNCTION 'BBP_PD_INV_UPDATE'  "
    EXPORTING
         I_PARK = lv_i_park
         I_SAVE = lv_i_save
         IV_REJECT = lv_iv_reject
         I_HEADER = lv_i_header
         IT_ATTACH = lv_it_attach
         IV_MSG_SCENARIO = lv_iv_msg_scenario
    IMPORTING
         E_CHANGED = lv_e_changed
    TABLES
         I_ITEM = lt_i_item
         IT_EXCHRATE = lt_it_exchrate
         I_HCF = lt_i_hcf
         I_ICF = lt_i_icf
         E_MESSAGES = lt_e_messages
         I_ACCOUNT = lt_i_account
         I_PARTNER = lt_i_partner
         I_LONGTEXT = lt_i_longtext
         I_FREIGHT = lt_i_freight
         I_MSGI = lt_i_msgi
         I_ORGDATA = lt_i_orgdata
         I_TAX = lt_i_tax
         IT_HUB_IREL = lt_it_hub_irel
. " BBP_PD_INV_UPDATE




ABAP code using 7.40 inline data declarations to call FM BBP_PD_INV_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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!