SAP MOTHER_PLANT_ASSIGN_CHANGE Function Module for Price reference plant assignment in popup
MOTHER_PLANT_ASSIGN_CHANGE is a standard mother plant assign change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Price reference plant assignment in popup 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 mother plant assign change FM, simply by entering the name MOTHER_PLANT_ASSIGN_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIAM
Program Name: SAPLOIAM
Main Program: SAPLOIAM
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MOTHER_PLANT_ASSIGN_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 'MOTHER_PLANT_ASSIGN_CHANGE'"Price reference plant assignment in popup.
EXPORTING
I_MATNR = "
I_PLANT = "
I_VAL_TYPE = "
IMPORTING Parameters details for MOTHER_PLANT_ASSIGN_CHANGE
I_MATNR -
Data type: MBEW-MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_PLANT -
Data type: MBEW-BWKEYOptional: No
Call by Reference: No ( called with pass by value option)
I_VAL_TYPE -
Data type: MBEW-BWTAROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MOTHER_PLANT_ASSIGN_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_i_matnr | TYPE MBEW-MATNR, " | |||
| lv_i_plant | TYPE MBEW-BWKEY, " | |||
| lv_i_val_type | TYPE MBEW-BWTAR. " |
|   CALL FUNCTION 'MOTHER_PLANT_ASSIGN_CHANGE' "Price reference plant assignment in popup |
| EXPORTING | ||
| I_MATNR | = lv_i_matnr | |
| I_PLANT | = lv_i_plant | |
| I_VAL_TYPE | = lv_i_val_type | |
| . " MOTHER_PLANT_ASSIGN_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM MOTHER_PLANT_ASSIGN_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 MATNR FROM MBEW INTO @DATA(ld_i_matnr). | ||||
| "SELECT single BWKEY FROM MBEW INTO @DATA(ld_i_plant). | ||||
| "SELECT single BWTAR FROM MBEW INTO @DATA(ld_i_val_type). | ||||
Search for further information about these or an SAP related objects