One more thing…if you are using STD cost and you do not have a roll up query to find items where the roll up does not equal the STD cost on the item card, you will continue to have variances at every output where they are not equal. We have too many items to roll up costs on all items, so I have a query that I run that shows if any component STD cost changed and/or the BOM route was updated and cost was not rolled up. It used to be a huge issue when accounting did not control all of the changes, hence the query. Now our biggest driver of variances is where STD cost changes on components or changes to BOM/Routes occur in the middle of a run. The variance will post once the PDR is finished. No way around it unless you close out all PDR’s, make changes, roll cost and then create new PDRs. We accept the small variances on the runs for these situations because we try to keep our runs relatively short.
Login
Report
There was a problem reporting this post.
Block Member?
Please confirm you want to block this member.
You will no longer be able to:
See blocked member's posts
Mention this member in posts
Invite this member to groups
Message this member
Add this member as a connection
Please note:
This action will also remove this member from your connections and send a report to the site admin.
Please allow a few minutes for this process to complete.
Report
You have already reported this .
Welcome to our new site!
Here you will find a wealth of information created for people that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!