Tutorial: ERPlite Bar Code Reader Data Import

Overview

The following tutorial focuses on importing/ uploading of data from the Batch PDT mode of bar code scanners in a WIP component consumption scenario.

Background

Collecting the data for inventory transfers (PO receipts, WO picks/receipts, WIP part consumption etc) can often be done more productively using a barcode scanner.  Barcode scanners come in 3 basic modes:

  1. Wedge
  2. RF Portable Terminal
  3. Batch Portable Terminal

The easiest, quickest, and most cost effective is to install a keyboard wedge device.  This is a bar code reader that has a Y-cable, where you unplug your keyboard, plug the Y-cable into the keyboard port and the keyboard into the Y-cable.  All scans made with the bar code scanner appear like keyboard entry to the application.  The wedge barcode reader requires a PC at the data collection workstation.

Since wedges are very straightforward (i.e. plug them in and scan rather than type), they will not be discussed further in this tutorial.

A more complex system, let's say an RF system with several PDTs (Portable Data Terminals, small hand held devices with integrated laser scanners) with antennas attached to a network.  An RF system is usually beyond most users to install themselves and thus, will not be discussed in this tutorial.

Batch systems use a Portable Data Terminal (PDT) which has it's own program and stores the data for periodic uploading to the host.  Batch PDT's are easy to implement and can be less expensive than a wedge because they require no PC at the data collection workstation and are substantially less expensive than RF systems.  In addition, shop floor procedures and related training are straightforward, thus improving quality and productivity.

The rest of this tutorial will demonstrate the importing (uploading) of data from a Batch PDT.  Since there are many opportunities to scan data in, we will demonstrate one very common scenario.  Adaptation of this demo to other scan scenarios can be easily done by a person with basic Microsoft Access skills.

The demo is "manual" in the sense that the user must perform a few steps to complete the scanner data import.  These steps include some Access Queries.  The manual method is more than adequate for many companies.  However, the manual method makes a perfect rapid prototype and can be easily fully automated by someone with basic Visual Basic programming skills.

WIP Consumable Component Consumption Scenario

The WIP component consumption scenario will be used throughout the tutorial.  Components in WIP inventory can be consumed via the WO Receipts or Inventory Transfer forms.  WO Receipts is very efficient if a WO was issued for a multilevel BOM.  The WO picklist transfers the components from Stores to WIP.  The WO Receipt then backflushes the components out of WIP when the finished goods are transferred to Stores.

However, when consumables (i.e. items that are stored in bins on the shop floor, say screws, resistors, etc.) are used on the production floor, they are transferred from WIP to a virtual inventory location (like Backflush) in order to downcount the WIP inventory.  Backflush is considered virtual because no real inventory exists, and the virtual counts do not have inventory value.  This is usually done using the Inventory Transfer Form.  If large quantities are involved or if it is not desirable to have a PC on the shop floor, then a Batch barcode PDT can be a very attractive way to transfer the inventory out of WIP.

Importing Process Overview

The general procecure for importing barcode data is as follows:

  1. Capture data via the barcode scanner
  2. Export teh data from the scanner to a text file and store it on yoru PC
  3. Import the text using one of the import utilities provided (physcial count or inventory transfer)

ERPlite Barcode Import Utilities

There are 2 import utilities in ERPlite:


Figure 1.


Figure 2.