× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. BPCS-L
  3. December 2005

Re: Cost Roll Up Jobs

We also on 405 CD, operating multi-facility.

We used to run those jobs more often than now.
Also CST900 when there are no unresolved labor problems.
We minor modified CST900 because CST270 was blowing up the spool file and we wanted it to be able to run unattended. We also capture a work file right before CST900 that lists some details about the items coded for purge, so that after the purge we can run some reports on just those items, showing cost changes due to the purge, and which of those items had significant variances.
We found that having run a recent BPCS files reorg helps certain long running tasks go significantly faster, but the downside is that we have late nite factory inquiry. Some reorg can run concurrent with this, but it is greatly slowed down, and misses the files that the nite factory inquiry is accessing.. So if you can get a window of no one on the system, and know which Reorg help the most. 

We also experimented with using more than one JOBQ.
One JOBQ for tasks that will take a long while.
One JOBQ for tasks that can be expected to only take a few minutes.
We found we needed more "gas" on our AS/400 to use this effectively and had to be very careful that jobs that should not be running concurrently ended up on different JOBQ.
Used to be, after an engineer completed BOM Routing changes, they would do a cost rollup on just the item range they been working on. A rolup touches all component parts, which are shared with the work a different engineer might be working on, so it is critical that these different rollups not be going concurrently from different people.
If you rollup standard costs all the time, then you have no such thing as a standard.
We are currently running BPCS 4.05 CD. Our managers would like to have the Cost Roll up jobs to process every day.
Currently we are processing these jobs every week and they take about 5 - 5 ½ hours to run. 

Here is a list of the CST Jobs that we run:

CST600C

CST920C

CST940C
Does anyone else run these jobs every day and do you find it necessary since they do take a lot of time? 



Thanks!



Janet Talalai

Senior Programmer/Analyst

IT Department

717.832.8838

jtalalai@xxxxxxxxxxxxxxx <mailto:jtalalai@xxxxxxxxxxxxxxx>

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.