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

Function BAPI_RE_MP_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 'BAPI_RE_MP_GET_DETAIL'".
EXPORTING
MOVEPLANID = "
* DETAIL_DATA_FROM = RECA0_DATE-MIN "
* DETAIL_DATA_TO = RECA0_DATE-MAX "
IMPORTING
MOVE_PLAN = "
TABLES
* MP_OCCUPANT = "
* MP_TARGET = "
* MP_OCCPLAN = "
* TEXT = "
* STATUS = "
* EXTENSION_OUT = "
* RETURN = "
IMPORTING Parameters details for BAPI_RE_MP_GET_DETAIL
MOVEPLANID -
Data type: BAPI_RE_MOVE_PLAN_KEY-MOVE_PLAN_IDOptional: No
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_FROM -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROMDefault: RECA0_DATE-MIN
Optional: Yes
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_TO -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TODefault: RECA0_DATE-MAX
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RE_MP_GET_DETAIL
MOVE_PLAN -
Data type: BAPI_RE_MOVE_PLANOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_MP_GET_DETAIL
MP_OCCUPANT -
Data type: BAPI_RE_MP_OCCUPANTOptional: Yes
Call by Reference: Yes
MP_TARGET -
Data type: BAPI_RE_MP_TARGETOptional: Yes
Call by Reference: Yes
MP_OCCPLAN -
Data type: BAPI_RE_MP_OCCPLANOptional: Yes
Call by Reference: Yes
TEXT -
Data type: BAPI_RE_TEXTOptional: Yes
Call by Reference: Yes
STATUS -
Data type: BAPI_RE_STATUSOptional: Yes
Call by Reference: Yes
EXTENSION_OUT -
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RE_MP_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.| DATA: | ||||
| lv_move_plan | TYPE BAPI_RE_MOVE_PLAN, " | |||
| lv_moveplanid | TYPE BAPI_RE_MOVE_PLAN_KEY-MOVE_PLAN_ID, " | |||
| lt_mp_occupant | TYPE STANDARD TABLE OF BAPI_RE_MP_OCCUPANT, " | |||
| lt_mp_target | TYPE STANDARD TABLE OF BAPI_RE_MP_TARGET, " | |||
| lv_detail_data_from | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, " RECA0_DATE-MIN | |||
| lt_mp_occplan | TYPE STANDARD TABLE OF BAPI_RE_MP_OCCPLAN, " | |||
| lv_detail_data_to | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, " RECA0_DATE-MAX | |||
| lt_text | TYPE STANDARD TABLE OF BAPI_RE_TEXT, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS, " | |||
| lt_extension_out | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_RE_MP_GET_DETAIL' " |
| EXPORTING | ||
| MOVEPLANID | = lv_moveplanid | |
| DETAIL_DATA_FROM | = lv_detail_data_from | |
| DETAIL_DATA_TO | = lv_detail_data_to | |
| IMPORTING | ||
| MOVE_PLAN | = lv_move_plan | |
| TABLES | ||
| MP_OCCUPANT | = lt_mp_occupant | |
| MP_TARGET | = lt_mp_target | |
| MP_OCCPLAN | = lt_mp_occplan | |
| TEXT | = lt_text | |
| STATUS | = lt_status | |
| EXTENSION_OUT | = lt_extension_out | |
| RETURN | = lt_return | |
| . " BAPI_RE_MP_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_MP_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.| "SELECT single MOVE_PLAN_ID FROM BAPI_RE_MOVE_PLAN_KEY INTO @DATA(ld_moveplanid). | ||||
| "SELECT single DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_from). | ||||
| DATA(ld_detail_data_from) | = RECA0_DATE-MIN. | |||
| "SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_to). | ||||
| DATA(ld_detail_data_to) | = RECA0_DATE-MAX. | |||
Search for further information about these or an SAP related objects