"Error 1189: taSopHdrRecalc - Payment total does not match deposits+payments"

Error: Payment total does not match deposits+payments entered for the document

This error usually occurs when the taSopHdrIvcInsertPre stored procedure has been modified.

Solution: Check with your IT team to determine if modifications have been made to this stored procedure. The stored procedure may have been overwritten during a Dynamics GP update or upgrade. If your IT team cannot resolve the issue, contact support@panatrack.com.

"Error 1356: taIVTransferHeaderInsert - Batch is currently being posted"

Transaction Type: Site Transfer

The Batch ID assigned to the transaction has a status of "Marked" in GP, preventing batch posting. This may occur when an automated posting solution is enabled and the submit happens while the posting solution is processing the batch.

Solution: Re-submit the transaction later, or check the Batch status in GP and update it to "Available".

"Error 1379: taIVTransferLineInsert - Unit of Measure does not exist"

Transaction Type: Site Transfer

This is a rare error. Review the Unit of Measure Schedule setup for the item. If you recently updated the GP database, run Check Links to resolve the error.

"Error 1526: taSopSerial - Serial Number has already been sold"

Transaction Type: Order Fulfill

The serial number selected is marked as sold in GP. This occurs when another user selected the same serial in another GP transaction or when a transaction was submitted to GP between serial selection and order fulfillment submit.

Verification Steps:

1. In GP, navigate to Inventory > Inquiry > Serials.
2. Search for the serial number.
3. Check if the Alloc flag is checked.
4. Identify the transaction through Serial/Lot Trace in GP.

Solution: Delete the serial number from the other transaction holding the allocation OR remove it from the current transaction before submitting.

"Error 1731: taSopLineIvcInsert - Unable to update SOP Header Values"

This error typically occurs when orders are entered directly into the database by an eCommerce solution. Dynamics GP doesn't have a chance to check if the TAXSCHID exists in the schedule for the item.

Solution:

1. Open the order mentioned in the error message.
2. Select the line item mentioned.
3. Verify the tax schedule information.
4. If the TAXSCHID exists, confirm the syntax is correct with no extra spaces.
5. Save changes and resubmit the failed transaction from the portal.

"Error 1748: taSopHdrRecalc - Primary Bill to Address ID does not exist"

Solution: Confirm in GP that the customer has a correct bill-to address, then resubmit the transaction.

"Error 1751: taSopHdrRecalc - Tax Schedule does not exist"

This error indicates incorrect tax schedule setup. It most often occurs when a new tax schedule is set up incompletely.

Solution: Review Tax Schedule Maintenance and confirm the tax detail is set up and linked correctly. If no tax details are assigned, this is likely the cause.

"Error 1757: taSopHdrRecalc - Unable to create commissions"

The most common cause is related to company access to the Currency ID.

Solution: Confirm that multicurrency is set up in GP for the GP company you are connected to.

"Error 2233: taSopLineIvcInsert - QTYFULFI cannot be greater than remaining quantity"

This error indicates that the quantity fulfilled by PanatrackerGP exceeds the remaining quantity to fulfill. This may occur when:

• The order pick was completed and left in-progress for a period of time. At submit, other updates to the fulfilled quantity made the original picked quantity exceed the remaining quantity.
• Changes were made to the GP sales order (order quantity or canceled quantity) after picking but before submission.
• A second pick on a partially picked order/invoice may create this error depending on settings.

Solution: Review the current order fulfillment quantity in GP and identify the actual remaining quantity. Delete the line item on the failed transaction in the PanatrackerGP portal. Add the pick for the remaining quantity (if any). Review other transactions submitted for this sales order to identify other pick transactions.

"Error 3353: taIVTransferLotInsert - Lot Number does not exist"

Transaction Type: Site Transfer

This error occurs when the selected lot being submitted doesn't exist in GP. It may occur if the lot is selected on another transaction after it was selected on the transfer but before submit. This error also occurs when inventory setup Auto-Assign Lot Numbers Based on = "Expiration Date".

Solution: Confirm the lot in GP under Lot Inquiry for the site and bin selected. If using Auto-Assign based on Expiration Date, change to "Receipt Date".

"Error 3442: taSopLineIvcInsert - Invalid Currency, functional currency must be set up"

Transaction Types: Order Fulfillment, Pack Order

Solution: Perform the following steps in Dynamics GP:

1. Navigate to Tools > Setup > System > Multi-Currency Access. Confirm the company has access to Z-US$.
2. Navigate to Tools > Setup > System > Currency Setup. Confirm Z-US$ is set up.
3. Navigate to Tools > Setup > Financial > Multicurrency. Set up a functional currency.

If this doesn't resolve the issue, confirm you have the latest version of eConnect (Microsoft's API for posting to GP) for your Dynamics GP version.

