Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: VSCE - Messages for SCE
Message number: 359
Message text: Variant table &1 does not exist on date &2
The variant table does not exist for the date on which the runtime
version is generated. The variant table was possibly created with a
change number and is only valid at a later time.
Generation of the knowledge base is terminated.
Check the table and the dependency in which this table is used.
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.
VSCE359
- Variant table &1 does not exist on date &2 ?The SAP error message VSCE359 indicates that the variant table specified does not exist for the given date. This error typically occurs in the context of variant configuration or when dealing with configurable materials in SAP.
Cause:
Non-Existent Variant Table: The variant table specified in the error message does not exist in the system for the date provided. This could be due to:
- The variant table was never created.
- The variant table was deleted or archived.
- The date specified is outside the validity period of the variant table.
Incorrect Date: The date provided in the error message may not correspond to the validity period of the variant table.
Configuration Issues: There may be issues with the configuration settings or master data that are causing the system to look for a variant table that is not available.
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 check if it is active and available.
Verify Validity Dates:
- Check the validity dates of the variant table. Ensure that the date you are using falls within the valid range.
- You can do this by checking the configuration settings in the variant table.
Create or Adjust Variant Table:
- If the variant table does not exist, you may need to create it using transaction CU01 (Create Variant Table).
- If it exists but is not valid for the specified date, you may need to adjust the validity dates or create a new variant table that covers the required date.
Check Configuration Settings:
- Review the configuration settings related to the material or product that is causing the error. Ensure that all necessary configurations are in place.
Consult Documentation:
- Refer to SAP documentation or help resources for more detailed information on variant tables and their configuration.
Related Information:
Transaction Codes:
SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
VSCE358
Dependency &1 contains unsupported syntax &2
What causes this issue? Dependency contains syntax that is not supported in the knowledgebase.System Response The dependency will not be copied to t...
VSCE357
Procedure &1 to &2 not supported
What causes this issue? The procedure is assigned to a characteristic or characteristic value.System Response The procedure is not copied to the kno...
VSCE360
Table &1 has no entry in column &2
What causes this issue? You cannot process variant tables with empty cells in the IPC.System Response Generation of the knowledge base is terminated...
VSCE362
Variant table in KB &1 &2 cannot be activated during system upgrade
What causes this issue? The generation of a knowledgebase runtime version requires the creation of one or several variant tables on the database. The...
Click on this link to search all SAP messages.