SAP REXC_ES_GET_PARCEL_BY_MUNIC Function Module for Get parcel keys by municipality
REXC_ES_GET_PARCEL_BY_MUNIC is a standard rexc es get parcel by munic SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get parcel keys by municipality 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 rexc es get parcel by munic FM, simply by entering the name REXC_ES_GET_PARCEL_BY_MUNIC into the relevant SAP transaction such as SE37 or SE38.
Function Group: REXCES_F4_EXITS
Program Name: SAPLREXCES_F4_EXITS
Main Program: SAPLREXCES_F4_EXITS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REXC_ES_GET_PARCEL_BY_MUNIC 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 'REXC_ES_GET_PARCEL_BY_MUNIC'"Get parcel keys by municipality.
EXPORTING
IT_MUNICIPALITY = "Code of the Municipality
EXCEPTIONS
MISSING_CUSTOMIZING = 1 NOT_FOUND = 2
IMPORTING Parameters details for REXC_ES_GET_PARCEL_BY_MUNIC
IT_MUNICIPALITY - Code of the Municipality
Data type: RE_T_ES_SELECTIONCRITERIAOptional: No
Call by Reference: Yes
EXCEPTIONS details
MISSING_CUSTOMIZING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for REXC_ES_GET_PARCEL_BY_MUNIC 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_it_municipality | TYPE RE_T_ES_SELECTIONCRITERIA, " | |||
| lv_missing_customizing | TYPE RE_T_ES_SELECTIONCRITERIA, " | |||
| lv_not_found | TYPE RE_T_ES_SELECTIONCRITERIA. " |
|   CALL FUNCTION 'REXC_ES_GET_PARCEL_BY_MUNIC' "Get parcel keys by municipality |
| EXPORTING | ||
| IT_MUNICIPALITY | = lv_it_municipality | |
| EXCEPTIONS | ||
| MISSING_CUSTOMIZING = 1 | ||
| NOT_FOUND = 2 | ||
| . " REXC_ES_GET_PARCEL_BY_MUNIC | ||
ABAP code using 7.40 inline data declarations to call FM REXC_ES_GET_PARCEL_BY_MUNIC
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