It is my understanding from Infor that the system will allocate and
backflush phantoms. It will also show demand over and above the current
QOH of the phantom on to the children of the phantom. It will not,
however, allocate and backflush the children of the phantom.
We are on version 6.04 and the process is as such. We have an item, say
QOH of 1,000 pieces that is being replaced by an item from a new supplier,
and for this reason the item number revision level is changing. The OLD
item becomes a phantom, the new item is put into the BOM as a child to the
phantom. Now, when MRP runs it will take into account the 1,000 pieces of
the phantom. If/when demand goes over the 1,000 available, it will show
demand for the children so that purchasing can buy the new part. It will
not, however, allocate and backflush the children. It will only allocate
and backflush the phantom. If you step away from this for a moment and
forget that this item is a phantom, what you're wanting BPCS to do is to
allocate and backflush 2 levels of the BOM in one pass. BPCS doesn't do
that.
I hope this helped.
Norman K. Boyd
MIS Administrator
Showa Aluminum Corp. of America
Phone: (740) 869-5007
CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. If you are the intended recipient but do not wish to receive
communications via email, please advise the sender immediately.
From:
Dan Sweeney <dsweeney@xxxxxxxxxxxxxxxx>
To:
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Date:
11/02/2009 01:25 PM
Subject:
Re: [BPCS-L] Backflushing and Phantoms
When you create the shop order and then subsequently release it the system
will look at the QOH=Quantity on-hand of the phantom first. If there is
enough of the phantom on hand then it stops looking and allocates the
quantity of the phantom and creates the ELA and FMA records. If there is
not enough on hand of the phantom it then blows to the next level and
allocates the quantity of the components per the BOM of the phantom and
creates the FMA and ELA records.
Hope that this helps!
If not feel free to contact me off-line.
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: Monday, November 02, 2009 1:09 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] Backflushing and Phantoms
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.
QOH = Quantity on hand (I assume)???
OK, I will accept that INV500 doesn't have the logic for phantoms. Where
does it backflush components then if the shop order does exist? It
backflushes everything else without a shop order. Does SFC500 create FMA
records tied to the shop order and then INV500 uses those to know what
components to backflush?
Dave Parnin
midrange.com
