CK11N - Default "Costing Date To"

[former_member636854]

Hi Experts,

We have a requirement to change the  default date of the field 'Costing Date To'  (CK11N) to change to maximum period i.e., 31.12.9999. I have changed the config and the new default date is 31.12.9999 at CK11N.

Here in this blog, I would like to seek your guidance if any other Cut over activities required when I move this changes to Product.

Scenario:

• Our fiscal year is calendar year - Jan to Dec
• We have already costed all materials in the beginning of the 2016.
• I change the default costing date to 31.12.9999 at CK11N and tested.
• I am planning to move to Production

Upon moving the changes to Production is there any cut over activities to be done? Please advice.

Thanks & Regards

Gopi

[pavan_kumar18 · Accepted solution]

Hi,

You are just changing the maximum validity period.

There will be no issue,you can move the configuration.

After moving the configuration, if required re-run the cost estimate.

Regards,

Pavan Kumar Arvapally

[kamalkumar_biswas2]

Hi Gopi

You can move..no issue but you have to run cost estimate if your previous run is not support the change. Even if you change validity upto 31.12.9999 every year at the day one new estimate should run.

Kamal

[former_member636854]

Hi Kamal,

Thanks for the reply.

But just to clarify - on which scenarios our previous cost estimation run (for 2016) will not support.

We have already ran cost estimate for 2016 and no issues. I guess no need to run again as existing estimation is valid till end of 2016 (31.12.2016) so we just need to run CK40N/CK11N at the end of this year which will be valid till 31.12.9999. However, we will run every year as to have accurate cost.

Please confirm

Thanks & Regards

Gopi

[kamalkumar_biswas2]

Hi Gopi

You are right that you need not to run for 2016..and you have to run for next year and will be valid as per change valid date.

I mean to say that if you have no cost estimate for entire 2016 then you have to run under new change..but in your case it will not be required for 2016.

Kamal