S/4HANA Cloud MRP Operations
Manage Planned Orders in SAP S/4HANA Cloud
Use Manage Planned Orders to review, create, change, delete, and convert planning proposals with practical checks for day-to-day MRP operations.
Planned orders are nonbinding procurement proposals. The Manage Planned Orders app supports creating, changing, displaying, and deleting them within its documented scope. Where supported, you can convert a planned order into a production or process order, or into a purchase requisition.
Use the app to resolve a specific planning proposal, then check that its demand, timing, quantity, and intended follow-on document align with your operating process. For a wider view of supply and demand, start with reviewing material coverage; for urgent exceptions, see monitoring MRP shortages.
Choose the right action for the proposal
Treat each planned order as a proposal to assess, not as a confirmed production or purchasing commitment. Before changing or converting it, compare its intended supply with current demand and the relevant operational plan. This helps avoid creating a follow-on document from a proposal that is no longer needed.
Use the available app actions according to the state of the proposal and your process:
- Display the planned order when you need to inspect it before acting.
- Change it when its planning details need adjustment and the proposal remains valid.
- Create one when your process requires a planned order that is not already present.
- Delete it when the proposal should no longer remain in the planning set and deletion is appropriate for your workflow.
- Convert it when the next step is a supported production order, process order, or purchase requisition.
Review and maintain planned orders
- Open Manage Planned Orders from the SAP S/4HANA Cloud launchpad.
- Locate the proposal you intend to work on using the selection and list capabilities available in the app.
- Display the proposal and validate it against the current planning need. Confirm that the proposed supply still makes sense for the intended material, quantity, timing, and operational destination.
- Choose the required action: create, change, display, or delete. Review the proposal again after a change, or before confirming a deletion.
- Record the outcome in your operational handoff or follow-up process so planners and execution teams work from the same decision.
If the proposal no longer matches demand, investigate the planning context before changing it. A planned order can be a symptom of a broader coverage or shortage issue, so review the relevant material position and exceptions rather than adjusting the proposal in isolation.
Convert only after validating the next step
Conversion moves the proposal into a follow-on document, where supported by the app and process. Choose the destination that matches the supply process: production or process execution, or procurement through a purchase requisition. Conversion is an operational handoff, so confirm that the destination is appropriate before proceeding.
After conversion, verify the result through the follow-on process used by your team. Make sure the planned order is no longer treated as an unprocessed proposal and that the resulting document is visible to the responsible execution or purchasing role. If the expected conversion action is unavailable, check that the selected planned order and its business context are eligible for that destination, then confirm the app scope for the system's release.
Troubleshoot common handling issues
The planned order is difficult to locate. Refine the app's selection criteria and verify that you are looking in the correct planning context. If you are investigating a broader supply gap, use the material coverage and shortage views that support your operational review.
The proposal appears outdated. Reassess it against current demand and supply before editing or deleting it. Coordinate with the planner responsible for the material when another planning run or operational action may have changed the context.
A conversion action is unavailable or does not fit the process. Confirm that the intended follow-on document is supported for the selected proposal and that the process calls for that destination. Use the release-specific app documentation when validating the supported scope.
A converted document is not visible to the next team. Check the handoff with the responsible production, process, or purchasing role and confirm that the follow-on document was created and can be accessed through that team's normal process.
Keep planning and execution aligned
A dependable routine is to review the proposal, confirm the need, make only the necessary change, and verify any conversion with the receiving team. This keeps planned orders useful as planning signals while ensuring that follow-on documents reflect current operational decisions.
The referenced Manage Planned Orders documentation describes the app functions and conversion scope for release 2608. Check the documentation applicable to your system when confirming available actions.