Specify the name and ID format for creating solution variants

Learn how to maintain consistency in the name and ID format of solution variants.

In Teamcenter, if the Enable Multi-Level Creation option is enabled, you can use the PSESolutionVariantItemProperties preference to specify a format for the name and the ID when creating a solution variant. This preference accepts a combination of values, which can be specified manually or can be system generated.

By default, this preference does not contain any values. If you do not specify any value or specify an invalid value, Teamcenter uses the name from the source structure and automatically generates the ID.

Procedure

To define the solution variant ID or name by combining existing property values from the source item revision, specify the internal names of the properties from the source Item Revision, separated by the plus (+) character. No spaces are allowed.

• To define the ID, use the following format: item_id_format=<itemrev_prop1>[+<itemrev_prop2>]*. For example, item_id_format=custom_prop1+item_id+custom_prop2.
• To define the solution variant object name, use the following format: object_name_format=<itemrev_prop1>[+<itemrev_prop2>]*. For example, object_name_format=custom_prop1+object_name+custom_prop2.

The resulting object name or ID is a combination of the specified property values and the system generated ID if the specified property is item_id, separated by the minus (-) character, for example, 000260-custom_prop1_value. The source name or ID gets truncated if it exceeds the limit for the maximum allowed length.

Teamcenter continues to support the earlier format for specifying values, for example, item_id=bl_item_object_desc and object_name=bl_rev_object_desc.

If you want advanced control of generating the solution variant ID, use the following format to generate the solution variant ID in two parts: an ID for prefix and an ID for postfix. The combination of these two parts creates the complete solution variant ID. Multiple values using this format are supported within the preference.

item_type_and_id_format="generic_item_type=<Source_Item_Type>;sv_item_type=<Solution_Variant_Item_Type>;prefix=<prefix_definition>;seperator=<separator_char>;postfix_start_value=<postfix_definition>"

Guidelines for generating the ID for solution variants:

• The keyword item_type_and_id_format creates the advanced logic for generating the solution variant ID and Item Type.
• The item_type_and_id_format and item_id_format must not be used together for creating the solution variant ID. The object_name_format can be used with item_type_and_id_format or item_id_format.
• Use generic_item_type to specify the source structure Item type. The values can be blank, Item, or any subtype of Item.
• When defining multiple item_type_and_id_format entries, each entry must specify a unique generic_item_type to avoid configuration conflicts.
• Properties that have attribute level security (ALS) enabled cannot be used in any preference value. ALS is enabled for a property by setting the Fnd0SupportAls property constant to true.
• Use sv_item_type to specify the required item type for the solution to be created. The values can be blank, Item, or any sub-type of Item. If left blank, the default Solution Variant Item type is used.
• Use prefix to define the initial part of the solution variant ID. The format is Item.item_id[N], where N indicates that only the first N characters from the source item's item_id is used for the prefix. For example, prefix=Item.item_id[6] uses the first six letters from the source structure.
• Use postfix_start_value to define the trailing part of the solution variant ID, used in conjunction with the prefix. You can use an alphanumeric incrementing counter without special characters. For example, if you specify A0A0A0, the postfix value is automatically incremented to A0A0A1, A0A0A2, and so on. You can use business object properties, such as Cfg0VariantCriteria.fnd0ThreadId and Item.custom_prop1.
• Use a separator as an optional single special character to be inserted between the generated prefix and postfix strings.
• The semicolon (;) is reserved as a delimiter for arguments within the item_type_and_id_format string itself. Therefore, it cannot be used as a value.

Example

item_type_and_id_format="generic_item_type=Part;sv_item_type=Part;prefix=Item.item_id[6];seperator=-;postfix_start_value=XYZ123"

Save your changes.