Automatically add structure elements to partitions

Before populating the partitions with structure elements, ensure that you have set the values of the indexed properties on partitions and structure elements correctly. After a property-based partition scheme instance is created, the property names that are listed in the Ptn0SchemeOrgPropertyNames business object constant are saved in the Teamcenter database, and you cannot change these property names.

To add the structure elements to the respective partitions, run the populate_property_based_partition_members utility on the Teamcenter command prompt:

populate_property_based_partition_members -u=admin_user -p=admin_user_password -g=dba -product=item_id_of_top_item

For detailed information about the different arguments of this utility, see its help on the Teamcenter command prompt:

populate_property_based_partition_members -h

When added to partitions, the structure elements are called partition members.

Tip

It is recommended that while creating partitions based on the indexed properties, you choose partition-owned memberships.

When you create a partition scheme that has properties specified, memberships are created automatically based on these property values.

When you add structure elements to partitions, the business user can create new partitions, partition hierarchy, and set or update partition recipes. Teamcenter automatically synchronizes the memberships based on the new partition recipes.

For this, it is critical that the user fully populates the recipes by specifying a value for each supported term or property in the recipe. If they do not specify all values in the recipe, the memberships are not created for the partition. After they populate all the values, Teamcenter automatically synchronizes the memberships based on the new partition recipe.

Note After the structure elements have been added to the partitions, the users cannot move or delete a partition.

Partition-owned membership vs. member-owned membership

For member-owned membership, the value of the Ptn0IsOwningMemberships business object constant in Business Modeler IDE (BMIDE) is set to false. This is applicable for the System and Functional partitions. Conversely, for a partition-owned membership, the value of the Ptn0IsOwningMemberships business object constant in BMIDE is set to true. This is applicable for the Zone and Manufacturing partitions.

If you are the owner of an assembly, you create member-owned memberships while organizing your data in a partition hierarchy. Thus, you have the access privileges to perform various tasks on your data, such as create, copy, and paste.

If other users need to organize your data in a partition hierarchy, they create partition-owned memberships for your data. This is because they do not modify the data, they just organize the data. Thus, partition-owned memberships do not require you to have any access privileges on the data.

When you create partitions based on the indexed properties, the partitions own the data. Therefore, it is recommended to choose partition-owned memberships while creating partitions. If you choose member-owned memberships and the populate_property_based_partition_members utility is run, for your data, the Last Modifying User and the Last Modified Date fields get updated to the Admin user who has run the utility. Instead, when you choose partition-owned memberships and the utility is run, the data is not modified in any way. In this case, the owner of the data, the Last Modifying User, and the Last Modified Date remain as they are.

Essentially, for member-owned memberships, Teamcenter checks the privileges against the data. Conversely, for partition-owned memberships, Teamcenter checks the privileges against the partition.

Repopulate property-based partition schemes after synchronization interruption or reindexing

Overview

Structure Partitions uses a background synchronization process to keep property-based partition schemes up to date with changes made in Teamcenter. This process continuously monitors changes to BOM lines, partitions, and component properties. Then, it automatically updates the relevant partition schemes in near real time.

When this synchronization process is interrupted for an extended period, or when a full reindex of the search index is performed, previously populated property-based partition schemes can become desynchronized. In such cases, you must repopulate all affected schemes to restore data consistency before resuming normal operations.

You can use a single command to automatically repopulate all previously configured property-based partition schemes. You do not need to repopulate each scheme individually.

How does synchronization work?

When you perform the initial population of a property-based partition scheme using the populate_property_based_partition_members utility, Teamcenter registers that scheme for continuous background synchronization. From that point on, any changes made to the relevant products and components in Teamcenter are automatically detected and reflected in the corresponding partition schemes.

Teamcenter tracks only the schemes for which the initial population has been completed. Products and schemes for which the initial population has not been run are not maintained by the background process.

When is the synchronization lost?

Synchronization can be lost in the following situations:

Background process interrupted beyond the threshold period:

The background synchronization process must run continuously to maintain data consistency. Teamcenter retains the log of pending changes for a configurable threshold period.

Note The TC_TIMESTAMP_THRESHOLD parameter specifies the number of hours till which the timestamp records are to be retained. For a site, you can add the value for this parameter in the POM_PARAMETERS table. If no value is added, Teamcenter considers 96 hours as the default value.

For more information about managing the maintenance of the POM_timestamp table, see POM_timestamp maintenance.

If the background process does not run within this threshold period, Teamcenter automatically clears the pending change log. When the background process resumes, it has no record of what changed during the interruption, and the property-based partition schemes are no longer in sync with Teamcenter.

Full reindexing of the search index:

When a full reindex of the Solr search index is performed, the pending change log is cleared because reindexing rebuilds the index from scratch. Therefore, the synchronization registrations for property-based partition schemes are lost, and the schemes are no longer maintained by the background process.

Note If Global Search Index, or Smart Discovery Index, or both of these indexes are redone, you must restore the synchronization for all previously populated property-based partition schemes. To know how to do that, see the "How to resolve synchronization loss?" section below.

Impact of synchronization loss

When synchronization is lost, the following occurs:

• All property-based partition schemes that were previously populated and actively maintained are no longer updated when changes are made in Teamcenter.
• The partition membership data becomes stale and does not reflect the current state of the product structure.
• The background process cannot automatically recover the lost synchronization registrations.

How to resolve synchronization loss?

To restore synchronization for all previously populated property-based partition schemes, run the following command before restarting the background synchronization process:

populate_property_based_partition_members -u=admin_user -p=admin_user_password -g=dba -repopulateAllSchemes

This command automatically identifies all products for which property-based partition schemes were previously populated and repopulates all of those schemes. You do not need to identify or specify individual schemes manually.

After the command runs successfully, restart the background synchronization process. The background process resumes maintaining all repopulated schemes automatically.