Debug-Defect-Entry

Creation date: 2/28/2023 9:29 PM Updated: 3/3/2025 9:05 PM ate debug defect defect fix defect status logfile review rework unit location unit status

1. There is an error while processing the unit where the unit fail due to a defect called "Bubbles".

Image 1

2. When the unit is fail at a test process, unit location will become "Debug" and unit status will become "In Process"

Image 2

Image 3

3. At unit history, user will be able to see the details of the defect such as the defect status, fail item, defect code and other related information.

4. When the defect status, which is the test code status stays in Open state, user is NOT allow to proceed to next process until user close the defect. User is required go to Production > Debug to either send to rework by click on the "Submit" button or retest the unit by click on the "Retest" button.

5. When user click on the "Retest" button, all the defects will be CLOSED to allow user to re-run the unit to retest. On the other hand, user can also just directly re-dump a logfile to ATE which is equal to manually click on the "Retest" button on the Debug/Review page where system will automatically close the previous defect of the same unit.

Image 4

6. When user retest the unit, the unit defect will be CLOSED, and unit location will be changed to WIP and status will be changed to In Process to allow user to re-run the process.

Image 5

Image 6

7. However, if a rule hierarchy called "RetestLimitWithoutDebug" is set, then there will be a limit for retest, which mean user will NOT be allowed to retest or redump the logfile when user has exceeds the limit to retest. The "Retest" button on Debug/Review page will be DISABLED and ATE will also NOT be able to process the logfile successfully as system will NOT automatically close the previous defect and it will show an error message that indicates invalid unit location and unit status.

8. When user has exceeds the limit to retest, user is required to rework the unit by click on the "Submit" button on Debug/Review page to send the unit to rework.

Image 7

9. When user has successfully send to unit to rework, the unit location will be changed to "Rework" and unit status will be changed to "In Process".

Image 8

Image 9

10. Then, user can go to Production > Rework > Rework to rework the unit.

11. User is required to rework the unit by following the sequence showed in Image 10.

Image 10

12. After user has successfully reworked the unit, the unit location will be changed to "WIP" and unit status will be changed to "Queued". A new task called "Rework" will be displayed in unit history.

Image 11

Image 12

Image 13

Retest for Quantity Route Step = Quantity

1. If user had fail at route step equal to quantity for test operation, the quantity will appear in Debug/Review. Example below is showing 2.

2. User can go to Debug/Review page by Production >Rework>Debug and click on the "Search Icon" as below

2. Key in Work Order (step 1) and select operation (step 2) key in the quantity and generate (step) 3.

For step 3 the quantity allow is smaller the quantity equal to 2 or smaller at step 1 (This quantity is depend on the quantity you had fail at step 1 need to smaller or equal to).

3. After clicking generate it will appear a tab like this with temporary serial number to temporary hold the quantity inserted at step 2 and

3. Click on the dropdown list (step 1) and select a fail item, after that click on add (step 2) and key in Note on (step 3). Finally click on Retest (step 4)