Planned Purchase Order

This document describes how to work with planned purchase orders and how to release them to purchase orders in M3.

A planned purchase order is a proposal for a purchase order. The planned orders can be created in different ways in M3 both automatically and manually. The proposed values in the planned orders, for example the quantity, can be changed. After release of a planned purchase order a purchase order is created with the values from the proposal.

Outcome

A planned purchase order is created and is released to a purchase order. Planned purchase orders are stored in the MPOPLP table.

After a planned purchase order is released, a purchase order is created with the values from the proposal.

Before you start

Basic settings for the purchase flow must be specified according to the following: .

Different ways to create a planned purchase order

The following section describes the different ways in which a planned purchase order can be created.

The system can automatically create planned purchase orders during an MRP run.
A planned purchase order can be created automatically when a customer order is specified. This is called a customer-order-driven purchase order.
A planned purchase order can be created automatically when a service order is specified.
A planned purchase order can be created automatically when an item is subcontracted.
A planned purchase order is created when a requisition order is specified.
A planned purchase order can be specified manually.

Statuses

Each planned purchase order has a status which indicates its progress in the flow. For example, if the status is 00 then the planned order is stopped due to errors.

The errors can be reviewed through warning messages, which indicate what is missing or wrong in the planned order. If the warning message is a letter, then it is a stop message and the planned order cannot be released until the error is corrected.

If a planned order refers directly to a superior order (such as a direct purchase against a customer order), the planned order status cannot fall below 20.

When the planned order is for a firm planned order, the status is set to 20 at least, except for errors and warnings (status codes 00 and 05 as below).

A manually set status involves setting the status for the planning policy as default release status.

The valid alternatives are:

00 = Automatically assigned to indicate database errors or stop as defined in the message code.
05 = Automatically assigned to indicate a database warning as defined in the message code.
10 = Planned orders and manual status.
15 = Planned orders where the item has several suppliers. Automatic rescheduling of quantity not performed.
20 = Purchase requisitions/planned work orders and manually defined status.
30 = If the planning policy has status 60 (proposal - planned order) and the action is A1, then the status of the planned order is set to 30. Status 30 can also be set manually.
40 = Manual status.
50 = Manual or automatic status. The amount requires authorization processing.
55 = Automatically assigned when inquiries are created.
60 = Manual or automatic. Released to create purchase/work order.

Origin (Generation reference)

The Origin (Generation reference) field on the planned purchase order indicates how the planned order was created. For example, a value of 29 in this field means that the planned purchase order was created from a purchase requisition.

The valid alternatives are:

10 = Planned manufacturing order
18 = Manufacturing order, manually specified
20 = Planned purchase order
21 = Planned purchase order, generated through manufacturing order
22 = Planned purchase order, generated manufacturing order and subcontract order
23 = Planned purchase order, generated through customer order, not a direct delivery
24 = Planned purchase order, generated through customer order, direct delivery
26 = Planned purchase order, generated through maintenance order
27 = Planned purchase order, generated through material requisition
28 = Manually specified in the planned order routine
29 = Manually specified in the purchase requisition routine
30 = Planned purchase order, direct purchase
33 = Planned purchase order, generated through service order, not a direct delivery
34 = Planned purchase order, generated through service order, direct delivery
38 = Planned purchase order, generated through project order
40 = Planned purchase order, generated through e-Procurement
41 = Planned purchase order, generated through Scheduling Workbench
50 = Planned distribution order
58 = Distribution order, manually specified
60 = Planned maintenance order
61 = Deferred planned maintenance work order
62 = Forecast orders
63 = Maintenance work order, from removal
64 = Maintenance work order, historical (pre M3)
65 = Maintenance work order, from MOS326
66 = Maintenance work order, position based which has equipment updated in MOS070
67 = Maintenance work order, from condition based maintenance
68 = Maintenance work order, manually specified
69 = Maintenance work order, from inspection.