Determining precedence in MVL

MVL statements comprise the following three elements: Error checks, consisting of error, information, or warning messages Internal module constraints Child module constraints Teamcenter expects each statement to contain these elements in the order listed. When you use the Internal module constraints dialog box and the Child module constraints dialog box to construct constraints or error checks, respectively, Teamcenter arranges the MVL elements into the required order. However, if you develop statements in the MVL editor and enter the elements in an incorrect order, Teamcenter does not rearrange them. No error or warning messages are displayed, but the variant structure may not be configured correctly. Similarly, if your MVL statements contain comments, Teamcenter may not rearrange the elements into the required order. Also, internal and child constraints are evaluated in the following order, where 1 has the lowest priority and 7 the highest: Default User set Set User fix Fix External Variant item For example, a user set takes precedence over the default value of an option for a given type of constraint.