Marketing Name
|
Marketing name of the product
configuration.
|
Name
|
Name of the product configuration.
|
Owner
|
Click
to search for and select a new person to own the
product configuration.
|
Date Effectivity |
Click to select the date on which the product configuration becomes effective. |
Milestone |
Click to search for and select a project milestone to associate with this product configuration. |
Sales Intent
|
Select 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
|
Select 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 it is preferred that this be blocked, you can configure the
command action to be hidden when the configuration is invalid.
- Order: For sale to customers.
- Accessory: The default for
product configurations based on variants and option groups. For a product
configuration in the context of a logical feature, the purpose is
Accessory and cannot be changed.
|
Top Level Part
|
Click
to select
Top Level Part to select the part
that is the top-level part for the product configuration. The top-level part is
the context for the product configuration and can be any part. 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. The
Search page opens. The criteria for
creating a top-level part are as follows:
- The part policy should be Development Part and it
should not be in the Obsolete state.
- The part should not be connected to other parts with
an
EBOM relationship.
- The part should not be connected to other product
configurations as a top-level part.
With regard to the BOM generation process, if you do not
assign a top-level part to a product configuration, one is automatically
created and assigned to the product configuration when the EBOM is generated
from the
Preview BOM page. The prerequisite
for this to occur is that in the context in which the product configuration is
present, a part family must also be present in that
GBOM. For example, if a product
configuration is present in the model version context, then in the model
version's GBOM a part family should also be present.
|
Description
|
Type the details of the product
configuration or replace the existing description.
|
Marketing Text
|
Type the marketing text for the product
configuration.
|