Do you have any question about this error?
Message type: E = Error
Message class: MD - Material Requirements Planning (MRP)
Message number: 132
Message text: Simulation planned orders cannot be converted
The planned order selected is a simulative planned order from long-term
planning. In long-term planning, the system only creates planned
orders. These planned orders are not converted into either production
orders or purchase requisitions.
Planned orders that are created in long-term planning cannot be
converted. They are used to check the effects of the simulative demand
program on production and procurement. Thus, a preview is availble of
the planned demand program.
The planned orders are changed or replanned in the operative planning
run.
Error message extract from SAP system. Copyright SAP SE.
MD132
- Simulation planned orders cannot be converted ?The SAP error message MD132, which states "Simulation planned orders cannot be converted," typically occurs in the context of the Material Requirements Planning (MRP) process when attempting to convert planned orders into production orders or purchase requisitions. This error indicates that the system is unable to convert planned orders that are marked as "simulation" or "not firm."
Causes of MD132 Error
Simulation Mode: The planned orders you are trying to convert are in simulation mode. This means they are not intended for actual production or procurement and are used for planning purposes only.
Order Type Restrictions: The order type of the planned order may not allow conversion. Some order types are specifically designated for simulation and cannot be converted.
Missing Data: Required data for conversion may be missing, such as material availability, routing, or BOM (Bill of Materials) information.
Status of Planned Orders: The planned orders may have a status that prevents conversion, such as being marked as "not firm" or "not released."
Configuration Issues: There may be configuration settings in the MRP or production planning module that restrict the conversion of planned orders.
Solutions to MD132 Error
Check Order Type: Verify the order type of the planned orders. If they are in simulation mode, you may need to create actual planned orders instead.
Firm Up Planned Orders: If the planned orders are not firm, you can firm them up using the appropriate transaction (e.g., MD04 or MD02) to ensure they can be converted.
Review Required Data: Ensure that all necessary data for conversion is available and correct. This includes checking material master data, routing, and BOM.
Use Correct Transaction: Make sure you are using the correct transaction for converting planned orders. For example, use transaction CO40 for converting planned orders to production orders.
Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to planned order conversion.
Check for User Exits or BAdIs: Sometimes, custom logic implemented through user exits or BAdIs may affect the conversion process. Review any custom code that may be impacting this functionality.
Related Information
By following these steps, you should be able to identify the cause of the MD132 error and implement a solution to convert your planned orders successfully.
Get instant SAP help. Start your 7-day free trial now.
MD131
Simulation planned orders cannot be changed manually
What causes this issue? The planned order that was selected is a simulative planned order from long-term planning.System Response Planned orders tha...
MD130
You do not have the necess.authorization for this function (see long txt)
What causes this issue? To carry out this activity in long-term planning, you require the appropriate authorization. This must contain the values &am...
MD133
Simulation planned orders cannot be firmed
What causes this issue? The planned order that was selected is a simulative planned order from long-term planning.System Response Planned orders tha...
MD134
Multi-level replacements are not possible
What causes this issue? You specified that version &V1& is to replace version &V2&. On the other hand, version &V2& is to rep...
Click on this link to search all SAP messages.