Why are the orders that I fulfilled not showing up on Order Verify?

Check for one of the following reasons:

Automatic Verification Setting

Under Order Fulfillment Settings, check if you have Order Fulfill Ship ID Behavior enabled AND CreateSOPick Records On Order Fulfill Submit set to true. With this configuration, the SOPicks table (populated for Verify Order) is updated automatically with the Order Fulfillment transaction, marking orders as verified.

Other Causes

• Confirm the sales order has not been previously verified by reviewing the Verify Order transaction log.
• Confirm the sales order has line items fulfilled in GP (verify the order pick was submitted to GP).

Can I use vendor barcodes to track my inventory?

Yes! If the barcode is not the same as your GP Item Code, you can still use it. Dynamics GP supports alternate item numbering:

Vendor and Manufacturer Item Numbers

In Dynamics GP, you can define:

• Vendor item numbers — Used on purchase orders; each vendor can have a different number for the same item.
• Manufacturer's item numbers — Typically what appears on barcoded inventory.

If you have alternate item numbers set up in GP under the Manufacturer's Item Number Maintenance window, PanatrackerGP will translate the scanned item number to your GP item number.

Dynamics GP Manufacturer's Item Number Maintenance Window

Setup and Access

• Have your GP Partner or database administrator import item number lists. The GP table is IV00115.
• Access in GP: Navigate to Inventory > Cards > Item Purchasing Options. Enter the item number, then tap the gear icon to the right of the Item Number field.
• Alternative: From the Item Maintenance window, select Purchasing from the GoTo action.

On-the-Fly Association

PanatrackerGP also supports associating alternate item numbers on-the-fly. This can be enabled for PO receiving in PanatrackerGP. When an unrecognized item number is scanned, the user can make the association immediately.

Why do I receive Unit of Measure conversion errors?

When setting up GP Unit of Measure schedules, the corresponding equivalents must be defined. To use an alternate unit of measure for PanatrackerGP transactions, both the equivalent setup AND the decimal place setup must support the quantity entry.

Example: Zero Decimal Places

UOM schedule with decimal place setup of 0:

• Base UOM = EACH
• CASE = 12 EACH

On a purchase order where the PO line is in CASE:

• Valid: User enters 24 EACH (converts to 2 CASES).
• Invalid: User enters 6 EACH (no equivalent to CASE conversion possible).

The unit of measure can be changed to EACH, but only multiples of 12 can be submitted as CASES.

Why isn't my sales order showing up in the order list?

Use the Diagnostics Tool

On the Panatracker portal, navigate to Administrator > Diagnostics > Missing Sales Order tab. Enter the sales order number under the profile you're using on the handheld to get initial diagnostics.

Settings to Review

• Batch Code List for Order Fulfill — Can be defined at the profile level. For partially fulfilled orders with specified Batch Codes, confirm the Batch Code For Partial Picks is included in the list.
• Use Allocations for Order Pick — If set to TRUE, the sales order must be allocated before appearing. Confirm the order is allocated in GP.
• Sales Types Enabled for Order Fulfill — Verify the sales order type in GP is supported for picking in your profile.
• Batch Pick Group UDF — Confirm your order isn't in a Batch designated for Batch Pick, or that the UDF field on the sales order is empty.

Other Conditions

• Order is already fulfilled in GP (fulfilled orders don't appear).
• Sales orders not set up with separate fulfillment process (may auto-fulfill during entry).
• Process hold assignment restricts fulfillment (remove holds flagged to prevent fulfillment).
• Backorder quantities exist (backordered lines won't appear).
• Order transferred to backorder type or invoice document.
• Filters applied for site selection (remove filters or verify site matches).
• Order list limited to 100 records (enter more of the order number to narrow the search).

How do I find why a transaction failed?

When a transaction fails on submit, review it in the PanatrackerGP portal:

1. Log into the portal and open the corresponding transaction logging page.
2. Filter transactions by status if needed, or view all failed transactions from the main dashboard.
3. Tap the expand arrow to access units, transaction details, and integration details.
4. Select the Transaction Details tab to view error messages.
5. For eConnect errors, look for the section starting with "Error Number" to read the error message.

Note: If multiple error messages appear, the last error typically represents the actual issue. For item-specific failures, the problem item is included in the message.

Check the eConnect error message section of this help site for documented errors. Otherwise, take a screenshot of the transaction details to include in a support ticket.

Example eConnect error message on a failed transaction

Where do I find my version and license information?

From the PanatrackerGP portal:

1. Navigate to Administration > System Status.
2. The current version is displayed at the top of the page.
3. Scroll down to find license information, including:
   • Number of device licenses
   • Licensed features