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



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





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.