Message type: E = Error
Message class: GR - Report Writer
Message number: 673
Message text: &1 in key figure set &2 (row &3) does not exist
Error message extract from SAP system. Copyright SAP SE.
GR673
- &1 in key figure set &2 (row &3) does not exist ?The SAP error message GR673 indicates that there is an issue with a key figure set in the context of a planning application, typically within SAP BW (Business Warehouse) or SAP Integrated Business Planning (IBP). The error message specifically states that a key figure set does not exist for the specified parameters.
Cause: Missing Key Figure Set: The key figure set referenced in the error message does not exist in the system. This could be due to it not being created, being deleted, or being incorrectly referenced. Incorrect Configuration: There may be a configuration issue where the key figure set is not properly linked to the planning area or the data model. Data Model Changes: If there have been recent changes to the data model or key figures, it may lead to inconsistencies that result in this error. Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the key figure set,
Get instant SAP help. Sign up for our Free Essentials Plan.
GR672
Characteristic & (&) is missing from a column in section &
What causes this issue? Characteristic &v2& (field name &V3&) is used in at least one column of the checked report. It is missing, ho...
GR671
In row &, one set is missing for period field & (&)
What causes this issue? If you use a set for the period field in a row block, each row set must contain a set for the period field. In the current r...
GR674
&1 in key figure set &2 (column &3) does not exist
INCLUDE RG-RW-NA_GR673 ID TX The system issues an error message and will not allow you to continue with this transaction until the error is resolved....
GR675
&1 in key figure set &2 (selection) does not exist
INCLUDE RG-RW-NA_GR673 ID TX The system issues an error message and will not allow you to continue with this transaction until the error is resolved....
Click on this link to search all SAP messages.