SAP BAPI_RE_PL_GET_LIST Function Module for
BAPI_RE_PL_GET_LIST is a standard bapi re pl get list 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 bapi re pl get list FM, simply by entering the name BAPI_RE_PL_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: RELM_BAPI_PARCEL_LAND
Program Name: SAPLRELM_BAPI_PARCEL_LAND
Main Program: SAPLRELM_BAPI_PARCEL_LAND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RE_PL_GET_LIST 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 'BAPI_RE_PL_GET_LIST'".
EXPORTING
* DETAIL_DATA_FROM = "
* DETAIL_DATA_TO = "
* SELECT_X = "
* MAX_ROWS = 0 "
TABLES
SELOPTION = "
* PARTNER = "
* CHARACT = "
* TEXT = "
* OBJ_ASSIGN = "
* RESUBM_RULE = "
* RESUBM_DATE = "
* STATUS = "
* EXTENSION_OUT = "
* RETURN = "
* PARCEL_OF_LAND = "
* LOC_HIER = "
* ADDRESS = "
* MEASUREMENT = "
* INFRASTRUCTURE = "
* PL_MAP = "
* PL_SLIDE = "
* PL_USAGE = "
IMPORTING Parameters details for BAPI_RE_PL_GET_LIST
DETAIL_DATA_FROM -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROMOptional: Yes
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_TO -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TOOptional: Yes
Call by Reference: No ( called with pass by value option)
SELECT_X -
Data type: BAPI_RE_PARCEL_LAND_SELXOptional: Yes
Call by Reference: No ( called with pass by value option)
MAX_ROWS -
Data type: BAPI_RE_ADDITIONAL_FIELDS-BAPIMAXROWOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_PL_GET_LIST
SELOPTION -
Data type: BAPI_RE_SELOPTIONOptional: No
Call by Reference: No ( called with pass by value option)
PARTNER -
Data type: BAPI_RE_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
CHARACT -
Data type: BAPI_RE_CHARACTOptional: Yes
Call by Reference: Yes
TEXT -
Data type: BAPI_RE_TEXTOptional: Yes
Call by Reference: Yes
OBJ_ASSIGN -
Data type: BAPI_RE_OBJ_ASSIGNOptional: Yes
Call by Reference: Yes
RESUBM_RULE -
Data type: BAPI_RE_RESUBM_RULEOptional: Yes
Call by Reference: No ( called with pass by value option)
RESUBM_DATE -
Data type: BAPI_RE_RESUBM_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUS -
Data type: BAPI_RE_STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION_OUT -
Data type: BAPI_RE_IDENT_PAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
PARCEL_OF_LAND -
Data type: BAPI_RE_PARCEL_LANDOptional: Yes
Call by Reference: Yes
LOC_HIER -
Data type: BAPI_RE_LOC_HIEROptional: Yes
Call by Reference: Yes
ADDRESS -
Data type: BAPI_RE_MULTI_ADDROptional: Yes
Call by Reference: Yes
MEASUREMENT -
Data type: BAPI_RE_MEASUREMENTOptional: Yes
Call by Reference: Yes
INFRASTRUCTURE -
Data type: BAPI_RE_INFRAOptional: Yes
Call by Reference: Yes
PL_MAP -
Data type: BAPI_RE_PL_MAPOptional: Yes
Call by Reference: Yes
PL_SLIDE -
Data type: BAPI_RE_PL_SLIDEOptional: Yes
Call by Reference: Yes
PL_USAGE -
Data type: BAPI_RE_PL_USAGEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RE_PL_GET_LIST 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: | ||||
| lt_seloption | TYPE STANDARD TABLE OF BAPI_RE_SELOPTION, " | |||
| lv_detail_data_from | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, " | |||
| lt_partner | TYPE STANDARD TABLE OF BAPI_RE_PARTNER, " | |||
| lt_charact | TYPE STANDARD TABLE OF BAPI_RE_CHARACT, " | |||
| lt_text | TYPE STANDARD TABLE OF BAPI_RE_TEXT, " | |||
| lt_obj_assign | TYPE STANDARD TABLE OF BAPI_RE_OBJ_ASSIGN, " | |||
| lt_resubm_rule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, " | |||
| lt_resubm_date | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS, " | |||
| lt_extension_out | TYPE STANDARD TABLE OF BAPI_RE_IDENT_PAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_detail_data_to | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, " | |||
| lt_parcel_of_land | TYPE STANDARD TABLE OF BAPI_RE_PARCEL_LAND, " | |||
| lt_loc_hier | TYPE STANDARD TABLE OF BAPI_RE_LOC_HIER, " | |||
| lv_select_x | TYPE BAPI_RE_PARCEL_LAND_SELX, " | |||
| lt_address | TYPE STANDARD TABLE OF BAPI_RE_MULTI_ADDR, " | |||
| lv_max_rows | TYPE BAPI_RE_ADDITIONAL_FIELDS-BAPIMAXROW, " 0 | |||
| lt_measurement | TYPE STANDARD TABLE OF BAPI_RE_MEASUREMENT, " | |||
| lt_infrastructure | TYPE STANDARD TABLE OF BAPI_RE_INFRA, " | |||
| lt_pl_map | TYPE STANDARD TABLE OF BAPI_RE_PL_MAP, " | |||
| lt_pl_slide | TYPE STANDARD TABLE OF BAPI_RE_PL_SLIDE, " | |||
| lt_pl_usage | TYPE STANDARD TABLE OF BAPI_RE_PL_USAGE. " |
|   CALL FUNCTION 'BAPI_RE_PL_GET_LIST' " |
| EXPORTING | ||
| DETAIL_DATA_FROM | = lv_detail_data_from | |
| DETAIL_DATA_TO | = lv_detail_data_to | |
| SELECT_X | = lv_select_x | |
| MAX_ROWS | = lv_max_rows | |
| TABLES | ||
| SELOPTION | = lt_seloption | |
| PARTNER | = lt_partner | |
| CHARACT | = lt_charact | |
| TEXT | = lt_text | |
| OBJ_ASSIGN | = lt_obj_assign | |
| RESUBM_RULE | = lt_resubm_rule | |
| RESUBM_DATE | = lt_resubm_date | |
| STATUS | = lt_status | |
| EXTENSION_OUT | = lt_extension_out | |
| RETURN | = lt_return | |
| PARCEL_OF_LAND | = lt_parcel_of_land | |
| LOC_HIER | = lt_loc_hier | |
| ADDRESS | = lt_address | |
| MEASUREMENT | = lt_measurement | |
| INFRASTRUCTURE | = lt_infrastructure | |
| PL_MAP | = lt_pl_map | |
| PL_SLIDE | = lt_pl_slide | |
| PL_USAGE | = lt_pl_usage | |
| . " BAPI_RE_PL_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_PL_GET_LIST
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 DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_from). | ||||
| "SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_to). | ||||
| "SELECT single BAPIMAXROW FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_max_rows). | ||||
Search for further information about these or an SAP related objects