|
Here are some ideas for you to explore which come closest to your needs. Joining FRT+MBM will give you the STANDARD story, but won't help you with substitutions. Have you looked at JIT300 & SFC350? I think JIT300 reflects the LAST labor reported on an item, with no weighted averaging, so if you do not have standard quantities and standard rates, this is going to give you a distorted picture. At one time we considered a modification that would take SFC350 output, then for each item in its chart, have another SFC350, the purpose being to identify items with a problem, because some user was uncomfortable with MRP reports. Your interest is a bit different, but this is one way that FRT+MBM are ALREADY linked. The 400 magazine web sites, such as iSeries News (formerly News/400) have forums with lots of Query/400 tips. Do you use common sub-assemblies where the same part is a component of more than one end item? This can make it difficult to calculate how much of work on some components were really for which end items. A big variable for us is setup time. We have some queries that go down a level, send the results to a query work file, then use that query work file in combination with BPCS data to go down another level. But it is really helpful to know how many levels needed for each item you want to explore this way. You can access the same file more than once for different reasons in query, by using different logicals for the different purposes. We have some queries used when the shop orders are still open, that go down one level at a time. Start with FMA on the finished item (we use an IIM item type to know which are end items), which identifies all the component items needed. Link the FMA component items to FSO FOD or FLT (which means purchased items not linked) FLT has the labor history (standard and actual hours, efficiencies) ITH has the inventory history (costs) and you can link the two via labor ticket # We might look at the ITH file layout for CI transactions ... do they show both the parent item # and the child item? If so, you could use a series of query work files to interlink the actual materials involved in a production, as opposed to the standard from FRT+MBM, then use the labor ticket #s to get at the FLT hours involved. When shop orders purge, you lose access to what items were involved in the purge ... before we run CST900 we do a query/400 that creates a work file listing what FSO items involved, and what their CIC actual cost was before the purge, then after the purge is done, we compare to the new cost for those items involved in the purge, using the work file ... our interest is in changes to cost variances due to the purge ... you could use the same technique to see total hours on parts that just got purged. MBM is not a good file for query navigation. We did build our own work files for BOM exploration, but that was not practical as a query output work file, but we also doing something more sophisticated with that than you looking for. I have a modification that takes one of the BOM2* reports and for each manufactured component uses code from one of the SFC routing list reports to chart what the standards are for making that item, then for each manufactured component accesses FSO and other shop floor order records to see what is in current production and compare so far to standards. People run this by prompt screen select facility and item they interested in.
Does anybody have any query definition to get the total hours for a finished item? I understand that I would need to join FRT+MBM Files to get the total time. The problem starts when I am trying to get the indented routing for items wich has more than 3 levels. Thanks in advance for your help. Rene _______________________________________________ Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.
- Al Macintyre (macwheel99@sigecom.net via Eudora) Al's diary http://radio.weblogs.com/0107846/ Cure cancer. http://members.ud.com/about/
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.