Life Cycle of Actions

The life cycle of an action/action log is mainly handled by the status. The status is updated when an action is implemented. This status can achieve these values:

Status for Action log header

Error occurred during implementation (00)
No actions have been implemented (20)
Contains both implemented and non-implemented actions (60)
Implementation of actions are in progress (80)
All actions has been successfully implemented (90)

Status for Actions

Error occurred during implementation (00)
The action has not been implemented (20)
Implementation is in progress (80)
Implemented (90)

Life Cycle of an Action

To avoid complications during implementations of actions it is recommended that only one live action log exists per user and role or sub-set of data.

Note: There is no validation that this is the case so it must be handled in the process between the client and the Infor M3 BE.

As an example of this process, the new Infor M3 SWB planning tool is starting a new planning session by first uploading all non-implemented actions for the same user/role. These actions are then re-implemented in the planning process. When the new planning has been finalized a new action log is created in the M3 BE, which might contain same actions that where uploaded in the beginning if they are still relevant. When the new action log has been transferred the old one is closed through a separate API-transaction.