Delete active Cost Element

[Former Member]

I have a client who created a cost element in error.

They then posted to it, so it can be deleted.

It needs to be deleted as it affect CO-PA postings.

Does anybosy know of a way to delete a Cost Element, mid Fiscal Year for a Cost Element that has a balance.

I have looked on OSS but cant see anything. There must be a re-set program somewhere.

[former_member188826]

The prerequisite to delete a Cost element is that, there shall be no transaction data for the cost elements in the planning or commitments data in the affected fiscal years.

Additionally. No statistical key figures have been planned. Then use KA04

[Former Member]

Hi,

thanks for the response.

I am aware of that, I just wondered if there is a way around it.

The client will now need to wait a year to delete the Cost Element

I am lookinh through OSS and come across note 483340, do you think this will work?

[former_member188826]

Note 38955 mentions that CE cannot be deleted once data posted for that year. I doubt if we can delete the CE. Some work around may need to be looked upon.

[Former Member]

Hi Mark

Don't think note 483340 would have any bearing in this case.

The only method SAP delievers for this is to delete the cost element via KA04 for the analysis periods required.

In this date range to be deleted there can be no dependent data as already stated. That includes plan, actuals and control records.

The control records are stored in table COKA and are created in for a fiscal year once the cost element receives postings.

Now there are programs that SAP provides if there is a possibility to delete the actual / plan / COKA data. In your case though this may not be possible for accounting or audit reasons.

Perhaps you can use a validation so as to prevent the cost element from being used further this year.

Additionally I would recommend to delete via KA04 the nearest date range possible for the cost element. For example if you have data in FY 2008, but none for 2009 onwards. Goto KA04 enter the cost element and a date range of:

01.01.2009 to 31.12.9999 (or whatever the end date is of the master data).

At the very least it will prevent any "accidental" future postings causing a similar problem.

Regards, Elaine