Implementing Action Logs and Correcting Possible Errors

This document explains how you update data in M3 Business Engine (BE) so it reflects decisions made during a planning session in an external planning system.

This is done by implementing the actions in the action log that was transferred from the external system to M3 BE.


The data in M3 BE is changed and updated, so that manufacturing and/or further planning can proceed.

If the action log is not closed, you can transfer the actions that were not implemented to the external system so that they can be a part of the next planning session. This is done automatically when importing M3 BE data to the external system. (The API transaction that is automatically used is ListLine in API program CMS051MI.)

These are the impacts on the system:

Before you start

Follow These Steps

  1. Implement Actions Automatically

    All actions that are defined to be automatically implemented are implemented when the action log is exported from the external planning system to M3 BE. The export/implementation is triggered by the API transaction Implement in API program CMS051MI.

    The implementation of actions is carried out in the same sequence as the planning decisions were made in the external system.

    If all actions in the action log were successfully implemented, the action log is automatically set to 90 (Closed) and the implementation phase is concluded.

    Note that this activity is triggered by the person responsible for the planning in the external system.

  2. Analyze and Correct Possible Errors

    If the automatic implementation failed for one or more defined actions or if the action log contained open actions, the responsible person will receive the application message “Action log could not be fully implemented” (958) in ‘Application Message. Open’ (CRS420), if the functionality is activated.

    To identify what went wrong, the responsible person can do the following:

    • Get a quick overview of the (first) error for an action, by reading the message that is automatically created for the action in the ‘Return data’ field in ‘Actions. Open’ (CMS051).
    • Analyze all errors that occurred for the action log by reading the detailed messages in ‘Detailed Mail Message. Open’ (CMS421). These messages describe the errors and contain information about which functions the errors originate from. If you select the related option Open for a message, you open the M3 BE function where the error can be corrected. Which function is open depends on the type of error. (CMS421) can be accessed from ‘Application Message. Open’ (CRS420), ‘Action Log. Open’ (CMS050), or ‘Actions. Open’ (CMS051).

    When you have analyzed what went wrong, you need to make a decision about how to proceed and correct the error. What you do depends on the error itself and the individual situation. For example, if the detailed message states that the planning date is invalid you might choose either not to implement the action but send it back to the external system to be a part of another planning session, or you might change the planning date for the action in (CMS051) and manually trigger a reimplementation for the action.

    If the automatic implementation of an action has failed, the status is set to 00 (Error) for the action itself and for the action log.

  3. Implement All Defined Actions Manually

    When you have corrected the errors, you can manually trigger an automatic reimplementation of all defined actions with a status less than 90 (Closed) for the action log.

    You do this by selecting the option Implement for the action log in (CMS050).

  4. Implement a Single Defined Action Manually

    If the correction only referred to one or two actions, you might instead prefer to manually trigger the automatic reimplementation of actions one by one.

    You do this by selecting the option Implement for the action in (CMS051).

    When you reimplement actions individually, there is one important factor to consider: If the action refers to a macro order and the macro order has been changed in M3 BE after it was transferred to the external system, a warning message will normally be issued and the implementation is interrupted. If you implement a single action, however, the implementation will be carried through nevertheless.

  5. Analyze Open Actions

    If there are any open actions in the action log, the responsible person will receive an application message in (CRS420) notifying him that the action log was not fully implemented, as long as the application message functionality is activated.

    These actions must be managed manually since they refer to a problem that needs to be solved rather than a decision. The problem is described in the action text in (CMS051).

    Open actions have status 20 (Not implemented) and implementation method 1 (Manually) in (CMS051).

  6. Implement Open Action Manually

    Implement the decision you have made manually in M3 BE. How you proceed depends on the problem itself and the resources that are available. For example, if the action refers to a capacity problem when it comes to manufacturing an item at a specific work center, the solution might be one of the following: Add extra shifts for the work center, outsource the manufacturing of the item, or delay the demand.

  7. Set Open Actions as Implemented

    When the open action is implemented, you must manually change the status of the action to 90 (Closed).

    You do this by selecting the option Implement for the action in (CMS051).

Related topics