Action Log
In an interaction between a client based planning system and Infor M3 BE there are two main challenges. One is the data volume of the transfer and the second is the visibility on which changes that have been performed in the database due to decisions made in the planning system.
The new Infor M3 BE planning solution is designed around decisions as a central concept. A decision normally results in several actions that has to be taken to data in the Infor M3 BE database. This in conjunction with the two above statements resulted in the new concept, action log, to receive the result from the planning. This new concept results in the following:
- The result from the planning is transferred as actions, not orders
- Minimized data volumes in the transfer
- Facilitates a life cycle of decisions and actions
- Facilitates a multi level planner structure because made decisions and corresponding actions can be viewed by other
- Possibility to keep a history, especially useful during testing
- Adds visibility to the taken actions – not a black box.
Requirements
- Minimized Data Volume
The transferred data volumes must be minimized to get highest possible performance in the communication
Solution: Only the actions are transferred. An action contains the required keys to the Infor M3 BE database and the result from the action.
- Simple Addition of
Additional Decisions
Adding new valid actions to the action log must be simple.
Solution: The valid actions are defined in a separate function. A definition of an action includes the required fields to be sent and the function to be used for the implementation of the action in the Infor M3 BE database (if it is automatically implemented).
- Facilitate a Life Cycle of
a Decision
Each decision has a life cycle, from the decision is made up to the point when the necessary actions has affected relevant data. The life cycle can be quite short for some decisions while for others it can stretch across multiple planning sessions.
Solution: All actions are stored in the action log together with status information. The status reflects if an action has been implemented to the database or not. Non-implemented actions can be uploaded to the planning tools through a API-transaction and can affect the new planning session.
- No Black Box Planning
There must be a good visibility of what have been affecting the data in the Infor M3 BE database.
Solution: All actions are stored in the action log and can be kept as history.
Solution
Action Log
An action log contains all actions that are a result of made decisions in a client system. Apart from defining what to be done it also defines the order in which the actions must be implemented. This information is crucial because the implementation otherwise could end up in impossible situations where required data is not yet created, etc.