SAP ISU_BBP_GET_CURRENT_AMOUNT Function Module for Determine Current Budget Billing Amount
ISU_BBP_GET_CURRENT_AMOUNT is a standard isu bbp get current amount SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Current Budget Billing Amount 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 isu bbp get current amount FM, simply by entering the name ISU_BBP_GET_CURRENT_AMOUNT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EA61EX
Program Name: SAPLEA61EX
Main Program: SAPLEA61EX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_BBP_GET_CURRENT_AMOUNT 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 'ISU_BBP_GET_CURRENT_AMOUNT'"Determine Current Budget Billing Amount.
EXPORTING
X_OPBEL = "Budget Billing Plan
* X_VERTRAG = "Contract
* X_DATUM = "
* X_OBJ = "Budget Billing Plan
IMPORTING
X_ACT_BETRW = "
X_ACT_KUMBETRW = "
X_ACT_OPENBETRW = "
X_ACT_OPENKUMBETRW = "
IMPORTING Parameters details for ISU_BBP_GET_CURRENT_AMOUNT
X_OPBEL - Budget Billing Plan
Data type: EABP-OPBELOptional: No
Call by Reference: Yes
X_VERTRAG - Contract
Data type: EABP-VERTRAGOptional: Yes
Call by Reference: Yes
X_DATUM -
Data type: SY-DATUMOptional: Yes
Call by Reference: Yes
X_OBJ - Budget Billing Plan
Data type: ISU25_BUDBILPLANOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_BBP_GET_CURRENT_AMOUNT
X_ACT_BETRW -
Data type: DFKKOP-BETRWOptional: No
Call by Reference: Yes
X_ACT_KUMBETRW -
Data type: DFKKOP-BETRWOptional: No
Call by Reference: Yes
X_ACT_OPENBETRW -
Data type: DFKKOP-BETRWOptional: No
Call by Reference: Yes
X_ACT_OPENKUMBETRW -
Data type: DFKKOP-BETRWOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_BBP_GET_CURRENT_AMOUNT 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_x_opbel | TYPE EABP-OPBEL, " | |||
| lv_x_act_betrw | TYPE DFKKOP-BETRW, " | |||
| lv_x_vertrag | TYPE EABP-VERTRAG, " | |||
| lv_x_act_kumbetrw | TYPE DFKKOP-BETRW, " | |||
| lv_x_datum | TYPE SY-DATUM, " | |||
| lv_x_act_openbetrw | TYPE DFKKOP-BETRW, " | |||
| lv_x_obj | TYPE ISU25_BUDBILPLAN, " | |||
| lv_x_act_openkumbetrw | TYPE DFKKOP-BETRW. " |
|   CALL FUNCTION 'ISU_BBP_GET_CURRENT_AMOUNT' "Determine Current Budget Billing Amount |
| EXPORTING | ||
| X_OPBEL | = lv_x_opbel | |
| X_VERTRAG | = lv_x_vertrag | |
| X_DATUM | = lv_x_datum | |
| X_OBJ | = lv_x_obj | |
| IMPORTING | ||
| X_ACT_BETRW | = lv_x_act_betrw | |
| X_ACT_KUMBETRW | = lv_x_act_kumbetrw | |
| X_ACT_OPENBETRW | = lv_x_act_openbetrw | |
| X_ACT_OPENKUMBETRW | = lv_x_act_openkumbetrw | |
| . " ISU_BBP_GET_CURRENT_AMOUNT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_BBP_GET_CURRENT_AMOUNT
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 OPBEL FROM EABP INTO @DATA(ld_x_opbel). | ||||
| "SELECT single BETRW FROM DFKKOP INTO @DATA(ld_x_act_betrw). | ||||
| "SELECT single VERTRAG FROM EABP INTO @DATA(ld_x_vertrag). | ||||
| "SELECT single BETRW FROM DFKKOP INTO @DATA(ld_x_act_kumbetrw). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_x_datum). | ||||
| "SELECT single BETRW FROM DFKKOP INTO @DATA(ld_x_act_openbetrw). | ||||
| "SELECT single BETRW FROM DFKKOP INTO @DATA(ld_x_act_openkumbetrw). | ||||
Search for further information about these or an SAP related objects