santosh
31st August 2005, 15:53
Hi All,
We are facing a problem related to customised item costing in PCS module which i will explaing with the help of an example.
There are two manufacture item - M1 & M2. M2 is a component of M1.
a routing has been defined(has a setup time and run time) for M2 and suppose the cost price of M2 is 10. Now if the M1:M2 relation is 1:1 then the cost price of M1 is 10. But if it is 1:2 ie for 1 M1 2 M2 are rquired then the cost price is calculated as 20. It is simply multiplying the cost price of child by the bom qty. But we dont want the setup time of the M2 to be considered twice. It has to be only 1. Because of this our standard cost prices are showing excess amounts than normal and if the there are many components in the BoM then the difference is pretty big.
Even the cost price for standatd item is calculated this way.
I rellay cannot understand this method of calculation. Do anybody face/faced the same problem. Can anybody explaing me the logic behind such a calculation. When contacted baan support i got an explanation that that is the standard functionality. But we are not satisfied with the explanation. Can anybody help me.
Thanks & Regards
Santosh
:confused:
We are facing a problem related to customised item costing in PCS module which i will explaing with the help of an example.
There are two manufacture item - M1 & M2. M2 is a component of M1.
a routing has been defined(has a setup time and run time) for M2 and suppose the cost price of M2 is 10. Now if the M1:M2 relation is 1:1 then the cost price of M1 is 10. But if it is 1:2 ie for 1 M1 2 M2 are rquired then the cost price is calculated as 20. It is simply multiplying the cost price of child by the bom qty. But we dont want the setup time of the M2 to be considered twice. It has to be only 1. Because of this our standard cost prices are showing excess amounts than normal and if the there are many components in the BoM then the difference is pretty big.
Even the cost price for standatd item is calculated this way.
I rellay cannot understand this method of calculation. Do anybody face/faced the same problem. Can anybody explaing me the logic behind such a calculation. When contacted baan support i got an explanation that that is the standard functionality. But we are not satisfied with the explanation. Can anybody help me.
Thanks & Regards
Santosh
:confused: