Purpose
Existence check: The system checks whether the attributes from theTFIPR_ATTRTREE table are also in the TFIPR_ATTRIBUTE table. Inconsistententries are deleted.
Relationship check: The system checks the relationship entries for allattributes in the TFIPR_ATTRTREE table_
Does each attribute in the TFIPR_ATTRTREE table have a relationship
to its higher-level attribute?: Each attribute knows its lower-levelattribute. Only the highest attribute does not have an entry for itshigher-level attribute.
to its lower-level attribute?: If an attribute has more than onelower-level attribute, it knows only one of these attributes.
to the next same-level attribute?: Each attribute knows only onesame-level attribute. This leads to a chain of attributes at the samehierarchy level. The last attribute in the chain does not have an entryfor the next, same-level attribute.
Does each of these relationships refer to attributes that are in thesame attribute hierarchy?
Do all attributes in an attribute hierarchy belong to the same productcategory?
Totals check: Checks whether the number of attributes with the sameentry for the higher-level attribute is the same as the number ofattributes that there are for the chain of entries for the nextsame-level attribute. If the number of attributes with the same entryfor the higher-level attribute is higher, then the attribute that is notreferenced by another attribute is deleted. Instead, it is assigned tothe last attribute in the chain as the next, same-level attribute. Thistype of error can arise as a result of transports delivered by SAP ifthe customer has created attributes that collide with new deliveryattributes in the hierarchy.