How To Fix CU360 - Variant table &1 contains blanks in column &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CU - Variants / configuration messages

• Message number: 360

• Message text: 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 a dependency:
INTERIOR,,EXTERIOR
RED,,RED
RED,,GREEN
RED,,BLUE
BLUE
GREEN,,RED
GREEN,,YELLOW
If you want to show that all exterior colors are allowed with a BLUE
interior, you must enter all possible combinations before the table can
be processed in dependencies.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CU360 - Variant table &1 contains blanks in column &2 ?

  The SAP error message CU360 indicates that there is an issue with a variant table where there are blank entries in a specific column. This typically occurs in the context of variant configuration, where the system expects certain fields to be populated with valid data.
  Cause:
  The error message "CU360 Variant table &1 contains blanks in column &2" is triggered when:
  
  A variant table (identified by &1) has one or more entries in a specified column (identified by &2) that are blank or null.
  This can happen due to incorrect data entry, data migration issues, or inconsistencies in the variant configuration setup.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Variant Table and Column:
  
  Check the error message for the specific variant table name and the column that contains the blanks.
  
  
  
  Access the Variant Table:
  
  Use transaction codes like CU01 (for creating variants) or CU02 (for changing variants) to access the variant table in question.
  
  
  
  Review Entries:
  
  Look through the entries in the specified column to identify any blanks or null values.
  
  
  
  Correct the Data:
  
  Fill in the missing values in the column. Ensure that all required fields are populated with valid data.
  If the blanks are not supposed to be there, you may need to delete those entries or correct them as necessary.
  
  
  
  Check Configuration Settings:
  
  Review the configuration settings related to the variant table to ensure that they are set up correctly and that there are no inconsistencies.
  
  
  
  Test the Changes:
  
  After making the necessary corrections, test the variant configuration to ensure that the error no longer occurs.
  
  
  
  Transport Changes:
  
  If you are working in a development environment, ensure that any changes are transported to the appropriate systems (e.g., quality assurance, production) as needed.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CU01, CU02, CU03 (for displaying variants), and CU04 (for deleting variants).
  Documentation: Refer to SAP documentation or help resources for more detailed information on variant configuration and handling errors.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to variant tables and provide additional guidance or patches.
  
  By following these steps, you should be able to resolve the CU360 error and ensure that your variant tables are correctly populated.