SAP API_RE_PL_GET_DETAIL Function Module for

Search SAP Function Modules

API_RE_PL_GET_DETAIL is a standard api re pl get detail 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 api re pl get detail FM, simply by entering the name API_RE_PL_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: RELM_API_PARCEL_LAND
Program Name: SAPLRELM_API_PARCEL_LAND
Main Program: SAPLRELM_API_PARCEL_LAND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function API_RE_PL_GET_DETAIL 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 'API_RE_PL_GET_DETAIL'"
  EXPORTING
*  ID_LOCHIER =  "
*  ID_PLSUBDIVNO =  "
*  ID_PLNO =  "
*  ID_OBJNR =  "
*  ID_INTRENO =  "
*  IO_OBJECT =  "
*  ID_DETAIL_DATA_FROM =  "
*  ID_DETAIL_DATA_TO =  "
*  IF_OLD_DATA = ' ' "

 IMPORTING
   ES_PARCEL_OF_LAND =  "
   ET_CHARACT =  "
   ET_TEXT =  "
   ET_OBJ_ASSIGN =  "
   ET_RESUBM_RULE =  "
   ET_RESUBM_DATE =  "
   ET_STATUS =  "
   ES_CI_DATA =  "
   ET_EXT_DATA =  "
   ET_LOC_HIER =  "
   ET_ADDRESS =  "
   ET_MEASUREMENT =  "
   ET_INFRASTRUCTURE =  "
   ET_PL_MAP =  "
   ET_PL_SLIDE =  "
   ET_PL_USAGE =  "
   ET_PARTNER =  "

EXCEPTIONS
   ERROR = 1 

.

IMPORTING Parameters details for API_RE_PL_GET_DETAIL

ID_LOCHIER -

Data type: BAPI_RE_PARCEL_LAND_INTK-LOCHIER
Optional: Yes
Call by Reference: Yes

ID_PLSUBDIVNO -

Data type: BAPI_RE_PARCEL_LAND_INTK-PLSUBDIVNO
Optional: Yes
Call by Reference: Yes

ID_PLNO -

Data type: BAPI_RE_PARCEL_LAND_INTK-PLNO
Optional: Yes
Call by Reference: Yes

ID_OBJNR -

Data type: RECAOBJNR
Optional: Yes
Call by Reference: Yes

ID_INTRENO -

Data type: RECAINTRENO
Optional: Yes
Call by Reference: Yes

IO_OBJECT -

Data type: OBJECT
Optional: Yes
Call by Reference: Yes

ID_DETAIL_DATA_FROM -

Data type: BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDFROM
Optional: Yes
Call by Reference: Yes

ID_DETAIL_DATA_TO -

Data type: BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDTO
Optional: Yes
Call by Reference: Yes

IF_OLD_DATA -

Data type: RECABOOL
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for API_RE_PL_GET_DETAIL

ES_PARCEL_OF_LAND -

Data type: BAPI_RE_PARCEL_LAND_INT
Optional: No
Call by Reference: Yes

ET_CHARACT -

Data type: BAPI_RE_T_CHARACT_INT
Optional: No
Call by Reference: Yes

ET_TEXT -

Data type: BAPI_RE_T_TEXT_INT
Optional: No
Call by Reference: Yes

ET_OBJ_ASSIGN -

Data type: BAPI_RE_T_OBJ_ASSIGN_INT
Optional: No
Call by Reference: Yes

ET_RESUBM_RULE -

Data type: BAPI_RE_T_RESUBM_RULE_INT
Optional: No
Call by Reference: Yes

ET_RESUBM_DATE -

Data type: BAPI_RE_T_RESUBM_DATE_INT
Optional: No
Call by Reference: Yes

ET_STATUS -

Data type: BAPI_RE_T_STATUS_INT
Optional: No
Call by Reference: Yes

ES_CI_DATA -

Data type: RELM_PARCEL_OF_LAND_CI
Optional: No
Call by Reference: Yes

ET_EXT_DATA -

Data type: RE_T_EXT_DATA
Optional: No
Call by Reference: Yes

ET_LOC_HIER -

Data type: BAPI_RE_T_LOC_HIER_INT
Optional: No
Call by Reference: Yes

ET_ADDRESS -

Data type: BAPI_RE_T_MULTI_ADDR_INT
Optional: No
Call by Reference: Yes

ET_MEASUREMENT -

Data type: BAPI_RE_T_MEASUREMENT_INT
Optional: No
Call by Reference: Yes

ET_INFRASTRUCTURE -

Data type: BAPI_RE_T_INFRA_INT
Optional: No
Call by Reference: Yes

ET_PL_MAP -

Data type: BAPI_RE_T_PL_MAP_INT
Optional: No
Call by Reference: Yes

ET_PL_SLIDE -

Data type: BAPI_RE_T_PL_SLIDE_INT
Optional: No
Call by Reference: Yes

ET_PL_USAGE -

Data type: BAPI_RE_T_PL_USAGE_INT
Optional: No
Call by Reference: Yes

ET_PARTNER -

Data type: BAPI_RE_T_PARTNER_INT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for API_RE_PL_GET_DETAIL 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.

ABAP code using 7.40 inline data declarations to call FM API_RE_PL_GET_DETAIL

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