Product Configuration Properties Page

The Properties page for a product configuration lists details about the configuration.

To access this page, open the required product configuration. See Opening a Product Configuration.

This topic describes:

This page discusses:

See Also
Product Configurations Page
Product Configurations Page for a Model Version or Logical Feature
Product Configuration Selected Options Page

Fields

Field Name Description
Marketing Name The marketing name for this product configuration.
Name The name for the product configuration.
Type The business object type: product configuration.
Revision The revision level for this product configuration.
Owner The person responsible for the product configuration.
Policy The policy that governs the lifecycle of the product configuration.
State The current lifecycle state of the product configuration.
Date Effectivity The effectivity date of this product configuration.
Sales Intent Indicates how the configuration is intended to be used to sell the model version:
  • Standard Configuration: Can be sold in the market and appears in a model version catalog.
  • Custom Configuration: Created for one customer and is not available in the model version catalog.
Purpose Indicates how the configuration will be used:
  • Evaluation: For internal engineering, for example, to test configuration rules.
    Note: It is possible to create an invalid configuration for evaluation purposes, and to generate a BOM from an invalid configuration for prototyping. If your company prefers that this be blocked, your Business Administrator can hide the command action when the configuration is invalid.
  • Order: For sale to customers.
  • Accessory: For a product configuration in the context of a logical feature, the purpose is Accessory and cannot be changed.
Based On The name of the model version or logical feature on which this product configuration is based.
Top Level Part The context for the product configuration and can be any part.

In the model version context, a part family can be created on the GBOM page. This part family is used to auto-generate the top-level part if one is not already assigned to the product configuration. If you do not assign a top-level part, a new part can be created from the context part family and assigned as the top-level part.

Derived From The product configuration from which this product configuration is derived.
Description Details that describe the product configuration.
Marketing Text Descriptive text used by marketing for this product configuration.
Base Price Displays the base price of the associated model version. This field is read-only.
Total Price Displays the total price of the product configuration, which equals the model version base price plus the prices of the selected variants and option groups with a key-in value set and the selected variant values and options.

This field can also contain if the total price needs to be recalculated because of changes to the price of the model version, variants, option groups, variant values, or options. Click to recalculate the total price and update the value shown.

Note: On mobile devices, the text "Out-of-date" is shown instead of and the total price cannot be updated because the content is read-only on that platform.
Rules Compliancy Status Indicates whether the product configuration is compliant with configuration rules:
  • Valid: Selected options are all compatible. No conflict was found.
  • Invalid: Some selected options are not compatible. They are in conflict with one or more rules defined in the system.
  • Unknown: No status was computed. Rules are disabled.
Completeness Status Indicates how complete the product configuration is:
  • Partial: At least one "must select" feature does not have a value, part of the model version definition is missing—the resulting model version is partial.
  • Complete: All "must select" features have a value and "single select" features have no more than one option selected—the resulting model version is coherent and complete.
  • Hybrid: At least one "single select" feature has multiple options selected, so the resulting model version is a mix of several valid model version—it is hybrid.
Originator The person who originally created the product configuration.
Model Version Context

Only shows if Based On is a logical feature.

Shows a model version derivation related with the Based On logical feature.
Originated The date the product configuration was created.
Modified The last time the product configuration was changed in some way.

Toolbar Commands

Action Description For More Information
Edit Details Edits the product configuration details.

Required access role: Author

and Configured BOM to validate design rules. 		Editing Product Configuration Properties
Preview EBOM Opens the Preview EBOM page where you can modify the configuration prior to generating an EBOM.

To successfully preview an EBOM, the product configuration must be associated with the top-level part of the context model version and should have a part family as GBOM.

Note: This action is not available under the following circumstances:
  • If the product configuration was created for a leaf node logical feature.
  • If the product configuration was created under a stand-alone logical feature with no model version context.

Required access role: Reader

Product Engineers must be licensed for both Variant Analysis and Reuse and Configured BOM to validate design rules. 		Preview EBOM Page
Generate Precise BOM Allows you to generate the Precise BOM. Click OK to close the confirmation message. Click Precise BOM in the navigation pane to view the generated PBOM.

You can only create a PBOM once. After creating it, this command is no longer available.

Note: This action is available for validated product configurations in the Active state. For a product configuration of a logical feature, this command is not available for leaf-level logical features.

Required access role: Author

Opening the Precise BOM