|
In a message dated 4/7/00 9:34:42 AM Eastern Daylight Time, Mrogers@miwheel.com writes: << In our case, we created a 'working' cost set(33) for 'frozen standard' and then at the end of 1999 copied cost set 33 to cost set 3. Now, after 3 months, we compare cost set 33 to 3 and have seen changes in set 3. We run CST600 on new items only for cost set 3 and always single-thread the jobs. >> BEAWARE........ If you think you are doing a cost rollup ( CST600 or CST500 ) for only one item# ( from Item# = to Item#) you may actually be updating other items ! In order to 'roll-up' the cost of a new finished good item number, the system first flags all of its children & grandchildren & great grandchildren..... so that it can start at the bottom and roll the costs up. It recalculates the costs of all intermediate children. IF any BOM's have beeen changed, or any Items costs have changed, then intermediate items will have their costs changed also. I always recommend that for new items that need a new frozen cost calculated; you do a cost rollup in cost set "XX" ( some 'temporary' or 'working' cost set). So that IF some intermediary item#s get their costs re-calculated, you are changing cost set XX not cost set 3. Once you have the new calculated costs in cost set XX, MANUALLY enter those costs into cost set 3 via CST100. Some of my clients created a new program that 'transfers' cost set XX to cost set 3 ONLY if cost set 3 is zero cost. Thus, you can transfer new costs for new items that never had a cost before without 'accidentally' changing a frozen cost ( since the accountants do NOT like you changing FROZEN costs...) Jim Barry +--- | 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.