MRP Scheduling Issues

Yahoo Archive
1
In the past we had experienced a similar issue with scheduling. We discovered that the operations were being scheduled on the correct day but the scheduler was populating the JobOper.StartHour fields in the database with values like 17200 instead of values 0-23. So the job was started on the correct day but 17200 hours later. This would only ever happen during MRP or global scheduling and always on the same resource. 

We could never figure out what caused it and it quit occurring after we moved to a different service pack/patch level.

2

We are on 9.04.507A


Running a full regen of MRP every night.


With ignore material constraints and allow historical dates.

All of our resources are not marked as finite capacity and are all running on the same calendar.

Resources don't have a queue time or a move time.


When MRP runs, it schedules each job, however, it schedules the first operation, but then the second operation gets scheduled to start 8 - 16 months after the first one finished.


Why wouldn't Epicor schedule it to start right after the first one finished?


3
Wondering what your company setup looks like?
--> Modules --> Production --> Jobs
---->  "Global Reschedule Started Operations"
---->  "Allow Scheduling Before Today"

May not be related to your issue but good to know what they are anyway.
4
Is the first operation marked as Finish to Start?



Bethany Rye
Epicor Business Analyst

<http://www.teampti.com/>















[Non-text portions of this message have been removed]
5

Do you have non-working days set on your calendar?

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, March 3, 2015 7:42 AM
To: vantage@yahoogroups.com
Subject: [Vantage] MRP Scheduling Issues

 

 

We are on 9.04.507A

 

Running a full regen of MRP every night.

 

With ignore material constraints and allow historical dates.

All of our resources are not marked as finite capacity and are all running on the same calendar.

Resources don't have a queue time or a move time.

 

When MRP runs, it schedules each job, however, it schedules the first operation, but then the second operation gets scheduled to start 8 - 16 months after the first one finished.

 

Why wouldn't Epicor schedule it to start right after the first one finished?

 

6

Make sure your production standards on your ops are valid.  At one company we wanted everything in minutes.  It turned out we had a few in hours.  SO something that should have been 120 minutes was 120 hours!

 

Manasa

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, March 03, 2015 3:55 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] MRP Scheduling Issues

 

 

Do you have non-working days set on your calendar?

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, March 3, 2015 7:42 AM
To: vantage@yahoogroups.com
Subject: [Vantage] MRP Scheduling Issues

 

 

We are on 9.04.507A

 

Running a full regen of MRP every night.

 

With ignore material constraints and allow historical dates.

All of our resources are not marked as finite capacity and are all running on the same calendar.

Resources don't have a queue time or a move time.

 

When MRP runs, it schedules each job, however, it schedules the first operation, but then the second operation gets scheduled to start 8 - 16 months after the first one finished.

 

Why wouldn't Epicor schedule it to start right after the first one finished?

 

IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.

IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.