How To Fix GG690 - Error in the definition of field &

GG690 - Overview

• Message type: E = Error

• Message class: GG - Messages for FI-SL customizing

• Message number: 690

• Message text: Error in the definition of field &

What causes this issue?

When defining summary tables, you must enter the modified key fields of
the object table as value fields (data fields). The value fields of the
summary table are formed by adding the letter 'S' to each key field of
the object table.
Example: BUKRS in the object table -> SBUKRS in the summary table.
The error could be due to the following:
a) Field &V1& does not exist in the definition of table &V2&.
b) Field &V1& is defined as a key field and not as a data field.
c) Field &V1& is not at position &V3& in table &V2&.
d) The domain of field &V1& is not called &V4&.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Note the above requirements.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GG690 - Error in the definition of field & ?

  The SAP error message GG690, which states "Error in the definition of field &," typically indicates that there is an issue with the definition of a field in a data structure, table, or report. This error can arise in various contexts, such as during data entry, report generation, or when executing a transaction.
  Causes:
  
  Field Definition Issues: The field may not be defined correctly in the database or data dictionary. This could include incorrect data types, lengths, or attributes.
  Missing Field: The field referenced in the error message may not exist in the specified table or structure.
  Inconsistent Data Model: Changes in the data model (like adding or removing fields) that have not been properly propagated throughout the system can lead to this error.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or modify the field.
  Transport Issues: If the field definition was transported from one system to another (e.g., from