"Error 5047: taIVMultibinBinToBinTransfer - Lot number is not available"

eConnect only checks whether the item/bin combination has a Lot Number Sold (LTNUMSLD) value in the IV00300 table. Even if enough quantity exists in the bin, eConnect doesn't check for more than one instance of the item before generating this error.

Solution (Workaround):

1. Update the LTNUMSLD column to 0.
2. Resubmit the failed transaction in the PanatrackerGP portal.
3. Update the LTNUMSLD column back to 1.

"Error 7321: taPopRcptLineInsert - Decimal Places on UNITCOST does not match setup"

Submitting a Dynamics GP eConnect transaction for a purchase order without a UNITCOST node for non-inventory items returns this error.

Additional Symptoms:

• Currency decimal places set to 5 for non-inventory items always received this error.
• Error still occurred when set to 2 decimal places (system default).
• Error did not occur with decimal place set to 0.

Solution: Multi-Currency was not enabled, but a multicurrency field for a checkbook ID was filled in during setup. Microsoft advised running the following query:

UPDATE CM00100 SET CURNCYID = '' WHERE CHEKBKID = 'XXXXX';

Warning: Only use this solution if multi-currency is not enabled; otherwise, you may cause configuration issues.

This behavior was encountered on Dynamics GP 2010 but may occur on other versions.

"Error 8162: taPopRcptLineInsert - Item is Inventoried, NONINVEN flag incorrect"

Cause: The item was originally entered on the PO before being set up as an inventory item in GP, marking it with a non-inventory flag. Before receiving, the item was set up as an inventory item in GP. The non-inventory flag isn't natively changed on the existing PO. At receiving, the item is validated as an inventory item, throwing the error.

Solution: Contact your system administrator to update the PO line non-inventory flag in the database. Alternatively, add a new line on the PO for the inventory item and delete (cancel) the original.

"Error 8673: taIVMultibinBinToBinTransfer - Lot combination does not exist in Bin"

Full Error: Lot number / qty type / location / expiration date combination does not exist in the Bin entered

Transaction Type: Item Bin Move

Cause: The usual cause is a different time zone on the handheld versus the application server. The application server or handheld translates SQL Server's "empty" date. Since the GP database cannot store a null date, it uses 1/1/1900 to mark an empty date. A time zone mismatch translates the date back (e.g., to 12/31/1899).

Solution: Confirm that the handheld has the same time zone setup as the application server. Also confirm the application server and database server are in the same time zone.

"Error 9370: taSopHdrIvcInsert - Currency ID mismatch between header and line"

Transaction Type: Verify Order

Error: You are passing a Currency ID in the header and you did not pass the same one to the line

Solution:

1. Double-check your functional currency setup: Functional Currency Troubleshooting .
2. Confirm there are no blank line items on the order (i.e., Item Number field is empty).
3. If unresolved, run the attached query on your GP company database with your Sales Order Number specified, and send results to support@panatrack.com along with an updated usage file.

"Error 11971: taPopRcptLineInsert - Prepayment exists for Purchase Order"

Cause: eConnect doesn't support passing prepayment purchase orders to GP. Microsoft introduced the Prepayment feature in GP 2013 without including an eConnect update method.

Solution: While Microsoft hasn't changed this, a consultant was able to create a workaround. If this error affects you, we can refer you to:

Larry Ressler
Vice President, Consulting
Keel & Company, LLC
701.371.9945
Email: Larry@keelcompany.com

"Error 12013: taPopRcptLineInsert - Active Purchase Order Approval workflow"

Microsoft explains this error in their community article.

Solution: File a ticket with Microsoft or your GP Partner. However, customers have reported success by changing the value in the Workflow_Status column in POP10100 from 0 to 9.

"An item with the same key has already been added"

Dynamics GP eConnect may throw misleading errors if functional currency is not set up. Examples include:

• Purchase order submission: "An item with the same key has already been added"
• Adjustment submission: "Cannot insert the value NULL into column 'EXTDCOST', table 'DATABASENAME.dbo.IV10001'; column does not allow nulls"

Cause: Functional currency is not set up in Dynamics GP. The eConnect Install Administration Guide for Dynamics GP 2013 (from Microsoft) states that functional currency is required for eConnect to function properly.

Solution: Set Functional Currency:

1. Navigate to Microsoft Dynamics GP > Tools > Setup > Financial > Multicurrency.
2. If Functional Currency is set up, there should be a value like Z-US$.
3. If not set up, use the lookup to view options and select the appropriate currency. Tap OK to save.
4. eConnect and Dynamics GP both recommend running Check Links at this point.

If Functional Currency lookup was empty:

