Does anyone know how the costing workbench pulls in the revisions for manufactured parts? I have some parts in the costing workbench with revisions that are not approved. When i look at those parts, they have another approved revision which i expected the workbench to pull in? I tried to simulate and pull the same part in 2 different plants, assuming it may have something to do with what plant i am in. It still pulls in the Un-approved Revision.
Thanks,
AL Thomas
In the primary Costing WorkBench app on the main screen you can select whether to include alternate revisions.
When performing the Action of Cost Roll up, you can select whether to consider Only Approved Revisions.
We strictly only maintain one approved revision at a time so I don’t know the impact of having multiple rev’s approved.
We are single Site but still have a Cost group for our site that sets defaults etc.,: That may limit which site is being impacted if you are multisite. (I would think it would.)
It was rock solid on version 10 & so far on Kinetic 2022.
Hope that helps.
Hope that is helpful.
I have excluded any “Alternate Revisions” in the Main Group tab of Costing Workbench. Only 1 revision is approved for that part but there happens to be 2 revisions. The other revision is unapproved and was superseded by the new revision which is the approved one. But Costing Workbench pulls in the un-approved revision.
Also, When doing the rollup and if i select “Only Approved Revisions” then it ignores that part for cost rollup. I want to roll up the cost of the part but with the new revision that’s approved. The effective date on the new revision is from 2021. The old unapproved revision’s effective date 2019. So why is it pulling in the old unapproved revision?
We also only have 1 Site Cost ID for all our plants so the cost would be the same in all plants.
Hmmm… Long ago (way back in Epicor 9) I wrote some custom searches that effectively result in only approved rev’s for parts being returned and brought in to the workbench OR displayed search results indicating whether rev was approved yet by engineering. That was all just to simplify my life as (particularly that second one) it effectively created a workflow (at least my piece of it) when new items are entered.
I suppose because of that, I may never have encountered what you are describing as the workbench is a bit of a ‘what if’ tool before potentially posting the results.
Perhaps try something like that and see if it then doesn’t roll through old unapproved revisions.
In general (on Vantage 7 now through every major version up to Kinetic 2022) most revision-centric apps want to use the 1st rev found (“1st” alpha numerically) unless it is also filtering on only approved rev’s.
Curious what you learn if you try that…