Message type: E = Error
Message class: CU - Variants / configuration messages
Message number: 359
Message text: Variant table &1 does not exist on date &2
The variant table does not exist on the date when the runtime version
is being generated. The variant table may have been created with a
change number, so that it does not come into force until a later date.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
CU359
- Variant table &1 does not exist on date &2 ?The SAP error message CU359 indicates that a variant table specified in the system does not exist for a given date. This error typically arises in the context of variant configuration, where the system is trying to access a variant table that is either not defined or not valid for the specified date.
Cause: Non-existent Variant Table: The variant table specified in the error message does not exist in the system. Date Validity: The variant table may exist, but it is not valid for the date specified in the error message. Variant tables can have validity periods, and if the date falls outside this range, the system will not find the table.
Configuration Issues: There may be issues with the configuration settings or the way the variant table is being called in the program or transaction. Transport Issues: If the variant table was recently transported from another system, it may not have been properly imported
Get instant SAP help. Sign up for our Free Essentials Plan.
CU356
Procedure/action &1 for &2 not suppoerted in the SCE
What causes this issue? A dependency of type "action" or "procedure" is allocated to a characteristic value. This is not allowed ...
CU355
KNUM is assigned in CUOB but missing in CUKB (net: &)
What causes this issue? a constraint that no longer exists is assigned to a constraint net. This error has no consequences, but you see this message ...
CU360
Variant table &1 contains blanks in column &2
What causes this issue? Variant tables that are used in dependencies must have an entry in each line. You cannot use a table such as the following in...
CU361
Variant table &2 has no language-dependent description in &1
What causes this issue? You selected a language for generating a runtime version of a knowledge base. However, there is no description of this varian...
Click on this link to search all SAP messages.