The Directed Transfer infrastructure has multiple supporting transactions.
Directed Transfer Order
The Transfer Order is available to enter through the Panatracker portal. For many organizations, the transfer order can be populated from another source. Transfer orders can be entered in a number of different ways.
- Straight Site Transfer. This option will create a single site transfer from the source site location to a destination site.
- Via Site Transfer. This option adds a ‘via’ site level and will result in a two-step transfer. The first transfer will be based on the order pick which will create a GP Transfer transaction with the From site as the source site to the via site. The pick will also result in automatically creating an Inbound Transfer transaction (Panatracker tables). When the destination site receives the transfer, the receipt is recorded using the Receive Transfer transaction and a second GP Transfer Transaction is created from the Via site to the destination site. Note: The first transfer needs to be posted prior to the second transfer for the items being transferred to be correctly available for the second transfer. If not, the second transfer submit may fail.
- Bin Move. When both the from (source site) and to (destination) site is the same (and a via site is not entered), the order pick will result in a bin-to-bin move transaction. This is often used in manufacturing environments to move component inventory from stock areas to the manufacturing floor areas.
Directed Transfer Order Table Infrastructure
dbo.PanatrackerGP7_DirectedTransOrder (Header Table)
| TransOrderCode | [PK] Directed Transfer Order Number |
| SourceLocCode | Site for items to be sourced (picked) from (TRANSFER FROM Site) Must be a valid Site in GP. |
| ViaLocCode | Via or in-transit site option. When set, the order pick will create a transfer TO the ViaLocCode as the TO Site. A Panatracker Inbound Transfer transaction will automatically be created to support the transfer receipt and second transfer transaction. Must be a valid Site in GP. |
| DestinationLocCode | Requesting Site and final destination site for the transfer. When the SourceLocCode is the same Site AND there is not a ViaLocCode entered for the transaction, the transaction for the pick will be a Bin-to-Bin move. |
| ShipMethodCode | Text field for entering a shipping method. This is informational data only. |
| FulfilledDate | Updated from the order pick action. |
| DueDate | Requested date from the order entry. This date is informational only. |
| FlexField1 | User definable field as information only. |
| FlexField2 | User definable field as information only. |
| FlexField3 | User definable field as information only. |
| FlexField4 | User definable field as information only. |
| FlexField5 | User definable field as information only. |
| OrderGroupCode | Group logic for order picking. |
| Notes | Notes entered and available to view from the order entry/edit screen |
| UserName | User that created the order. |
| ApprovedBy | User that approved the order. Populated when order approval function is enabled and updated by the approval action. |
| OrderStatus | 0=New 1=Released 2=In Progres 3=Partial Pick 4=Closed |
| DEX_ROW_ID | To match GP table infrastructure. Unique ID for the record. |
dbo.PanatrackerGP7_DirectedTRansOrderUnit (Order Lines)
| TransOrderCode | [PK] Directed Transfer Order Number (matches the header) |
| LineItemSeq | Order Line Sequence. Each line must have a unique sequence number. |
| ItemCode | GP Item Number. Must match to an existing GP Item Number. |
| ItemDesc | Corresponding GP Item Description. |
| ToBin | DestinationLocCodeBin to be replenished. |
| QtyOrder | The quantity to transfer for the order. |
| QtyFulfilled | The quantity picked and transferred. This field is updated as part of the order pick for the transfer. |
| QtyCancel | Quantity canceled. Updated on edit of the order grid on the Panatracker portal. |
| UnitOfMeasure | Unit of Measure for the item. Note: The UOM must match a UOM associated with the item number in GP setup. |
| QtyBaseUnitOfMeasure | If the Unit of Measure is not the Base UOM for the item, option to include the quantity in the base UOM for UOM calculations. |
| DEX_ROW_ID | To match GP table infrastructure. Unique ID for each row. |
Transfer Order Entry
Transfer Request
The Transfer Request is used to create a Transfer Order from the mobile application. It may also be referred to as a restock request. There are multiple options to set for entry for the Transfer Request:
- User Entry. This allows the user to enter the items and the quantity they are requesting for a transfer.
- Count Against Max Site Quantity. A count can be completed against the max quantity setup for the site. The user would enter a count and the transfer request would be calculated (GP Site Max Quantity) – (User Item Count Quantity) = Transfer Quantity.
- Count Against Max Bin Quantity. This requires priority bins to be defined in GP for items and max levels set for each bin. The logic is the same as the site quantity. (GP Bin Max Quantity) – (User Item Count for the selected Bin) = Transfer Quantity.
- KanBan Entry. This requires that a priority bin is setup for the item in GP with max level. There is no count for this type option. The bin is selected, and the Max Quantity defined for that bill will be requested for the restock.