|
If you are new to BPCS it is extremely dangerous to be adding custom programs to BPCS. Give careful thought to testing ... how will you know if something has got messed up, and how will you be able to fix it?
For example, you write a program to update fields X Y Z in file ABC when the conditions are I J K, and you check the output and in fact it did do that, but how do you know that it did not update X Y Z and/or some OTHER fields in some OTHER conditions that you did not intend to be updated?
I apologize for not being a genius like other members of this group but I'm new to BPCS and I became the only member of my department, so I am in a bit of a struggle here. I will try to follow more standards on future posts to the group. Thank you, Daniel -----Original Message----- From: bpcs-l-bounces+dwilkins=suz.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dwilkins=suz.com@xxxxxxxxxxxx] On Behalf Of Al Mac Sent: Tuesday, October 25, 2005 1:35 PM To: SSA's BPCS ERP System Subject: RE: [BPCS-L] Forecasting question People who do not read the documentation have a tendency to come up with terminology that is contrary to ERP standards. Also at many companies people insist on using their own terminology for stuff. It is important when posting to discussion groups to be able to translate from the unique language of your company to use standards technology of the package you asking the questions about. MRP100 feeds forecasting info into MRP just like minimum balance safety stock also influences what is needed. You can also have dynamic safety stock that is sensitive to seasonal variations in customer demand. We use a system that I think is more trouble than what comes with BPCS. We have customer orders with a PO# of FORECAST, then we have people asking me to include or exclude those orders from some BPCS functions, and I tell them that BPCS is not designed for modifications that are not totally thought through. If we want to do MRP reports that list only the activity of a particular customer, then we ought to use planner codes, but when we are looking at MRP on some item, we looking at it for the whole item, not able to separate reasons for MRP doing this or that, except pegging to parent orders, for that we need an add-on package such as RPM. >MRP600 is MRP not forecasting. MRP500 is MPS. The forecasting program >is a FOR program. > >Daniel J. Sweeney >Senior Technical Consultant >PHOENIX Business Consulting, Inc. >Matching What's New With What Already Works! >P. O. Box 237, Greensburg, PA 15601 >Tel: 724.836.4446 x9, Fax: 425.988.7102 >Cell: 860-490-6712 E-Fax: 832-550-5144 >dsweeney@xxxxxxxxxxxxxxxx >www.phoenixbcinc.com > > >SSA GLOBAL Recognized Services Provider > > >-----Original Message----- >From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx >[mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf >Of Daniel Wilkins >Sent: Tuesday, October 25, 2005 11:58 AM >To: bpcs-l@xxxxxxxxxxxx >Subject: [BPCS-L] Forecasting question > >BPCS Version 6.1.01 > > > >In the MRP600C, how can I tell that the forecasting is running and not >the MRP? > > > >I need to add a custom program to call but only during the forecasting >run and not the MRP run. > > > >Daniel -- 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: dwilkins@xxxxxxx -- 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: macwheel99@xxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
