Message number 012 of class IW is used to display message "MRP-relevance will be changed" and can be triggered using the following ABAP code:
MESSAGE W012(IW). "Warning message example
MESSAGE I012(IW). "Information message example
MESSAGE E012(IW). "Error message example See here for more options
What causes this issue
In Customizing under Define Field Selection for Order Operations (PM and CS) you have configured the field Reservation/P.Reqsuch that it is only displayed when control key &V1& is used. Thus, itcannot be used to change the MRP-relevance.
System Response
The MRP relevance is reset depending on the Customizing settings under Define Change Documents, Collective Purchase Requisitions, MRPRelevance and depending on the order status. The system proceeds asfollows:When creating an order:The system sets the MRP relevance, that is currently configured withthe Customizing setting Define Change Documents, CollectivePurchase Requisition, MRP-Relevance.In status created (CRTD):If the MRP-relevance is set to never in Customizing, the systemsets it to never.If the MRP-relevance is set to immediate in Customizing, thesystem sets it to immediate.If the MRP-relevance is set to from release in Customizing, thesystem sets it depending on the activation of the reservation /purchase requisition: If the generation of reservations and purchase requisitions wasactivated manually using the pushbutton Activate Res/PReq (Ctrl+F3), the MRP-relevance is set to immediate.If the generation of reservations and purchase requisitions was notactivated manually, the MRP-relevance is set to from release.In status released (REL):If the MRP-relevance is set to never in Customizing, the systemsets it to never.If the MRP-relevance is set to from release or immediatein Customizing, then the system sets it to immediate.When changing an existing order:The system sets the MRP-relevance that was valid when creating theorder under the Customizing setting Define Change Documents,Collective Purchase Requisitions, MRP-Relevance. This ensures theconsistency of the individual operations within an order, if, forexample, new operations are added and the MRP-relevance in Customizinghas changed in the meantime.In status created (CRTD):If the MRP-relevance in Customizing was set to never forcreation, then the system sets it to never.If the MRP-relevance in Customizing was set to immediate forcreation, then the system sets it to immediate.If the MRP-relevance in Customizing was set to from release forcreation, then it is set depending on the activation of the reservationor purchase requisition:If the generation of reservations and purchase requisitions wasactivated manually using the pushbutton Activate Res./P.Req (Ctrl+F3), or if the activation of the reservation/purchase requisitionwas triggered by the change, then the MRP-relevance is set toimmediate.If the generation of reservations and purchase requisitions was notactivating manually and was not triggered by the change, then theMRP-relevance is set to from release.In status released (REL):If the MRP-relevance in Customizing was set to never duringcreation, the system sets it to never.If the MRP-relevance in Customizing was set to from release orimmediate, the system sets it to immediate.
How to fix
&SYS_ADMIN&
Message text extract from SAP system. Copyright SAP SE.