• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

? 4 Mfg Companies re Work Order Scheduling on B733

Larry_Jones

Legendary Poster
Just a curiosity question to those companies using Manufacturing / MRP in B733.x

We have encountered multiple problems in the synchronization of MRP's scheduling of Work Orders / materials vs. Work Order Operations (routing) scheduling. One major problem was Mfg Engineering and Production Mgmnt playing with the work center capacities and calendar (Resource Units) so that the Plant Calendar no longer matched the individual work center calendars (Resource Units). However even after slapping hands and synchronizing the calendars we saw Start Dates of Work Orders and their Routings still having significant variances due to s/w bugs in the W/O routing back scheduling function.

My question to you is this something you (and your company) live with or did you fix the problems yourselves or get JDE to fix?

We've implemented our own code fixes but would like to get JDE to correct once and for all so we don't have to keep patching their attempts to correct the problem. Support line is famous for stating "no one else has reported that problem ..." so I'm looking for some validation of our experience with this problem.

Specific problems run into (and fixed) include:
1) Queue/Move/Setup reduced by additional resources (more than 1 employee/machine) when they should not be. (Problem partially corrected by JDE in XE Update 1.)

2) Overlapping operations - problems too complex to explain here but there were several. Again JDE has tried to fix in XE with very limited success.

If you are having these kinds of issues I would be interested in hearing from you.

TIA,

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP13
 

pk_wu

Active Member
Larry,

MRP uses the start dates of the attached parts list
which in my experience has always been in synch with
the start date of the work order header. The start
date that doesn't come into synch consistently is the
first step of the attached routing - which can be
easily fixed by a RPG program to synchronize the start
date of the first step after JDE performs its
backscheduling with P31410 or R31410 if your are in
One World.
Any further questions please give me an e-mail.
paul
--- Larry_Jones <ljones@wagstaff.com> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=9082


__________________________________________________
 

mdeloria

Member
We had the same issue on B7332 we are now on Xe service pack 14.2 . We have
installed several sars along with a soft mod and the issue has still not
been corrected. The latest sar number 5002443 and ESU were downloaded and
failed to build. Denver is still working on this. We have been chasing this
issue since August. We have also encountered some serious MRP issues.
Marlene
----- Original Message -----

From: Larry_Jones <ljones@wagstaff.com>
To: <jdelistml@jdelist.com>
Sent: Thursday, April 12, 2001 2:19 PM
Subject: ? 4 Mfg Companies re Work Order Scheduling on B733


B733.x
scheduling of Work Orders / materials vs. Work Order Operations (routing)
scheduling. One major problem was Mfg Engineering and Production Mgmnt
playing with the work center capacities and calendar (Resource Units) so
that the Plant Calendar no longer matched the individual work center
calendars (Resource Units). However even after slapping hands and
synchronizing the calendars we saw Start Dates of Work Orders and their
Routings still having significant variances due to s/w bugs in the W/O
routing back scheduling function.
did you fix the problems yourselves or get JDE to fix?
once and for all so we don't have to keep patching their attempts to correct
the problem. Support line is famous for stating "no one else has reported
that problem ..." so I'm looking for some validation of our experience with
this problem.
employee/machine) when they should not be. (Problem partially corrected by
JDE in XE Update 1.)
there were several. Again JDE has tried to fix in XE with very limited
success.
from you.
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=9
082
 

Larry_Jones

Legendary Poster
Paul,

thx for the reply and validation of the issues. Your method of forcing the first step externally was not an option for us, our routings are such that several steps would be scheduled days shorter than they actually should have been - screwing up work center capacity / scheduling. Inaccurate dispatch lists are a big no-no here.

As previously stated we have fixed the code to schedule correctly - I just wanted validation that these problems were occurring in manufacturing environments other than our own.

Thx,

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP13
 

Larry_Jones

Legendary Poster
Marlene,

your copy of the original post looks all chopped up.
It doesn't appear that you received the all of the
original post. You may want to go to the forums at
www.jdelist.com to see the full text.

Anyway, thx for responding and validating these
issues. Our experience is similiar to yours, JDE
tried to fix in XE but it doesn't seem that the
developers really have a handle / understanding of
the issues. If you have an outstanding SAR we can
weigh in on please let me know. That's basically what
I wanted was to let JDE know that a lot of us have
these issues and to up the priority of them.

Thx again,

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP13
 
Top