RE: Cost Roll Up Jobs

Hi Janet,

It would seem the need to run them everyday may be due to NOT knowing what
cost changes have occurred and are they significant. So lets just run it
everyday just to be sure.

If this is the case, you can solve this by monitoring the cost fields for a
change or a change of, say, greater than 10%. When the condition occurs,
send a notification and/or kick off/schedule the job. It's also a great way
to monitor for cost entry errors that can throw off a cost roll. Also, you
can roll just the items that have changed, drastically reducing run time,
that is, if it does need to run everyday due to volume of cost changes.

I have several bpcs sites doing this with a tool. If you have a single
situation, you may just want to write it yourself. 

I have a design overview on how to code these. I can share it with you if
you like or feel free to give me a ring if you'd like to chat about how
other shops are doing this. 

Cheers, Bill
Tel 508-415-1541

 
 


-----Original Message-----
From: bpcs-l-bounces+bill.brennan=seabiscuit.biz@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+bill.brennan=seabiscuit.biz@xxxxxxxxxxxx] On Behalf
Of Janet Talalai
Sent: Thursday, December 01, 2005 9:58 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Cost Roll Up Jobs


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>