SAP BBP_UPDATE_CONTRACT_FROM_BID Function Module for Create Contract from RFx Response

Search SAP Function Modules

BBP_UPDATE_CONTRACT_FROM_BID is a standard bbp update contract from bid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Contract from RFx Response 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 bbp update contract from bid FM, simply by entering the name BBP_UPDATE_CONTRACT_FROM_BID into the relevant SAP transaction such as SE37 or SE38.

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

Function BBP_UPDATE_CONTRACT_FROM_BID 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_UPDATE_CONTRACT_FROM_BID'"Create Contract from RFx Response
  EXPORTING
   IV_GUID =  "Globally Unique Identifier
   IS_GLOBAL =  "Globaldaten Ausschreibung/Angebot

 IMPORTING
   EV_CTR_OBJECT_ID =  "Vorgangsnummer
   EV_CTR_GUID =  "Globally Unique Identifier
   ET_MESSAGES =  "Tabellentyp für Fehlermeldungen
   EV_CONTRACT_UPDATED =  "Feld zum Ankreuzen

EXCEPTIONS
   CONTRACT_UPDATE_FAILED = 1 

.

IMPORTING Parameters details for BBP_UPDATE_CONTRACT_FROM_BID

IV_GUID - Globally Unique Identifier

Data type: BBP_GUID
Optional: No
Call by Reference: Yes

IS_GLOBAL - Globaldaten Ausschreibung/Angebot

Data type: BBPS_BID_UI_GLOBAL
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for BBP_UPDATE_CONTRACT_FROM_BID

EV_CTR_OBJECT_ID - Vorgangsnummer

Data type: CRMT_OBJECT_ID_DB
Optional: No
Call by Reference: Yes

EV_CTR_GUID - Globally Unique Identifier

Data type: BBP_GUID
Optional: No
Call by Reference: Yes

ET_MESSAGES - Tabellentyp für Fehlermeldungen

Data type: BBPT_MESSAGES
Optional: No
Call by Reference: Yes

EV_CONTRACT_UPDATED - Feld zum Ankreuzen

Data type: XFELD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CONTRACT_UPDATE_FAILED - Kontrakt konnte nicht aktualisiert werden

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_UPDATE_CONTRACT_FROM_BID 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.

ABAP code using 7.40 inline data declarations to call FM BBP_UPDATE_CONTRACT_FROM_BID

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