Import - Check Outs
Description
The Datapel Inventory Controller Series supports a number of Data Exchange interfaces. Using the DataEx interface configuration information can be IMPORTED and EXPORTED from the ICXE database.
This feature allow Administrators or Consultants to quickly configure the Inventory Management System Workspace with datasets already prepared in Excel or via export from other systems. Likewise, information already entered or captured by an Inventory Controller workspace can be exported to provide External Systems indirect access to stock tracking datasets.
Import Format
The format supported IS:
- TSV (Tab Separated Variables)
Import Header
- XE import recognises and skips header record.
- All Headers must be kept in a particular sequence (refer to table below and sample attachment file).
Detail Steps
The following support note describes how the ICXE files should be formed and how they are imported into the ICXE.
1. Create a folder that will be used to hold Import/Export files.
It is recommended that .txt file be named by their import/export type. (Transactions, Items, Suppliers, Customers, Shipping Methods, Custom Lists, Users)
2. Once preparations are complete within Excel save the transaction import file as a text (tab delimited).
3. Select File, Import, Transactions... then selcted the transaction type (All Types, Check In, Check Out, Transfer).
4. Select Import Transactions... and browse for the .txt file. Once selected Open File.
To check the system details of import the Status Report should be used.
CHECKOUT HEADERS and FIELDS
Table below Provides an overview of ICXE the transaction headers and a description on each field.
Attached is an .txt sample file of a Check Out Transactions Import File.
| Field | Type | Max | Required | Notes |
| Transaction Type | Varchar | 2 | Y | Must be set to CO for CHECKOUT |
| Item Number or Barcode | Varchar | 20 | Y | Required either ItemNumber or Barcode |
| Quantity | Integer | 15 | Y | Required integer only |
| UOM | Varchar | 10 | N | Defaults to inventory quantity - future use |
| BRN / Batch-Serial# | Varchar | 50 | N | If left blank the UNTRACKED code is used (~) |
| LOT # | Integer | 5 | N | If left blank 0 is used |
| Expiry | Datetime | 15 | N | If left blank no expiry date is applied1 |
| LocationID | Varchar | 50 | Y | Location CardID (exact name of Location) to desptach from. |
| BinID | Varchar | 50 | N | Bin CardID (exact name of Bin) goods to be despatch from. |
| DstLocationID | Varchar | 50 | I | Ignored, used for Transfers Only |
| DstBinID | Varchar | 50 | I | Ignored, used for Transfers Only |
| Reference | Varchar | 15 | N | If left blank CO-XXXX-XXXX format code is substituted |
| CheckInDate | Datetime | 15 | N | If left blank the current date is used1 |
| ContactID | Varchar | 20 | N | If left blank Location CardID is used |
| Username | Varchar | 20 | Y | User login identification |
| Comment | Varchar | 100 | N |
1 Datetime format is dependent on your Regional settings either DD/MM/YYYY or MM/DD/YYYY e.g. 23/12/2010 or 12/23/2019 is acceptable.
ERRORS and EXCEPTIONS
- If a Required field is missing the transaction group is skipped - an error log is written to SYSTEM STATUS REPORTER
- If a Duplicate Serial / Batch Number is scanned with incorrect EXPIRY DATE - an error log is written and EXPIRY DATE IGNORE
- If a field exceeds the specified CHAR WIDTH it will be truncated
- If CONTACT ID or LOCATION ID not found the transaction group is skipped.
- If ITEMCODE not found the transaction group is skipped.
Related Information
Need Assistance?
Call 1800 137 032 Email support@datapel.com