Non-Real Time Update Process

Location Touch works in both an Eclipse RF and non RF branch environment. In an Eclipse RF enabled branch the Location Touch cycle count process is real time meaning all cycle counts update Eclipse real time. In an Eclipse RF Branch, Location Touch uses the Eclipse warehouse operation queue, which is the exact same queue and process as used by the Eclipse RF warehouse management system. All transactions such as cycle counting, location adjustments, and movement of product between locations is real time. Any product count discrepancies created during the cycle count process update to the RF counts adjustment in Eclipse.

In an Eclipse non RF branch, cycle counting with Location Touch does not update real time. Rather, it uses the same manual Eclipse cycle count process where a cycle count is generated but instead of printing paper and keying in the counts manually, Location Touch is used to perform the cycle counts. As products are cycle counted the quantities are automatically updated in the Eclipse load in screen. The Eclipse variance report is then run and if required products can be recounted in Location Touch which will update the count into the Load In screen. Once the variance process is completed, the Eclipse "update physical on hand " program is run to update the cycle counts into Eclipse. The "update physical on hand" program will update the counts as the first transaction for the day that the count was updated (as displayed in the Eclipse load in screen).

In a non RF branch, it is recommended that counts are performed when the warehouse is quiet and all outstanding sales orders and PO receiving's have been identified. During the cycle count process, no movement of product or adjustments to locations should be initiated as this may impact overall inventory accuracy.

The first step for cycle counting in a Non RF branch is to generate the Eclipse cycle count control file.

As the cycle count is performed in Location Touch, the quantity counted for a product will be automatically updated in the Eclipse load in screen.

If products are added to the cycle count during the count process, meaning they were not in the original cycle count that was generated, a new control # will be added and the product will display on the Eclipse load in screen. If a recount is required, the recounted quantity will be automatically updated to the Eclipse load ln screen.

Note that when the update physical on hand program is run it updates the counts as the first transaction of the day. Location Touch will update the date in the Eclipse Load In Screen date field with the date the cycle count was performed on. If you need to move the date you can do so from the Eclipse load in screen.

It is recommended that the Eclipse variance report is run and reviewed after the cycle count is completed in Location Touch. Products may be identified on the variance report and recounted through Location Touch. There is no automated way to initiate a recount; rather the items need to be highlighted on the variance report, which then can be recounted in Location Touch.

When the cycle count is complete and approved, the update physical on hand program is run to update the cycle count quantities. This will update the counts as the first transaction of the day. If you need to change the date for any reason, you may do so from the load in screen.