Define a Macro Order Policy

Order aggregation from a product dimension

…the item level to use when orders or supply chains are connected to a macro order.

Valid alternatives

MMITNO = The item number is used. Only orders or supply chains with the same item number can be connected to the same macro order.

MMHDPR = The main product is used. Only orders or supply chains with items connected to the same main product in 'Item. Open' (MMS001/G) can be connected to the same macro order.

NHCCIT = The planning entity is used. Only orders or supply chains with items connected to the same planning entity in 'Planning Entity. Connect Items' (RPS046) can be connected to the same macro order.

MMITCL = The product group is used. Only orders or supply chains with items connected to the same product group in (MMS001/E) can be connected to the same macro order.

MMITGR = The item group is used. Only orders or supply chains with items connected to the same item group in (MMS001/E) can be connected to the same macro order.

MMPRGP = The procurement group is used. Only orders or supply chains with items connected to the same procurement group in (MMS001/E) can be connected to the same macro order.

&AL84 to &AL87 = The alias type is used. Only orders or supply chains with items connected to the same alias type in (MMS024) can be connected to the same macro order.

Note

The value you select here also affects the item level used when planning in M3 Planning Workbench (M3 PWB).

Ensure that the value you select does not lead to the aggregation of items with different basic units of measure into the same macro order.

… the ID of the attribute that will be used to select which orders or supply chains are aggregated into the same macro order.

Up to six attributes can be specified.

The attribute fields are only used if the macro order should be created on a sublevel to the item level defined in the Qualifier field. Only orders or supply chains that qualify according to the Qualifier field and have the same value for the selected attribute IDs will then be aggregated into the same macro order. This can be useful if you want to perform aggregation on, for example, main fashion product and color.

Note

If the aggregation refers to supply chains, the attribute information is retrieved from the top demand level.

If an order or supply chain does not have the attribute ID, then blank (or zero) is selected as the attribute value during the aggregation check.

Order aggregation from a demand dimension

… whether firm-planned manufacturing orders (status 20) should be aggregated into separate macro orders.

If the check box is not selected, then firm-planned manufacturing orders and released manufacturing orders are aggregated into the same macro order. If the check box is selected, then a firm-planned manufacturing order will be reconnected to a new macro order when the firm-planned manufacturing order is released.

Note that this activation should only be used if firm-planned manufacturing orders must be planned separately from released orders. Normally this is not the case.

Also note that this separation into different macro orders is not valid for firm-planned manufacturing orders that are connected to a supply chain. A supply chain is always treated as a released order. The only exception to this rule is if the planned manufacturing order is connected to the supply chain and set to be the lowest level of the supply chain.

… whether the macro order will be aggregated for each customer number.

If this is selected, only orders connected to the same customer will be aggregated into the same macro order.

Note

This check box is only used if orders are generated by supply chains with a customer order as a top-level demand. In other cases, the customer number will not be retrieved.

… whether the macro order will be aggregated per order number.

If this is selected, only orders connected to the same order will be aggregated into the same macro order.

Note

This check box is only used if orders are generated by supply chains with a customer order as a top-level demand. If used otherwise, there will be a one-to-one relation between the order and the macro order.

Content aggregation from a material dimension

… the item level to use when you aggregate materials in a macro order.

Valid alternatives

MMITNO=Item number is used. Only materials (in the orders that have been selected to be aggregated) with the same item number can be aggregated to the same line in a macro order.

Note

The value you select here also affects the item level of the material lines used for planning in M3 PWB.

It is recommended that you select the same item level in both Qualifier fields (that is, for both the macro order header and the materials and operations) if the same item number can exist both on the header and on the material. This is often the case if your company does not use supply chains or single-level order networks.

… the ID of the attribute that will be used to select which materials from orders and/or supply chains should be aggregated into the same macro order material.

These fields are only used if the material line in a macro order should be created on a sublevel to the item level defined in the Qualifier field. Only materials that qualify according to the Qualifier field and have the same value for the selected attribute identities will then be aggregated into the same material line.

Note

If the material does not have the attribute ID, then blank (or zero) is selected as the attribute value during the aggregation check.

It is recommended that equivalent attributes are used for both the macro order header and the materials if the same item number can exist on both the header and the material. This is normally the case if your company does not use supply chains or single-level order networks.

The material synchronization in M3 PWB will not function if you select attributes here.

Content aggregation from a work center dimension

… if the aggregation will be performed for each work center and operation number.

If the check box is not selected, the aggregation will be performed only for each work center.

Note

The aggregation is always done on a work center resource of type 1 (Operation). If the operation is defined with work center resource type 6 (Work center resource), the work center with resource type 1 that it belongs to is automatically retrieved from 'Work Center. Open' (PDS010).