|
So we get a new item with Customer Order, but people neglected to make it an MPS item. MRP500 ignores the Customer Demand because it is not an MPS item. MRP600 ignores it because it is not child of any MPS item. We end up not making the part in time to meet promise to customer. To help with this, I have a query/400 to list any customer orders on items that are not MPS items.
I also have similar query/400 to list any items that someone has coded to have safety stock, but they are not MPS items, so MRP will ignore that request also.
We have a complex BOM hierarchy in which MPS items have children that are not MPS items, and also children that are MPS items, and non-MPS children who have children that are not MPS items and some that are MPS items. I have query to list items coded as been active and in need of MRP500 MRP600 work but are still that way after full regeneration. Many of them are plain coded wrong & it is not just MPS type missing, also order policy code and other stuff. 99% of our problems solved by running MRP500 twice followed by MRP600 once.
Other variables in here are multi-facility, DRP, and CAP, with respect to right sequence to run everhthing.
Sounds pretty good to me, except I would change the last sentence (which may have been a typo) to "This continues till end of explosion of all non-MPS items.".For this to work correctly, you need to be sure that your non-MPS items do not have any children that are MPS items. If a non-MPS item has a child that is an MPS item, MRP600 will generate requirements for the MPS Item, but since MRP500 (that plans the MPS items) has already been run, there will not be any planned orders generated for that MPS item. I have seen this happen occasionally. The Item low level codes (which should be maintained automatically during BOM maintenance) must also be correct. If not, you could generate requirements for items that have already been planned.At 09:37 PM 8/9/2005, you wrote:Hi, Would like to have your feedback on following (my understanding of MPS-MRP processes in BPCS): Forecast (in case of make-to-stock) or Customer Order (in case of make-to-order or assemble-to-order scenario) creates Demand or Requirement for FG (Finished Goods) MPS item i.e. KMR record for FG MPS item. Upon running MPS (MRP500-Master Schedule), this Demand or Requirement (KMR) drives & creates Planned Order (KFP record) for this FG MPS item which further drive & creates Demand or Requirement (KMR) for next (Child) MPS item which in-turn creates Planned Order (KFP) for that MPS item. This continues till the end of BOM structure. Upon running MRP (MRP600-Explode Requirements) which takes MPS item Planned Order (KFP) as Input & generates Demand or Requirement for next (Child) non-MPS item which in-turn creates Planned Order (KFP) for the same non-MPS item. This continues till end of explosion of all MPS items. Pl. correct me wherever I am wrong. Regards, PrashanthDave Murvin DRM Enterprises, Inc. -- 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
