SAP ABAP Message Class ABADR Message Number 590 (System error during derivation: &-& was not found in the ABAP Dictionary)
Hierarchy
SAP_ABA (Software Component) Cross-Application Component
   CA-GTF (Application Component) General Application Functions
     ABADR (Package) Derivation Tool
Attribute
Message class ABADR  
Short Description Message Class for Characteristic Derivation    
Message Number 590  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20010522   
Message Text
System error during derivation: &-& was not found in the ABAP Dictionary
Help Document

Diagnosis

The customizing settings for derivation reference a field with the name -. This field does not exist in the ABAP Dictionary.

System Response

The system generated a short dump, because there is an inconsistency in Customizing.

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 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.

History
Last changed on/by 20010525  SAP 
SAP Release Created in   620