SAP ISU_MI_SECURITY_CREATE Function Module for INTERNAL: Request Security Deposit for Move-In









ISU_MI_SECURITY_CREATE is a standard isu mi security create 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: Request Security Deposit for 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 security create FM, simply by entering the name ISU_MI_SECURITY_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: EC50A
Program Name: SAPLEC50A
Main Program: SAPLEC50A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_MI_SECURITY_CREATE 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_SECURITY_CREATE'"INTERNAL: Request Security Deposit for Move-In
IMPORTING
Y_SECURITY_CHANGED = "Indicator
Y_SECURITY_FAILED = "Indicator

CHANGING
XY_OBJ = "
.



EXPORTING Parameters details for ISU_MI_SECURITY_CREATE

Y_SECURITY_CHANGED - Indicator

Data type: REGEN-KENNZX
Optional: No
Call by Reference: Yes

Y_SECURITY_FAILED - Indicator

Data type: REGEN-KENNZX
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ISU_MI_SECURITY_CREATE

XY_OBJ -

Data type: ISU06_MOVEIN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_MI_SECURITY_CREATE 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_xy_obj  TYPE ISU06_MOVEIN, "   
lv_y_security_changed  TYPE REGEN-KENNZX, "   
lv_y_security_failed  TYPE REGEN-KENNZX. "   

  CALL FUNCTION 'ISU_MI_SECURITY_CREATE'  "INTERNAL: Request Security Deposit for Move-In
    IMPORTING
         Y_SECURITY_CHANGED = lv_y_security_changed
         Y_SECURITY_FAILED = lv_y_security_failed
    CHANGING
         XY_OBJ = lv_xy_obj
. " ISU_MI_SECURITY_CREATE




ABAP code using 7.40 inline data declarations to call FM ISU_MI_SECURITY_CREATE

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 KENNZX FROM REGEN INTO @DATA(ld_y_security_changed).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_security_failed).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!