Fixed Standard cost estimate

[former_member221048]

Hello

I want to keep standard cost estimate for the next year fixed without any change as this will be our budgeted COGS. Please inform how to store this standard cost so that it will be used in COPA,

Regards

Ahmed

[Former Member]

Dear Ahmed,

Please check Report T.code:S_99_4100111 , Where you can compare Two standard cost estimates

Hope this will help You

With Regards,

Nasir

[michael_savarimuthu]

Ahmed,

Your question needs clarification, as Ajay aptly put it.

If you are talking about just the released standard cost total, please read on, otherwise skip.

Are you currently using Planned Price 2 or 3?  If not, why don't you use an LSMW task to update the Planned Price field with the current cost estimate?  You can use that later in populating a COPA field.

If on the other hand, you want to EXTEND the current cost estimates which ends at the end of the current fiscal year to next year also, this may not be possible.  If the end date of the current cost estimate is end of NEXT year or beyond, then this is easy since you don't have to cost/release a new standard.  (This is why I prefer creating costing runs with an end date of 12/31/9999 which gives you the freedom of releasing a cost estimate when you want it). 

If on the other hand you are concerned that someone may accidentally cost and release a standard, the best way to prevent this is by having basis lock up program SAPRCK23 in CK24.

Please clarify.

Cheers,

TD

[ajaycwa1981]

Yes, that will be the right approach.. Store your 1st std cost in any of the fields likeTax price, commercial price or Planned price, etc

Also, if you perform COPA valuation using Std price, then you are in better situation because you need not worry even if std cost is later removed

br, Ajay M

[former_member221048]

Thanks Ajay and TD

I agree to store the first released cost in commercial price field. Please inform how this will be done and how do I retrieve this cost to be read in COPA reports?

Regards

[ajaycwa1981]

Hi

You can create a new costing variant like this

1. Costing type - Release to prices other than std cost

2. val variant - have only one val strategy i.e. current std cost

Execute this costing run after the std cost is released.. You can choose to update the result in the Tax price field before releasing the cost in CK24 or CK40N

How to read this in COPA?? - If you perform COPA valuation at the start of the year using this cost, it will be auto read in COPA... Else, use user exit COPA0002 depending on your need

br, Ajay M

[ajaycwa1981]

Hi Ahmed

Not clear with your question...

You want to keep the current year std cost for next year or you want that no one must be able to change the std cost in next year once released??

For the later part, there is no check possible... you need to control it through discipline

br, Ajay M

[former_member221048]

Dear All,

My question is that when I realease my standard cost for next year through CK40N, assume my standard cost for a certain product is 40 units, This cost will be my budget cost, I want to keep it in certain version so that whenever I run a report I can ask for my original budget cost. It goes without saying that during the next year the cost for this product can be released say it will be 41 units, so no problem with that, my standard product cost will be affected with the new 41 cost but at the same time I need to see in COPA my original cost of 40 in a specific column (Budget Cost).

Regards

Ahmed

[michael_savarimuthu]

Ahmed,

Your created cost estimates will be there in KEKO and KEPH tables.  They are not deleted unless you create cost estimates for the same period with the same costing variant or until you delete them with transaction CK44.  You can use them for report purposes.  If you enable flow of cost estimates to COPA, you can assign specific cost estimates to flow to COPA value fields. 

Cheers,

TD