How To Fix FVD_PROD_ATTR435 - Required attribute &1 is red, although higher-level attribute &2 is green

FVD_PROD_ATTR435 - Overview

• Message type: E = Error

• Message class: FVD_PROD_ATTR - Messages: Attribute Definition

• Message number: 435

• Message text: Required attribute &1 is red, although higher-level attribute &2 is green

&CAUSE&,,
The System has detected that the attribute &v1& is not active (red
light) and the required attribute checkbox is set. This attribute is
nevertheless inserted below the attribute &v2&, which is active (green
light). This situation is not permissible.
Required attributes must always be active (green light) if their higher-
level attribute is also active.

System Response

Processing is terminated.

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?

Contact your System Administrator.

Procedure for System Administrators

In Customizing for CML, the following options are available under
product definition:
Remove the required attribute indicator for the attribute &v1&.
Do not position the attribute &v1& below the attribute &v2& in the
attribute hierarchy.

Error message extract from SAP system. Copyright SAP SE.

FVD_PROD_ATTR435 - Details

• The SAP error message FVD_PROD_ATTR435 indicates a situation in which a required attribute (denoted as &1) is marked as red (indicating an error or missing information), while a higher-level attribute (denoted as &2) is marked as green (indicating that it is correctly filled or valid). This inconsistency typically arises in the context of product master data or variant configuration in SAP.
  
  Cause:
  
  Data Inconsistency: The required attribute is not filled in, even though the higher-level attribute is correctly filled. This can happen if the system expects certain attributes to be filled based on the configuration of the product.
  Configuration Settings: The configuration settings for the product might not be correctly defined, leading to a mismatch between required and higher-level attributes.
  Missing Dependencies: There may be dependencies defined in the configuration that require the lower-level attribute to be filled based on the value of the higher-level attribute.
  
  
  Solution:
  
  Check Attribute Values: Review the values of both the