Update other than Standard cost

[Former Member]

Hey all

We have a scenario here in which we update the planned price 3 field with help of a "DUMMY" costing variant. In this cost variant the logic of selection picks up the standard cost or rolls up the standard cost with bills and routings. Then this rolled up cost is updated into planned price 3 field as per the cost variant settings.

I marked and released the standard cost on Jan 1 for all the materials. Now when i run this "Dummy" variant it rolls up the New and Correct cost for only the plant which has the Bill and routing. the other plants for same material does not reflect the change in the rolled up cost.

The reason for this i found out was the date. I had to change the "costing date from" to mext month and it came up fine but in this case i m not updating Standard Cost. Cant I just run this costing variant in same period and same month and get the new cost

[ajaycwa1981]

Hi Ankur

A costing variant which does not update Std Cost, can be used any no of times... There is no limitation

You can proceed

BR,Ajay M

[Former Member]

Ajay- Correct. Thats what i was doing last Month (Dec 2010)... But now its giving me worng cost.

For example a material ( has released cost in Jan) which has Bill and routing in Plant A gives right cost... but other plants which has same material does not get the right cost... The cost transfer is not happening between plants. But when I change the date to Month of Feb all is becomes perfect. I dont understand why its taking date as a criteria to cost one plant correctly and not transfer the cost to other plants

[ajaycwa1981]

Hi

That should not happen...

Run cost estimate for this material in Plant A and immediately run in Plant B on the same day with same dates.. It should pick up the cost in Plant B also.. If you are using special proc key in Plant B, then it should pick up the same cost estimate in Plant B also...

Just ensure that there are no errors in the cost estimate at Plant A... if your transfer control in costing variant is intended to transfer the cost in "Cross Plant" scenario also, then it should work...

BR,Ajay M

[Former Member]

Hey Ajay

I tested it and there are no errors. I am doing ck40n for the material in all plants. It is still giving different cost with this dummy cost variant. I check the cross plant status also looks fine. My logic in cross plant says

Future planned price

current planned price

previous planned price

Only future one has fiscal year checked in front of it

Single plant tab says no transfer

[ajaycwa1981]

Hi Ankur

Sorry, but absolutely no idea why is it happening so.. It should not happen, given the settings you have mentioned

I hope the spl proc key is in place already.. You must have ensured it

BR,Ajay M

[Former Member]

Yes Ajay... All spec procurement keys in MRP 2 are good. and its for all the materials its happening...

Thanks for help. If i find something will update

[Former Member]

Ajay

In qty structure data of the plant that has no Bill and routing it shows nothing but it shows these three things

Special procurement 7 Stock transfer

SpclProcurementPlant IA01

SpecProcuremKey CS

what does 7 mean here and where can i find it in Material?

[Former Member]

Ajay

There is another thing was noticed. On running the cost run with dummy cost variant... in the lower levels of the Bill it is selecting the standard cost variant to cost it.

[Former Member]

A way to do this correctly is ...select the "always recost material" check box in selection criteria at time of selection parameters in ck40n

[Former Member]

resolved

[Former Member]

It seems you have to have the BOM and routings for each of the plants you are working with. Other than that, you have to configure a special procurement costing key and enter it in the costing 1 view of the materials you want to cost roll. Then you have to cost roll the material for which you enter this new key. This will save you the need of creating new BOMS or routings for the same material in the other plants.

I hope this helps.

BR,

Luis.

[Former Member]

Thanks for reply Luis but I am afraid you have wrongly interpreted the scenario.

All is working fine here the only problem is can i run the cost run (with a dummy variant which does not update std cost) more than once in a month