Diagnosis
The customizing settings for derivation reference a field with the nameV1-v2. this field does not exist in the abap dictionary.

System Response
The system generated a short dump, because there is an inconsistency inCustomizing.

Procedure
This can typically occur at two points:

• A: during derivation


• B: while an operating concern is being generated in Profitability
Analysis (CO-PA)
In case A, table TKEDRSF contains inconsistent entries with the tablename cited above and field names TABNAME and FIELDNAME.
In case B, this may also be due to inconsistent entries in tables T258Mor TKEVA05. In this case, the addressed field typically has the ending"_ME". Check whether table T258M contains an entry with SD_MENGE =Field name and without an ending "_ME". If so, delete that entry. Dothe same for table TKEVA05 and the fields QSOURCE and QTARGET.
In case A above, you should delete the entire derivation step. Usingtransaction SE16, check table TKEDRSF for the inconsistent entry withTABNAME and FIELDNAME. You can find the relevant Customizingtransaction using table TKEDR, field TRX1, by using the key of theentry you found. The content of the field STEP_NO tells you the numberof the derivation step concerned that you see in the overview list ofthe Customizing function. Alternatively, you can delete the step bycalling up function module KEDR_STRATEGY_STEP_DELETE (transaction SE37,"Test"). However, find out why this step is inconsistent, and checkwhether you need to define an equivalent step again.