Receiving a Prepaid Purchase Order Fails with eConnect Error 11971 "A Prepayment Exists"

Receiving a Prepaid Purchase Order Fails with eConnect Error 11971 "A Prepayment Exists"

Receiving a Prepaid Purchase Order Fails with eConnect Error 11971 "A Prepayment Exists"

Receiving a Purchase Order that has a prepayment applied against it fails with eConnect error 11971. This is a known limitation of Microsoft Dynamics GP's eConnect integration, not a PanatrackerGP defect — there is no fix to apply. This article explains why it happens and what to do instead.

Symptom

When receiving against a Purchase Order that has a prepayment applied, the transaction is rejected with:

Error Number = 11971
Stored Procedure = taPopRcptLineInsert
Error Description = A Prepayment exists for the Purchase Order

This happens whether the receipt is submitted from the handheld or resubmitted from the portal — the transaction never posts to GP.

Cause

NOTE: This is a platform limitation in Dynamics GP / eConnect, not something in PanatrackerGP that can be fixed or configured around.

Microsoft introduced Purchase Order Prepayments in Dynamics GP 2013, but never released an eConnect method for submitting a receipt against a PO that has a prepayment applied. PanatrackerGP posts receiving transactions to GP through eConnect's taPopRcptLineInsert stored procedure, and that procedure has no path for prepaid POs — so any receipt against one is rejected, regardless of how it was entered. This has remained the case since the feature was introduced.

How to Fix / What To Do

  1. Receive Purchase Orders that have a prepayment applied directly in Dynamics GP instead of through PanatrackerGP. This is the standard path customers use for this specific class of PO, since eConnect cannot carry the receipt through.
  2. If receiving prepaid POs through PanatrackerGP is important to your workflow, contact Panatrack Support. We're aware of at least one Dynamics GP partner who has built a custom workaround for this limitation for another client, and can facilitate an introduction on request. This would be a custom engagement with a GP consultant — it is not something Panatrack can build into the standard eConnect integration, since the gap is in Microsoft's own eConnect API.

Questions? Contact Panatrack Support.

Related articles