SAP BAPI_RE_MP_CHANGE Function Module for









BAPI_RE_MP_CHANGE is a standard bapi re mp change 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 change FM, simply by entering the name BAPI_RE_MP_CHANGE 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_CHANGE 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_CHANGE'"
EXPORTING
MOVEPLANID = "
* MOVE_PLAN = "
* MOVE_PLAN_X = "
* TRANS = "
* TEST_RUN = ' ' "

TABLES
* MP_OCCUPANT = "
* MP_TARGET = "
* MP_OCCPLAN = "
* TEXT = "
* STATUS = "
* EXTENSION_IN = "
RETURN = "
.



IMPORTING Parameters details for BAPI_RE_MP_CHANGE

MOVEPLANID -

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

MOVE_PLAN -

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

MOVE_PLAN_X -

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

TRANS -

Data type: BAPI_RE_ADDITIONAL_FIELDS-TRANS
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEST_RUN -

Data type: BAPI_RE_ADDITIONAL_FIELDS-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_RE_MP_CHANGE

MP_OCCUPANT -

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

MP_TARGET -

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

MP_OCCPLAN -

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

TEXT -

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

STATUS -

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

EXTENSION_IN -

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

RETURN -

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

Copy and paste ABAP code example for BAPI_RE_MP_CHANGE 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_moveplanid  TYPE BAPI_RE_MOVE_PLAN_KEY-MOVE_PLAN_ID, "   
lt_mp_occupant  TYPE STANDARD TABLE OF BAPI_RE_MP_OCCUPANT_DATC, "   
lv_move_plan  TYPE BAPI_RE_MOVE_PLAN_DAT, "   
lt_mp_target  TYPE STANDARD TABLE OF BAPI_RE_MP_TARGET_DATC, "   
lt_mp_occplan  TYPE STANDARD TABLE OF BAPI_RE_MP_OCCPLAN_DATC, "   
lv_move_plan_x  TYPE BAPI_RE_MOVE_PLAN_DATX, "   
lt_text  TYPE STANDARD TABLE OF BAPI_RE_TEXT_DATC, "   
lv_trans  TYPE BAPI_RE_ADDITIONAL_FIELDS-TRANS, "   
lt_status  TYPE STANDARD TABLE OF BAPI_RE_STATUS_DATC, "   
lv_test_run  TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN, "   SPACE
lt_extension_in  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_RE_MP_CHANGE'  "
    EXPORTING
         MOVEPLANID = lv_moveplanid
         MOVE_PLAN = lv_move_plan
         MOVE_PLAN_X = lv_move_plan_x
         TRANS = lv_trans
         TEST_RUN = lv_test_run
    TABLES
         MP_OCCUPANT = lt_mp_occupant
         MP_TARGET = lt_mp_target
         MP_OCCPLAN = lt_mp_occplan
         TEXT = lt_text
         STATUS = lt_status
         EXTENSION_IN = lt_extension_in
         RETURN = lt_return
. " BAPI_RE_MP_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_RE_MP_CHANGE

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 TRANS FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_trans).
 
 
"SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_test_run).
DATA(ld_test_run) = ' '.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!