How Sourcing Rules are Applied
It is important to understand how the sourcing rules are applied in order to avoid global changes that are undesirable.
Consider the following information:
• To define a set of parts to which the rules are applied, you must select the supplier, the sourcing context, and the classification node (if Windchill PartsLink is installed). When you execute the rule, all parts that belong to that set change their sourcing status to the value specified by the rule.
• You can create a rule that specifies a different sourcing value for each node in the classification structure. The rule applies the sourcing values to the specified node, and any child nodes. When defining rules for several nodes, the Sourcing Status Assignments table lists each node as a row with the assigned sourcing status value.
• The position of the row defines the priority of the sourcing assignment. The top row has the highest priority.
• Applying the rules does not require you to check out OEM parts.
 |
If parts are checked out by other users, the sourcing rules cannot be applied to them.
|
• The sourcing rules are applied to parts even if the wt.property com.ptc.windchill.suma.iterateOnModifyPreference is set to yes (which requires OEM parts to be checked out before making changes to the AML/AVL). In such cases, the sourcing status value is updated without iterating the part.
 |
All attempts to apply rules to parts that are checked out are recorded in a log file defined by the propertycom.ptc.windchill.suma.access.errors.log.filename.
The default log file SourcingRules.log is located in the common Windchill log directory. The output to the log file can be configured by the property com.ptc.windchill.suma.access.errors.log.enabled. This property is set to true by default.
|
• Executing the rules is done independently of the access control list that is associated with the user that initiated the action.