SAP Netweaver Enterprise Controlling

Symptom
Runtime problems occur for the application of overheads in actual if you repeat the calculation or execute a reversal.
Runtime problems occur for the application of overheads in plan if you repeat calculation or execute a reversal and integrated planning is active.
Additional key words
Overhead, performance, COEP, COEJ, index, KGI4, CJ45, CO43, KSA3, KSA8,
Actual overheads, plan overheads
Cause and prerequisites

Solution
1. Actual overheads
In addition, create a secondary index in the customer namespace with the following fields on table COEP:
MANDT
OBJNR
KSTAR
GJAHR
PERIO
PAROB1
WRTTP
As of Release 4.0, a similar index is delivered in the standard system, the index COEP-2. However, do not use it.
The index COEP-2 is NOT created on the DB but only in the dictionary and therefore has NO influence neither on the database optimizer nor any other influence.
The index COEP-2 was only copied to the Data Dictionary to serve as a proposal for a customer index.
Since it cannot be excluded at present that an index that is only defined in the dictionary is deleted again from the database during the upgrade, this would have to be prevented in Transaction SPDD during the upgrade.
As a precaution, SAP currently recommends to create the index in the customer namespace. This prevents problems during the upgrade.
This index cannot be delivered as database index, since not all customers require it.
Make sure to create the index on the database during time of minimal work load.
If you deleted or modified old secondary index 1 of table COEP according to a former version of this note, also consider Note 135132.
Some databases (Oracle) still use the old index even after creation of the secondary index.In this case, also implement the attached source code changes.2. Planned overheads
Create an additional secondary index in the customer namespace with the following fields in table COEJ:
MANDT
OBJNR
KSTAR
GJAHR
VERSN
PAROB1
WRTTP
VRGNG
BEKNZ
Make sure to create the index on the database during time of minimal work load.
Also make sure that index 2 delivered by SAP does not additionally exist on table COEJ, because otherwise the new index may not be used.
Source code corrections