We recently came up with a situation where there are assemblies that are manufactured in Plant-A and that assembly is being used as a component in Plant-B. ( for such items the oracle cost is not matching with Legacy JDE cost),Solution to Cost Rollup in this type of scenarios is as follows:
1. Identify all the Items of this type ( eg: XXX) that are manufactured in Plant-A
2. Create a Sourcing Rule in Plant-B for these items ( Name the sourcing Rule as “ B Transfer”)
3. Perform a complete cost Rollup in Plant-A. ( with this Rollup, all the assemblies in Plant-A and Plant-B will get rolled up, to the Parent assemblies in Plant-A)
4. Copy cost of all the items from Plant-A to Plant-B,doing so the rolled up cost of item like XXX will get copied to Plant-B.
5. Now perform a cost rollup in Plant-B, we can see the Parent assembly with the assemblies that are manufactured in Plant-A and that assembly is being used as a component in Plant-B,will get costed.
Concurrent Programs need to be scheduled in such a manner first Complete cost rollup in Plant-A, second copy cost to Plant-B, third Run complete Rollup in Plant-B.
From conversion point of view::
a) We need to collect data from business and add all Items to the sourcing Rule “ B Transfer” in Plant-B.
b) We need to run a new concurrent program to “update the lead time”
Logic for this will be :
1) Based on sourcing Rule “ B Transfer From” copy the cumulative lead time from Plant-A and Paste to the Processing Lead time in Plant-B.
There should not be Planner code for these items in Planner-B, but planner code is must in Plant-A. Then ASCP will create a Planned work order for Plant-A, similar to “ B Transfer” Items
This is just my thought, you can leverage to the extent to match with your case.
No comments:
Post a Comment