Users can generate an inventory export file specific to items scanned with Paladin’s RF terminals. No reprogramming is necessary on any of the current RF terminals to support the feature.
The data collection phase is an action you may already be utilizing in your store. Step one is to review if a pending RF-generated PO exists. You may verify this at P.O. (Alt-4) – F6 Recall P.O. and visually verify if a pending PO exists for your RF terminal number (every RF device creates their own pending file). If you leave this file in existence, your new work will be appended/updated to this existing file. Should you wish to begin anew, either complete the pending PO or click the Delete button when this file is highlighted. Be certain your RF terminal is not logged into the system while you perform this action. Exit PO Recall file control.
Now log into the RF terminal and select the option to create a PO. Remember your RF unit will open an existing pending (stored) PO and will update/add to it if it exists. If a pending PO file does not exist for this specific RF unit, a new empty PO file will be created. Scan the inventory items you want an export file created for. You must enter an “order” quantity > 0 to cause the software to store your entry. Unless you purchase this PO, the quantity entered isn’t used.
Once your list building is complete, exit the RF unit. From Paladin’s main menu, select Maintain >Data Viewer >Purchase Orders and select Stored POs from the Type field list. The upper display box now displays ALL pending POs. Select the PO of your choice, view the contents of that PO in the large display window, and click the Export Inventory located on the bottom of the screen. The Paladin system asks for a file name and location in which to store your export file.
The file exported will not be the contents of the pending PO, but rather the full (large) inventory export format based on the specific list of part numbers contained in your pending PO.
If you have questions or suggestions about this information, contact email@example.com.