|
Their are dangers in incorrect low-level codes even for cost roll-up, The purpose of the low-level code is to control the order in which parts are processed. In your case it is to make sure that you do not roll the costs of components into a parent item before you have 'rolled-up' the cost of the component. Example component C goes into Assembly A. C carries a pre-rollup cost of 10 cents. If A is processed before C, then 10 cents is what rolls into the cost of A. If C is later rolled up in the same run and produces a cost of 12 cents, you effectively have a 2 cent error on your cost of Assembly A. The problem with this error is that it is almost impossible for even the most eagle eyed accountant to notice a problem. However problems can mount. Every time you issue C to a shop order for A, WIP gets incremented at 12 cents apiece. When you receive the finished good, A is missing 2 cents in its cost that will never be relieved from WIP. I'm not an accountant so your milage may vary. +--- | 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.