|
From Al Macintyre to Jesus Maynez & other folks interested in increasing an understanding of this subject There was another BPCS_L thread on this a few days ago & variations come up periodically. You need to make absolutely sure that you do not have several people running copies of CST600 at the same time & probably also CST500 which is called by CST600. Check your security for all the people who are authorized to do this task, and see that they understand that only one copy of this job should be in the works at a time & that it be allowed to get to a conclusion before another copy is launched. You may need to adjust your security so as to reduce the number of people who are authorized to run this job, to exclude those who "don't get it." Some companies have people who try to do rollups of individual items that they just changed the routings on, who are ignorant of the fact that the BOM of those items might be shared with other items that co-workers are doing the same thing on. It would be simpler if there was one person designated as the one who runs the cost roll-ups, then have other people message that person ... we need a cost roll-up soon because of item # whatever. One solution offered was to create a jobq just for cost roll-ups & modify the interactive CL to force it to always go there irrespective of user wish to run on-line or on some other jobq ... that way you force single threading of execution. Something else you might like to check out is the correlation between CIC & CMF ... I have a query that identifies parts that have data in one but not the other, and another query that identifies what items have different costs in different files, because a lot of my users have been asking how come the cost in INV300 does not always agree with the cost in CST300, and I determined that usually the cost is identical & wanted to see which items had the discrepancies. CST600 is part of our nighly routines but we cannot leave the AS/400 running unattended with assurance that all will be well the next morning, because CST600 is one of those jobs that blows up the spool file with a ridiculously large report. We determined that the problem is that CST600, and also CST900 for that matter, is treating the additional description lines of routines as if they were type 1 real routings. We use the type-3 text lines to communicate detailed production steps for our operations to the production floor & QC & easy viewing via SFC300. I reported to help line that I thought this was a bug, that both CST600 & CST900 should be using the FRT logical that excludes type-3 text lines, since they are not relevant to the functions of either of these programs. Help Line disagreed. SSA believes that other customers need this data in these reports & that to exclude them would break BPCS for other customers. Well, in my mountain of to do some time, we intend to fix the bug as a modification, because we have a ratio of approx 20 type-3 text lines for every 1 type-1 line & I figure the whole thing will run 10 times faster without them & right now we do not run CST900 as regularly as we should due to the many hours that it takes grinding through all those type-3 lines. I am also tempted to change the defaults on the CST600 prompt screen since cost type 2 standard is the only one we ever roll-up & I fear that some day someone is going to launch this using the defaults without changing the screen. > From: bpcsmaynez@yahoo.com (Jesus Maynez) > > Checking costs were equal in two facilities, I > discovered that my CMF file has duplicated costs. I > mean there is more than one record for the combination > CFPROD, CFFAC, CFCSET, CFCBKT. This was reason why I > had diferent costs between two facilities after doing > a Cost Inter-Facility transfer. I deleted those > records but I am getting more. I suspect the CST600 is > the program that is making these duplicated. Has > anyone has seen this problem? Any ideas how to solve > it? > > Best Regards, > Jesus Maynez Al Macintyre ©¿© http://www.cen-elec.com MIS Manager Programmer & Computer Janitor Y2K is not the end of my universe, but a re-boot of that old Chinese curse. This message was written and delivered using 100% post-consumer (recycled) data bits The road to success is always under construction. Accept that some days you are the pigeon and some days the statue. Murphy's Mom brought wrong baby home from hospital so it should be Kelly's Law. If consistency is the hobgoblin of little minds, only geniuses work here. When you want it cheap - you get what you paid for. When in doubt, read the manual, assuming you can find the right one. +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
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.