One type of ticket we often help with is determining the current status of a line item or unit. Sometimes, the unit status is not what you expected when viewing the Incomplete Items screen in Core or Tracking, or when viewing BI - Production - Incomplete Items. We receive questions like:
- Why isn't the unit marked Complete when I know it has already been produced?
- Why is it marked Complete when it should not be?
- Why isn't it marked Shipped now, when it was before?
The BI Unit Details page often clears up this mystery because it shows where and when a unit, and its parts, are scanned.
How to Open BI Unit Details
- In BI, navigate to Production > Incomplete Items
- Click on the Status column link for the unit.
This opens the Unit Details page (below) showing the status of the BOM. Scroll down to the History section for more details on where and when the unit was scanned and by whom. A unit's status comes from the last (most recent) scan.
Another path to the Unit Details page is:
- Search for the order number in BI
- Select Production Status from the Order Status header
- Select the link in the Status column for the unit you are interested in
Possible Causes for Incorrect Status
- A user may have accidentally:
- scanned the wrong label
- the label was for a different unit
- it was the wrong type of label (glass label vs. finished goods label)
- the label is for a different level of the BOM (individual lite of glass instead of the IG unit)
- missed a scan at a station in the work route
- performed a manual "scan" (not using the scanner) and mistyped the unit number
- scanned the wrong label
- The Tracking station settings may not be what you expect for this step of the work route
- Check that the station is in the correct mode, such as Part Updating vs. Ordered Part Updating
- Completion Poller and Reject Monitor - The Completion Poller is responsible for updating the status of completed, shipped and rejected units. If these statuses are not being reflected for many units, then verify the Completion Poller is running. The Reject Monitor processes rejected items, routing them to the Opti Remakes queue or the FeneVision Core Remake queue as designated by the configuration. Verify the Reject Monitor is running. See related article SQL Agent & FeneVision Agent Jobs
- One thing to keep in mind: FeneVision allows scanning of units after they are completed so the user has the ability to reject and return items, and to reprint labels at a completion station where the unit remains in the Complete state. So, at times accidental scans are the cause of the mystery.
- When using the Incomplete Items screen, investigate custom filters selected since it could be excluding some incomplete items.
- The unit was accidentally, or legitimately, rejected. For further details on reject issues, see Rejecting Troubleshooting
Common Troubleshooting Scenarios
Complete Items Showing in Incomplete Items:
A frequently reported issue is a completed item showing on the Incomplete Items screen. The cause is usually a user incorrectly scanned the item again at a station that does not complete items, which flips the status back to Accepted. In BI Unit Details, when you see an additional Accepted scan from some station after the Complete scan, and that is why the item is no longer Complete. If you need to reprint labels for the unit, use a completion station which keeps the unit status Complete.
Another frequent cause occurs with line items with multiple quantities and one unit gets missed. For example, the user, scans only 9 out of 10 ordered units complete.
Was the unit rejected and not correctly reprocessed?
The "Possible Causes for Incorrect Status" above lists more causes.
Incomplete Items Not Showing in Incomplete Items:
The "Possible Causes for Incorrect Status" above lists areas to investigate, including accidentally scanning the wrong unit. Troubleshoot these scenarios using the Unit Details page in BI. Don't forget to examine custom filters selected in the Incomplete Items screen, since they could be excluding some incomplete items.
Shipped Unit is No Longer Marked Shipped:
Verify there is no other scan after Shipped, because the unit may have been accidentally scanned again.
When transfer shipments are involved, the additional scan after Shipped status can reopen the order and/or add an additional shipping requirement in Route Builder. For manufacturers with multiple facilities, say a customer's order gets dropped at the wrong manufacturing facility when the order could not be delivered. This can cause the additional shipping requirement. And this can also occur due to an accidental scan.
Advanced - Tracking History in the Database
You can view the same information in BI Unit Details History for a unit with a query against the FVMaster database on the TrackingHistory table. Add the correct schedule and unit number into the query.
USE FVMaster
GO
SELECT * FROM TrackingHistory WHERE SchedID = 2222 and UnitID = 111 ORDER BY DateTime