|
With kits, you have little control over backflush location. BPCS will use the first location in that warehouse that has inventory. It takes them in alphabetical order. That's why it's backflushing from DWIP instead of FGDI. If you run out of inventory in DWIP, it will backflush from FGDI. Richard Bird Corp Mgr/Business Systems Accuride Corporation Ph. 812-962-5028 Fx. 270-831-6144 Mo. 812-431-7177 -----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.
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.
midrange.com
