MRP on a schedule

Kinetic ERP
, ,
1

Hi All,

I’m not sure if this is a bug.

When I use the browser UI or Classic UI or Kinetic UI and set MRP to run on a schedule and select Logging Level MRP and Scheduling I receive an error:
Business Layer Exception

Logging Level should be Basic or MRP when process is not scheduled for Immediate Run

Error Detail

Correlation ID: c1e3bd7d-bd21-43ba-8ad7-9fcaece55423
Description: Logging Level should be Basic or MRP when process is not scheduled for Immediate Run
Program: Erp.Services.Proc.MRP.dll
Method: ExValidateParam
Table: Logging Level
Field: undefined

I have a script that I run on my MRP Logs that scans for errors and presents planning staff with email alerts.
I have lost this functionality now because of this ‘bug’.

Does anyone else have this issue?

Roberto

2 Likes
2

I have seen the same thing when I try and run MRP with MRP logging turned on. I am not sure if it was a bug.

3

We run it on a schedule with logging and aren’t seeing this. Are you cloud or on-prem?

4

Same here.

5

We too have logging enabled (MRP and Scheduling, Split) and also do not have this issue with our scheduled MRP. We are on cloud.

To note, we used to schedule MRP by itself. Now I include it in a process set. Neither method has had an issue with logging enabled.

6

Hi @chaddb - we are On Premise.

7

I have raised a case with Epicor support because based on the feedback here it is 100% a bug.
This bug has only appeared on version 2024.2.9.

8

We’re on 2024.2.10 and don’t have any issues running MRP. I don’t have access to the change log right now. Have you looked there to see if a fix was put in place for the .10 patch?

9

I think we are 2023.2.21? Just parched from .17.

10

Back from Epicor Support:
ERPS-241466-When MRP generates log files, it can generate thousands of files each run if the wrong logging levels are set.
When submitting MRP to anything but Immediate run, limit the Logging Type = Override and Logging Level to either Basic or MRP.
Also need to limit the logging when submitting to a Process Set
Enhancement Version: Kinetic 2024.1

I’m confused by this response as a numbe of users on this topic contradict this.

Can everyone confirm they are able to run MRP on a schedule with logging level MRP and Scheduling please, and post your version.

11

That makes no sense. We do full logging all the time. I wonder if it’s because we already had it scheduled? Let me test it with a new schedule.

1 Like
12

I can confirm I am seeing this in 2025.1.12. I think we did not notice because our MRP schedules were already scheduled to run with MRP logging level prior to whenever they changed this.

This is a huge travesty. So now if I have an MRP issue, I should run MRP ALL OVER AGAIN which takes HOURS just to get a fucking log file? Really Epicor? I have no words for the laziness and sloppiness of this solution. This is outrageous.

There have been requests for many years to have better MRP log management. On prem, its not a huge issue since its a trivial task to write a ps script to clean them up. In cloud, they quickly grow out of control - we had our system crash several times due to out of disk space.

Cloud ops themselves are not capable of keeping the epicor data directory cleaned up despite claiming that they clear your files after 30 days. I recently spent 2 months going back and forth on a support case begging and pleading for them to clear the old files. They finally did, but only in our production environment, and they wouldn’t clear the empty folders, and I am just supposed to open yet another case if I need it cleaned up again.

This is typical Epicor:

  • Completely ignore customer need (log file management) for many many years
  • Come up with a lazy shortcut solution to address their own operations concerns, completely ignoring customer requirements
  • Implement the new functionality silently
  • Gaslight anybody who complains about it

Now I am curious to see if anybody is able to force the systask params back to MRP or MRP and scheduling via function or UBAQ after the task is scheduled, to get around this absurdity.

3 Likes
13

You should be able to do this via UBAQ. We have one designed to update tasks for when positions/personnel change. When we move to Kinetic, I plan on doing an App that lets you update all the parameters.

1 Like
14

Extremely lazy and done with zero regard to Customers.

To make matters worse:

  1. I ran MRP using the browser UI and selected logging level as MRP and Scheduling for a specific Part - the logs did not generate and the Unfirm Job did not get created.
  2. I ran MRP using the Classic UI and selected logging level as MRP and Scheduling for the same Part - the log files were created but did not get populated and the Job did get created.

It’s like using a piece of software kids put together for a school assignment.

No QA, riddled with bugs and no regard to Customer requirements.

I’ve been using Epicor for 13 years since 9.05.702A and the number of bugs I encounter is increasing.

The only other thing increasing is Epicor’s requests for us to pay for ‘enhancements’.

5 Likes
15

Was this immediate run or scheduled run? If I do immediate I get the log files.

1 Like
16

Sharing is caring. :face_blowing_a_kiss:

17

I can confirm this in 24.2.21 with new schedules. This is really bad.

1 Like
18

They are going to say submit an Idea to change this…

3 Likes
19

Immediate run.

20

Epicor support appear to acknowledge this as a ‘bug’ / problem and have raised a ticket to fix.
I think this was causing Epicor problems for cloud customers and disk space.
I’m on-prem so Epicor should not have this type of restriction.