PRD.LOCATION.MAINT:
Cycle Counting permissions:
If there is a discrepancy between the entered count and quantity on-hand for a location, the following will determine how that discrepancy is resolved. This logic applies to an RF enabled branch and to a Non-RF enabled branch when real-time cycle counting is enabled.
We highly recommend your users have at least level 2 of this authorization key to perform cycle counts.
If the value of the discrepancy is lower than what is set in the control file RF Cycle Count Dollar Cutoff, the inventory adjustment is made.
If the value of the discrepancy is greater and this product has a single location, the count cannot be completed and will remain in the count queue.
If the value of the discrepancy is greater and this product is in multiple locations, we look to the Unauthorized User Finds Discrepancy In RF Cycle Cnt By Loc control file to determine behavior.
If set to Force Related Counts or if blank, the user will be brought into the Related Counts screen. If the count across all locations matches the overall on-hand quantity of the product, the appropriate adjustments are made. If not, the user will have the option to cancel the related counts process which will leave the original count in the queue or have the option to queue all remaining locations to the count queue.
If set to Queue Remaining the related locations will be added to the count queue.
If the dollar value of the discrepancy is a negative adjustment, but a lower value than what is set in the control file RF Cycle Count Dollar Cutoff, the inventory adjustment is made and the user will not be taken through the related counts flow.
If the value of the discrepancy 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 will be controlled by the RF.COUNT.ABORT authorization key and related Innovo Control Files discussed below.
Location Maintenance permissions:
Allows a user to move quantity from one location to another.
Ability to edit location, location status, location type, min, and max.
Ability to create new locations with 0 on-hand quantity.
Ability to delete locations with 0 on-hand quantity.
Ability to move quantity from one location to another.
Allows a user to add locations, delete locations, move quantity from one location to another, and edit all fields in Location Maintenance.
RF.COUNT.ABORT:
This authorization key will determine if a user can abort or skip counting related locations when there is a quantity discrepancy. This logic applies to an RF enabled branch and to a Non-RF enabled branch when real-time cycle counting is enabled. The user MUST have level 3 of PRD.LOCATION.MAINT for this to apply.
If the user does NOT have this authorization key, Location Touch looks to the control files, Allow Abort From Related Counts in RF or Innovo Location Touch Allow Abort From Related Counts in Non-RF, depending on RF enabled status to see whether the user can abort the related counts process. The authorization key can give a specific user(s) this capability, where the control files would give all Location Touch users this capability. If you have the control file set to allow aborting from related counts AND the app users also have RF.COUNT.ABORT, their RF.COUNT.ABORT authorization level is used.
Note: If this is an immediate count, authorization key RF.COUNT.ABORT.IM is used in place of RF.COUNT.ABORT.
Forces the user to count all related locations when there is a discrepancy.
Allows the user to count all related locations or queue locations and add to the count queue.
Allows the user to count all related locations, queue locations and add to the count queue, or skip counting the related locations and update inventory for that location.
Comments
Please sign in to leave a comment.