SAP BD_ABBP_EMAIL Function Module for Send E-Mail with New Budget Billing Data

Search SAP Function Modules

BD_ABBP_EMAIL is a standard bd abbp email SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Send E-Mail with New Budget Billing Data 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 bd abbp email FM, simply by entering the name BD_ABBP_EMAIL into the relevant SAP transaction such as SE37 or SE38.

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

Function BD_ABBP_EMAIL 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 'BD_ABBP_EMAIL'"Send E-Mail with New Budget Billing Data
  EXPORTING
   BUDBIPLAN =  "Transfer Structure for Budget Billing Amount Adjustment
   PAYDATES =  "Data for Future Budget Billing Payments
*  I_SPRAS = SY-LANGU "Language Key
   I_GPART =  "Business Partner Number

 IMPORTING
   RETURN =  "Return Parameter(s)

TABLES
*  XT_UCES_EXTENSION =  "UCES: Display Customer-Specific Fields from JSP

.

IMPORTING Parameters details for BD_ABBP_EMAIL

BUDBIPLAN - Transfer Structure for Budget Billing Amount Adjustment

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

PAYDATES - Data for Future Budget Billing Payments

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

I_SPRAS - Language Key

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GPART - Business Partner Number

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

EXPORTING Parameters details for BD_ABBP_EMAIL

RETURN - Return Parameter(s)

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

TABLES Parameters details for BD_ABBP_EMAIL

XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP

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

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

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