Re: Backflushing From Wrong Location?

Dan think you may be on to something. I do think recently when the user runs the Shop Packet Print he started changing the allocated flag to 1(yes) instead of 0.  

And the setting the backflush location to forced shouldn't  hurt. 

I'm a little unclear about how the JIT110 JIT override location works but I checked and found all the parts in there and the usage code on all parts are set to BLANK. I'm assuming since none have a code 0(forced) then it's ok with the JIT110. Is that assumption correct?

Thanks




________________________________
From: "Dan.Zimmerley@xxxxxxxxxxxxx" <Dan.Zimmerley@xxxxxxxxxxxxx>
To: bpcs-l@xxxxxxxxxxxx
Sent: Fri, November 20, 2009 10:31:40 AM
Subject: Re: [BPCS-L] Backflushing From Wrong Location?

Hi Lorenzo, we're also on 6.1, heavily modified.
When we had items backflushing from locations we did not want we had a couple causes.
There is a JIT110 program, JIT override location, where an item can get tied into a location and if the relationship is "forced", it will backflush from there.

We also found that if an item is hard allocated to a shop order it will backflush from that location, again regardless of whether it is a backflush location or not.  That happened more frequently when people would run the shop order print and they would leave the allocate flag at 1, yes.

We did set up our backflush locations as forced locations.  Not sure if that really helped or whether it just doesn't get in the way.

Dan Zimmerley

-----Original Message-----
From: bpcs-l-bounces+dan.zimmerley=npmedical.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dan.zimmerley=npmedical.com@xxxxxxxxxxxx] On Behalf Of Larenzo Alexander
Sent: Friday, November 20, 2009 9:52 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Backflushing From Wrong Location?

Sorry, I forgot to put my version. We are running BPCS Version 6.1 Release 01.

Thanks Dan, I didn't know that option was there. I just checked all the facility planning records (CIC) facility wide alloc/backflush flag and all parts facility wide alloc/backflush flags are set to '0' (No).




________________________________
From: Dan Sweeney <dsweeney@xxxxxxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Fri, November 20, 2009 9:32:40 AM
Subject: Re: [BPCS-L] Backflushing From Wrong Location?

Lorenzo,

Check in the facility planning record (CIC) and see if you have checked yes to facility wide alloc/backflush - the wording may different dependent upon
Your release.

If you have checked yes then the system will try and allocate/backflush the components from the first alphanumeric location, in your case blank, and then search the facility/warehouse for the remainder of the required quantity.

How the finished good is set-up has no bearing on the backflush of the components.

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 Larenzo Alexander
Sent: Friday, November 20, 2009 9:15 AM
To: BPCS Forum Post
Subject: [BPCS-L] Backflushing From Wrong Location?

Hello All,

I posted a post in the past about backflushing and I thought we found the solution to this issue but I must have been dreaming. LOL

We have 1 warehouse called 'AA' with a BLANK location and other locations. Everything should get backflushed from the BLANK location only. The other locations within warehouse 'AA' is only for tranfers.

For some reason we have component items that started to back flush from the wrong locations other than the BLANK location in warehouse 'AA' all of a sudden. The only change I can think of close to time it sarted happen was the installation of a new System i5.

* Checked the Shop Orders for the FG Item and the Warehouse/Location is correct. (AA-BLANK)
* Checked the Item Master & Facility Planning and the warehouse/Location is correct. (AA-BLANK)
* Checked the Location Master for each location and the settings are the same for all locations in 'AA' included Blank. This may be the problem but we never changed this and they seem to work in the beginning.
        - Allocatable = 1 (Yes) Allow Automatic Allocations
        - Location usage = 1 (standard)
* I did notice that each part in question had a parent that was a phantom. Not sure if the phantom blow through had something to do with it.

If anyone know something I miss to check it would be greatly appreciated. (TGIF)