RE: Question on allocations and default warehouse -- BPCS-L

In order to correct the allocation problems, I have done the following
(in a test system first).

1.  Remove the default location and warehouse from IIM
2.  Set all locations to be "non forced" locations
3.  Validate the BOM and routings for correct ops numbers etc.
4.  Set the flag in the CIC to not allow "batch allocations" from within
the entire facility.

These steps usually fix the allocation problems where we know there is
sufficient inventory.

There are two many variable in BPCS that can cause the allocation
algorithms to be incorrect.

So I suggest starting from scratch and reset all of the variables and go
from there.


-----Original Message-----
From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf
Of Roger.Henady@xxxxxxxxxx
Sent: Friday, March 04, 2005 9:53 AM
To: SSA's BPCS ERP System
Subject: RE: [BPCS-L] Question on allocations and default warehouse

There is a default location in IIM and one in IWI.     If there is a 
location in IWI then that seems to be the only place an allocation is 
allowed from.     The problem with IIM how to give a default for more
than 
one WH.

Do most use the lowest location allocates first?  or do allocate from
the 
default location in IWI?


Roger Henady
Thorco Industries
(417) 682-1340



"Yan Shargorodsky" <yshargorodsky@xxxxxxxxxx> 
Sent by: bpcs-l-bounces+roger.henady=thorco.com@xxxxxxxxxxxx
03/03/2005 07:52 PM
Please respond to
"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>


To
"'SSA's BPCS ERP System'" <bpcs-l@xxxxxxxxxxxx>
cc

Subject
RE: [BPCS-L] Question on allocations and default warehouse






Jim,
"0" - Forced Location
"1" - Default Location
"2" - Standard
If you use maintenance, these are the values. It probably treats *BLANK
as
ZERO, assuming you have test database, change all locations, which have 
ILI
record for an Item to "2" and see what happens.


The following is help text from the field:

The location associated with a given Item/Warehouse will be considered
during Order Warehouse Processing and the Forced Location Search.
This option has no effect on a location defined within a managed 
warehouse.
Choose one of the following Usage Codes:

Standard                 The standard alphanumeric or zone/pick sequence

is used.
Default          No other location is considered within the current 
warehouse. The
search continues in other warehouses.
Forced           No other location is considered in the current
warehouse. 
No other
warehouse is considered. The search stops.
Note:  At the Item level, entered through the JIT product, the usage
codes
have different meanings. Valid values are: 0 = Forced Location. 1 = 
Default
Location. 2 = First Location.

If you are defining locations for a managed warehouse with the shop
order
reservations flag in Warehouse Master Maintenance set to 1 (Yes), enter
0
(Forced Location) or 2 (Standard Location). Reservations processing 
locates
stock at the warehouse level: therefore, no shop order reservations
occur
for default or forced locations.



Yan Shargorodsky
Y&Y Solutions Inc.
Phone:(215) 741-7138
Cell:    (267) 934-8327
Email: yshargorodsky@xxxxxxxxxx


-----Original Message-----
From: bpcs-l-bounces+yshargorodsky=yysinc.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+yshargorodsky=yysinc.com@xxxxxxxxxxxx]On Behalf
Of Jim
Sent: Thursday, March 03, 2005 8:26 PM
To: SSA's BPCS ERP System
Subject: RE: [BPCS-L] Question on allocations and default warehouse


Yan,

That field, WFLOC in ILM is *BLANK for all locations.

Jim

-----Original Message-----
From: bpcs-l-bounces+jmergen=pctcnet.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+jmergen=pctcnet.net@xxxxxxxxxxxx]On Behalf Of Yan
Shargorodsky
Sent: Thursday, March 03, 2005 6:30 PM
To: 'SSA's BPCS ERP System'
Subject: RE: [BPCS-L] Question on allocations and default warehouse


Jim,

I think your problem is forced location flag in Location Master. 
Allocation
searches each location for which record exist in ILI in alphabetical 
order.
Once it encounters location with forced location flag yes in ILM and no
inventory allocated so far (including forced location), it stops. Also
location must be allocatable.

Yan Shargorodsky
Y&Y Solutions Inc.
Phone:(215) 741-7138
Cell:    (267) 934-8327
Email: yshargorodsky@xxxxxxxxxx


-----Original Message-----
From: bpcs-l-bounces+yshargorodsky=yysinc.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+yshargorodsky=yysinc.com@xxxxxxxxxxxx]On Behalf
Of Jim
Sent: Thursday, March 03, 2005 7:23 PM
To: SSA's BPCS ERP System
Subject: [BPCS-L] Question on allocations and default warehouse


Hi

Does anyone have the BPCS rules/hierarchy on how parts are allocated to
a
Shop Order. From what I understand:

IF in IIM(Item Master) we use a default location, then at Shop Order
Print(SFC520 as SFC500 doesn't actually allocate until print runs) parts
from the default location will be allocated, if inventory exists, but
from
this location ONLY.

IF in IIM there is no default location, then it will try to allocate
available inventory beginning with the first location with
inventory(alphabetically).

We have a situation where several parts did not allocate, although there

was
inventory on-hand.

Some of the parts didn't allocate, I believe, because of a default in
IIM
not matching locations where inventory exists(I reason for not using a
default in my mind).

Some of the parts didn't allocate, didn't have a default location in
IIM,
but did have available inventory in at least one location.
As a test on one of these parts, I updated IIM default location to a
location that had inventory, ran SFC400(batch allocations) and the parts

DID
allocate.

This confuses me-I cannot figure out why, with the default location in
IIM
set to BLANKS, and available inventory existing in at least one 
location(Yes
warehouse and location are defined as allocatable) it didn't allocate
the
parts, but then when I entered a default and ran SFC400 it did allocate.

Does anyone have a set of comprehensive rules that define how BPCS
allocates, other than the  vague help screens?

Also, can anyone point out reasons for and against a default location in
IIM?

Thanks for any guidance

Jim


--
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.

Delivered-To: yshargorodsky@xxxxxxxxxx




--
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.

Delivered-To: jmergen@xxxxxxxxxxx

--
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.

Delivered-To: yshargorodsky@xxxxxxxxxx




-- 
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.

Delivered-To: Roger.Henady@xxxxxxxxxx

-- 
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.

Delivered-To: dsweeney@xxxxxxxxxxxxxxxx