Bin Import Guide

From Adjutant Wiki

General Data Import Notes

Refer to the Data Import General Information page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.


Bin Import Notes

Timing and Preparation

The Bin Import should be run prior to importing OHF records is the customer intends to set ProBin or PWOBin locations by OHF combination.

It is also ideal to run the Bin Import prior to the Inventory Quantity Import, if the customer intends to set the item bin location during the quantity import process. The quantity import will create bin records that do not exist, but the automatically created bin records will likely need clean up.

If the customer intends to use Bin Zones, each zone must be defined in the Zone Maintenance screen prior to performing the bin import. Bin Zones are a rarely used option.


General Notes

Bins are created per Warehouse. Separate import lines will need to be created for each Warehouse/Bin combination needed.


Bin File Data Scrubbing

There are no unique requirements for scrubbing bin data. Generally, the bin name is the only data field that will be pulled from the legacy system's data. The rest of the import file fields will need to be manually set.


Bin Import Screen (IMPORTBINS)

Menu Location: Transaction>>Importers/Exporters>>Item Control>>Bin Import

IMPORTBINS.png


File Name/Browse: Use the Browse button to locate and select the completed Bin Import template file (in XLS format).

Map Fields: Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.


Template: The Bin Import does not have an 'Export Template' option. You can either create a new Microsoft Excel file in the Microsoft Excel 5.0/95 Workbook (*.xls) format with the exact column labels indicated below, or download a copy of the template file from the Adjutant Wiki site here.

The columns needed for the Bin Import Template are listed below. Note that the f1-f255 column identifiers and the third row descriptions are not used on this template. The imported data should begin on row 2.

Import Bin Template.png


Bin File Definitions

Required fields are indicated with an *

*WhseName - Warehouse name for the associated bin record. Note that bins are specific to each warehouse location, so separate bin records must be created for each warehouse.

*BinName - Bin name (30 alphanumeric characters max)

Zone - Zone name from the Zone Maintenance screen (if using)

Multi - Enter 'Y', or leave the field blank, to set the 'Allow Multiple Items' flag. Enter 'N' to only allow a single item code for the bin location.

PSNum - Enter a numeric value (whole number, no decimals) to set the Pulling Sequence Number for the associated bin.

TmpLoc - Enter 'Y' to set the 'Temporary Location' flag. If left blank, the 'Temporary Location' flag will be unchecked.

WMSCon - Enter 'Y', or leave the field blank, to make the bin valid in the Warehouse Management Control system. This field should not be set to 'N' unless directed by ABIS personnel.

Active - Enter 'Y', or leave the field blank, to set the bin as an active bin. Enter 'N' to import an inactive bin record.


Bin Import Additional Steps

There are no additional steps needed after the import.


Bin Import Reconciliation

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Verify that imported bin records are available in the various Inventory Control applications that use bins.


Bin Database Tables

BINID - Bins are imported to the BINID table with a unique KEYNO for each Bin/Warehouse combination. The warehouse name is stored as the LOCTID value for the warehouse.