SAP BBP_BID_UI_GETDEFAULT Function Module for RFx Determination of Default Values









BBP_BID_UI_GETDEFAULT is a standard bbp bid ui getdefault SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFx Determination of Default Values 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 bid ui getdefault FM, simply by entering the name BBP_BID_UI_GETDEFAULT 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_BID_UI_GETDEFAULT 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_BID_UI_GETDEFAULT'"RFx Determination of Default Values
EXPORTING
IV_USER = "R/3-System, Anmeldename des Benutzers
* IV_OBJECT_TYPE = "BBP-BOR-Objekttyp für Item und Header

IMPORTING
ES_DEFAULT = "Ausschreibung Vorschlagswerte
ES_SEARCH_VALUES = "Suchkriterien in Bidding Engine
ET_MESSAGES = "Tabellentyp für Fehlermeldungen
.



IMPORTING Parameters details for BBP_BID_UI_GETDEFAULT

IV_USER - R/3-System, Anmeldename des Benutzers

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

IV_OBJECT_TYPE - BBP-BOR-Objekttyp für Item und Header

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

EXPORTING Parameters details for BBP_BID_UI_GETDEFAULT

ES_DEFAULT - Ausschreibung Vorschlagswerte

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

ES_SEARCH_VALUES - Suchkriterien in Bidding Engine

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

ET_MESSAGES - Tabellentyp für Fehlermeldungen

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

Copy and paste ABAP code example for BBP_BID_UI_GETDEFAULT 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:
lv_iv_user  TYPE SYUNAME, "   
lv_es_default  TYPE BBPS_BID_UI_DEFAULT, "   
lv_iv_object_type  TYPE BBP_OBJECT_TYPE, "   
lv_es_search_values  TYPE BBPS_BID_QUOT_SEARCH_CRITERIA, "   
lv_et_messages  TYPE BBPT_MESSAGES. "   

  CALL FUNCTION 'BBP_BID_UI_GETDEFAULT'  "RFx Determination of Default Values
    EXPORTING
         IV_USER = lv_iv_user
         IV_OBJECT_TYPE = lv_iv_object_type
    IMPORTING
         ES_DEFAULT = lv_es_default
         ES_SEARCH_VALUES = lv_es_search_values
         ET_MESSAGES = lv_et_messages
. " BBP_BID_UI_GETDEFAULT




ABAP code using 7.40 inline data declarations to call FM BBP_BID_UI_GETDEFAULT

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!