SAP ISU_MI_BBP_CREATE_PREPARE_EXT Function Module for INTERNAL: Prepare to Create Budget Billing Plan in Move-In
ISU_MI_BBP_CREATE_PREPARE_EXT is a standard isu mi bbp create prepare ext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Prepare to Create Budget Billing Plan in Move-In 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 mi bbp create prepare ext FM, simply by entering the name ISU_MI_BBP_CREATE_PREPARE_EXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EC50_CONTR
Program Name: SAPLEC50_CONTR
Main Program: SAPLEC50_CONTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_MI_BBP_CREATE_PREPARE_EXT 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_MI_BBP_CREATE_PREPARE_EXT'"INTERNAL: Prepare to Create Budget Billing Plan in Move-In.
EXPORTING
* X_EINZBELEG = "Consecutive Number of Move-In Document
* XT_VERTRAG = "
IMPORTING
Y_OBJ = "
YT_EMIBBPEVER = "Table Category for EMIBBPEVER
EXCEPTIONS
NOT_FOUND = 1 MOVE_IN_REVERSED = 2 INTERNAL_ERROR = 3 BBP_EXISTS = 4 BBP_NOT_STOPPED = 5 INVALID_KZABSVER = 6 BBP_CYCLE_ZERO = 7
IMPORTING Parameters details for ISU_MI_BBP_CREATE_PREPARE_EXT
X_EINZBELEG - Consecutive Number of Move-In Document
Data type: EINZBELEGOptional: Yes
Call by Reference: No ( called with pass by value option)
XT_VERTRAG -
Data type: TISU_VERTRAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_MI_BBP_CREATE_PREPARE_EXT
Y_OBJ -
Data type: ISU06_MOVEINOptional: No
Call by Reference: Yes
YT_EMIBBPEVER - Table Category for EMIBBPEVER
Data type: EMITBBPEVEROptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
MOVE_IN_REVERSED -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
BBP_EXISTS -
Data type:Optional: No
Call by Reference: Yes
BBP_NOT_STOPPED -
Data type:Optional: No
Call by Reference: Yes
INVALID_KZABSVER -
Data type:Optional: No
Call by Reference: Yes
BBP_CYCLE_ZERO -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_MI_BBP_CREATE_PREPARE_EXT 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_y_obj | TYPE ISU06_MOVEIN, " | |||
| lv_not_found | TYPE ISU06_MOVEIN, " | |||
| lv_x_einzbeleg | TYPE EINZBELEG, " | |||
| lv_xt_vertrag | TYPE TISU_VERTRAG, " | |||
| lv_yt_emibbpever | TYPE EMITBBPEVER, " | |||
| lv_move_in_reversed | TYPE EMITBBPEVER, " | |||
| lv_internal_error | TYPE EMITBBPEVER, " | |||
| lv_bbp_exists | TYPE EMITBBPEVER, " | |||
| lv_bbp_not_stopped | TYPE EMITBBPEVER, " | |||
| lv_invalid_kzabsver | TYPE EMITBBPEVER, " | |||
| lv_bbp_cycle_zero | TYPE EMITBBPEVER. " |
|   CALL FUNCTION 'ISU_MI_BBP_CREATE_PREPARE_EXT' "INTERNAL: Prepare to Create Budget Billing Plan in Move-In |
| EXPORTING | ||
| X_EINZBELEG | = lv_x_einzbeleg | |
| XT_VERTRAG | = lv_xt_vertrag | |
| IMPORTING | ||
| Y_OBJ | = lv_y_obj | |
| YT_EMIBBPEVER | = lv_yt_emibbpever | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| MOVE_IN_REVERSED = 2 | ||
| INTERNAL_ERROR = 3 | ||
| BBP_EXISTS = 4 | ||
| BBP_NOT_STOPPED = 5 | ||
| INVALID_KZABSVER = 6 | ||
| BBP_CYCLE_ZERO = 7 | ||
| . " ISU_MI_BBP_CREATE_PREPARE_EXT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_MI_BBP_CREATE_PREPARE_EXT
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