Debug Retest Limit
Creation date: 5/30/2023 11:09 PM
Updated: 5/30/2023 11:09 PM
1. When user set a rule hierarchy named RetestLimitWithoutDebug, then a limit will be created for retest action. The limit will be determined by the rule hierarchy value like Image 1.
Image 1
2. In order to retest the unit without rework, user will have to go to Maintenance > Operation Sub Type Maintenance page to setup the operation and tick the Allow Retest Without Rework option.
Image 2
3. If the limit is set to 3 and the operation is allow to retest without rework, then user will only be able to retest the fail unit for 3 times. When the unit has failed for the forth time, the button on Debug/Review page will be DISABLED and user is required to send to rework.
Image 3
4. On the other hand, if the unit was processed through ATE, the defect will be automatically closed when user dump the file again for the same unit. This action will be limited to 3 times when the rule hierarchy is set.
5. If a rule hierarchy called ResetRetestLimitWithoutDebug is set, then after the unit was sent to rework, the limit for retest of the particular operation will be reset and the limit will based on another rule hierarchy called ResetRetestLimitWithoutDebugCount.
6. For example, if the rule hierarchy ResetRetestLimitWithoutDebug is set and ResetRetestLimitWithoutDebugCountis set to 1, then the unit is only allow to retest for 1 time after the rework process for operation FCT01 like Image 4.
Image 4
Action Required: User
DataImage19.png
DataImage53.png
DataImage37.png
DataImage23.png