SAP ME_GET_AREA Function Module for
ME_GET_AREA is a standard me get area SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 me get area FM, simply by entering the name ME_GET_AREA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVI2
Program Name: SAPLFVI2
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_GET_AREA 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 'ME_GET_AREA'".
EXPORTING
* I_BUKRS = "
* I_KZ_ALL = "
* I_REFRESH_BUFFER = ' ' "
* I_SWENR = "
* I_SMENR = "
* I_DSTICH = SY-DATUM "
* I_INTRENO = "
* I_OBJNR = "
* I_IMKEY = "
* I_KZ_ONE_UNIT = "
* I_UNIT = "
TABLES
T_VIOB40 = "
* T_RANGES_SFLART = "
EXCEPTIONS
ERROR_READING_OBJECT = 1
IMPORTING Parameters details for ME_GET_AREA
I_BUKRS -
Data type: VIMI01-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_KZ_ALL -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
I_REFRESH_BUFFER -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SWENR -
Data type: VIMI01-SWENROptional: Yes
Call by Reference: No ( called with pass by value option)
I_SMENR -
Data type: VIMI01-SMENROptional: Yes
Call by Reference: No ( called with pass by value option)
I_DSTICH -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_INTRENO -
Data type: VIMI01-INTRENOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJNR -
Data type: VIMI01-SNKSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_IMKEY -
Data type: VIMI01-IMKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_KZ_ONE_UNIT -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
I_UNIT -
Data type: VIOB40-FEINSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ME_GET_AREA
T_VIOB40 -
Data type: VIOB40Optional: No
Call by Reference: No ( called with pass by value option)
T_RANGES_SFLART -
Data type: RSOSFLARTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_READING_OBJECT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_GET_AREA 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_i_bukrs | TYPE VIMI01-BUKRS, " | |||
| lt_t_viob40 | TYPE STANDARD TABLE OF VIOB40, " | |||
| lv_error_reading_object | TYPE VIOB40, " | |||
| lv_i_kz_all | TYPE C, " | |||
| lv_i_refresh_buffer | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_swenr | TYPE VIMI01-SWENR, " | |||
| lt_t_ranges_sflart | TYPE STANDARD TABLE OF RSOSFLART, " | |||
| lv_i_smenr | TYPE VIMI01-SMENR, " | |||
| lv_i_dstich | TYPE SY-DATUM, " SY-DATUM | |||
| lv_i_intreno | TYPE VIMI01-INTRENO, " | |||
| lv_i_objnr | TYPE VIMI01-SNKS, " | |||
| lv_i_imkey | TYPE VIMI01-IMKEY, " | |||
| lv_i_kz_one_unit | TYPE C, " | |||
| lv_i_unit | TYPE VIOB40-FEINS. " |
|   CALL FUNCTION 'ME_GET_AREA' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_KZ_ALL | = lv_i_kz_all | |
| I_REFRESH_BUFFER | = lv_i_refresh_buffer | |
| I_SWENR | = lv_i_swenr | |
| I_SMENR | = lv_i_smenr | |
| I_DSTICH | = lv_i_dstich | |
| I_INTRENO | = lv_i_intreno | |
| I_OBJNR | = lv_i_objnr | |
| I_IMKEY | = lv_i_imkey | |
| I_KZ_ONE_UNIT | = lv_i_kz_one_unit | |
| I_UNIT | = lv_i_unit | |
| TABLES | ||
| T_VIOB40 | = lt_t_viob40 | |
| T_RANGES_SFLART | = lt_t_ranges_sflart | |
| EXCEPTIONS | ||
| ERROR_READING_OBJECT = 1 | ||
| . " ME_GET_AREA | ||
ABAP code using 7.40 inline data declarations to call FM ME_GET_AREA
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 BUKRS FROM VIMI01 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_refresh_buffer). | ||||
| DATA(ld_i_refresh_buffer) | = ' '. | |||
| "SELECT single SWENR FROM VIMI01 INTO @DATA(ld_i_swenr). | ||||
| "SELECT single SMENR FROM VIMI01 INTO @DATA(ld_i_smenr). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_dstich). | ||||
| DATA(ld_i_dstich) | = SY-DATUM. | |||
| "SELECT single INTRENO FROM VIMI01 INTO @DATA(ld_i_intreno). | ||||
| "SELECT single SNKS FROM VIMI01 INTO @DATA(ld_i_objnr). | ||||
| "SELECT single IMKEY FROM VIMI01 INTO @DATA(ld_i_imkey). | ||||
| "SELECT single FEINS FROM VIOB40 INTO @DATA(ld_i_unit). | ||||
Search for further information about these or an SAP related objects