SAP EXIT_SAPMILO0_001 Function Module for User Exit Before Update of a Functional Location
EXIT_SAPMILO0_001 is a standard exit sapmilo0 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Exit Before Update of a Functional Location 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 exit sapmilo0 001 FM, simply by entering the name EXIT_SAPMILO0_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XLOM
Program Name: SAPLXLOM
Main Program:
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMILO0_001 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 'EXIT_SAPMILO0_001'"User Exit Before Update of a Functional Location.
EXPORTING
ACTIVITY_TYPE = "Transaction Type: 1 = Add; 2 = Change
DATA_IFLO = "Functional Location Master Data (View IFLO)
DATA_IFLO_OLD = "Before-Image of Functional Location
MAIN_CLASS = "Standard Class
DATA_IFLOS = "Indicators Functional Locations (IFLOS)
IMPORTING
UPDATE_DATA_IFLO = "Field Contents Defined by Customer
UPDATE_FLAGS_IFLO = "Update Indicators per Field
EXCEPTIONS
POSTING_NOT_ALLOWED = 1 POSTING_NOT_ALLOWED_EXT = 2
IMPORTING Parameters details for EXIT_SAPMILO0_001
ACTIVITY_TYPE - Transaction Type: 1 = Add; 2 = Change
Data type: IREF-ACTYPOptional: No
Call by Reference: No ( called with pass by value option)
DATA_IFLO - Functional Location Master Data (View IFLO)
Data type: IFLOOptional: No
Call by Reference: No ( called with pass by value option)
DATA_IFLO_OLD - Before-Image of Functional Location
Data type: IFLOOptional: No
Call by Reference: No ( called with pass by value option)
MAIN_CLASS - Standard Class
Data type: RILO0-KLASSEOptional: No
Call by Reference: No ( called with pass by value option)
DATA_IFLOS - Indicators Functional Locations (IFLOS)
Data type: IFLOSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPMILO0_001
UPDATE_DATA_IFLO - Field Contents Defined by Customer
Data type: IFLO_USR1Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_FLAGS_IFLO - Update Indicators per Field
Data type: IFLO_USR1UOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
POSTING_NOT_ALLOWED - Update not Possible, SAP Standard Message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
POSTING_NOT_ALLOWED_EXT - Update not Possible, Customer-DefinedMmessage
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMILO0_001 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_activity_type | TYPE IREF-ACTYP, " | |||
lv_update_data_iflo | TYPE IFLO_USR1, " | |||
lv_posting_not_allowed | TYPE IFLO_USR1, " | |||
lv_data_iflo | TYPE IFLO, " | |||
lv_update_flags_iflo | TYPE IFLO_USR1U, " | |||
lv_posting_not_allowed_ext | TYPE IFLO_USR1U, " | |||
lv_data_iflo_old | TYPE IFLO, " | |||
lv_main_class | TYPE RILO0-KLASSE, " | |||
lv_data_iflos | TYPE IFLOS. " |
  CALL FUNCTION 'EXIT_SAPMILO0_001' "User Exit Before Update of a Functional Location |
EXPORTING | ||
ACTIVITY_TYPE | = lv_activity_type | |
DATA_IFLO | = lv_data_iflo | |
DATA_IFLO_OLD | = lv_data_iflo_old | |
MAIN_CLASS | = lv_main_class | |
DATA_IFLOS | = lv_data_iflos | |
IMPORTING | ||
UPDATE_DATA_IFLO | = lv_update_data_iflo | |
UPDATE_FLAGS_IFLO | = lv_update_flags_iflo | |
EXCEPTIONS | ||
POSTING_NOT_ALLOWED = 1 | ||
POSTING_NOT_ALLOWED_EXT = 2 | ||
. " EXIT_SAPMILO0_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMILO0_001
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 ACTYP FROM IREF INTO @DATA(ld_activity_type). | ||||
"SELECT single KLASSE FROM RILO0 INTO @DATA(ld_main_class). | ||||
Search for further information about these or an SAP related objects