× 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.



When you created the M1 transaction and attempted to use if for backflushing by chasing the BOM and not using the shop order as the vehicle for transacting the inventory movement, BPCS will not function as you would like. SFC500 (shop order create) has the logic built in to review the BOM and if at the time of shop order release the QOH of the phantom is below the requirements of the components for the material allocations, then the system will use the logic and chase the BOM and allocate the components for the phantom to the shop order. INV500 does not have the logic built in to look for the components of the phantom. This is still true in the latest version of the software.

Dan Sweeney - Sr Technical Consultant
PHOENIX Business Consulting, Inc.
Cell: 860.490.6712
www.phoenixbcinc.com
 



-----Original Message-----
From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf Of daparnin@xxxxxxxxxxxxxx
Sent: Saturday, October 31, 2009 9:46 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] Backflushing and Phantoms

Is the "Multiple Issue" flag on the "M1" transaction code set to 'Y'.


Yes, I checked it and it is set to 'Y'. It backflushes components just
fine. In fact, it backflushes the phantoms but it shouldn't--it should
blow through the phantom part number and backflush the components of the
phantoms.


Dave Parnin

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.