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



I need to see the pegging from the child item in the bom (lowest level)
to the end item to the customer order.  
Essentially, we would like to have individual shop orders per customer
orders, but, as I understand it, that is not possible with BPCS.  (I am
new to this system, I might add).

Regards,

Marc Graff
Production Control Manager
States Industries, Inc.
(541) 688-7871 ext. 283


-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]
On Behalf Of Andy Newell
Sent: Wednesday, August 04, 2004 6:50 AM
To: 'SSA's BPCS ERP System'
Subject: RE: Pegging planned items back up to discrete customer orders.

In what way did the MRP300 pegging disagree with you? How many levels in
the
BOM do you need to peg through? Do you need individual shop orders per
customer order or do you just need to identify the affect, on customer
orders, of changes to child item planned orders?

Andrew Newell, CIRM/CPIM

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]
On
Behalf Of Marc Graff
Sent: Tuesday, August 03, 2004 5:16 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: Pegging planned items back up to discrete customer orders.

I would like to know if anyone has solved the issue of planned item
pegging back to the customer order.  I know the data exists in BPCS, I
just haven't found anyone who knows how to extract it.  I had a
consultant in who said if we could flatten the bill of materials for a
planned item we should be able to drill from the child item up through
the bom to the end item, and to the customer order number.
Unfortunately he was not able to do this.  (We use Production version
405 CD.)

 

This is an example of what I am hoping to solve:

 

Currently, in our version of BPCS, all planned items (items that have a
demand in the system and have a planned order but have no open shop
orders yet), are consolidated based on the requested ship date.  

 

For example:



Customer:

Item 

Qty

Due

 

 


1

A

60

15-Apr

 

 


2

A

90

15-Apr

 

 


3

A

120

15-Apr

 

 


4

A

30

15-Apr

 

 


 

 

 

 

 

 


 

 

 

 

 

 


One 'planned' order for Item A for 300 pieces is created in BPCS.

 

 

 

 

 

 

Is there are way to not have BPCS do this automatic consolidation?  In
MRP systems I have used, automatic consolidation was a server flag that
was set to Yes or No, with a consolidation interval and horizon.  I
would think that BPCS would at least have the option to turn automatic
consolidation on or off.

 

Any help would be appreciated..

 

Regards,

 

Marc Graff

Production Control Manager

States Industries, Inc.

(541) 688-7871 ext. 283

 

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