About dynamic attributes

Classified and configurable products can include attributes to define their characteristics. In CPQ, product characteristics are represented by dynamic attributes (DAs), which hold values for those characteristics. Product modelers can use these characteristics to define rules that explode subcomponents of a main product.

A dynamic attribute (DA) is a non-standard data point primarily used in product configuration. Characteristics synced from SAP ERP are created as dynamic attributes in Zilliant CPQ.

Dynamic attributes are of two types:

• Dynamic Data Attribute (DDA)—Holds literal values (Boolean, string, numeric, date, currency) but lacks localization support for string values.
• Dynamic Symbolic Attribute (DSA)—Holds string or text values with localization. The range values must exclude special characters (such as vertical bars, periods, commas, and spaces) except for dashes and underscores.

In this topic, learn about:

• Accessing dynamic attributes
• Dynamic attribute data types
• Dynamic attribute properties

Access dynamic attributes

1. From the application left navigation area, select Model.
2. From the top navigation bar, select Attributes Management.

You will see a list of dynamic attributes.

Dynamic attribute data types

Dynamic attributes support the following data types:

• Dynamic Data Attribute (DDA)—Boolean, string, numeric, date, currency.
• Dynamic Symbolic Attribute (DSA)—String.

Numeric data type allows setting minimum and maximum values and precision. If you don't set the precision, CPQ uses the global precision setting.

Currency data type allows a DDA to hold the value and currency information. DDAs of this type are used when CPQ utilizes the internal pricing engine with a pricing step that fetches the attribute value and currency.

Dynamic attribute properties

You can configure dynamic attributes with additional properties:

• Enumerable—Available for DDA (only string or numeric data type) and DSA. If an attribute is enumerable, users can select the attribute value from the dropdown list. For DDA, range values cannot contain special characters (such as vertical bars, commas, or spaces); if needed, convert to DSA and localize values without special characters.
• Mandatory—User or system must define a value for a mandatory attribute. Without a value, SalesItem (SalesItem represents a line item in a quote) errors occur and users can't submit a quote (a sales document). Set an attribute as mandatory through attribute global properties, product conditional rules, or IMCScript.

• Read-Only—Marks attributes as non-editable by users. Set an attribute as read-only through attribute global properties, product conditional rules, or IMCScript.

• Multi-Value—Allows multiple values for an attribute. Multi-value attributes can be set globally or through a rule. Set an attribute as multi-value through attribute global properties or product conditional rules.

• Hidden—Conceals the attribute from users on the configuration page. Set an attribute as hidden through product conditional rules, IMCScript, or DA profile.

• Costing Relevant—When marked as costing relevant, the attribute triggers the internal pricing engine to calculate total SalesItem cost/price based on interactive pricing settings. Set an attribute as costing relevant through attribute global properties, product conditional rules, or IMCScript.

• Use Lookup Table for Range Value—Allows DSAs to pull range values from a lookup table. Requires to set the following properties:

  • Lookup Table Name—Defines the lookup table name to retrieve the range value based on the Lookup Field for Range Value property.
  • Lookup Field for Range Value—Defines the field in the lookup table to retrieve range values.
  • Lookup Field for Localization—(Optional.) Defines a localized range value. The table must include the SPRAS column for language code maintenance.