How To Fix CU359 - Variant table &1 does not exist on date &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CU - Variants / configuration messages

• Message number: 359

• Message text: Variant table &1 does not exist on date &2

What causes this issue?

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.

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?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 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 or activated.
  
  Solution:
  
  
  Check Variant Table Existence:
  
  Use transaction code SE11 (Data Dictionary) to check if the variant table exists. Enter the name of the variant table and see if it is present.
  
  
  
  Verify Validity Dates:
  
  If the variant table exists, check its validity dates. You can do this by navigating to the variant table in the configuration and checking the validity period. Ensure that the date you are using falls within this range.
  
  
  
  Review Configuration:
  
  Check the configuration settings related to the variant table. Ensure that it is correctly set up and that there are no missing entries or incorrect settings.
  
  
  
  Transport Check:
  
  If the variant table was recently transported, ensure that the transport was successful and that the table is active in the target system. You can check the transport logs for any errors.
  
  
  
  Consult Documentation:
  
  Review any relevant SAP documentation or notes related to variant configuration and the specific variant table you are working with.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), CU50 (Configuration Profile), CU01 (Create Variant Configuration Profile).
  SAP Notes: Check the SAP Support Portal for any notes related to error CU359 or variant configuration issues.
  Documentation: Review the SAP Help Portal for documentation on variant configuration and related topics.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.