Difference between revisions of "GT:Receiving ASNs"

Revision as of 17:45, 6 November 2014

Overview

The ability to receive inventory through the use of an inbound ASN has been added to Whistle GT. The ASNs are entered into new tables in Whistle through the use of a 3rd party EDI translator. This information is used to streamline the Receiving transaction, taking the place of requiring the user to manually enter in the receipt information. It results in new pallets being created and received, containing the inventory information from the ASN.

Database Schema There are two new tables to hold the data from the ASN, a header table and a detail table, as follows:

50px

wmASNHdrRecpt CREATE TABLE [dbo].[wmASNHdrRecpt]( [company] [varchar](8) NOT NULL, [branch] [varchar](8) NOT NULL, [warehouse] [varchar](8) NOT NULL, [bolNumber] [varchar](25) NOT NULL, [customerPO] [varchar](10) NOT NULL, [toWhs] [varchar](8) NULL, [orderType] [int] NOT NULL, [soKey] [varchar](10) NOT NULL, [billTo] [varchar](10) NULL, [shipTo] [varchar](10) NULL, [shipFrom] [varchar](10) NULL, [numOfPallets] [int] NULL, [numOfCases] [int] NULL, [numOfChep] [int] NULL, [grossWeight] [int] NULL, [SCAC] [varchar](25) NULL, [seal] [varchar](45) NULL, [trailer] [varchar](25) NULL, [shipDate] [datetime] NULL, [createDate] [datetime] NULL, [recStatus] [int] NOT NULL DEFAULT 0, [lockCounter] [int] NOT NULL DEFAULT 0

CONSTRAINT [PK_wmASNHdrRecpt] PRIMARY KEY CLUSTERED 

( [company] ASC, [branch] ASC, [warehouse] ASC, [customerPO] ASC, [bolNumber] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] wmASNDtlRecpt CREATE TABLE [dbo].[wmASNDtlRecpt]( [company] [varchar](8) NOT NULL, [branch] [varchar](8) NOT NULL, [warehouse] [varchar](8) NOT NULL, [customerPO] [varchar](10) NOT NULL, [SSCC] [varchar](18) NOT NULL, [bolNumber] [varchar](25) NOT NULL, [CaseKey] [varchar](60) NOT NULL, [ProdKey] [varchar](20) NULL, [GTIN14] [varchar](14) NULL, [custItem] [varchar](30) NOT NULL, [custPack] [varchar](10) NOT NULL, [LotKey] [varchar](25) NOT NULL, [Quantity] [float] NULL, [totalReceived] [float] NULL, [OrderLine] [int] NULL, [UOM] [varchar](6) NULL, [ProdDate] [datetime] NULL, [PullDate] [datetime] NULL, [Layers] [int] NULL, [CasesPerLayer] [int] NULL, [TareWt] [float] NULL, [ShipWt] [float] NULL, [recStatus] [int] NOT NULL DEFAULT 0, [lockCounter] [int] NOT NULL DEFAULT 0, [DtlRecptID] [int] IDENTITY(1,1) NOT NULL CONSTRAINT [PK_wmASNDtlRecpt] PRIMARY KEY CLUSTERED ( [DtlRecptID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]

The 3rd party EDI translation product mentioned above will parse the incoming ASN into these fields, which will be read by Whistle and used to create new container header, container detail and container case records. The wmASNDtlRecpt table holds both the net weight (bulk) and case information. If a case is being received, the case weight is entered in the Quantity field. If a net weight item is being received, the amount received is entered in the Quantity field. The recStatus is the receipt status for that item. It starts with a value of 0 as un-received, and Whistle will set it to 1 when it is received. The totalReceived will also be filled in at time of receipt. If it is a case, it will be set to 1, if it is netweight, the value entered will be the quantity received, currently the entire amount that was sent.

Whistle Setup There is a new setting in the Whistle Receiving screen that controls this functionality. It is called "Receive using ASN", and will need to be turned on. When it is turned on, after the users selects which Purchase Order they want to receive, Whistle will look in the tables mentioned above for any ASN’s that are set up for this Purchase Order, and inform the user that there are ASN’s set up for that order, and ask if they want to receive the ASNs.

Any ASNs received will be put on a new pallet, with a pallet number derived in the standard Whistle fashion, unless the user decides that they want to use the same SSCC number sent in. In this case, they will need to turn on "Use ASN SSCC as pallet number when receiving ASNs".

Another setting on this screen is "If receiving ASNs, do not print case labels". If this setting is turned on, new case labels will not be printed. If the Print checkbox is checked , the pallet label will still print.

Receiving using an ASN

When a user is in the Receiving screen, they will select the Purchase Order they want to receive. Whistle will look for any ASNs in the tables listed above that correspond to that Purchase Order. If any matches are found, the user will be informed of this, and asked if they want to receive the ASNs.

If they answer “No”, then they will just enter data in the Receiving screen as normal. If they answer “Yes”, Whistle will validate the ASN data to be sure it is set up properly in Whistle, and is valid for the order. Users will be informed if there are problems that need to be addressed before the pallets can be received.

Focus will then be put on the Track field. Here, they can scan in the barcode of the pallet to be received.. Whistle will match the pallet number scanned to an ASN entry. If a match is found, the user will be shown a list of the inventory on that pallet and will be asked if they want to receive it.