Macro Orders

This document explains what a macro order is, how and why it is used, how it is created, and how its content (materials and operations) is aggregated into the macro order.


Understanding the macro order functionality can help you working with macro orders and carry out planning in M3 Business Engine (BE) and M3 Planning Workbench (M3 PWB).

Information about macro orders is saved in the following tables:

Before you start

To use macro orders, the functionality must be activated and basic settings must be defined. This process is described in Enabling Macro Orders.

What Is a Macro Order?

A macro order is an aggregated order that summarizes information from several manufacturing orders and/or supply chains that refer to the same group of items.

Macro orders can be used for planning purposes if M3 PWB is integrated with M3 BE. Macro orders are especially suited for planning performed on a medium-term horizon or long-term horizon.

Why use Macro Orders?

The planner's work in M3 PWB is considerably simplified by macro orders for the following reasons:

One effect of this is that system performance is improved and the transfer time to M3 PWB greatly reduced.

Basic facts about Macro Orders

An order or supply chain can automatically be connected to a macro order if the order or supply chain meets the following conditions:

When the content of the macro order is generated, only the materials and operations from the connected orders and/or supply chains that are considered critical are aggregated. The content can be regenerated whenever needed, which means that the information in the macro orders always is kept up to date.

The aggregation rules are user defined. This makes it possible to tailor the macro orders according to the planning requirements and routines at your company.

Processing Macro Orders

The following section provides an overview of how the macro orders are processed through the system.

  1. Macro orders are generated and maintained in M3 BE. The macro order header and its relation to orders and/or supply chains are generated automatically, while the information about materials and operations can be generated both automatically and manually. A number of programs further described below are used for this.

  2. The macro orders are then transferred to M3 PWB as API transactions. The program used for this purpose is RPS300MI.

  3. The planner in M3 PWB uses the macro orders for planning. The results of the planning are different types of decisions. Examples of decisions are to change planning dates or to move the entire production of an item or parts of the production to another date.

  4. When the planning has been carried out, only the decisions that were made – and not the macro orders themselves – are sent back to M3 BE. This is done in the form of an action log. The API program used for this purpose is CMS050MI.

  5. The action log is then displayed in M3 BE and the decisions are implemented. The concept of the action log is not further described in this document.

The building blocks of Macro Orders

This section describes the building blocks of a macro order as well as when the different blocks are generated and where they are displayed.

Creating Macro Order header and Macro Order relations

Every time a manufacturing order or supply chain is created in M3 BE, a check is made to determine whether or not the order should be connected to a macro order. For a connection to take place, one of the following conditions must be met:

The following flow chart describes how the macro order header is created and how an order or supply chain is connected to the macro order:

  1. Retrieving Macro Order policy

    The macro order policy for the new order or supply chain item is retrieved.

  2. Checking if an existing Macro Order can be used

    A check is made to determine whether or not the new order or supply chain can be connected to an existing macro order. All conditions must be met for the connection to take place.

    • Is there a macro order in status 10 or 20?
    • Is there a macro order with macro order type 001? (In the current version of the system, this is the only valid type.)
    • Do they have the same macro order policy?
    • Do they have the same facility/warehouse?
    • Do they have the same ID for the item level that has been selected for the macro order policy?
    • If the aggregation is done for each customer, do they have the same customer number?
    • If the aggregation is done on a sublevel to the item level (according to the macro order policy), do they have the same attribute values?
    • Do they have the same order status, that is, preliminary or definite?
    • Does the order have a finish date – or the supply chain a due date on the top-level demand – that is later than the bucket start date and earlier than the bucket end date?
  3. Creating a new Macro Order

    If not all conditions are met, a new macro order is created. The macro order automatically receives the following:

    • A macro order number, according to the macro order number series in 'Number Series. Open' (CRS165).
    • Key values mentioned in the check above.
    • A time frame, according to the bucket lengths set in 'Settings – Macro Order' (RPS800).
    • Group technology, free item fields 1 to 5, item hierarchy 1 to 5, planning entity, procurement group, and schedule number from the item to which the order refers.

    Error Management

    In certain situations, the item level for the macro order can be automatically changed to the item number (MMITNO) instead of the item level on the macro order policy. This happens if an item that is connected to a macro order with

    • main product (MMHDPR) as the item level is not a stocked variant (that is, the item does not have configuration code 3).
    • planning entity (NHCCIT) as the item level is not connected to a planning entity.

    A message about the change of item level is then logged in 'Detailed Mail Message. Open' (CMS421).

  4. Connecting order or supply chain to Macro Order

    When the procedure above is completed, the order or supply chain is connected to a macro order.

    Manufacturing orders are always connected one by one, while a supply chain is always connected as a whole, using the supply chain number.

Generating Macro Order details

When the macro order details are generated, it affects not only the materials and operations. All of the components in the macro order are affected. The effects are described below.

Related topics