SAP ISU_BBPLAN_CHANGE_AMNT_REMOTE Function Module for Change BB Amount at Contract Level
ISU_BBPLAN_CHANGE_AMNT_REMOTE is a standard isu bbplan change amnt remote SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change BB Amount 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 isu bbplan change amnt remote FM, simply by entering the name ISU_BBPLAN_CHANGE_AMNT_REMOTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EA61EXR
Program Name: SAPLEA61EXR
Main Program: SAPLEA61EXR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ISU_BBPLAN_CHANGE_AMNT_REMOTE 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_BBPLAN_CHANGE_AMNT_REMOTE'"Change BB Amount at Contract Level.
EXPORTING
X_VERTRAG = "Contract
X_VTRAMOUNT = "Budget Billing Amount at Contract Level
X_ABANPDATUM = "From-date of change
* X_OPBEL = "Budget Billing Plan
IMPORTING
Y_SUBRC = "Return Value, Return Value after ABAP Statements
TABLES
* YT_MSG = "Return Table
EXCEPTIONS
SYSTEM_FAILURE = 1 COMMUNICATION_FAILURE = 2 NO_VALID_DATE = 3 NOT_AUTHORIZED = 4
IMPORTING Parameters details for ISU_BBPLAN_CHANGE_AMNT_REMOTE
X_VERTRAG - Contract
Data type: EABP-VERTRAGOptional: No
Call by Reference: No ( called with pass by value option)
X_VTRAMOUNT - Budget Billing Amount at Contract Level
Data type: EABP-VTRBETRWOptional: No
Call by Reference: No ( called with pass by value option)
X_ABANPDATUM - From-date of change
Data type: REA61-ABANPDATUMOptional: No
Call by Reference: No ( called with pass by value option)
X_OPBEL - Budget Billing Plan
Data type: EABP-OPBELOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_BBPLAN_CHANGE_AMNT_REMOTE
Y_SUBRC - Return Value, Return Value after ABAP Statements
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_BBPLAN_CHANGE_AMNT_REMOTE
YT_MSG - Return Table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
NO_VALID_DATE -
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_BBPLAN_CHANGE_AMNT_REMOTE 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_yt_msg | TYPE STANDARD TABLE OF BAPIRET2_T, " | |||
| lv_y_subrc | TYPE SYSUBRC, " | |||
| lv_x_vertrag | TYPE EABP-VERTRAG, " | |||
| lv_system_failure | TYPE EABP, " | |||
| lv_x_vtramount | TYPE EABP-VTRBETRW, " | |||
| lv_communication_failure | TYPE EABP, " | |||
| lv_x_abanpdatum | TYPE REA61-ABANPDATUM, " | |||
| lv_no_valid_date | TYPE REA61, " | |||
| lv_x_opbel | TYPE EABP-OPBEL, " | |||
| lv_not_authorized | TYPE EABP. " |
|   CALL FUNCTION 'ISU_BBPLAN_CHANGE_AMNT_REMOTE' "Change BB Amount at Contract Level |
| EXPORTING | ||
| X_VERTRAG | = lv_x_vertrag | |
| X_VTRAMOUNT | = lv_x_vtramount | |
| X_ABANPDATUM | = lv_x_abanpdatum | |
| X_OPBEL | = lv_x_opbel | |
| IMPORTING | ||
| Y_SUBRC | = lv_y_subrc | |
| TABLES | ||
| YT_MSG | = lt_yt_msg | |
| EXCEPTIONS | ||
| SYSTEM_FAILURE = 1 | ||
| COMMUNICATION_FAILURE = 2 | ||
| NO_VALID_DATE = 3 | ||
| NOT_AUTHORIZED = 4 | ||
| . " ISU_BBPLAN_CHANGE_AMNT_REMOTE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_BBPLAN_CHANGE_AMNT_REMOTE
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 VERTRAG FROM EABP INTO @DATA(ld_x_vertrag). | ||||
| "SELECT single VTRBETRW FROM EABP INTO @DATA(ld_x_vtramount). | ||||
| "SELECT single ABANPDATUM FROM REA61 INTO @DATA(ld_x_abanpdatum). | ||||
| "SELECT single OPBEL FROM EABP INTO @DATA(ld_x_opbel). | ||||
Search for further information about these or an SAP related objects