Processing Action Logs

This document explains how you process information about planning decisions that were made in an external planning system and how you implement those decisions in M3 Business Engine (BE).

This process is carried out by using action logs. An action log is a log containing all decisions made in the external system in the form of actions.

Outcome

The affected data in M3 BE is changed so it reflects the decisions made. This means that the manufacturing process can take place according to the planning done in the external system. For more details, see reference documents listed in the See also section.

Before You Start

Follow These Steps

Note: The activities in this process are carried out in different systems. This usually means that the activities are performed by different people and roles as well.
  1. Export Action Log from External System to M3 BE (mandatory)

    When a planning session is performed and completed in the external planning system, the result of the planning is exported to M3 BE as an action log.

    This is done via API program CMS051MI, which is manually started by the person in the external system. (When the export is triggered, the API transactions CreateHeader, CreateLine, CloseAction, and Implement are started.)

  2. Implement Actions in M3 BE (mandatory)

    The data in M3 BE that is affected by the decisions made during the planning sessions needs to be updated in M3 BE. This is done by implementing the actions in the action log.

    This step is carried out automatically when you export the action log to M3 BE for all actions that are defined to be automatically implemented (according to the action type in CMS109).

    All implemented actions are automatically set to status 90 (Closed). If the entire action log is successfully implemented, its status is set to 90 (Closed) and the implementation process is completed.

    The action log is displayed in 'Action Log. Open' (CMS050).

  3. Correct Errors and Implement Actions Manually (mandatory)

    If some actions were not implemented, they must be processed manually. The responsible person can be notified of this by an automatically generated application message.

    An action might be open for the following reasons:

    • The action is not a defined decision, but points out a problem that needs to be solved. These actions must always be processed manually.
    • The automatic implementation failed.

    The responsible person must analyze the possible errors or problems to be solved, and then correct the errors or implement the decision.

  4. Perform New Planning Session in External System

    This step is included to describe how to ensure that only one action log is open per user and role.

    Note: It is recommended that you only have one open action log per responsible user and role. By doing so, you avoid situations where decisions in an action log are based on data that has been changed in M3 BE after it was transferred to the external system where the decisions were made.

    Basic data from M3 BE is transferred to the external system the next time a new planning session is about to start.

    If the action log is still open, the actions that are not implemented are transferred back to the external system by using the API transaction ListLine in CMS051MI.

  5. Export New Action Log to M3 BE

    This step is included to describe how to ensure that only one action log is open per user and role.

    Note: It is recommended that you only have one open action log per responsible user and role. By doing so, you avoid situations where decisions in an action log are based on data that has been changed in M3 BE after it was transferred to the external system where the decisions were made.

    When the planning session is performed and completed, the result of the planning is exported back to M3 BE as an action log as described in activity 1. Note that this new action log might contain actions that were included in the previous action log.

    The API transaction CloseAction in CMS051MI can be used to close the previous action log. The API transaction performs a check to ensure that there is no open action log for the same user and role. If an open action log exists, that action log is automatically closed.

Related topics