Events can be defined to trigger certain activities. You can combine them with milestones to monitor your projects.
Beas has an own event control system that can generate a message or action about any event that can occur in SAP or Beas.
An action is not just a message. It also provides the possibility to make up to three different decisions, e.g. to grant a release, to provide more information or simply as a confirmation.
See News
For certain events, the event control can also have a direct influence on the action, e.g. block or influence an operation.
Which events can Beas react to:
- any type that is associated with capturing data
- any type that is associated with not capturing data
How can Beas react:
- SAP Business One text message
- SAP Business One activity with decision-making functions
- beas activity with decision-making functions
- user-defined action
Beas is supplied with a catalog of predefined events. This also suggests sensible interactions that simplify setup.
What can be represented?
Here are a few examples:
- A person changes something in the item master. Another person must be informed and s/he checks the changes.
- Work order is printed: Message to the production manager, who has to release this for production.
- delivery date of the production order is changed. delivery date as per contract can no longer be met: message to the sales department
- production order is registered for the first time. Message to the sales department and to the customer via email.
- Block work order completion message if full quantities were not reported, including message and release options
- Email to customers when supplying delivery note
- Message to production manager when goods arrive in the goods receipt
- Message to organization manager when an action occurs in a work sequence connected to a milestone or a milestone is exceeded.
- Message incl. actions when warehouse stock is exceeded
An action can also generate another action, whereby a work flow can also be represented.
Because everything can be freely defined in this area, all requirements can be represented.
What can the system not do?
SAP Business One offers a release approval procedure. All entries (e.g. the order) are saved as draft documents and must be released by another person. The draft document is saved as the correct order.
This kind of release approval procedures are not possible here. Processes can be saved but "intermediate storage" of the entries and changes is not possible.
Training slides on event control