1. Close the Multicurrency Setup.
2. Navigate to Microsoft Dynamics GP > Tools > Setup > System > Multicurrency Access.
3. Under Currencies, select the currency for the Multicurrency Setup screen.
4. For each company, check the Access box.
5. Tap OK and repeat the steps above.

"Bin transfer of lot-tracked item after allocation handled incorrectly"

Cause: Native GP handles Item Bin Moves of allocated lot quantities differently with eConnect than direct entry into GP. When a lot with allocated quantities has a portion moved from Bin A to Bin B, the proper behavior is to leave the allocated quantity in Bin A. Manual entry in GP properly results in a "split lot", moving unallocated quantity to Bin B and leaving allocated quantity in Bin A.

Solution: Microsoft Sr. Support Engineer Isaac Olson (iolson@microsoft.com) created an updated eConnect stored procedure (UpdatedtaIVMultibinBinToBinTransfer.sql) to replace the existing eConnect stored procedure. Run the altered stored procedure to prevent the issue going forward.

Note: If a user upgrades, the stored procedure reverts to its original form. You may need to run the updated script again after upgrades.

"Cannot insert NULL into column 'DSCPCTAM', table 'XXX.dbo.POP10300'"

Cause: Discount Type is not defined in the Payment Terms Setup in GP. This needs to be defined even if the Payment Term doesn't calculate a discount.

Solution: Access the Payment Terms Setup in GP: Tools > Setup > Company > Payment Terms. Define the Discount Type.

Corresponding Table: SY03300 Payment Terms Master

Alternative Access: From the Purchase Order, tap the arrow next to the Vendor ID to open the Purchasing Vendor Detail Entry window. Tap the Payment Terms link to open the Payment Terms Setup window.

"Document is currently being edited by another user"

Cause: The error occurs when an order is open in GP during transaction submission. GP locks the order to prevent conflicts.

Solution: Close the order in GP and submit again from the PanatrackerGP portal.

"eConnect error related to Analytical Accounting"

Error: Violation of PRIMARY KEY constraint 'PKAAG20000'. Cannot insert duplicate key in object 'dbo.AAG20000'

Transaction Type: Adjustment (could occur on any inventory transaction)

Cause: This common eConnect error in test companies indicates incomplete or inaccurate Analytical Accounting setup. The next AA ID for the test company is lower than the next ID in the live company. This causes AA to pass an ID that already exists to the AAG20000 table. The next ID is stored in table AAG00102 in the DYNAMICS database.

Solution: This requires GP database maintenance. The error occurs when a company database is cloned and the Analytical Accounting (AA) tables in the DYNAMICS company aren't updated to reflect the new company. Update the value in table AAG00102 for the record where aaTableID=20000 and CMPANYID=(your company ID from Table SY01500). When adding a new record, use the max value in the table plus one.

"Failed to convert parameter value from string to DateTime"

Cause: This is not a PanatrackerGP issue but rather a Microsoft eConnect issue. The date format is determined by the region settings under which the PanatrackerGP portal runs.

Solution: Change the regional settings on the server where PanatrackerGP is installed:

1. Open Control Panel.
2. Select Clock, Language, and Region.
3. Under Region, select Change date, time, or number formats.
4. Confirm the date format matches your GP server format.
5. On the Administrative tab, tap Copy settings.
6. Check Welcome screen and system accounts and tap OK.

This pushes the Date/Time settings to the account that runs IIS.

"SecurityException: Source not found, event logs could not be searched"

Full Error: The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: State.

Cause: Microsoft locked out applications from making changes to the newly added State event log.

Solution: Run the Registry Editor as a SYSTEM account to grant PanatrackerGP rights to modify the State event log:

1. Download PsExec from Microsoft Sysinternals.
2. Extract the tool to a permanent folder (e.g., c:\tools).
3. Open an elevated Command Prompt.
4. Start the Registry Editor under the SYSTEM account: c:\tools\psexec.exe -sid c:\windows\regedit.exe
5. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\State
6. Right-click and select Permissions.
7. Add the user IIS APPPOOL\PanatrackerGP and grant Full Control.

After completing these steps, resubmit the transaction twice. The correct error should appear in the portal.

"No endpoint listening at net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations"

Full Error: There was no endpoint listening at net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations that could accept the message

Cause: This message occurs in Dynamics GP 2010 and later, as the eConnect mechanism was moved to a WCF service.

Solution: This usually indicates eConnect is not running on your server:

1. Open Services.
2. Verify that eConnect is started and running.
3. Verify the startup is set to Automatic.

Note: If eConnect stopped suddenly (often after reboot), you may be using an expiring login account for your eConnect service. This problem will recur when the account expires. Per the eConnect installation guide, set this account to not expire and minimize account privileges.