SAP BBP_PD_SUSINV_UPDATE Function Module for









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

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



Function BBP_PD_SUSINV_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_SUSINV_UPDATE'"
  EXPORTING
*  IV_PARK =  "
*  IV_SAVE =  "
*  IV_REJECT =  "
   IS_HEADER =  "
*  IT_ATTACH =  "
*  IV_MSG_SCENARIO =  "

 IMPORTING
   EV_CHANGED =  "

TABLES
*  IT_ITEM =  "
*  IT_PARTNER =  "
*  IT_LONGTEXT =  "
*  IT_FREIGHT =  "
*  IT_TAX =  "
*  IT_HCF =  "
*  IT_ICF =  "
*  ET_MESSAGES =  "
.



IMPORTING Parameters details for BBP_PD_SUSINV_UPDATE

IV_PARK -

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

IV_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)

IS_HEADER -

Data type: BBP_PDS_SUSINV_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_SUSINV_UPDATE

EV_CHANGED -

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

TABLES Parameters details for BBP_PD_SUSINV_UPDATE

IT_ITEM -

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

IT_PARTNER -

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

IT_LONGTEXT -

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

IT_FREIGHT -

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

IT_TAX -

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

IT_HCF -

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

IT_ICF -

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

ET_MESSAGES -

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

Copy and paste ABAP code example for BBP_PD_SUSINV_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_it_item  TYPE STANDARD TABLE OF BBP_PDS_SUSINV_ITEM_ICU, "   
lv_iv_park  TYPE XFELD, "   
lv_ev_changed  TYPE XFELD, "   
lv_iv_save  TYPE XFELD, "   
lt_it_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_iv_reject  TYPE XFELD, "   
lt_it_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lv_is_header  TYPE BBP_PDS_SUSINV_HEADER_U, "   
lt_it_freight  TYPE STANDARD TABLE OF BBP_PDS_FREIGHT, "   
lt_it_tax  TYPE STANDARD TABLE OF BBP_PDS_TAX, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_it_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_SUSINV, "   
lv_iv_msg_scenario  TYPE BBP_MSG_SCENARIO, "   
lt_it_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_SUSINV, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES. "   

  CALL FUNCTION 'BBP_PD_SUSINV_UPDATE'  "
    EXPORTING
         IV_PARK = lv_iv_park
         IV_SAVE = lv_iv_save
         IV_REJECT = lv_iv_reject
         IS_HEADER = lv_is_header
         IT_ATTACH = lv_it_attach
         IV_MSG_SCENARIO = lv_iv_msg_scenario
    IMPORTING
         EV_CHANGED = lv_ev_changed
    TABLES
         IT_ITEM = lt_it_item
         IT_PARTNER = lt_it_partner
         IT_LONGTEXT = lt_it_longtext
         IT_FREIGHT = lt_it_freight
         IT_TAX = lt_it_tax
         IT_HCF = lt_it_hcf
         IT_ICF = lt_it_icf
         ET_MESSAGES = lt_et_messages
. " BBP_PD_SUSINV_UPDATE




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