× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Since migrating to XA7 we are having trouble with MRP generating
requirements for rework work orders. Orders where the Parent is the same
and the Component. In XA6 it would properly see the component and parent
and net out to 0, however in XA7 it doesn't seem to see the component and
now always gives a cancel message.

While this may sound odd, Infor themselves suggested this method on their
own No Wait support site....

Create a New Rework Mfg order
Create a new rework manufacturing order using BOM = KEY and routing = NO
for the end item. You could use the reference field to describe this as a
rework order, or use a 'rework' order accounting class to identify this
order as a rework order. Add the end item as a component on the order and
specify any additional needed components needed in the rework operation.
Add routing steps that describe the rework operations that need to be
done. Release the order. Approve the rejected part (as in 2 above) and
issue to this manufacturing order. Perform the rework and RM/MQ it back to
stock.

We've submitted a ticket to Infor however they have said that's just the
way it has always been. Though we've proved that in XA6 it was different.
We've gone to our Infor rep though they have not been able to support us
or offer any help.

Has anyone experienced this since moving to XA7? Suggestions? Tips?



Regards,

Joe Rogalski
IT Manager
Weir Minerals North America


The information contained in this email (including any attachments) is confidential, subject to copyright and for the use of the intended recipient only. If you are not the intended recipient please delete this message after notifying the sender. Unauthorised retention, alteration or distribution of this email is forbidden and may be actionable.

Attachments are opened at your own risk and you are advised to scan incoming email for viruses before opening any attached files. We give no guarantee that any communication is virus-free and accept no responsibility for virus contamination or other system loss or damage of any kind.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.