When auto-logging is enabled, the system automatically generates log entries for many unquality events. Users can also manually create unquality event log entries connected with a sales order, purchase order, branch transfer, or an internal event. For example, if an employee goes to pick the 10 items and an order and only finds 5 of the item on the shelf, the employee can create a UET log entry for stock-unavailable or stock miscount. Train your users prior to giving them authorization to make a manual UET entry.
To enter an unquality event manually:
From the Events > Unquality Event Tracking menu, select UET Log Entry to display the UET Log Entry window.
You can also display this window by using the Shift-F6 key sequence from any window.
In the Category field, select the category to assign to the event: Customer, Internal, or Vendor.
In the UET Code field, select the UET code to assign to the event.
The system populates the following fields:
Note: Set the Do Not Log UET Events If UET Code Is Missing to Yes, to keep blank log entries from being entered.
Field |
Description |
UET Type |
(View Only) The two-letter UET Type and the type description. |
Downloaded to PC |
(View Only) Indication that this log entry has ever been downloaded for further analysis. The system selects this check box after downloading this event. |
Branch |
The branch where the unquality event occurred, which is always the shipping branch. The only other branch used in the UET system is the receiving branch in a branch transfer, and that branch number is entered in the Cus/Ven/Br field. |
Entry Date |
The date this log entry was created. Update the date, if necessary. |
Time |
The time this log entry was created. Update the time, if necessary. |
User |
The user ID of the person who created this log entry or was logged on when the automatic code was logged. When you create a log entry, the system populates the field with your user ID, but you can change it to another user ID, if necessary. |
If you display this window by pressing Shift-F6 from a transaction window, the system might also populate the Tracker #, Branch, Cus/Ven/Br, Ordr/Inv#, and Product fields with information from the transaction and the line on which the cursor was positioned in that transaction.
Complete the following fields in the Reference Information area, as needed:
Field |
Description |
Tracker # |
The tracker from which you accessed this window using Shift-F6. |
Cus/Ven/Br |
The customer, vendor, or branch associated with the event. |
Order/Inv# |
The order or invoice number associated with the event. |
Product |
The product associated with the event. |
Complete the following fields in the User Defined area, as needed, to describe the unquality event:
Field |
Description |
Qty Off |
The number the quantity was over or short from the ordered amount. Enter quantities less than the amount ordered as a negative number and quantities greater than the amount ordered as a positive number. For example, if the amount ordered was 25 units and only 15 arrived, enter -10. If the amount ordered was 25 and 50 arrived, enter 25. |
Days Off |
The number of days the delivery was early or late. Enter days before the promised date as a negative number and days after the promised date as a positive number. For example, if the shipment was to arrive on Monday and did not arrive until Thursday, enter 3. |
User ID |
The ID of the user logging the event. |
Type |
Whether the event was initiated by a Callback or Question. |
Orig ALog |
Original activity log entry, or tracker, to which this event applies. |
Revision |
A system-assigned revision number. |
Phase |
When logging a programming unquality event, select the programming phase to which the event applies. |
Location |
When logging a programming unquality event, select the programming account to which the event applies. |
In the Comments field, enter or view comments about this event. The system also adds these comments to the change log of the associated order.
More Options in the UET Log Entry Window
The following options are available from the UET Log Entry window:
To... |
Select this menu option... |
Select inquiry options for the selected field in view-only mode. |
File > View Item |
Select inquiry options for the selected field in edit mode. |
File > Edit Item |
File > View UET Log |
|
To create a tracker assigned to the activity log of the entity entered in the Cus/Ven/Br field. The system copies information from the UET Log Entry window, including the text in the Comments field to the tracker. |
File > Create Job Queue |
Delete the current log entry. If the log entry has been downloaded, the system displays a warning message prior to deleting the entry. You must have UET.EDIT (Level 3) authorization to delete a log entry. |
File > Delete |
See Also: