SAP BBP_LA_BID_CHECK_PROXYBID Function Module for Check bid validity for overall best bid









BBP_LA_BID_CHECK_PROXYBID is a standard bbp la bid check proxybid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check bid validity for overall best bid 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 la bid check proxybid FM, simply by entering the name BBP_LA_BID_CHECK_PROXYBID into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_LA_BID_CHECK_PROXYBID 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_LA_BID_CHECK_PROXYBID'"Check bid validity for overall best bid
  EXPORTING
   IS_VALIDATION_DATA =  "Bid validation data
   I_LANGUAGE =  "R/3 System, current language

 IMPORTING
   EV_VALID =  "boolean variable (X=true, -=false, space=unknown)

CHANGING
   CS_BID =  "Bid
   C_EXT_ALREADY =  "Checkbox
   I_NEW_END_TIME =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

TABLES
*  IT_ALL_BIDS =  "All bids submitted
*  ET_MESSAGES =  "Error Messages
.



IMPORTING Parameters details for BBP_LA_BID_CHECK_PROXYBID

IS_VALIDATION_DATA - Bid validation data

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

I_LANGUAGE - R/3 System, current language

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

EXPORTING Parameters details for BBP_LA_BID_CHECK_PROXYBID

EV_VALID - boolean variable (X=true, -=false, space=unknown)

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

CHANGING Parameters details for BBP_LA_BID_CHECK_PROXYBID

CS_BID - Bid

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

C_EXT_ALREADY - Checkbox

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

I_NEW_END_TIME - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

TABLES Parameters details for BBP_LA_BID_CHECK_PROXYBID

IT_ALL_BIDS - All bids submitted

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

ET_MESSAGES - Error Messages

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

Copy and paste ABAP code example for BBP_LA_BID_CHECK_PROXYBID 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_cs_bid  TYPE BBPS_LA_BID, "   
lv_ev_valid  TYPE BOOLEAN, "   
lt_it_all_bids  TYPE STANDARD TABLE OF BBPS_LA_BID, "   
lv_is_validation_data  TYPE BBPS_LA_BID_VALIDATION_DATA, "   
lv_i_language  TYPE SYLANGU, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_MESSAGES, "   
lv_c_ext_already  TYPE XFELD, "   
lv_i_new_end_time  TYPE TIMESTAMP. "   

  CALL FUNCTION 'BBP_LA_BID_CHECK_PROXYBID'  "Check bid validity for overall best bid
    EXPORTING
         IS_VALIDATION_DATA = lv_is_validation_data
         I_LANGUAGE = lv_i_language
    IMPORTING
         EV_VALID = lv_ev_valid
    CHANGING
         CS_BID = lv_cs_bid
         C_EXT_ALREADY = lv_c_ext_already
         I_NEW_END_TIME = lv_i_new_end_time
    TABLES
         IT_ALL_BIDS = lt_it_all_bids
         ET_MESSAGES = lt_et_messages
. " BBP_LA_BID_CHECK_PROXYBID




ABAP code using 7.40 inline data declarations to call FM BBP_LA_BID_CHECK_PROXYBID

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!