Tuesday, June 27, 2017

Dynamics GP - Setup PO Approvals - Purchase Order Enhancements

Do not confuse this with Workflow Purchase Approvals, which is a completely different module that allows users to approve via e-mail.

Review this article
Run this to ensure no transactions have blank users.
This will prevent po approvals from enabling.
update pop10100 set USER2ENT = 'sa' where USER2ENT = ''

  • Go to GP>Tools>Setup>Purchasing>PO Enhancements
  • Tick Activate approvals
  • Click Approval Setup
  • Set sa for unlimited approval
  • Configure approvers accordingly

Thursday, June 22, 2017

Dynamics NAV - LS Retail - The POS Data Entry already exists. Identification fields and values: Entry Type := 'GIFTCARDNO', Entry Code='xxx'

Possible data corruption from disconnection or bad sync

Clear the corrupted records.
Re-synchronize the table

Delete FROM [POS Data Entry] where [Entry Code] = 'xxx'


Wednesday, June 21, 2017

Dynamics NAV - LS Retail POS - Pharmacy - "POS Prescription Order Posting already exists."

This happens when a prescription has had lines against it in the POS, but is then deleted or removed at the store level.
This results in orphan lines with references to a prescription that does not exist, and causes the POS to crash when attempting to exit the prescription from the POS.

Update the POS Trans. Line table, remove any references to the offending Prescriptions in the Prescription Order no. column.
Once removed, you will be able to void the pos lines as regular transactions.

  update [CRONUS].[dbo].[CRONUS$POS Trans_ Line]
  set [Prescription Order No_] = ''
  where [Prescription Order No_] = 'PRPO095043'

Tuesday, June 20, 2017

Dynamics GP - Purchasing - Blanket Orders

You can only have one item per blanket order.
The first line represents the total amount to be ordered.
All other lines represent the dates and quantities of receipts.

  • Create Blanket Purchase Order
  • Enter Line item for total amount to be purchased
  • Click the "Blanket" button in the toolbar
  • Enter the breakdown schedule for the quantities and dates of expected receipts

Dynamics GP - Purchasing - Drop Ship Process

There are multiple ways to use the drop-ship functionality, this is just one of the ways

  • Create Sales Order
  • Enter Line Item
  • Back Order Quantity
  • Tick Drop Ship (D Column) in the line item
  • Click Actions>Purchase to Generate PO
    • Will generate drop ship po to customer address with sales document commitment link
  • On PO Screen, click Actions>Invoice
  • Post Invoice
    • This fulfils the sales order
  • Transfer Sales Order to Sales Invoice
  • Post Invoice

Saturday, June 17, 2017

Data Director - Error: Table [$Item] Not found in Database [POS]

A previous action or job is locking the specific table in question, causing DD to stop all pending jobs.
If you attempt to cancel the job from head office, it does not cancel.


  • You can only cancel the errant job from the head office after all destinations have been restarted or DD service restarted
  • Restart Machine or Data Director service on terminal
    • Login to machine
    • Run Data Director Configuration Tool as Administrator
    • Connect to terminal
    • Stop service
    • Start Service
    • Repeat for all offending terminals
  • Cancel the job on just this terminal
    • Run Job Monitor
    • Connect to terminal
    • Select the error job on top
    • Select the error terminal on the bottom
      • Right click>Cancel job on Destination>This Only
  • OR Cancel the offending job on all hosts (this will only work for the terminals that have restarted the DD service or machine)
    • Run Job Monitor
    • Connect to head office
    • Select the error job on top
      • Right click>Cancel job on All Hosts

Wednesday, June 14, 2017

eOne Smartconnect - Input variable contains a duplicate document (IVDOCNBR)

Other Errors: The Lot quantity passed in is <> to the transaction quantity
This error occurs during Purchase Receipt Imports, or Item Transaction imports

The integration is creating the header first, and when it attempts to create the line, it detects the header already exists and fails.
By default, it attempts to create a new document instead of update the existing document.
The document numbers may genuinely already exist, ensure that your map is pointing to the correct company. Check the tables for any duplicate document numbers you may have already imported.


  • If there is a flag to update lines, this should be marked
  • Key Field should be: Document Number
  • Include a LineItemSequence
  • Change the order of integration to Lots>Lines>Transaction Header

If all else fails, use Integration Manager.