×
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.
Yes, the BOM flag controls whether the Item will be selected for inclusion
in the backflush process. This assumes that you are using an Inventory
Transaction that is configured to trigger backflush (i.e. Multiple Issue =
Y) or you are using the JIT Production Reporting.
Regarding the question in your subsequent e-mail reply to Al, the Location
will be controlled by the any Allocations (ELA) records that are assigned to
the Component on the S.O. They will be Type = 'S'. If there are no ELA
records allocated, then BPCS will attempt to locate allocatable available
Onhand to satisfy the Quantity to be issued. Also, on the Backflush screen
you can maintain the allocations if needed.
If you have additional questions, feel free to contact me offline.
Thanks.
Les Mittman
847-858-5235
BPCS Consultant for over 20 years
-----Original Message-----
From: bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx] On Behalf Of
Larenzo Alexander
Sent: Wednesday, October 28, 2009 8:49 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Controlling Backlushing
Excellent explanation. Besides the "Must Single Issue" Flag is there
anything else effects wheater or not an item is backflushed. I belive the
Operation code tells it at what point to backflush. But I am about to
explain it to the users on the changes they need to make to an item to stop
it from backflushing and what to change if they want it to make flush.
Currently my understanding is the only flag is the should be worried about
the "Must Single Issue" in the BOM. (Item Master to but the BOM flag will
override the item master). Is that correct?
________________________________
From: Les Mittman - SBC <lmittman@xxxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Tue, October 27, 2009 5:14:08 PM
Subject: Re: [BPCS-L] Controlling Backlushing
Larenzo:
The BPCS function is exactly opposite to your understanding. This is a
common misunderstanding because of how SSA (nor Infor) chose to pose the
question.
A Single Issue is where a specific Item/Whse/Lot/Location is specified for
issue. That is, I tell BPCS exactly what I want to issue rather than
allowing Backflushing to suggest something. So, the question "Must Single
Issue" means "is a Single Issue required".
If you say "Y", they you are saying that the Item must be single issued.
That is, it is not eligible for Backflush. It will be skipped in the
Backflushing process and you will have to post a Single Issue in order to
consume it on a S.O.
If the setting is "N", then you indicate that the Item does not need to be
single issued. That is, it is eligible for Backflush.
The Must Single Issue value in the Item Master will be used as the default
on the BOM. And, it is the value on the BOM that will be carried to the
Shop Order Material Allocation (FMA) File. It is the FMA value that will
control whether the Component will backflush.
I hope that my explanation clarifies the function of Must Single Issue.
Please feel free to contact me offline if you have some additional
questions.
Thanks.
Les Mittman
847-858-5235
BPCS Consultant with over 20 years experience
-----Original Message-----
From: bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx] On Behalf Of
Larenzo Alexander
Sent: Tuesday, October 27, 2009 3:46 PM
To: BPCS Forum Post
Subject: [BPCS-L] Controlling Backlushing
What settings in BPCS controll if items backflush or not. I thought I
understood but apparently I dont.
I thought that if an Item's "Must Single Issue" Flag in the Item Master and
the BOM is set to "N" at the time that the Parent's Shop Order is created,
then the item will not backflush?
If any one can help me understand what I'm missing it would be greatly
appreciated.
Thanks
As an Amazon Associate we earn from qualifying purchases.
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.