SAP BD_APP_CALCULATE Function Module for Calculation of Budget Billing Amounts at Contract Level
BD_APP_CALCULATE is a standard bd app calculate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calculation of Budget Billing Amounts at Contract Level 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 app calculate FM, simply by entering the name BD_APP_CALCULATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BDISU_APP
Program Name: SAPLBDISU_APP
Main Program: SAPLBDISU_APP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BD_APP_CALCULATE 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_APP_CALCULATE'"Calculation of Budget Billing Amounts at Contract Level.
EXPORTING
I_CUST_ENTRY = "User Entry for Budget Billing Amount
I_AB_FAEDN = "Due Date for Net Payment
I_SAVE = "Flag: Save New Budget Billing Amounts
I_SPRAS = "Language Key
I_BUPA = "Business Partner Number
* I_USER = "User Name in User Master Record
IMPORTING
RETURN = "Return Parameter(s)
TABLES
BUDBIPLAN = "Table Type for UCES_BBP
* XT_UCES_EXTENSION = "UCES: Display Customer-Specific Fields from JSP
IMPORTING Parameters details for BD_APP_CALCULATE
I_CUST_ENTRY - User Entry for Budget Billing Amount
Data type: UCES_CUST_ENTRYOptional: No
Call by Reference: No ( called with pass by value option)
I_AB_FAEDN - Due Date for Net Payment
Data type: FAEDN_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_SAVE - Flag: Save New Budget Billing Amounts
Data type: UCES_SAVEOptional: No
Call by Reference: No ( called with pass by value option)
I_SPRAS - Language Key
Data type: SPRASOptional: No
Call by Reference: No ( called with pass by value option)
I_BUPA - Business Partner Number
Data type: GPART_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_USER - User Name in User Master Record
Data type: USR04-BNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BD_APP_CALCULATE
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BD_APP_CALCULATE
BUDBIPLAN - Table Type for UCES_BBP
Data type: UCES_PP_TABOptional: No
Call by Reference: Yes
XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP
Data type: UCES_EXTENSIONOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BD_APP_CALCULATE 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_return | TYPE BAPIRET2, " | |||
| lt_budbiplan | TYPE STANDARD TABLE OF UCES_PP_TAB, " | |||
| lv_i_cust_entry | TYPE UCES_CUST_ENTRY, " | |||
| lv_i_ab_faedn | TYPE FAEDN_KK, " | |||
| lt_xt_uces_extension | TYPE STANDARD TABLE OF UCES_EXTENSION, " | |||
| lv_i_save | TYPE UCES_SAVE, " | |||
| lv_i_spras | TYPE SPRAS, " | |||
| lv_i_bupa | TYPE GPART_KK, " | |||
| lv_i_user | TYPE USR04-BNAME. " |
|   CALL FUNCTION 'BD_APP_CALCULATE' "Calculation of Budget Billing Amounts at Contract Level |
| EXPORTING | ||
| I_CUST_ENTRY | = lv_i_cust_entry | |
| I_AB_FAEDN | = lv_i_ab_faedn | |
| I_SAVE | = lv_i_save | |
| I_SPRAS | = lv_i_spras | |
| I_BUPA | = lv_i_bupa | |
| I_USER | = lv_i_user | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| BUDBIPLAN | = lt_budbiplan | |
| XT_UCES_EXTENSION | = lt_xt_uces_extension | |
| . " BD_APP_CALCULATE | ||
ABAP code using 7.40 inline data declarations to call FM BD_APP_CALCULATE
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.| "SELECT single BNAME FROM USR04 INTO @DATA(ld_i_user). | ||||
Search for further information about these or an SAP related objects