on 01-10-2014 10:52 AM
Hi SAP Gurus,
Release step of previous CK40n costing run was failed (auto cancelled) due to ABAP error and now its been corrected.
Do I need to delete previous unsuccessful costing run as "Marking" step is already been completed before execute a new CK40n run.
If so should I use CK44 OR do i need to reorganize costing (CKR1) as it carries "marked" cost ?
[Please refer attached costing run image]
Thanks,
Tharaka
Hi
This is the problem with CK40N
Go to CKR1 and delete future cost estimate. Then do ck40n again.
Ajay M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tharaka,
Did you unchecked the test run, What are the parameters you have selected?
Company code, plant etc, select the future std cost estimate.
if you did above then the future might have been deleted check the material master if not then select these parameters and execute again.
Thanks
Hrusikesh
Hi Tharaka,
In addition to Hrushikesh Dalai please make note of it.
Even I faced this kind of situation several times while testing.
In this case my suggestion is just log off your SAP log on system (with which ID you are working) and log in again. Then continue your CKR1 with Hrushikesh suggestions.
Sounds funny but works, I believe strongly...
Regards..
Jose
Hi Tharaka
As Marking was successful, you can trigger the Release process only, however I would suggest you start Costing -> Marking -> Release from the current costing run itself. No need to create new costinng run.
Regards
Mustafa Sakerwala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tharaka,
You may run the Tcode CKR1 for your Consting Run.
Select the option * Future Standard Cost Estimates. It will delete the Marked cost from the materials, so you be able to run it again.
However what kind of error the SAP show you when you run Release step? If your Costing run is correctly you have just to release.
BR
RK
Dear Tharaka
System will not allow you to release the cost in back date. And actually its not the costing run date but Costing 'from' should not be in past.
Now, If in this period using the same costing variant if you have not released any cost estimate earlier, then you can cancel the marking allowance. This way CKR1 can be avoided as this (CKR1) is not a good practice and SAP itself gives you warning message for possible inconsistencies.
Regards
Rajneesh Saxena
Tharaka,
When marking is completed it updates the future cost in material master as Rudi already told, if you don't want to release the same cost for whats ever reason then you need to delete future cost estimate in CKR1 first before releasing new cost estimate for the same materials.
Regards
Hrusikesh
Hi,
There are no problem in reorganize a Future Standard Cost. I can't say the same for a Released Cost option.
I already did it several times in Production or Test system.
If you business processes allow you, don't need to delete this future cost. Just run the CK40N for 01/02/2014 and release the this cost in that date. The system will work with the standard cost regarded in the master data.
BR,
RK
Hi Tharaka
I am writing this as I see the thread is not yet closed.
To the best of my knowledge, you can do marking of cost estimate n number of times for a period. In your case, since its falling under the same period, the new marking will overwrite old marked cost estimate. System may only prompt you with a warning message about existence of an already marked cost estimate.
To save yourself from all complications about CKR1, I would suggest simply create costing run and complete it (ignoring the old marked cost estimate).
If however the period was different (say earlier costing date was 31.12.2013 & now its 01.01.2014) in this case, since we are crossing the periods (December & January), you would want to take up a call for whether you need old mark cst estimate of December. Unless it impacts any other requirement (Reporting or valuation), you can keep ignoring it.
CKR1 should be used as a LAST resort only, because not only mishandling may greatly impact you but also it doesnt register any change logs, for any future analysis.
Hope it helps
Regards
Mustafa Sakerwala
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.