SAP BBP_PD_BID_UPDATE Function Module for









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

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



Function BBP_PD_BID_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_BID_UPDATE'"
  EXPORTING
*  I_PARK =  "X: Daten sichern mit Status 'geparkt'
*  I_SAVE =  "X: Vorgang 'bid_finish'/'confirm'/'post'/'quot_submit'/'order' setzen
   I_HEADER =  "Schnittstelle Kopf-Daten Beschaffungs-Beleg
*  IT_ATTACH =  "KW-Anlagen inkl. Dokument
*  IT_DYN_ATTR =  "Dynamische Attribute
*  IT_CONDITIONS =  "Tabellentyp Stammkonditionen
*  IV_WITH_CHANGE_APPROVAL = 'X' "Checkbox

 IMPORTING
   E_CHANGED =  "X: Daten wurden verändert
   ES_HEADER =  "Schnittstelle Kopf-Daten Ausscheibung GetDetail-Fall.

TABLES
*  I_ITEM =  "Schnittstelle Positions-Daten Beschaffungs-Beleg
*  IT_EXCHRATE =  "
*  I_PARTNER =  "Geschäftspartner-Set
*  I_LONGTEXT =  "Langtexte zum Procurement Document
*  I_SDLN =  "Geschäftsvorgangsposition -Einteilung (Ausgabe an Anwendung)
*  I_ORGDATA =  "Org-Daten
*  I_HCF =  "Tabellenartige Kunden- und Solutionfelder am Kopf
*  I_ICF =  "Tabellenartige Kunden- und Solutionfelder an der Position
*  I_WEIGHT =  "Gewichtung bei Bewertung von Auschreibungen
*  E_MESSAGES =  "Fehlermeldungen zu einer PD-Methode
.



IMPORTING Parameters details for BBP_PD_BID_UPDATE

I_PARK - X: Daten sichern mit Status 'geparkt'

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

I_SAVE - X: Vorgang 'bid_finish'/'confirm'/'post'/'quot_submit'/'order' setzen

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

I_HEADER - Schnittstelle Kopf-Daten Beschaffungs-Beleg

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

IT_ATTACH - KW-Anlagen inkl. Dokument

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

IT_DYN_ATTR - Dynamische Attribute

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

IT_CONDITIONS - Tabellentyp Stammkonditionen

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

IV_WITH_CHANGE_APPROVAL - Checkbox

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

EXPORTING Parameters details for BBP_PD_BID_UPDATE

E_CHANGED - X: Daten wurden verändert

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

ES_HEADER - Schnittstelle Kopf-Daten Ausscheibung GetDetail-Fall.

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

TABLES Parameters details for BBP_PD_BID_UPDATE

I_ITEM - Schnittstelle Positions-Daten Beschaffungs-Beleg

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

IT_EXCHRATE -

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

I_PARTNER - Geschäftspartner-Set

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

I_LONGTEXT - Langtexte zum Procurement Document

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

I_SDLN - Geschäftsvorgangsposition -Einteilung (Ausgabe an Anwendung)

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

I_ORGDATA - Org-Daten

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

I_HCF - Tabellenartige Kunden- und Solutionfelder am Kopf

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

I_ICF - Tabellenartige Kunden- und Solutionfelder an der Position

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

I_WEIGHT - Gewichtung bei Bewertung von Auschreibungen

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

E_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

Copy and paste ABAP code example for BBP_PD_BID_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_BID_ITEM_ICU, "   
lv_i_park  TYPE XFELD, "   
lv_e_changed  TYPE XFELD, "   
lt_it_exchrate  TYPE STANDARD TABLE OF BBP_PDS_EXR, "   
lv_i_save  TYPE XFELD, "   
lv_es_header  TYPE BBP_PDS_BID_HEADER_D, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_i_header  TYPE BBP_PDS_BID_HEADER_U, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_i_sdln  TYPE STANDARD TABLE OF BBP_PDS_SDLN, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lv_it_dyn_attr  TYPE BBPT_PDS_DYNATTRIBUTE, "   
lt_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_BID, "   
lv_it_conditions  TYPE BBPT_PD_CND_ICU, "   
lt_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_BID, "   
lv_iv_with_change_approval  TYPE XFELD, "   'X'
lt_i_weight  TYPE STANDARD TABLE OF BBP_PDS_WEIGHT, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES. "   

  CALL FUNCTION 'BBP_PD_BID_UPDATE'  "
    EXPORTING
         I_PARK = lv_i_park
         I_SAVE = lv_i_save
         I_HEADER = lv_i_header
         IT_ATTACH = lv_it_attach
         IT_DYN_ATTR = lv_it_dyn_attr
         IT_CONDITIONS = lv_it_conditions
         IV_WITH_CHANGE_APPROVAL = lv_iv_with_change_approval
    IMPORTING
         E_CHANGED = lv_e_changed
         ES_HEADER = lv_es_header
    TABLES
         I_ITEM = lt_i_item
         IT_EXCHRATE = lt_it_exchrate
         I_PARTNER = lt_i_partner
         I_LONGTEXT = lt_i_longtext
         I_SDLN = lt_i_sdln
         I_ORGDATA = lt_i_orgdata
         I_HCF = lt_i_hcf
         I_ICF = lt_i_icf
         I_WEIGHT = lt_i_weight
         E_MESSAGES = lt_e_messages
. " BBP_PD_BID_UPDATE




ABAP code using 7.40 inline data declarations to call FM BBP_PD_BID_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_iv_with_change_approval) = 'X'.
 
 
 


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!