Action Logs in Manufacturing

This document explains the concept of action logs in M3 Manufacturing Operations and M3 Supply Chain Planning, as well as how the actions in the log are implemented in M3 Business Engine (BE). The document also contains a list with all actions available in the current version of the system.


Understanding action logs in manufacturing can help you working with planning related manufacturing in M3 BE and external planning systems, such as M3 Planning Workbench and M3 Assortment Replenishment Planner.

What is an action log?

An action log is a log containing either of the following:

Examples of decisions are to split a macro order or change a planning date. Problems that need to be solved can refer to an overload of demand for a certain item.


The action log is used as the communication channel between an external planning system (such as M3 Planning Workbench and M3 Assortment Replenishment Planner) and M3 BE.


The advantages of using action logs include:


The action log is used in the following cases:

All communication related to the action log is done through API transactions, via the API program CMS051MI.

The building blocks of an action log

The action log consists of:

Implementation sequence

When they are exported, all created actions are assigned a sequence number that corresponds to the order in which the decisions were made. The automatic implementation is carried out in the same order in which the decisions were made. This ensures that the actions are not implemented in an incorrect order, for example that an order is not moved to a new macro order before the new macro order is created.

The order sequence is controlled by the decision date, decision time, and suffix for the action. (All these values are set automatically by the external system when the actions are created.) The suffix is only used if actions were created at the exact same date and time.

Implementation rules in action type

The action type that is connected to each action controls how the implementation is performed.

Note that the action types are predefined. They are displayed in 'Action Type. Open' (CMS109). It is not possible to change the function that performs the actual implementation. However, it is possible to make other changes, such as whether or not the actions should be automatically implemented.

Implementation Method

The implementation method controls whether the action should be implemented automatically in M3 BE or manually.

Normally, defined actions are implemented automatically. Open actions must always be implemented manually.

Implementation Function

If the action is automatically implemented, this is the function that performs the implementation.

Implementation Error Control

The error control determines what happens if the automatic implementation of an action fails. There are three valid alternatives:

Normally, this field is always set to stop implementing all actions that are related to the same decision. A practical example of why this is normally the recommended alternative is the decision to split a macro order. This decision consists of the action to create a new macro order and actions for moving existing orders to the newly created macro order. If the action to create a new macro order fails, the actions to move orders should not be implemented since they will also result in errors.

Decision information in actions

Some fields displayed for the action in 'Actions. Open' (CMS051) can be useful when working with the implementation. These fields are 'Decision type', 'Decision reference' and 'Decision reference type'.

Defined actions for M3 Planning Workbench

Open actions for M3 Planning Workbench

Defined actions for M3 Assortment Replenishment Planner (M3 ARP)

Related topics