SAP BBP_SEND_MAIL_BIDUSER Function Module for FM to send mails to bidding users created through SUS









BBP_SEND_MAIL_BIDUSER is a standard bbp send mail biduser SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM to send mails to bidding users created through SUS 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 send mail biduser FM, simply by entering the name BBP_SEND_MAIL_BIDUSER into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PARTNER_MAINT
Program Name: SAPLBBP_PARTNER_MAINT
Main Program: SAPLBBP_PARTNER_MAINT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BBP_SEND_MAIL_BIDUSER 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_SEND_MAIL_BIDUSER'"FM to send mails to bidding users created through SUS
EXPORTING
IV_USERNAME = "User Name in User Master Record
IV_PASSWORD = "New password
IV_LANGU = "Language Key
IV_PARTNER = "Business Partner Number
IV_EMAIL = "E-Mail Address

TABLES
ET_RETURN = "Return Parameter

EXCEPTIONS
EMAIL_NOT_VALID = 1 USER_NOT_VALID = 2 PASSWORD_NOT_VALID = 3 PARTNER_NOT_VALID = 4 ERROR_SENDING_EMAIL = 5 DOCU_NOT_FOUND = 6 CANT_GENERATE_URL = 7
.



IMPORTING Parameters details for BBP_SEND_MAIL_BIDUSER

IV_USERNAME - User Name in User Master Record

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

IV_PASSWORD - New password

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

IV_LANGU - Language Key

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

IV_PARTNER - Business Partner Number

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

IV_EMAIL - E-Mail Address

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

TABLES Parameters details for BBP_SEND_MAIL_BIDUSER

ET_RETURN - Return Parameter

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

EXCEPTIONS details

EMAIL_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

USER_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

PASSWORD_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

PARTNER_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

ERROR_SENDING_EMAIL -

Data type:
Optional: No
Call by Reference: Yes

DOCU_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CANT_GENERATE_URL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_SEND_MAIL_BIDUSER 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_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_username  TYPE XUBNAME, "   
lv_email_not_valid  TYPE XUBNAME, "   
lv_iv_password  TYPE XUNCODE, "   
lv_user_not_valid  TYPE XUNCODE, "   
lv_iv_langu  TYPE SPRAS, "   
lv_password_not_valid  TYPE SPRAS, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_partner_not_valid  TYPE BU_PARTNER, "   
lv_iv_email  TYPE AD_SMTPADR, "   
lv_error_sending_email  TYPE AD_SMTPADR, "   
lv_docu_not_found  TYPE AD_SMTPADR, "   
lv_cant_generate_url  TYPE AD_SMTPADR. "   

  CALL FUNCTION 'BBP_SEND_MAIL_BIDUSER'  "FM to send mails to bidding users created through SUS
    EXPORTING
         IV_USERNAME = lv_iv_username
         IV_PASSWORD = lv_iv_password
         IV_LANGU = lv_iv_langu
         IV_PARTNER = lv_iv_partner
         IV_EMAIL = lv_iv_email
    TABLES
         ET_RETURN = lt_et_return
    EXCEPTIONS
        EMAIL_NOT_VALID = 1
        USER_NOT_VALID = 2
        PASSWORD_NOT_VALID = 3
        PARTNER_NOT_VALID = 4
        ERROR_SENDING_EMAIL = 5
        DOCU_NOT_FOUND = 6
        CANT_GENERATE_URL = 7
. " BBP_SEND_MAIL_BIDUSER




ABAP code using 7.40 inline data declarations to call FM BBP_SEND_MAIL_BIDUSER

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!