Create a property-based partition scheme

You create different partition schemes for a structure to include certain structure elements within them as per the business requirement.

Example

You create a functional partition scheme, and divide it into different partitions as per various functions such as electrical, mechanical, and so on. You include all the electrical parts of Crosskart within the electrical partition. Now, if a BOM engineer identifies that an issue with the brake assembly is due to some electrical component connected to it, the BOM engineer can work with the parts that are within the electrical partition instead of the entire Crosskart structure.

Creating a persistent partition scheme is a one-time setup. As part of this setup, you must perform the following tasks:

• Create a new partition scheme.
• Specify what type of partition this new scheme can use. The partition type should be partition-owned.
• Create a new partition. Make this partition partition-owned.

To simplify the preceding steps, you can use the following sample partition scheme guidance:

• For any partition scheme that you create, you must set the value of the Ptn0SchemeAllowedTypes business object constant to Ptn0PropertyBased.
• Set the value of the Ptn0IsOwningMemberships business object constant in Business Modeler IDE (BMIDE) to True (partition-owned).
• You use the sample condition called Ptn0IsPartitionableCond.

If you need to create any other persistent partition scheme, perform the following steps:

Procedure

1. Identify properties for partition scheme creation, and index them using Smart Discovery Indexing. You can index both item revision and occurrence properties. However, before indexing an item revision property, you must index at least one occurrence property.

   Structures are constantly updated. After you populate partitions of a structure with structure elements, elements can be added, removed, or modified. To ensure that the structure elements are correctly placed within appropriate partitions, you must set the Awp0SearchIsStored property constant to true for the workspace object properties that you have indexed (for example, PTY10), and which will be used as the search recipe.

   Caution To assign members to partitions automatically, you must mark at least one occurrence property for Smart Discovery indexing.

2. In BMIDE, locate the Ptn0SchemeAutoPopulate business object, and create a new business object under it, for example, Ptn0Custom_System.

3. In the newly added business object, go to the Business Object Constant tab, and edit Ptn0SchemeOrgPropertyNames.

   In the Modify Business Object Constant dialog box, include the indexed properties as Value in the following format:

   TypeName1.PropertyName1,TypeName2.PropertyName2
   

   Here, TypeName is a business object and PropertyName is the index property that you are using for the scheme creation.

   Make sure that the indexed properties that you include are available under the AWS_Discovery_FullTextSearch_FacetFilters preference.

   Example:

   Awb0DesignElement.PTY10,Awb0DesignElement.PTY20
   

   OR

   Awb0PartElement.PTY10,Awb0PartElement.PTY20
   

   OR

   ItemRevision.IndexedPropertyName1,ItemRevision.IndexedPropertyName2
   

   Ensure that the indexed property is not of the type Date.

   Caution In the Ptn0SchemeOrgPropertyNames business object constant for a scheme type, you designate the properties that you want to use for automatically populating a partition scheme. After you deploy the changes in BMIDE, these properties are also saved in the partition scheme instance that a business user creates.

   After the business user creates a partition scheme instance, you cannot change those properties in this partition scheme instance even if you change the properties in the Ptn0SchemeOrgPropertyNames business object constant.

   Therefore, to add, remove, or replace any properties, you must create a new scheme type in BMIDE.

   We recommend that you start by creating a scheme with a name that represents some number and then create another scheme with a new version in it. After that, you add any additional properties to the new scheme.

   Example: Consider that you have an existing partition scheme called SchemeA_v01 that has two properties associated with it. Now, to include an additional property, you create a new scheme called SchemeA_v02 and associate the additional property with this scheme. Then, you choose the SchemeA_v02 scheme and follow the next steps to create a persistent partition scheme.

4. In the Business Object Constant tab, edit Ptn0SchemeAllowedTypes.

   In the Modify Business Object Constant dialog box, you specify the types of partitions that can be created in the context of the partition scheme. It is recommended that the partitions in these schemes should have partition-owned membership.

5. Save and deploy the data model changes.

   Note The Active Workspace configuration is required to show the partition recipe properties in the primary work area, so that the user can interactively specify the property values to set the partition recipe.

6. Export the existing column arrangement in Active Workspace by running the export_uiconfig utility on the Teamcenter command prompt. Then, include the indexed properties in the exported XML file, for example, partitionCots.xml. You can specify any name that you want for this file. After you include the indexed properties in the file, the properties appear under the Partition Search Recipe Properties column arrangement in Active Workspace.

   The properties identified, for example, PTY10 and PTY20, to automatically add structure elements to partitions, may be of EBOM or of a regular BVR structure. If it's an EBOM structure, these properties are available on the part element. Else, the properties are available on the design element.

   After you save and deploy the data model changes in BMIDE, Teamcenter internally adds properties on the partition, which holds the recipe or criteria that are used to automatically populate partition members. These properties are prefixed with PS_. For example, PS_PTY10 and PS_PTY20.

   Note Note the following important points about the object type/property-name code snippets referenced in the source topic:

   • The Fgf0PartitionElement object is a part of the Fgf0Foundation template in BMIDE. This template is automatically installed while you are installing Partitions for Structure.
   • The columnName, filterable, and hidden properties are optional.
   • If the indexed properties are of an Item Structure (BVR) product, you must add the name and uri property values as Awb0OccurrenceManagement. Conversely, if the indexed properties are of an EBOM product, you must add the name and uri property values as Awb0OccurrenceManagement.Ebm0PartProductRevision.
   • Optionally, you can create only one file by merging the contents of these two files into a single file.

7. Finally, import the column arrangement in Active Workspace by running the import_uiconfig utility on the Teamcenter command prompt.