Attributes

Definition of Attributes

You can use configurable attributes to add individual characteristics to the utilities product. You can maintain these in the utilities quotation and the utilities contract and save them with the values you assign here.

You can use rules to adapt the graphical display using icons, value helps and information texts to meet your specific requirements. You can also use rules or product-specific standard values to define values.

Note Note

Defining configurable attributes for a utilities product is dependent on the corresponding master data template in the SAP ERP System.

The external attributes in the master data template must have an equivalent in the SAP CRM System. If this is not the case, system displays an error message. You can also use additional configurable attributes that do not have an equivalent in the master data template.

We recommend defining configurable attributes for the product in the SAP CRM System for the external attributes in the master data template.

End of the note.

Attribute Characteristics

Attributes are displayed during product modeling in the attributes tree for the product and in the detailed view for the respective attribute.

Display in the Attributes Tree

The attribute is displayed with a description in a hierarchical format in the attributes tree. If the attribute has an original product, such as a reference product or product module, the system also displays this relationship here.

The following features are defined by the hierarchy:

Feature	Description
Group	The view ID is used to group attributes and is observed on the user interface at the time of sale. Note The group is displayed and changed in the attributes tree. End of the note.
Sorting	Sorting defines the sequence of attributes within a group. Note The sorting is displayed and changed in the attributes tree. End of the note.

Detailed View of the Attribute

The following characteristics are displayed in the detailed view:

Field	Description
Attribute ID	You assign the technical attribute ID in Customizing.
Description	The attribute description is assigned in Customizing and explains the meaning of the attribute.
Value Determination Type	Determines whether the attribute value is determined from the default value or whether an existing value is retained.
Default Value	The standard value is the attribute value that is entered as an initial value in the document at the time of sale and can be changed as required.
Mandatory	This defines whether the system requires you to make an entry in the document at the time of sale.
Render Type	This defines the way in which the attribute is subsequently displayed, for example as a selection button or selection list. Note Possible display variants are dependent on the data type recorded for the attribute. Text input fields are for example always dispalyed as standard input fields. End of the note.
Changeability	This defines whether the field content for an attribute can be changed in the document at the time of sale.
Transient Value	Attributes with this indicator do not have their own persistence. They are only used to display, check or calculate dependent attributes. A new value is determined every time and the source of the value can be external to the document. User entries can also be involved here. If this is the case, the system initializes the values each time they are opened. Example The system determines and displays the postal code from the point of delivery allocation for the item. This value is also used to calculate a price attribute. You do not have to persist the postal code in this case, since the system can determine it again from the point of delivery key transferred to the BRF rule at any time. One example of this is opening the document again. End of the example. Example The bank data for the assigned contract account is to be displayed on the configuration interface. The system also checks whether the payment method for the corresponding contract account is admissible for this product. The values determined for the bank number, account number, payment method and account holder are transient in this case, since they can be determined from the contract account key transferred to the BRF rule at any time. If the bank details are checked, you can assign a product-specific check rule to the payment method transient value. End of the example.
Condition-Relevant	The default setting for this indicator is No. The system only runs rules for this attribute once during assignment of the product at the time of sale. No is the recommended setting. If you select the value Yes for this indicator, changing a value triggers an immediate reevaluation of the configuration.