PI Transfer Movement Rule

Inventory Movement Rules for Physical Inventory

During the Physical Inventory Commit process from Tagnet Mobile Physical Inventory module, any "expected" tag inventory 'Not Found' in the location selected will be removed from inventory completely. For those companies that wish to move those 'Not Found' tags to a reconciliation location for further analysis, there is an IMOVE rule setup that supports that. Depending on the level of granularity needed and the hierarchy of your location matrix, you can implement a single PI Transfer rule or multiple rules for different areas, zones, departments, etc.

Firstly, a dummy logical reader location of ‘PI_TRANSFER’ needs to be setup as shown in the example below. Note that a physical reader does not have to be associated.

Secondly, an IMOVE rule needs to be setup as shown in the examples below. Note that the movement code can be named anything but the ‘From location;’ must refer to PI_TRANSFER. During the Commit update, the logic will search for any IMOVE rules referring to PI_Transfer, if the ‘From Location’ matches then it will be executed.

Once the Commit is finished, looking in Inventory Inquiry will show a (-) transaction from the expected location of Tag and a (+) transaction to the target IMOVE reconcile location. This inventory should be cleared out on a regular basis once the reconciliation is done. Additionally, if you are using the Outbound Queue feature in the Extension Framework to send events to an ERP or similar, you can setup a rule like the below. On the receiving end the ERP will look at any transactions moved to RECONCILE as Not Found.