|
midrange.com
Paul,
Backflushing from the correct warehouse isn't the problem. Backflushing
from the correct *location* within that warehouse is. Others have written
that inventory is taken from the first alphabetical location that it comes
to. It's also been said that it takes it from the first location that has
inventory. I did some testing and both statements seem to have their
truths and non-truths. My experience was that just having a valid ILM
location defined for that warehouse that comes alphabetically before the
undesired location isn't enough. An inventory transaction must be done to
that location for that item so that an ILI record gets created. Once that
exists it will backflush from that location first. Get rid of that ILI
record and backflushing reverts to the next alphabetical ILI location for
that item. I have vague memories of this sort of methodology from a few
years back except that was for allocating finished good inventory for
customer order shipments.
The only solution that I can see for my current situation is to rename the
locations for that warehouse. They are currently DWIP and FGDI. If DWIP
were renamed to WIP, DWIP inventory transferred to WIP, and the DWIP ILI
records were removed then it would backflush the way that we want. Making
those changes is a decision for somebody else. If there's a better way to
handle things I would love to hear it.
Dave
P.S. I appreciate the advice from everyone who has responded. Thanks!
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxxxxxx
Paul LaFlamme
<laflammep@kenned To: "SSA's BPCS ERP
System" <bpcs-l@xxxxxxxxxxxx>
ydc.com> @SMTP@CTB
cc:
01/29/2004 01:48 Subject: RE: Backflushed
Location Headaches
PM
Please respond to
"SSA's BPCS ERP
System"
<bpcs-l@midrange.
com>
Hi Dave,
Sorry I haven't responded sooner.
I believe to do what you want to do, you need to cut the shop orders to
warehouse 21 like it sounds like you've been doing. Then you need to set
up the IIM defaults and possibly the CIC defaults (that depends on what
level of plant/facility you are planning at. Making these changes will
NOT fix open shop orders. New shop orders going forward should backflush
from the correct warehouse.
I'm thinking you should have the warehouse location usage fields set to
blank. (That's how I have them set up)
I'm making a couple other assumptions: Warehouse 21 is allocatable and
the locations are allocatable. The Default Receiving location in
warehouse master maintenance is blank.
Let me know how you make out!
Paul
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]
On Behalf Of David A Parnin
Sent: Monday, January 26, 2004 2:39 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: RE: Backflushed Location Headaches
Paul,
Thanks for the reply. I've worked with 4.05CD before at a place that I
used to work at although it's been awhile since I've dealt with material
planning, backflushing, shop orders, etc. The shop orders for both the
kits and the component FG parts are going to warehouse 21. The actual
location names are DWIP and FGDI. When the FG components are produced
we want their components to backflush from DWIP. When the kits are
assembled we want them to backflush from FGDI.
There is no ILM default location set for warehouse 21. There is also no
default location assigned in the Item Master for either the FG or kit
parts. Is it just backflushing the kits from the first location that it
finds for warehouse 21? The IWI default location for the kit part is
FGDI and the Default/Forced location flag is set to zero. Does this
give you a better picture?
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxxxxxx
Paul LaFlamme
<laflammep@kenned To: "SSA's BPCS ERP
System" <bpcs-l@xxxxxxxxxxxx>
ydc.com> @SMTP@CTB
cc:
01/26/2004 01:15 Subject: RE: Backflushed
Location Headaches
PM
Please respond to
"SSA's BPCS ERP
System"
<bpcs-l@midrange.
com>
Hi Dave,
We're on 405CD, very similar to what you're running. I have a couple of
questions: What warehouse are your FG item shop orders issued to? The
warehouse the shop order is "cut" to will be the warehouse location the
components are allocated to for later backflush and it has precedence
over any item master, facility or system parameter default.
My next question is To what warehouse is the kitted item being issued?
Paul
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]
On Behalf Of David A Parnin
Sent: Friday, January 23, 2004 3:24 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: Backflushed Location Headaches
Greetings everyone,
I've got a situation where one of our facilities is starting to make
"kits" that consist of two finished good parts. The two finished good
parts will also continue to be stocked and sold as individual items.
When these two parts are produced their production is posted to the FG
location for the warehouse and their components are backflushed from the
WIP location. When the kit item is produced its component finished good
parts are getting backflushed from the WIP location instead of the FG
location. This requires a corresponding transfer from FG to WIP to
correct the inventory balances in both locations. Another bit of
information is that shop orders are downloaded from BPCS to a PC-based
production reporting/barcode labeling/shipping system and then uploaded
back to BPCS. They are batch posted through JIT (JIT500?), I believe.
I've tried setting the override location in JIT110 to be FG. There are
two operations for the kit--"finish" and "report". I've copied the
workcenters and changed the new workcenter "from" and "to" location
values to both be "FG". The routing for the kit item was then changed
to use the new workcenters. Still, when I've tested posting
transactions with JIT600 it backflushes the kit components from WIP. Can
this be set up? Is there a program fix that we are missing? Am I
crazy? (I feel like I'm going
crazy!)
We are on 4.0.2 that was modified for Y2K by 3rd party software long
before I started working here. Thanks in advance for any advice and
suggestions.
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxxxxxx
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
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.
