There are several Data types that are able to be imported and exported within topShelf via SNAP. This section Deals with the data types and the required and optional fields used when using SNAP.

Bins

Bins are what your inventory will be contained within. Bins can be a shelf, a container, a section of a warehouse, or anywhere else inventory will be stored for eventual pick and shipment. Required Fields when importing Bins with SNAP are Bin, LocationName and AccountNumber. Optional fields are CommonLocation and BinTypeName.

Clients

Clients are any person or entity that you will be shipping to or receiving from. Required fields when importing with SNAP are AccountNumber and ClientName. The optional field is Email.

Locations

Locations are any addresses associated with a client record. Under clients there are locations. The required fields when importing this data type with SNAP, the required fields are LocationName and AccountNumber. The optional fields are ContactName, ContactPhone, Address1, Address2, City, State, Zip and CountryCode.

Parts

Parts are the descriptive record for your individual inventory. The part record Contains everything about the part except the quantity. Required fields when importing with SNAP are PartName and VendorName. Optional Fields are Description, RequiresSerial, ShippingWeight, RequiresLot, LotIsLIFO, LotIsFIFO, LotIsPerishable, LotStrictKitting, ClientDescription, Custom1-9, Cost, and Rate.

Items

Items are non-serialized part inventory that neither have a serial number nor a lot number. Required fields When importing in SNAP are Bin, PartName, and QTY. Optional fields are ClientName, LocationName.

Assets

Assets are serialized inventory. Anything that has a serial number that you would like to track must be classified as an asset. Required fields When importing with SNAP are SerialNumber, Partname, AccountNumber, and LocationName. The optional fields are Bin, Comments, Description, PONumber, ClientPONumber, and Custom1-4.

Asset Remove

AssetRemove is for removing Serialized inventory from a bin within topShelf. This data type will not delete the asset record from the system, it will simply remove it from inventory.

The required field When removing through SNAP is SerialNumber. The optional fields are LocationName, AccountNumber and Bin.

Kits

Kits are items, assets or lots that are assembled from other parts in your inventory.

The Kits import will create your bill of materials by tying the child parts and the QTY needed to build the master.

When importing Kits into Snap the required fields are MasterPartName, ChildPartName, and QTY.

Vendors

Vendors are entities in topShelf that you will be receiving product from.Required Fields when importing with SNAP are VendorName. Optional fields are ContactFirstName, ContactLastName, Title, Address, City, StateOrProvince, Country, PhoneNumber, FaxNumber, and Notes.

DocumentDetail

DocumentDetail is the addition of line items to shipping and receiving documents. The document must first be created through either SO or PO data types before adding line items. Required fields for importing DocumentDetail via SNAP are DocumentNumber, PartName, QTY and IntegrationID. IntegrationID is is the line number on the document. Each one should be unique and sequential.

Cartons

You can import cartons into topshelf. Cartons are used to ship multiple items on the same order in separate boxes. You will pick to the catrons and can give separate tracking numbers to the cartons. The required fields for cartons are DocNumber and Tracking Number. The optional Fields for Cartons are Notes, Shipdate, Lblprintout, Carrier Fee, CarrierName, ServiceName, CarrierCode, and Service Code.

Master Documents

masterdocuments is a data type for importing master document data information. There are only two required fields for SNAP import; DocNumber and Notes.

PO

You can create Purchase orders in SNAP. This import is just creating the document shell and does not create line items. Line items for PO's will be imported with docuemtndetail. The required fields for PO are DocumentNumber, TOLocationName, and TOAccountNumber. The optional Fields are VendorName, FROMLocationName, FROMAccountNumber, CustomerPO, Notes, TopShelfTransactionPrefix, and MasterDocNumber

Reorder Point

Reorder ponts can be mass imported through SNAP with the data type ReorderPoint. The required fields to set reorder points through SNAP are PartName, and ReorderPointQTY. Optional Fields are AccountNumber, LocationName, BinName, DesiredQTY, bIncludeHiddenBins, bIncludeNonDepots, bIncludeUnfulfilledReceiving, bIncludeUnflufilledShipping, bIncludeNonclosedWO, bIncludeUnbuiltKits, IntegrationID, and BDisabled.

PreDocumentLineItem

Predocument line items are for if you are picking an asset and you want to pick a particular asset, then you should use this object. Required Fields for PreDocumentLineItem are Document Number, IntegrationID and PreLineIntegrationID. Optional Fields are SerianNumber, LotNumber, QTY, ClinetName, LocationName and BinName.

ReOrderPointActions

Reorder point actions are objects that can be added to existing re-order points. Required fields are ReOrderPointIntegrationID, and ReOrderPointActionTypeName. Optional Fields are ReOrderPointActionIntegrationID, bDisabled, AutomaticallyCreateKitRequestNotes, AutomaticallyCreateReceivingVendorName, AutomaticallyCreateReceivingFromAccountNumber, AutomaticallyCreateReceivingFromLocationName, AutomaticallyCreateReceivingToAccountNumber, AutomaticallyCreateReceivingToLocationName, AutomaticallyCreateReceivingNotes, AutomatcallyCreateReceivingDocTypePrefix, AutomaticallyCreateTaskStatusName, AutomaticallyCreateTaskPriorityName, Automatically CreateTaskComment, AutomaticallyCreateTaskAssignedUsers, SendEmailToClient, SendEmailToUsers, SendEmailtoLocation, SendEmailToOtherEmails, SendEmailMessageTemplateName, and SendEmailbexcludeCreatedRecordInfo

ReorderPointEmail

The reorderPointEmail data type can be used to import re-orderpoints