Transaction Views. Panatrack PanatrackerGP
Pubblicità
Pubblicità
Transaction Views
Receive Inventory
(Inventory In)
Submit of the completed transaction will create a Receiving Transaction. When posted, inventory quantities and details will be added to on hand and available in GP, Batch assignment can be set by profile and configured under Settings: BatchCodeForReceiving. If none entered, current date is used.
Transaction sequence prefix default is “RCV” and may be changed under Transaction Setup.
Screen 1
Printer
Displayed and required when LabelPrintingForReceivingEnabled is set to 'True'
Site Filter
This field is used to filter the PO list and PO items by site. This field may be defaulted based on
DefaultReceivingSite. If not configured, DefaultSite will be used. This field may be read only based on configuration of AllowChangeSite. If receiving without a Purchase Order
(AllowReceivingWithoutPO = “true”) Site is required for the transaction.
Vendor Filter
Entry in this field will filter the PO look up list for open POs by Vendor ID selected. This field is optional when receiving against a PO; however, if receiving without a PO,
(AllowReceivingWithoutPO = “true”) then Vendor is required.
PO
Required to receive against open PO. May be left optional is AllowReveivingWithoutPO = 'True'
When receiving without a purchase order, Site and Vendor will be required. User will be prompted to confirm receiving action without PO.
Vendor Doc#
Setup is FlexField1 under FlexField set up. Entry in this field populates the Vendor Document
Number on the Receiving transaction. Behavior is set on FlexField set up. Note: If setting
ReceiptType = ReceiveAndInvoice, this must be set up as a required field.
26 / 75
Screen 2
Item
Required. Validation is based on PO line status and remaining expected quantity. Warning message returned to user for quantity greater than remaining expected.
Note: AllowMfgCodeAssignments = “true” will prompt the user when an item number not set up in
GP is entered. Reference Manufacturer Item Number information for more details
Bin
Required when multi-bins are enabled in GP. Default setting is based on ReceivingBinChoice setting. Options is Site, Item/Site, or Last Entered.
UOM
Required. Default will be the PO Setup UOM for the item.
Read only unless UseUOMForReceiving is set to 'True'. When selecting an alternate UOM, the receive quantity and remaining expected will be updated based on the PO item UOM. For example, if the PO UOM is Each and the user enters a Case which is equivalent to 10 Each, 1 Case will update the quantity received to 10 Each and lower the expected remaining quantity by the same 10 Each.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtReceiving = 'True'
Validation is based on the Remaining Expected Quantity on the purchase order
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Notes
After the first item is entered, focus returns to Item field. Continue to add items as needed for this transaction.
When transaction is complete go to [Review]
27 / 75
Review Screen (3)
No Pick Activity
Partial Pick
Pick Complete
Notes
The check boxes on top allow the user to see only the transaction that have been received [View
Receipt] or only the transactions that are not received yet [No Receipt Activity]
Select the [Submit] button to end the transaction.
28 / 75
Add Inventory
(Inventory In)
Submit of the completed transaction will create an Inventory Transaction. When posted, inventory quantities and details will be added to on hand and available in GP, Batch assignment can be set by profile and configured under Settings: BatchCodeForAdjustments. If none entered, BatchID will be assigned based on the FlexField1 entry. If no Batch ID and FlexField1 is empty, current date is used.
Transaction sequence prefix default is “A” and may be changed under Transaction Setup.
Printer
Displayed and required when LabelPrintingForAddAdjustmentEnabled is set to 'True'
Item Class
Visible when UseItemClassCodes is set to “true” Default setting = “false”. Optional filter for the Item look up and validation based on a selected Item Class.
Reason
Set up the list of Reason Codes under Inventory>>Inventory Setup>>Add Reasons
May be set as optional or required based on setting AdjustmentReasonRequired
FlexField1 & FlexField 2
Displayed based on configuration setup: Configure>>FlexFields
Shown in example above as User ID & WorkOrder
Site
Required. This field may be defaulted based on configuration setup: DefaultSite
May be set to read-only based on configuration setting AllowChangeSite
To Bin
Required when multi-bins is used in GP.
29 / 75
Item
Required. Validation is based on Site selected.
UOM
Required. Default will be Base UOM for the item.
Read only unless configuration setting UseUOMForInventory = 'True'
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtAdjusment = 'True'
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
# Labels
Displayed and required when LabelPrintingForAddAdjustmentEnabled = 'True' for bulk and lot tracked items.
Defaults may be presented based on LabelPrintQuantityDefaultEnabled & LabelPrintQuanitityDefault
Settings
Notes
After the first item is entered, focus returns to Item field. Continue to add items as needed for this transaction.
when transaction is complete go to [Review] to complete select [Submit].
30 / 75
Site Transfer
(Inventory Track)
Submit of the completed transaction will create a Transfer Transaction in GP. When posted, inventory quantities and details will be updated based on To and From Sites defined., Batch assignment can be set by profile and configured under Settings: BatchCodeForTransfers. If none entered, current date is used.
Transaction sequence prefix default is “XFR” and may be changed under Transaction Setup.
Printer
Displayed and required when LabelPrintingForTransferEnabled is set to 'True'
Item Class
Visible when UseItemClassCodes is set to “true” Default setting = “false”. Optional filter for the Item look up and validation based on a selected Item Class.
FlexFields 1 & 2
Displayed based on configuration setup: Configure>>FlexFields
Shown in example above as User ID & Reference.
From Site
Required. This field may be defaulted based on configuration setup: DefaultSite
May be set to read-only based on configuration setting AllowChangeSite = False.
Restrict the sites available with configuration TransferToSiteList. If none defined and AllowChangeSite =
True, all sites are available to select.
From Type
Defaults to On Hand. Visible when AllowTypeTransfer = True. Is not displayed when setting is “false”.
Shipping Method
Visible when configuration setting CaptureTransferShippingMethod is set to “true”. This is an optional field. It will not be displayed if setting is “false”
31 / 75
To Site
Required. Additional field validation may be added with TransferFromSiteList. If none set, then any site in GP can be selected.
To Bin
Required when multi-bins are used in GP. Validation is based on To Site.
Item
Required. Validation for quantity available is based on the From Site defined.
From Bin
Required when multi-bins are used in GP. Validation for available quantity is based on the From Site and
Item selected.
UOM
Required. Default will be Base UOM for the item.
Set as read only unless configuration setting UseUOMForInventory = 'True'
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
Allow use to accept a quantity greater than available (bulk inventory only) by setting
AllowTransferOverride = 'True'
Lot
Displayed when item tracking is "Lot". Validation is based on the Site and Item selected. Quantity validation is based on the lot selected. Transaction quantity cannot exceed the Lot Quantity Available.
The available Lot Quantity can be set to default by setting the LotQuantityDefault setting to “true”. For the look up list, set the Lot Sort Order under setting LotSortOrder with options for Expire Date, LotCode,
Location, LeastQuantity
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Validation is based on serial number scanned as available. From Bin prompt will be disabled for serial tracked items.
32 / 75
Item Bin Move
(Inventory Track)
This transaction moves items from one bin to another bin within the same Site. This transaction is a process in GP and requires no additional processing. Each item will be processed and quantities updated immediately. No Batch set up is required. Logging is maintained with the Panatracker logging database.
Internal transaction sequence number prefix is “MIV”.
Printer
Displayed and required when LabelPrintingForTransferEnabled is set to 'True'
Site
Required. This field may be defaulted based on configuration setup: DefaultSite
May be set to read-only based on configuration setting AllowChangeSite
Type
Required. Default is OnHand. Standard navigation does not prompt for Type.
Item
Required. Validation is based on the Site.
From Bin
Required. Validation is based on the Site and Item
UOM
Required. Default will be base UOM for the item.
This field is set to read only unless UseUOMForInventory is set to 'True'
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
33 / 75
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
To Bin
Required. Validation is based on the Site. Additional validation may be defined based on Priority Bin set up in GP. When priority bins are assigned for the item and configuration setting PrioritizePutAwayBins =
‘true' If user selects a bin not set up as a priority bin, a warning message will be displayed; however alternate bins can be selected.
Labels to Print
Displayed and required when LabelPrintingForMoveEnabled = 'True' for bulk and lot tracked items.
Defaults may be presented based on LabelPrintQuantityDefaultEnabled & LabelPrintQuanitityDefault
Settings
34 / 75
Bin Transfer
(Inventory Track)
The Bin Transfer provides the ability to complete an inquiry on all items and quantities within a bin.
Option to then “transfer” all items from that bin to another bin under the same site without scanning or selecting each item and item details. ALL items will be moved to the destination bin. On Hand and
Available Quantities MUST match for ALL items to complete a transfer transaction.
Site
Required.
Bin
Required. Bin selection retrieves and displays ALL items in that Bin and On Hand and Available quantities.
For Serial or Lot items, tap on the corresponding item line in the view and access the lot or serial details under the [Details] button on the lower menu.
To Bin
To move all items, confirm On Hand and Available quantities match for all items in the selected Bin.
Then select the destination bin location. Confirm the move.
35 / 75
Transfer Container
(Inventory Track)
Available within multi-bin environments only. This transaction provides the ability to “group” items under a designated “container” bin. The bins identified to be available for this transaction are set under
“ContainerFilter” configuration setting. Only bins matching the pattern(s) defined can be used within this transaction. A standard Site Transfer transaction will be created. The transaction sequence prefix is set under TransferContainer with default setting of “TXC”. This transaction shares the same Batch Code
Assignment with the standard Site Transfer: BatchCodeForTransfers.
Site
Required.
Container
This is the Container Bin. Validated based on the ContainerFilter defined.
To Site
The destination Site for the Transfer. The same Container Bin will automatically be created for the destination site if it does not exist.
Note
All items within the Container Bin MUST have both On Hand and Available quantities be the same to complete this transaction. Submit will create the Site Transfer in GP for ALL items in the Container Bin.
36 / 75
Count Stock
(Inventory Track)
This transaction uses the Stock Count Schedules set up in GP. This transaction does not have a “submit”.
The GP Stock Count Entry is updated in real-time as the counts are captured. Review and processing of variances will be completed in GP.
Stock Count
Required. This field allows the user to select from any stock counts that have been started in GP.
Site
Available Sites depend on the Sites set up on the Stock Count Schedule. Note that the Site look up will indicate the number of items to be counted.
Bin
When using multi-bins in GP, Bins to count are based on the Stock Count Schedule set up. The same as the Site, the number of items in the bin will be identified in the Bin look up.
Item
Items to verify are based on the Stock Count Schedule set up. Once a count has been entered on the item, if it is selected again, the user will be prompted to Add to Count OR be able to Replace the Count.
If the item is Lot tracked, all related lots must be verified before the item is marked verified complete. If the item is serial tracked, the user will have the option to enter an item level count first. If it matches to
GP, all serials can automatically be validated without individual scans. If the count does not match, all serials must be verified. The user may also select to scan every serial instead of entering a pre-count.
If the item is listed on the Stock Count Schedule, but not found, the user may enter a quantity of 0 to mark the item as verified.
UOM
Required. Default will be Stock Count Schedule UOM for the item.
This field is set to read-only UseUOMForStockCount= 'True'. If using an alternate UOM, the count will be
37 / 75
calculated back to the Stock Count UOM. For example, if the Stock Count Schedule is set for Each and the user enters Case, equivalent to 10 Each, 1 Case will be returned as a count of 10 Each.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtStockCount = 'True'
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Notes
After the first item is entered, focus returns to Item field. Continue to add items as needed for this transaction.
when transaction is complete go to [Review] to complete select [Submit].
38 / 75
Spot Count
(Inventory Track)
This transaction is designed to complete a simple one-step spot count for an item. It was created for multi-bin environments; however, it is not required. The user will be presented with the Expected
Quantity retrieved from GP. Entry of the count quantity will then create an Adjustment transaction in
GP. BatchCodeForSpotCounts is separate than the standard adjustment transactions. The sequence prefix is also uniquely set up under Transaction Setup. The default is “SPT”.
Site
Required.
Type
Default is set to OnHand
Item
Required. Validation based on the Site selected.
Bin
Required when multi-bins are used in GP. Validated based on site. All bins are available in the event of 0 or negative quantities in GP which require adjustments.
UOM
Required. Default will be base UOM for the item.
Option to select alternate if UseUOMForInventory = 'True'
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtAdjusment = 'True'
Notes
Entering a quantity will submit the transaction to GP and return focus to Site.
39 / 75
Remove Inventory
(Inventory Out)
Submit of the completed transaction will create an Inventory Transaction. When posted, inventory quantities and details will be removed from the on hand and available in GP, Batch assignment can be set by profile and configured under Settings: BatchCodeForAdjustments. If none entered, BatchID will be assigned based on the FlexField1 entry. If no Batch ID and FlexField1 is empty, current date is used.
Transaction sequence prefix default is R” and may be changed under Transaction Setup.
Item Class
Visible when UseItemClassCodes is set to “true” Default setting = “false”. Optional filter for the Item look up and validation based on a selected Item Class.
Reason
Set up the list of Reason Codes under Inventory>>Inventory Setup>>Usage Reasons
May be set as optional or required based on setting AdjustmentReasonRequired
FlexFields 1 & 2
Displayed based on configuration setup: Configure>>FlexFields
Shown in example above as User ID & WorkOrder
Site
Required. This field may be defaulted based on configuration setup: DefaultSite
May be set to read-only based on configuration setting AllowChangeSite
Item
Required. Validation is based on the Site selected.
From Bin
Required when multi-bins are used in GP Validation is based on the Item and Site selected.
40 / 75
UOM
Required. Default will be Base UOM for the item.
Read only unless configuration setting UseUOMForInventory = 'True'
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtAdjusment = 'True'
Lot
Displayed when item tracking is "Lot". Validation is based on the Site and Item selected. Quantity validation is based on the lot selected. Transaction quantity cannot exceed the Lot Quantity Available.
The available Lot Quantity can be set to default by setting the LotQuantityDefault setting to “true”. For the look up list, set the Lot Sort Order under setting LotSortOrder with options for Expire Date, LotCode,
Location, LeastQuantity
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Validation is based on serial number scanned as available. From Bin prompt will be disabled for serial tracked items.
41 / 75
WennSoft Intergration
JobTrackingAddOn is set to “WennSoftIntegration” additional fields for WennSoft will be available on the Inventory Adjustment Remove transaction. Job or Service details will be populated as part of the adjustment transaction.
If items are assigned to a job or service on a PO line item, the corresponding Receiving transaction will automatically be populated based on the purchase order assignment.
Note: These items are charged directly to the Job or Service and not added to inventory upon posting. It is recommended that these items be labeled accordingly.
42 / 75
Vendor Return
(Inventory Out)
The Vendor Returns transaction will create two separate transactions: Inventory Adjustment Remove and a Payable Return transaction. Both transactions will be assigned the SAME transaction number within GP for audit and clearing. The default transaction sequence prefix is “VRT”. Because there are two transactions, an offset account number needs to be defined under Settings
VendorReturnClearingAccount. Both transactions will also be assigned the same Batch ID, defined under setting BatchCodeForVendorReturns
Site
Required. This field may be defaulted based on configuration setup: DefaultSiteID
Vendor
Required. Select from a list of Vendors.
Reason
Set up the list of Reason Codes under Inventory>>Inventory Setup>>Vendor Return Reasons
May be set as optional or required based on setting AdjustmentReasonRequired. The selected reason code will populate the Description field on the Payables Transaction created.
FlexFields 1 & 2
Displayed based on configuration setup: Configure>>FlexFields
RMA Ref
Required. This number must be unique to the transaction and populates the Document Number on the
Payable Transaction created.
43 / 75
Ship Method
Required. Populates the Shipping Method field on the Payable Transaction created.
Item
Required. Validated based on Site and Vendor selected.
From Bin
Required when multi-bins are used in GP . Validated based on quantities for the site and item selected.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
44 / 75
Project Transfer
(Inventory Out)
This transaction will create a Project Accounting Transfer transaction in GP. The transaction sequence default is “PJT”. Batch Code assignment is shared with the Site Transfer under setting
BatchCodeForTransfers. This transaction uses a stored procedure to create the transaction in GP set under TrxProjectTransferStoredProcedure
Screen 1
FlexField 1&2
Displayed based on configuration setup: Configure>>FlexFields FlexField1 will populate the Requested
By field on the transaction. FlexField2 will populate the Reference Number field on the transaction.
Project
Required. Validated based on project status
Cost Category
Required. Validated based on Cost Categories set up for the Project related to inventory only.
Screen 2
Item
Required. Validated based on the project set up.
From Site
Required. Validated based on quantities available for the item selected.
From Bin
Required when multi-bins are used in GP. . Validated based on the Item and Site selected.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
45 / 75
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
46 / 75
Query Inventory
(Tools)
This feature allows the user to check inventory status and location for any item.
Item
Required
Notes
Item information will be displayed below.
The [Details] Button will bring up additional information for item tracked by Serial or Lot
47 / 75
Associate Mfg Item#
(Tools)
This transaction provides a tool to create an association of an alternate item number to a GP Item
Manufacturer Item Number functionality
48 / 75
Assemble
(Mfg.)
This transaction will create the Assembly Transaction in GP using the assigned Batch code under
BatchCodeForAssemblies setting. The transaction sequence prefix is defaulted as “ASM” and can be modified under the Transaction Setup. This transaction is created using a Stored Procedure identified under the setting “TrxAssembleStoredProcedure.
Screen 1
Printer
Displayed and required when LabelPrintingForAssemblyEnabled is set to 'True'
FlexField1
Displayed based on configuration setup: Configure>>FlexFields
To Site
Required. Define the Site to add the Assembled item quantities, The Assembly item MUST be assigned to the Site.
To Bin
Required when multi-bins are used in GP. Assembly item will be added to this Bin.
Item
Required. Validated based on open BOM Items.
Quantity
Displayed when item tracking is "bulk".
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
49 / 75
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Screen 2
All component items with the corresponding “use” quantity calculated on the associated BOM set up.
Tap on [AutoFill] to automatically issue all components and calculated quantities based on the
“Make” quantity and the BOM set up.
Alternatively, tap on a component line and tap on [Pick] to manually complete the usage recording.
If using multi-bins, the default bin set up in GP will be used unless otherwise specified.
If components are serial or lot tracked, use the manual process to issue the selected serial and lot components.
Screen 3
Pick
Validate Item
Here you are validating the component item selected in the previous screen. Scan or tap Enter to populate the field.
From Bin
Required when multi-bins are used in GP. Validation for available quantity is based on the Item selected.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
50 / 75
Lot
Displayed when item tracking is "Lot".
Other lot tracked settings: UseUOMForLots, LotMfgDateEnabled, LotExpireDateEnabled,
LotAttributesEnabled
Serial
Displayed when item tracking is "Serial"
Focus remains on serial field and serials scanned counted until user selects
Notes
The [Components] button will return the user to the previous screen.
The [Menu] BUtton will prompt the user to exit the transaction without completing.
51 / 75
Fulfill Order
(Orders)
Fulfill Order will update the Quantity Fulfilled on existing sales orders in GP. Order types must be set up to use a separate fulfillment process. Supported types include Order, Fulfillment Order, and Invoice. To pick against an invoice, set AllowPickingFromInvoice to “True”
When the pick is submitted back to GP, the Batch ID is updated based on the pick status.
BatchCodeForCompletedOrderFulfill will be used when all items on the order are fulfilled complete.
BatchCodeForPartialPicks will be used when there are remaining open line items. To maintain the original Batch ID, be sure to leave this setting blank.
The Panatracker logging will assign a transaction number as well as reference the Order Number as part of the log details. This transaction number is internal for Panatrack logging only. The transaction sequence number default is “ORD”.
Screen 1 Order List
Order
Orders or invoices available to pick can be defined based on a Batch Code as an option. Set this under
“BatchCodeListForOrderFulfillment”. Multiple Batch Codes may be set up here. To view only orders with
Allocated line items, set the Allocate setting to “true”. Note: Serial and lot tracked items can still be allocated on the item level without requiring selection of the specific serial and lot details.
For Advanced Inventory, Directed Transfer orders will be available in this list also.
Filter
On-demand filters are available to apply to the order list. Tap the Filter bar to open the options. The
Filter bar will display the applied filters when closed. Tap the X next to the filter to remove it.
Screen 2 Pick List
When the order is selected, the order pick list will be presented. The list will be presented based on the
FulfillmentOrderListSortOrder. This includes ItemCode, DefaultBinCode, LineNumber, ItemShortName.
Status icons are displayed representing the current pick status
52 / 75
No Pick Activity
Partial Pick
Pick Complete
As items are picked complete, the list is resorted and those line items are dropped to the bottom of the pick list. If using multi-bins, the [Query] button will access the list of all bins for the selected item in the list and on hand and available quantities.
[Notes] will access any notes set up in the order Comments.
[Details] will access the current pick details including lots and serial details. Only details selected within the current pick transaction can be removed.
[Pick] to access the validation screen for the selected line
53 / 75
Screen 3 Validate Item
From Bin
Required when multi-bins are used in GP. This may be defaulted based on the SOPFulfillmentBin default set. If a default bin is assigned to the item in a non-multi-bin environment, it will also be displayed in read-only format. The Bin lookup includes quantity information for the item.
Validate Item
Required. A scan or key entry is required in this field when RequireScanToPick is set to “true”. Best practice is to scan to validate the item pick; however, if the referenced setting is set to “false” the enter key can be used to confirm the item.
UOM
Required. Default will be the Order UOM for the item.
This will be read-only unless UseUOMForOrderFulfillment is set to 'True'. If set to “true” and an alternate UOM is selected, the “pick” quantity will be calculated to the Order UOM. For example, if the order is for 10 Each and the user selects a Case for the UOM which is set up to be equivalent to 10 Each, the pick quantity update will be the 10 Each.
Quantity
Displayed when item tracking is "bulk".
Key entry required when AllowScanInQuantityField = 'False'
No prompt and will count item scans when BulkItemAutoSaveAtOrderFulfillment = 'True'
Validation for the quantity will be the remaining quantity required. A pick exceeding the order quantity will return an error message unless a SOPOverPickTolerance is set. In this case, a warning message will be displayed to the user.
Serial
If the item is serial tracked, available serial numbers must be scanned. Use the [Serial] button to access available serial numbers. The order displayed is based on the SerialSortOrder setting with options of
SerialCode, ReceiveDate, Location
Lot
54 / 75
When the item is lot tracked, the lot number must be scanned or entered. Use the [Lot] button to access
All lots available and available quantities. List is displayed based on the setting LotSortOrder. Note – this is shared for all lot look ups on all transactions. Options include ExpireDate, LotCode, Location,
LeastQuantity.
UOM on the lot quantity may be available to select based on setting UseUOMForLots. Default will be based on or Order Line Item. Lot quantity may be automatically populated based on setting
LotQuantityDefault. Enter to accept or enter a new quantity. A warning message may display for expired lots if configured based on WarnForExpiredLots and WarnForExpiredLotDays
Shipping Box ID
This field will be available when UseShippingBoxTracking is set to “true”. Provides the ability to pick items to a specific box that can later to assigned a tracking number. It is recommended to have preprinted serialized box label printed to use
By tapping the [Next] when the pick is complete for the current item, automatically go to the next item on the pick list.
[Pick List] returns to the pick list screen for review and submit.
Printing
Automated printing of a packing list can be set up. Create a report that can be called outside of GP.
Contact Panatrack for assistance with additional set up. Note: This set up is not included under
Panatrack's standard install services.
A box label can be printed upon submit of the order fulfillment process. The user would enter the number of labels to print. Note: These labels are not intended to be shipping labels. Configure with
LabelPrintingForOderFulfillment
55 / 75
Batch Pick
(Orders)
Multiple orders can be grouped together to present a single pick list under order in the Panatracker portal. A list of orders will be presented. Mark the order to group. The Group ID is assigned to the order under the User Defined Text Field 1. Once an order is grouped, it is no longer available to pick from the
Order Fulfillment transaction. Note: The Group assignment can be removed on the order in GP if needed.
Each order in the group will be identified to pick to a “Bucket” for sorting. Each item for each order will be displayed and validated independently to provide the ability to manage inventory shortage situations. Items will be grouped together in the order pick list.
Follow the same process as the standard Order Fulfillment transaction.
56 / 75
Ship Order
(Orders)
This transaction associates tracking numbers to orders and Shipping Box ID. Option for signature capture for pick ups or delivery drivers. The option to update the Order with a new Batch ID is available with submit based on BatchCodeForShipOrder configuration setting.
The Panatracker logging will assign a transaction number as well as reference the Order Number as part of the log details. This transaction number is internal for Panatrack logging only. The transaction sequence number default is “SHP”.
Carrier
Optional – Enter the Carrier name.
Order | Shipping Box
If the Shipping Box is used, scan or select the Shipping Box to associate the Tracking Number. If Shipping
Box feature is not used, select the order.
Tracking #
Scan or enter a tracking number. The Tracking Numbers on the GP sales orders under User-Defined
Fields will be populated.
Continue adding tracking numbers to this transaction
57 / 75
Tap [Review] to view order/shipping box and tracking assignments for the Carrier
[Complete]
Displays number of boxes calculated by the tracking numbers entered.
Optional signature capture.
[Submit] will update the Batch ID on the corresponding sales orders and assign the tracking number under the User Defined field à Tracking Numbers on the sales orders.
58 / 75
Verify Order
(Orders)
This transaction provides the ability to verify items on a FULLY fulfilled sales order. Orders to be verified may be defined based on a Batch Code. Set this up under BatchCodeListForOrderVerify. The option to verify or “pack” to a shipping box can be set by setting the UseShippingBoxForVerify to “true”.
The Panatracker logging will assign a transaction number as well as reference the Order Number as part of the log details. This transaction number is internal for Panatrack logging only. The transaction sequence number default is “VER”.
Site Filter
This is a filter for the Order look up list and not required.
Order
Only fully picked orders can be processed. Additional validation based on the
BatchCodeListForOrderVerify configuration setting.
Item
Scan or confirm items. Validation is based items on the order.
Quantity
Displayed when item tracking is "bulk" Validation based on order quantity and remaining quantity to confirm.
Serial
If item is serial tracked, validate serial numbers. Validation is based on serial numbers assigned to the order.
Lot
It item is lot tracked, validate lot numbers. Validation is based on lot numbers assigned to the order.
59 / 75
Shipping Box
Configured with UseShippingBoxForVerify. Required when UseShippingBoxTracking = 'True'
[Review] to access items that have been verified and to Submit the verification to GP. ALL items must be verified complete to process. Exit an in-progress transaction and tap the [Yes] to save the verified progress and keep the transaction open in the Panatracker logging portal. The balance of the verify can then be resumed later.
Note
To close the open transaction in the portal to start the verify completely over after a save, go the to
Verify Order portal page and discard the transaction.
Submit of the completed verify will update the Batch ID assignment on the Order in GP based on the setting BatchCodeForVerifiedOrders. To keep the original Batch Code, be sure this setting is left empty.
60 / 75
Sales
(Orders)
The sale transactions provides the ability to create a new sales transaction and to edit or add to an existing sales order (designed to support environments that use sales orders as a work order). Customer sale returns can also be created from this transaction interface. These transactions are available using a continuous network connection. Contact Panatrack to discuss the Field Sales functionality for supporting data capture outside of a continuous network connection.
Screen 1
Site
Required when creating a new sales transaction. Provides a filter for the Order look up for editing an existing transaction. Default may be set: ConnectedSAlesDefaultSiteIDForSale
Customer ID
Required when creating a new sales transaction. Option to search by Customer Name by tapping the
Search Customer Name field. Enter the part of the customer name and then use the look up button to access the list.
Ship To ID
Required when creating a new transaction. Field will default based on the Customer Card setup. To select an alternate Ship To, [esc] or [bksp] to clear the default and select an alternate option.
Bill To ID
Required when creating a new transaction. Field will default based on the Customer Card setup. To select an alternate Ship To, [esc] or [bksp] to clear the default and select an alternate option.
Tap Sale initiate a new sales order or invoice for the customer.
Tap Return to initiate a sales return transaction for the customer.
61 / 75
Order
Scan, enter or select an existing order. Site and Customer fields will provide a filter for the look up list.
Orders can be restricted based on ConnectedSalesOrderDocumentIDFilterForOrderEdits
Use the [Enter] key to select the order or if order is scanned, it will open the order details screen.
Screen 2: New Order
Tap Add to begin capturing items for the order. Return to this screen to review the order lines. This transaction may be a direct sale or to create an order that will be fulfilled later. Tap on a line and tap on
[Remove] to remove the line from the order.
62 / 75
Screen 3 – Add Items
Item
Validated based on the Site selected at the start of the transaction. Miscellaneous, Flat Fee, and Service item types may be selected.
Price Level
Defaulted based on configuration set up. This may be set to read only based on configuration setup.
ConnectedSalesDefaultPriceLevelAssignment, ConnectedSalesAllowPriceLevelFrom (Customer or
System Default), ConnectedSalesAllowPriceLevelChange
UOM
Default based on Price Level selected. If multiple UOM exist for the Price Level, default will be based on item Base UOM setting.
Unit Price
Populated based on the Item, Price Level, and UOM selected. This may be set to read-only.
Quantity
Enter quantity for the order.
From Bin
Required if picking or fulfilling the item for the order at the same time. A “pick” status box will be displayed. If only creating an order, then tap à Next to enter next item.
Fulfilled Qty
Quantity being picked or fulfilled. May be left empty if no items are being fulfilled at this point.
ConnectedSalesDefaultFulfillQuantity when set to ‘true' will automatically populate the Fulfilled Qty from Order Quantity.
63 / 75
Details
Tap a line in the review screen and then tap details to view the pick details for that line. Tap on the line edit icon to edit price or quantity.
Tap on the fulfillment line detail and tap on the Edit on the lower menu bar to edit line fulfillment details.
64 / 75
Screen 4
Complete Order: Order Summary: Read Only.
Screen 5 Complete & Submit
PO Ref
Optional field.
Enter the customer PO or reference. Populates the PO field on the sales order.
Req Date
Optional Requested Ship Date. Date entry is based on date configuration which as a default is set to accept entry as 010113 which will be 01/01/2013.
Ship Method
Optional. Validated based on ship methods set up in GP.
65 / 75
Signature Capture
Optional signature capture. This is stored in the Panatracker transaction manager database.
[Review] will return to the item list.
[Clear] will clear the signature capture field.
[Submit] will commit the transaction and create the order in GP.
66 / 75
Edit Existing Order
Previously submitted lines will be displayed in yellow. Depending on configuration setting, edit may not be allowed to previously submitted lines. New line items added will be displayed to the top of the order list. Settings include: ConnectedSalesAllowAddToExistingTransaction; Connected
SalesAllowEditToExistingOrderLines;
Follow the same instructions for editing details, adding or removing lines as a new order.
Review and submit screen will show PO, Req Date, and Ship Method as read only based on previously entered data for that order. No edits can be made to these fields.
Submit will update the order or invoice.
Transaction logging is under Orders -- Sales
67 / 75
Directed Transfer
Directed Transfer functionality is available to set up under the Panatracker Advanced Inventory solution. Additional table are added to manage and support these transactions.
Panatrack has created a Directed Transfer infrastructure. This infrastructure supports the ability to create an internal transfer directive. This directive would be submitted to the Panatrack tables:
·
PanatrackerGPX_DirectedTransferOrder (order header details)
·
PanatrackerGPX_DirectedTransferOrderUnits (item details)
The following provides a guideline to populating these tables
PanatrackerGPX_DirectedTransferOrder
Field Name Description
TransOrderCode
SourceLocCode
ViaLocCode
Represents the internal order number for the transaction. This is the order number that will be displayed on the Order list on the Order
Fulfill transaction in the Panatracker mobile client interface
This is the Dynamics GP Site that the inventory will be picked "FROM". If using multi-bins, the default Sales Order Fulfillment bin assigned to the item will be the bin default presented. If not default bin is set up, the user will select the bin as part of the transaction data capture.
This is the Dynamics GP Site identified as the intransit site. When using the in-transit functionality, the destination receiving site will use the PO receiving transaction to create the in-transit transfer 'from' the ViaLocSite to the
DestinationLocSite. If using multi-bins, the default Purchase Receipt Bin will be assigned.
Requirements
This is a required field and must be a unique number. This is a primary key which will also relate to the corresponding item lines on the
DirectedTransferOrderUnits table.
This is a required field. The Site entered must be a valid Site set up in Dynamics GP. If using multi-bins, the Sales Order
Fulfillment bin must be set up.
Via Site is not required. If it is not provided, the Transfer will be created directly for the
Destination Site set up. The
ViaLocCode is required for a two-step transfer. The Site entered must be a valid Site set up in Dynamics GP. The
Purchase Receipt Bin must be set up in GP.
This is a required field. The Site entered must be a valid Site set up in Dynamics GP. If using multi-bin, the Purchase Receipt bin must be set up.
DestinationLocCode This is the Dynamics GP Site that the inventory is to be transferred 'TO' (i.e. the requesting location). If using multi-bins, the default bin will be the Purchase Receipts default bin set up on the item in Dynamics GP. If using the
AuditReqd
ViaLocCode, the GP Site set up for the
ViaLocCode populates for the 'FROM'
For future functionality
DocDate
ShipMethodCode
FulfilledDate
DueDate
This id the order date.
This identifies the shipping method for the transfer. It is logged as part of the Panatracker logging database.
Updated when the order is submitted and the transfer is created from the Panatracker mobile client.
This represents the requested delivery date for the inventory to the destination location. The order list in the Panatracker Order Fulfill
Valid date must be entered.
This field is optional.
Updated by Panatracker
Valid date must be entered.
68 / 75
interface is sorted based on requested dates
FlexFields 1-5 For future functionality
OrderGroupCode For support to Batch Picking. When orders are placed in a Group Code, those orders would then be grouped together in a single pick list for picking under the Batch Pick transaction. Orders assigned to a group are not available in the standard Order Fulfill screen.
PanatrackerGPX_DirectedTransferOrder
TransOrderCode Represents the internal order number for the transaction. This is the order number that will be displayed on the Order list on the Order
Fulfill transaction in the Panatracker mobile client interface
LineItemSeq
ItemCode
Item line item sequence.
This field is optional.
This is a required field and must be a unique number. This is a primary key and must correspond the
TransOrderCode on the
DirectedTransOrder (header)
Required - Corresponds to
ItemCode
Required - minimum 1
ItemDescription
QtyOrder
QtyFulfill
UnitOfMeasure
This is the GP Item Number for the items requested to be transferred.
This is the Item Description and should correlate the GP Item Card for the item number entered in ItemCode
This is the requested quantity to transfer.
For a new order submit, this should be quantity
0. This is updated with thesubmit to create the corresponding transfer from the Order Pick screen in the Panatracker interface.
This is the Unit of Measure corresponding the
Item to be picked. Alternate UOM may be entered; however, it must be a valid UOM based on the GP Unit of Measure Schedule assigned to the item. The transfer will be created based on the UOM entered
Corresponds to ItemCode
Required
= 0. Updated by Panatracker
Required
The Panatracker Order Fulfillment transaction is used to “pick” the transfer order. Refer to
for details on this transaction.
Once the order is picked and submitted, instead of updating a Sales Order , a Site Transfer transaction is created in GP based on the transaction setup. The Panatracker table will be updated based on quantity picked. Line items where quantity picked = quantity to transfer will no longer be available.
If using a “Via” Site, a pending Inbound Transfer transaction will be created in the corresponding
is used, the Shipping Box(es) entered for the pick will be
recorded as the corresponding transaction number. If a Shipping Box is not used, then the original
Transfer Order number will be used.
In the event of multiple picks, the suffix will be added. For example, Transfer Order “12345” would have the first pick transaction number as “12345”. If a second pick is done, then the inbound receiving transaction would be recorded as “12345-1”.
The receiving site location will then use the Receiving transaction which will create the corresponding
69 / 75
Site Transfer “from” the Via Site. The Inbound Transfer table for quantity received will then be updated and the transaction marked as closed.
70 / 75
ASN Receiving
Panatrack has added a table structure to support Inbound Vendor Shipments. This is commonly known as
Advanced Ship Notices (ASN). When a PO is selected within the Receiving transaction interface that is identified as a ship notice, the Shipment ID would be used to select each “package” and a receiving transaction will automatically be created in GP based on the file details supplied.
The supporting tables include::
PanatrackerGPX_InboundVendShipmentRepresents the header details for the transaction
PanatracerGPX_InboundVendShipmentUnits: The corresponding line details for the transaction
The following is the overview of the file structure and requirements:
PanatrackerGPX_InboundVendshipment
Field Name
PkgTrackingCode
Description
This represents the Shipment ID. If more than one package is included in the shipment, there may be several Shipment IDs associated
Status with a single PO. If there are multiple packages associated with the purchase order, the user will then be prompted to receive each specific Package by selecting the Package
Code.
The receipt status for the shipment. When the file is submitted, the Status would be set to 1 for each PkgTrackingCode. Once the
Transaction Header
Requirements
Required
Unique numbers must be assigned if receiving by individual packages
New transaction = 1
Required.
POCode
InboundLocCode
DocDate
AuditReqd
ShipMethodCode
ShipToName
DueDate transaction has been processed, the Status is updated to ‘4'
The corresponding purchase order in Dynamics
GP. This must be a valid and open Purchase
Order available to receive against in Dynamics
GP.
This is the Site ID. This must match to a Site set up in Dynamics GP and should match the PO assigned Site. The Site can be used to filter available purchase orders in the Panatracker
Receiving interface.
This is the file document date.
For future functionality
This is the shipping method of the transaction. Optional.
This is the Ship To name.
This is the expected delivery date for the
VendorCode
VendorName shipment.
This must match the Vendor ID assigned to the corresponding purchase order and must be a valid Vendor ID set up in Dynamics GP. Vendor can be used to filter the PO look up list in the
Panatracker Receiving transaction.
Corresponding Vendor Name to the
VendorCode supplied
ReferenceCode
ReferenceCode2
FlexField1-5 For future functionality
PanatrackerGPX_InboundVendshipmentUnt
Required
Optional.
Optional
Optional
Optional
Transaction Line Items
71 / 75
PkgTrackingCode
POLineNumber
ItemCode
ItemDescription
LotCode
SerialCode
ReceiptBin
ReceiptQtyType
QtyShipped
QtyReceived
UnitExpDate
UnitMfgDate
UnitOfMeasure
This represents the Shipment ID. If more than one package is included in the shipment, there may be several Shipment IDs associated with a single PO.
The associated PO Line Number on the
Dynamics GP Purchase Order. The line number and item MUST match the Dynamics
GP Purchase Order.
This is the Dynamics GP Item Number for the associated line sequence number.
The corresponding item description on the purchase order line
The Lot detail for the line number that will be received. Each lot will be represented in a separate line.
The Serial Number detail for the line number that will be received.
If using multi-bins, the designated bin for the receiving transaction. If no bin is designated, the defaults set up in Panatracker will be used.
The quantity shipped for the PO line
When the receiving transaction is completed through Panatracker, the QtyReceived will be updated.
For Lot Tracked Inventory.
Populates the Expire Date Attribute for the Lot passed in.
For Lot Tracked Inventory.
Populates the Manufacture Date Attribute for the Lot passed in.
The Unit of Measure for the Receipt. This must match the Unit of Measure on the corresponding purchase order line in
Dynamics GP. If Unit of Measure is not populated, the purchase order Unit of
Measure will be defaulted.
Required
Each line must be associated with the corresponding code.
This must match the Header.
Required
Required
Required if item tracking set in Dynamics = Lot
Required if item tracking set in Dynamics = Serial
Required if a default PO
Receiving Bin is not set for either the Site or the Item in
GP.
If the ASN transaction is identified by a Package ID, either the PO Number OR Package ID can be selected in the [PO] field. Otherwise, select the PO and then scan or select the corresponding Package ID to receive.
72 / 75
The purchase order or purchase order items associated with the Package ID will automatically be received creating the corresponding Receiving Transaction in
Dynamics GP. The receive quantity will be updated on the Pantracker table and the transaction status updated to closed.
73 / 75
Scarica
Link pubblico aggiornato
Il link pubblico alla tua chat è stato aggiornato. Puoi visualizzare e gestire i tuoi link di chat dopo la registrazione qui.
Link pubblico del documento
Pubblicità
