Location Touch Control Files

Applies to RF Cycle Counts only

Enabling this control file will give a user with authorization key PRD.LOCATION.MAINT level 3 the option of aborting out of the related counts process.

This control file is only used if the user does not already have authorization key RF.COUNT.ABORT. If they do, the level of that authorization key will determine the abort behavior. Please see the Authorization Keys article for more information.

Applies to both RF and Non-RF Cycle Counts

When the entered count does not match the on-hand quantity for the location AND the dollar value of  the discrepancy is a negative adjustment, but a lower value than what is set in this control file, the inventory adjustment is made, as long as user has PRD.LOCATION.MAINT level 2 and above, and the user will not be taken through the related counts flow.

If the value of the discrepancy is a negative adjustment and the value is greater than what is set in the control file RF Cycle Count Dollar Cutoff, the behavior of the related counts flow and the ability to make the adjustment will be controlled by the RF.COUNT.ABORT authorization key and related Innovo Control Files discussed in our Location Touch Authorizations Keys article.

This control file works in conjunction with Innovo Location Touch Cycle Count Dollar Threshold if you want to provide the user a warning in the app.

Location Touch uses this setting to determine whether the branch is an RF enabled branch.

Applies to both RF and Non-RF Cycle Counts

This control file only comes into play when a user has authorization key PRD.LOCATION.MAINT level 2. When the quantity entered does not match the on-hand quantity for a location, you can force the user to count all related locations or you can automatically queue the locations, and add to the count queue.

Please note, this is only applicable in non-RF when control file Innovo Location Touch Enable Related Counts in Non-RF is enabled.

Applies to both RF and Non-RF Cycle Counts

Only those location types specified in this control file will be presented to the user during related counts entry.

Applies only to customers that are RF, are switching to Advanced Cycle Counts and that have been, and want to continue, using the warehouse operation queueing phantom to manage replenishments.

Set the branches in this control file to 0  to prevent “random counts” from getting generated by the Warehouse Operations Queue phantom when also using Advanced Cycle Counting.

Applies to RF Cycle Counts only

By default, when a new location is created in Location Touch the location status is set to floating. This control file allows you to override the status in new locations to something different.

This control file must have the base URL required to reach your image share publicly. Enter the full http:// address of your web site for redirect programs to use.

 Alternatively, you set this in Document Storage Location Maintenance, find the storage ID you are using for your location touch images and use the Path hotkey to enter the base URL required to reach your image share publicly

Applies to Non-RF Cycle Counts only

Enabling this control file will give a user with authorization key PRD.LOCATION.MAINT level 3 the option of aborting out of the related counts process.

This control file is only used if the user does not already have authorization key RF.COUNT.ABORT. If they do, the level of that authorization key will determine the abort behavior. Please see the Authorization Keys article for more information.

Applies to both RF and Non-RF Cycle Counts

When a discrepancy results in a cost greater than the minimum defined in this control file, the user will be warned during the cycle count process that the discrepancy will exceed the threshold. At that point they can do more research before updating the on-hand quantity.

*New in Release 1.3.0*

Applies to Non-RF Cycle Counts only

By default, when a new location is created in Location Touch the location status is set to floating. This control file allows you to override the status in new locations to something different.

Applies to RF Cycle Counts only

This control file will determine whether the new related counts flow is used or the classic flow. If Yes, then the new flow is used, if No then the classic flow is used.

*New in Release 1.3.0*

Applies to Non-RF Cycle Counts only

Enable this control file to turn on real-time updates in a non-RF branch. In a real-time environment, the inventory will be adjusted immediately when the count occurs and there will be no need to manually update. 

Applies to Non-RF Cycle Counts only

This control file will enable the related counts flow in a non-RF branch. When there is a discrepancy, the user will be prompted to Enter Related Counts, Queue Remaining, or Skip based on their authorization.

By default, location touch will check for the product and label types detailed in our Product and Location Printing article. This control file allows you to customize beyond those formats if needed. If you configure a branch in this control file, the app will use this instead of those noted in the article.

Enter a branch and then set the label type for Product and Location, as well as the subroutine. NOTE: This control file is only viewable in Eterm.

Applies to both RF and Non-RF Cycle Counts

By default, only primary index products are displayed in Location Touch during a search or scan. This control file allows you to search and scan catalog products as well.

Applies to Non-RF Cycle Counts only

By default, all generated cycle count files in Eclipse are displayed in Location Touch. This control file allows you to limit that list to only files that were created in the last x number of days.

Applies to RF Cycle Counts only

Location Touch uses control file Enable RF Branches to determine if a branch is RF enabled. If a branch is determined to be RF, we use the Warehouse Operation Queueing file to display the counts. If you want to use Phys files for generating the counts in an RF enabled branch, use this control file to override that setting.

*New in Release 1.4.0*

This allows you to expand the fields checked when a barcode scan is performed in the app. This will include all 10 UD fields from product maintenance. By default, only the product ID, UPC code, and customer part number fields are used to match scans.

Applies to both RF and Non-RF Cycle Counts

This will send a job queue to the user specified when the dollar threshold is exceeded. The dollar threshold is set in control file, Innovo Location Touch Cycle Count Dollar Threshold.

Applies to Non-RF Cycle Counts only

This only applies to non-RF branches that use Advanced Cycle Counting in an RF mode. If this is enabled, we will use the Warehouse Operation Queueing file to display the counts instead of any generated Phys files.

You must enter the document imaging profile in the prompt, Innovo Product Images, where you will store the images on your imaging server for product images taken by authorization employees through Location Touch.

Set the rank position to be used per branch for display in the Cycle Count screen and Inventory Inquiry.

Applies to Non-RF Cycle Counts only