SAP BBP_ALERT_BID_GROUPING Function Module for









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

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



Function BBP_ALERT_BID_GROUPING 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_ALERT_BID_GROUPING'"
EXPORTING
IV_BID_NUMBER = "
IV_BID_ITEM_NUMBER = "
IV_MESSAGE_TEXT = "

EXCEPTIONS
INVALID_PARAMETERS = 1
.



IMPORTING Parameters details for BBP_ALERT_BID_GROUPING

IV_BID_NUMBER -

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

IV_BID_ITEM_NUMBER -

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

IV_MESSAGE_TEXT -

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

EXCEPTIONS details

INVALID_PARAMETERS -

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

Copy and paste ABAP code example for BBP_ALERT_BID_GROUPING 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_bid_number  TYPE BBP_DOC_NUMBER, "   
lv_invalid_parameters  TYPE BBP_DOC_NUMBER, "   
lv_iv_bid_item_number  TYPE BBP_ITEM_NO, "   
lv_iv_message_text  TYPE BAPI_MSG. "   

  CALL FUNCTION 'BBP_ALERT_BID_GROUPING'  "
    EXPORTING
         IV_BID_NUMBER = lv_iv_bid_number
         IV_BID_ITEM_NUMBER = lv_iv_bid_item_number
         IV_MESSAGE_TEXT = lv_iv_message_text
    EXCEPTIONS
        INVALID_PARAMETERS = 1
. " BBP_ALERT_BID_GROUPING




ABAP code using 7.40 inline data declarations to call FM BBP_ALERT_BID_GROUPING

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!