SAP GET_PARCEL_BY_MUNICIPALITY Function Module for Get parcel keys by municipality
GET_PARCEL_BY_MUNICIPALITY is a standard get parcel by municipality 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 get parcel by municipality FM, simply by entering the name GET_PARCEL_BY_MUNICIPALITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: REXCPT_F4_EXITS
Program Name: SAPLREXCPT_F4_EXITS
Main Program: SAPLREXCPT_F4_EXITS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

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