|
Judi Some good questions here that make us think, and reveal BPCS nuances we had not previously realized were there. I'm in 405 CD multi-facility so my perspective 100% opposite yours, but I think I can project guidance of value. MRP140 data ends up in CIC file by facility which is a summary of CMF costs and also IIM data by facility. We populate various planner fields differently for same items in different facilities. Because of risk of employee turnover in who is entering what items, we have a fix it program to repopulate some fields of IIM and CIC according to rules associated with item type item class and which facility. If you want some fields of CIC to be blank so that your MRP runs correctly, you could write a program to blank that CIC field, then run that program immediately before running MRP net change or regen. We have such a program we run at that point. In our case, we make end items in shipping warehouse but consume the materials from work in process warehouse, so we are seeding planning warehouse differently for different item types. You can eyeball the kind of contents from command line via RUNQRY *N CIC and enter, but if you want to view sub-sets this way, instead of enter at RUNQRY *N CIC do F4 then on bottom line of prompt screen make that *YES then enter, and you can do selection ... after viewing one selection F12 gets you to ability to do a different selection. This RUNQRY *N (no query definition) ANY-FILE-NAME deal works for any file in your library list. When you do MRP500 600 CAP500 600 etc. it asks you what facility you doing, and if you leave that blank, it ought to take the data off of IIM and ignore CIC which it uses when someone specifies facility. When we run cost rollups, CIC and CMF are players ... you might try a test of some items One item have CIC record but no CMF records. Other item have CMF records but no CIC. Which one rolls up Ok. That will tell you what is safe to delete from Cost perspective. Any such experiment should either be in dummy items, or a test environment. I have been mass deleting duplicate costs, in my case unwanted global because we by facility. It might be useful for you to total records by facility (e.g. Query/400) for those files that can contain facility. MBM Bill of Materials FRT Routings CMF Cost Master CIC Item Cost Planning by Facility ECH ECL Customer Orders In theory all your stuff should be in one consistent place, one facility or global (blank). I think the ZMF file has facilities defined, then various IWM Warehouses ILM Locations and other things are defined to be in which facility. In theory, CIC (MRP140) gets populated with item facility data because co-workers keyed something into some other file that is relevant to activity by that item in that facility. So you want to back track where that data is coming from. Al Macintyre BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/ See Al http://www.ryze.com/view.php?who=Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
On BPCS 4.05CD Globally is all that is needed at this plant. Facility Planning Data (MRP 140) contains data. Can the Facility Planning Data (MRP 140) be inactivated, so that information no longer gets transferred there upon creation of new parts? At what point does information get transferred automatically to Facility Planning Data (MRP 140)? If Facility Planning Data (MRP 140) were inactivated, would it be best to do a mass deletion of information currently in there? Where in BPCS would (MRP 140) be turned off:? MRP reads from IIM to plan. When looking in BOM the lead time is not being read from IIM but from Facility Planning Data (MRP 140). IF Facility Planning Data (MRP 140) is blank, then MRP rules for BOM info. What besides BOM is effected by Facility Planning Data (MRP 140) when not set up by Facility? Thanks -- Judi ___
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.