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

Function ISU_AMOUNT_PORTION_CHANGE 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_AMOUNT_PORTION_CHANGE'"Standard Module for Amount Transfer (R923).
EXPORTING
X_OBJ = "
X_EVER = "IS-U Contract
CHANGING
XY_EABPS = "Table with Budget Billing Data
IMPORTING Parameters details for ISU_AMOUNT_PORTION_CHANGE
X_OBJ -
Data type: ISU25_BUDBILPLANOptional: No
Call by Reference: Yes
X_EVER - IS-U Contract
Data type: EVEROptional: No
Call by Reference: Yes
CHANGING Parameters details for ISU_AMOUNT_PORTION_CHANGE
XY_EABPS - Table with Budget Billing Data
Data type: ISU25_BUDBILDATE_TABLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_AMOUNT_PORTION_CHANGE 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_obj | TYPE ISU25_BUDBILPLAN, " | |||
| lv_xy_eabps | TYPE ISU25_BUDBILDATE_TABLE, " | |||
| lv_x_ever | TYPE EVER. " |
|   CALL FUNCTION 'ISU_AMOUNT_PORTION_CHANGE' "Standard Module for Amount Transfer (R923) |
| EXPORTING | ||
| X_OBJ | = lv_x_obj | |
| X_EVER | = lv_x_ever | |
| CHANGING | ||
| XY_EABPS | = lv_xy_eabps | |
| . " ISU_AMOUNT_PORTION_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_AMOUNT_PORTION_CHANGE
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