PO Receiving Fails with eConnect Error 12013 "Active Purchase Order Approval Workflow"

PO Receiving Fails with eConnect Error 12013 "Active Purchase Order Approval Workflow"

PO Receiving Fails with eConnect Error 12013 "Active Purchase Order Approval Workflow"

Submitting a Receiving transaction from the PanatrackerGP portal fails, and Dynamics GP rejects it through eConnect with error 12013. This happens even on purchase orders whose GP workflow shows No Action Needed or is otherwise fully approved — there is no actual pending approval blocking the PO.

Symptom

The portal shows an eConnect rejection similar to:

An error occurred while submitting transaction ID <transaction-guid>.
An error occurred performing the Receiving transaction.
eConnect rejected this transaction.
Sql procedure error codes returned:

Error Number = 12013  Stored Procedure = taPopRcptLineInsert
Error Description = There is an active Purchase Order Approval workflow.
Use Dynamics GP to enter this data
Node Identifier Parameters: taPopRcptLineInsert
PONUMBER = PO0000XX

Cause

This is a known Microsoft eConnect behavior, not a PanatrackerGP defect. When a Purchase Order Approval workflow is enabled in the GP company, eConnect's taPopRcptLineInsert stored procedure checks the PO's Workflow_Status value in the POP10100 table before allowing a receipt to post. On affected GP versions this check doesn't correctly recognize every completed/"No Action Needed" workflow state, so it blocks the receipt even though nothing is actually awaiting approval on that PO.

NOTE: This is separate from the PanatrackerGP Require PO Workflow Completion for Receiving setting, which only controls whether POs with an incomplete workflow are offered for receiving in the portal. Toggling that setting does not correct the eConnect behavior described here.

How to Fix

  1. Per-PO workaround. After confirming the PO has no genuinely pending approval step in GP, have someone with database access update that PO's Workflow_Status value in POP10100 (for example, from 0 to 9) so eConnect treats the workflow as complete, then resubmit the receiving transaction from the portal.
  2. Durable fix. Contact Panatrack Support to apply a corrected version of the taPopRcptLineInsert stored procedure. Once applied, eConnect correctly recognizes completed workflow states, so this error stops recurring and you no longer need to update each PO individually.

Prevent

A GP or eConnect upgrade can overwrite a previously applied corrected stored procedure, causing this error to return. After any GP or eConnect upgrade, confirm receiving transactions still submit cleanly, and contact Panatrack Support to reapply the fix if error 12013 reappears.

Questions? Contact Panatrack Support.

Related articles