Message type: E = Error
Message class:  ABADR - Message Class for Characteristic Derivation 
Message number: 590
Message text: System error during derivation: &-& was not found in ABAP Dictionary
The customizing settings for derivation reference a field with the name
&V1&-&V2&. This field does not exist in the ABAP Dictionary.
The system generated a short dump, because there is an inconsistency in
Customizing.
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 table
name cited above and field names TABNAME and FIELDNAME.
In case B, this may also be due to inconsistent entries in tables T258M
or 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. Do
the same for table TKEVA05 and the fields QSOURCE and QTARGET.
In case A above, you should delete the entire derivation step. Using
transaction SE16, check table TKEDRSF for the inconsistent entry with
TABNAME and FIELDNAME. You can find the relevant Customizing
transaction using table TKEDR, field TRX1, by using the key of the
entry you found. The content of the field STEP_NO tells you the number
of the derivation step concerned that you see in the overview list of
the Customizing function. Alternatively, you can delete the step by
calling up function module KEDR_STRATEGY_STEP_DELETE (transaction SE37,
"Test"). However, find out why this step is inconsistent, and check
whether you need to define an equivalent step again.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message ABADR590 indicates that there is a system error during the derivation process, specifically stating that a certain object (denoted by &-&) was not found in the ABAP Dictionary. This typically occurs in the context of data processing or when trying to derive values from certain fields or structures that are expected to exist in the ABAP Dictionary but do not. Causes: Missing Data Element or Structure: The object that the system is trying to access may not exist in the ABAP Dictionary. This could be due to a missing data element, domain, or structure. Incorrect Configuration: There may be a configuration issue where the derivation logic is pointing to an incorrect or outdated object. Transport Issues: If the system is newly upgraded or if transports have been moved between systems, some objects may not have been transported correctly. Custom Development: If there are custom developments or enhancements that reference objects that
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
ABADR510 Report & could not be generated
What causes this issue?  Program &V1& could not be generated because operating concern &V2& is not consistent. The generated table &am...
ABADR301 No authorization to change these fields
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ABADR591 Inconsistent strategy! &1-&2 not found in structure, possibly deleted?
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ABADR599 System error during characteristic derivation maintenance
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.