Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF-CFG (Application Component) Product Configuration⤷
COM_IPC_UI (Package) Call and Interaction with the IPC User Interface
Basic Data
| Data Element | COMT_VARIANT_KEY |
| Short Description | Variant Condition Name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | COMT_VARIANT_KEY | |
| Data Type | CHAR | Character String |
| Length | 26 | |
| Decimal Places | 0 | |
| Output Length | 26 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Vcond. key |
| Medium | 15 | Vcond. key |
| Long | 20 | Vcond. key |
| Heading | 10 | Vcond. key |
Supplementary Documentation - COMT_VARIANT_KEY_MD0001
Use
The variant condition key can be used to create variant conditions for a configurable product.
The attribute VARIANT_CONDITION_KEY is a multiple-value attribute which is not visible in the configuration but is determined internally. It is assigned automatically to the configuration hierarchy. Due to the fact that it can have multiple values, several values can be assigned to it during configuration and therefore several variant conditions used in pricing.
You define the values allowed for the variant condition key for the relevant category in the configuration hierarchy by maintaining the value range for the attribute VARIANT_CONDITION_KEY. Alternatively, you can maintain the values allowed for a specific product by maintaining values for the attribute VARIANT_CONDITION_KEY on the tab page Configuration. Note however that you can only do this if you have not maintained any values at category level.
Dependencies
When defining a variant condition on the tab page Conditions in product maintenance, you enter a variant condition key and the price that applies to this key.
The variant condition is evaluated in pricing when this variant condition key is determined on the basis of the configuration selected.
You define when the variant condition key is evaluated in pricing. You can do this as follows:
- You assign a specific variant condition key directly to an attribute value. You can do this at product level on the tab page Configuration. The variant condition is evaluated in pricing as soon as the attribute has this attribute value.
- You define object dependencies so that the variant condition key is assigned a value. You can maintain these object dependencies at category level in the configuration hierarchy.
Example
History
| Last changed by/on | SAP | 20050311 |
| SAP Release Created in |
