Status entry: Scenario

The Status entry in revision rules selects item revisions based on their release status. The Status entry provides you with various settings, including selecting any release status, a specific status, or statuses configured by release date, effective date, or effective unit number. Understand the Status entry in revision rule with an example. A status entry is used for selecting item revisions that are released with a particular status. The following settings are available for status entries: Any release status Teamcenter configures the latest item revision with a released status, regardless of the actual status. Selected status Teamcenter configures the latest item revision with a selected status type. This setting allows you to configure a structure that contains only item revisions with a specified status. Released date Teamcenter selects the latest item revision according to the date the revision was released (that is, the date the particular status was added). Effective date Teamcenter selects the latest item revision according to effectivity dates defined on the release status. Effective unit number Teamcenter selects the latest item revision according to unit numbers defined on the release status.

Example of status hierarchy in a revision rule The following example shows how to use status hierarchy in a revision rule: Copy Has Status( Production, Configured by Date Released ) Has Status ( Pre-Production, Configured by Date Released ) Assume you configure the following item with this rule (dates are release dates): Copy Part1/A : Status = Pre-Production [1-Apr-2007] Part1/B : Status = Pre-Production [1-Jun-2007] Part1/C : Status = Production [1-Aug-2007] Part1/D : Working Part2/A : Status = Pre-Production [1-May-2007] Part2/B : Status = Production [1-Jul-2007] Part2/C : Status = Pre-Production [1-Sep-2007] Part3/A : Status = Pre-Production [1-Aug-2007] Part3/B : Working Teamcenter configures Revision C of Part 1 because it is the most recently released revision with Production status. It configures Revision B of Part 2 because it is also the most recently released revision with Production status. The later preproduction revision is not configured. It configures Revision A of Part 3. There is no revision with Production status, so it configures the latest Pre-Production revision.

Note The rule in this example creates a status hierarchy. If possible, the rules configures a Production release, but if one is not available, it configures a Pre-Production release.

Example of effective date configuration in a revision rule The following example shows effective date configuration in a revision rule: Copy Has Status( Production, Configured by Effective Date ) Assume you configure the following item with this rule (dates are effective date ranges): Copy Part1/A : Status = Production [1-Apr-2007 to ... ] Part1/B : Status = Production [1-Aug-2007 to ... ] Part1/C : Status = Production [1-Nov-2008 to ... ] The release status has both start date and end date attributes, but typically the end date attribute is not populated. The system selects the latest effective revision of the appropriate status type with a start date before the date specified in the date revision rule entry. If no date is set in the rule, it defaults to today, and the revision with the latest start date is selected. In the previous example, if today's date is sometime in 2007, Teamcenter configures revision B, because it has Production status and also has the later effective start date of the two revisions effective in 2007. If no start date or end date are defined on the release status of an item revision, it is assumed to be not effective; that is,effectivity criteria must be defined for an item revision to become effective, Example of effective unit number configuration in a revision rule The following example shows effective unit number configuration in a revision rule: Copy Has Status( Production, Configured by Unit Number ) Assume you configure the following item with this rule: Copy Part1/A : Status = Production [3 to 10] Part1/B : Status = Production [11 to 15] Part1/C : Status = Production [16 to UP] If the unit number is set to 3, Teamcenter configures revision A. Revision A falls within the range 3 to 10, but neither of the other ranges. If the unit number is set to 11, Teamcenter configures revision B. Revision B falls within the range of 11 to 15 upward, but neither of the other ranges. If the unit number is set to 16, Teamcenter configures revision C. Revision C falls within the range of 16 upward, but neither of the other ranges. If the unit number is set to 2, no revision of Part1 is configured. Unit number 2 is outside the effectivity ranges of all three parts. The release status has both start unit and end unit attributes, and typically both attributes are populated. The system selects the revision of the appropriate status type with the start unit closest to, and before, the unit number specified in the unit number revision rule entry. If no unit number is set in the rule, there is no practical default and no revisions are selected If no start unit or end unit are defined on the release status of an item revision, it is assumed to be not effective. That is, the effectivity criteria must be defined on an item revision to make it effective. Split unit number ranges can be defined by attaching multiple release statuses to the status type. If multiple revisions are eligible for configuration, the one with the highest start unit number is selected.