Show TOC

Background documentationField Attributes (Attribute Group with BDT Application and with Feature ID)

 

The product change function handles feature attributes and matrix elements individually. The field attributes, however, are handled together in the form of attribute groups, defined in the system Customizing settings. The system first determines whether the Attribute Group Exists indicator is set for an attribute group in the source and target products. The following overview shows when an attribute group in the product counts as “existing”.

· The Attribute Group Exists indicator is set.

· The Attribute Group Exists indicator is notset.

Attribute group with feature ID

Attribute group status

The Attribute Group Existsindicator

The superordinate feature attribute of the attribute group has a green traffic light in the product.

The superordinate feature attribute of the attribute group has a red traffic light in the product.

During a product change, the system handles the attribute groups differently, depending on the circumstances. There are four different cases. These depend on the value of the Attribute Group Exists indicator ( ) in the source product and the target product. Be aware of the different symbols used in the following overview. Instead of the traffic lights for the attributes ( ), the indicators ( ) of the attribute groups are displayed.

The Attribute Group Existsindicator

Claim

Source product

Target product

Contract after product change

A

B

C

D

Below you can see which values the fields of a contract have after the product change, depending on the case involved.

  • Case A: +

The fields belonging to an attribute group do not exist in the contract, also after the product change, so they cannot reflect any values.

  • Case B: + (attribute group no longer exists after the product change).

    A distinction is made, depending on the following conditions: The relevant feature attribute has an open padlock in the target product . The attribute origin of the attribute group reflects value 0100 (field values of the source contract).

    • If both conditions apply, the fields belonging to an attribute group exist in the contract after the product change and reflect the field values of the source contract.

    • If one of the conditions does not apply, the fields belonging to an attribute group no longer exist in the contract after the product change so they cannot reflect any values.

  • Case C: + (attribute group exists again after the product change).

    A distinction is made, depending on the following conditions: The relevant feature attribute has an open padlock in the target product . The attribute origin of the attribute group reflects value 0100 (field values of the source contract).

    • If both conditions apply, the fields belonging to an attribute group exist in the contract after the product change and reflect the field values of the source contract.

    • If one of the conditions does not apply, the fields belonging to an attribute group no longer exist in the contract after the product change so they cannot reflect any values.

  • Case D: + (attribute group still exists after the product change).

    • If the attribute origin of the attribute group reflects value 0100 (field values of the source contract), after the product change, the fields in the contract reflect the field values of the source contract.

    • If the attribute origin of the attribute group reflects value 0200 (attribute values of the target contract), after the product change, the fields in the contract reflect the attribute values of the target product.