Re: Purchasing order policy

Hi Joe


I dont think the order policy code will resolve this problem. From what you
are saying, this is an order management issue.

BPCS creates planned orders for a reason, usually because there is a
forecast or a customer order in the system, and there is not enough
available stock.  If you dont want to execute some planned orders, this is
symptomatic  of a planning problem right at the source of your MRP demand,
like having forecasts no one believes in,  or invalid (false) customer
orders. Either situation will not be corrected by order policy codes, but by
the appropriate management of the MRP demand input.

It sounds as if  someone is trying to double guess the whole MRP calculation
and logic process, which is terribly a bad practice. Might as well turn off
MRP completely, and do the shop order and purchase order planning outside of
BPCS.

Daniel Warthold P. eng CPIM



----- Original Message ----- 
From: "Joe McCormick" <joemccormick@xxxxxxxxxxxxxx>
To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
Sent: Tuesday, February 14, 2006 10:09 AM
Subject: [BPCS-L] Purchasing order policy


Hi,
What would be the most suitable order policy to use in order to only
purchase for firm (not planned ) shop orders. We currently by for both but
are finding this is contributing to excess inventory as many planned orders
are not made.

Thanks

Joe


----------------------------------------------------------------------------
----


No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.7/259 - Release Date: 13/02/2006



----------------------------------------------------------------------------
----


> -- 
> 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: daniel.warthold@xxxxxxxxxxxx
>