|
Preference
|
Description
|
||
|
List of applicable plant-specific functional data types
|
Specifies the types of plant-specific functional data that apply when creating plant-specific functional data objects from Windchill. This preference is available at User and Site levels.
|
||
|
Load The Structure in Visualization Tab On Demand
|
Allow loading of part structure either automatically or on need basis in the Visualization tab of Process Plan Browser. The default value is No, the part structure is loaded automatically. When set to Yes, a manual action will be required to load the part structure. Use this option when you want to load the part structure on a need basis and prevent performance issues, especially when loading large part structures. Click  ‘Load the structure in Creo View’ in the Visualization tab toolbar to load the part structure manually. The Load the structure in Creo View action is disabled when the preference is set to No. |
||
|
Automatically Create Plant-specific Functional Data
|
Specifies whether plant-specific functional data objects can be created automatically when creating enterprise data or through a loader after creating the enterprise data. Select Yes to create the objects automatically or No to create the objects through a loader. The default value is No.
|
||
|
Part Types for Creating Plant-specific Functional Data
|
Specifies the part types for which plant-specific functional data objects can be created as per the mapped view-specific enterprise data type. The mapping between the plant-specific functional data type and view-specific enterprise data type is defined in the preference: Plant-specific Functional Data Types for Enterprise Data.
|
||
|
Plant-specific Functional Data Types for Enterprise Data
|
Specifies the types of plant-specific functional data objects that can be created for each view-specific enterprise data type. The view-specific enterprise data types are listed based on the values entered in the preference: Views with Specific Enterprise Data.
|
||
|
Plant-specific Functional Data Types for Part Type
|
Specifies the types of plant-specific functional data objects that should be created for a part type. The part types are listed based on the values entered in the preference: Part Types for Creating Plant-specific Functional Data.
|
||
|
Include related Plant Specific Functional Data objects
|
Allows the user to specify which plant-specific functional data objects related to the selected parts or enterprise data objects should be displayed in the collector window by default.
• Select All to display plant-specific functional data objects for the initially selected and collected parts or enterprise data objects.
• Select Initially Selected Only to display plant-specific functional data objects only for the initially selected parts or enterprise data objects.
• Select None to hide the plant-specific functional data objects.
|
||
|
Maintenance of Equivalent Links to Self
|
Specifies whether the equivalent links to self, existing for downstream iterations reused as is from upstream, should be updated automatically or manually by end users when there is a change in the upstream structure. Valid option is Manual or Automatic.
|
||
|
Stop Structure Expansion by Criteria
|
Allows user to stop expanding the structure by given criteria. Specify the value in the following format:
Type:< part type>
For example, Type:wt.part.WTSubPart1
|
||
|
Enable Structure Cache
|
Specifies whether or not to generate the cache for MAPSB and SAPSB sessions. The default value is No. This user level preference controls the default behavior for handling structure content to improve MAPSB and SAPSB performance.
• Select Yes to store the entire structure information of a session in cache. This helps to improve performance in MAPSB actions.
• Select No if you do not want to store the structure information of a session in cache.
|
||
|
Allows Reuse of Existing Downstream Objects
|
Specifies whether or not to reuse the existing downstream object when the New Downstream Part action is invoked. The default value is Yes. When set to No the action will not reuse existing downstream objects. When set to Yes the action will reuse existing downstream objects.
|
||
|
Consider Applied Filters for APSB Actions
|
Specifies whether or not to consider the filter criteria for review and update actions while updating the downstream structure. The default value is No.
• Select Yes to consider the filter criteria. The downstream structure is updated and refreshed to display the structure according to the filter criteria.
• Select No to ignore the filter criteria. The downstream structure is updated and refreshed to display the structure without considering the filter criteria.
Some of the review actions are:
• Select Equivalent Parts on Other Side
• Select Equivalent Occurrence on Other Side
|
||
|
Implicit Replacement of Parts in Downstream for Replaced Part in Upstream
|
Specifies whether or not to replace a downstream part with a replaced upstream part. The default value is No.
Select Yes to replace the selected part in the downstream structure with:
• A replaced upstream part, if an equivalent downstream part does not exist for the upstream part.
• An equivalent downstream part, if it exists for the replaced upstream part. A warning message appears if multiple downstream equivalent parts exist for the replaced upstream part.
Select No if you do not want to replace the downstream part with the replaced upstream part.
|
||
|
Allow Plant-specific Filtering in MAPSB and SAPSB
|
Enables the Plant Filter tab in the Edit Filter dialog box in MAPSB and SAPSB. This tab allows plant filtering in MAPSB and SAPSB. This is a site level preference. The default value is No. If set to Yes, the Plant Filter tab is visible in MAPSB and SAPSB.
|
||
|
Views with Specific Enterprise Data
|
This is a site level preference. The Assign Plant action is available only if you specify a valid value for this preference in the Value field. Specify the value in the following format: ViewName1:Type1 Enterprise Data, ViewName2:Type2
|
||
|
List of Applicable Views
|
Defines the list of applicable views available in MAPSB and SAPSB components. The data is entered as a list of comma separated values. For example: Design, Manufacturing, Service
|
||
|
Load The Structure in Visualization Tab On Demand
|
Allow loading of part structure either automatically or on need basis in the Visualization tab of Process Plan Browser. The default value is No, the part structure is loaded automatically. When set to Yes, a manual action will be required to load the part structure. Use this option when you want to load the part structure on a need basis and prevent performance issues, especially when loading large part structures. Click ‘Load the structure in Creo View’ in the Visualization tab toolbar to load the part structure manually. The Load the structure in Creo View action is disabled when the preference is set to No.
|
||
|
Allow Positioning for Analysis of Equivalent Occurrences
|
This is a site level preference. The default value is Yes. If set to Yes, the occurrences with the same absolute position as some occurrence on the other side of the structure will be considered as consumed.
|
||
|
Display All Linked Iterations In Iteration Tables
|
Select True if you want the system to display every iteration of an object that is linked to the selected object.
Select False if you do not want the system to display every iteration of an object that is linked to the selected object. Only the iteration that matches the configuration specification is displayed.
|
||
|
Default Selection For Update Usage Options
|
When set to True processes downstream usages for which at least one valid occurrence link can be found to an upstream BOM.
|
||
|
Synchronize Configuration Specification and Filter Criteria between Upstream and Downstream
|
This preference will synchronize the configuration specification and filters between Upstream and Downstream based on the selected options.
|
