1. SCENARIO DESCRIPTION:
You are running the MRP in Beas as a Planned activity and it randomly crashes.
Here’s a list of the preliminary checks we would require and report to the support desk when submitting a ticket for such a scenario.
1) Check that the Beas service is running in the windows services with an account with the highest privileges. If you’re in a domain, a domain administrator account would be ideal. Please check the account Log-On information on the windows services screen in the windows services:
2) Check the windows Event viewer for the Beas service responsible for running the MRP planned activity. You can do this by:
Checking the Beas executable for the planning activity in the Beas Manage Server:
This setting will match the windows service name:
3) Send an attachment screenshot with the latest events reported in the Beas event log to the Beas support desk. You can access this by clicking here:
The Beas event log will report all MRP planned activities runs as you can see in the screenshot below:
4) Send the Windows event viewer report for the Beas service responsible for the planned activity. You can access this from the windows Event viewer:
Ideally, you should see no errors on this screen.
- Make sure that ONE separate Beas service is marked for planned activities execution.
- Make sure that ONE MRP SCENARIO IS separately MARKED FOR AUTOMATIC EXECUTION. This can be checked here:
By default, Beas will run ALL MRP scenarios that are marked for Automatic calculation. This might be resource intensive and, therefore, can lead to system hangs. We recommend having ONLY one MRP scenario set for automatic calculation.
- Make sure that the MRP scenario set for automatic calculation by the planned activity IS NOT RUN MANUALLY by any other user logging into the Beas client WHILE THE PLANNED ACTIVITY IS STILL RUNNING.
- Make sure that the DI API connection for Beas is set-up properly and tested.