EConnect Receiving Transaction Error A Prepayment exists for the Purchase Order

(0) Share

Report

Posted on by Community Member

We are having trouble with shipment receipts integrating from our WMS application through eConnect for purchase orders that have prepayments. The eConnect error is:

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

In test we don't have any problems entering and posting shipments for the very same orders with the very same posted prepayments if it is done by using front-end GP Receiving transaction entry window. So I'm assuming there are no settings in GP we need to change, but rather it is issue with eConnect.

Does anybody know a way around this error?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

soma 24,410 on at

Like (0)

Report

Have you checked you eConnect integration for receiving transactions with normal purchase orders (without prepayments)?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

It works fine until we added a prepayment. There are fields in the work tables that are not exposed in Econnect that I think need to be populated.

select Remaining_AP_Amount, OriginatingPrepaymentAmt from POp10310

select PrepaymentAmount, OriginatingPrepaymentAmt from POp10300

Don

Was this reply helpful? Yes No
soma 24,410 on at

Like (0)

Report

I have analysed this on eConnect schema references and some samples. But, not find anything related to receiving PO with prepayment. I think no option available for this requirement in eConnect schema(May be I am wrong). Give me some time I will check this on my side and let you know.

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Somakarpagamoorthy, I am going to put in a support request with GP and will let you know what they say.

Don

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Bad News, not supported. I am trying to find away around it with a pre or post sproc routine.

From Microsoft you need run this first to skip those that have prepayments.

----

IF EXISTS (SELECT 1

FROM POP10170 (nolock)

WHERE PONUMBER = @I_vPONUMBER)

BEGIN

SELECT @O_iErrorState = 11971

Since you do have a pre-payment in the POP10170 table for your PONUMBER it is not allowed by eConnect.

Was this reply helpful? Yes No
soma 24,410 on at

Like (0)

Report

Thank you so much for the information.

Was this reply helpful? Yes No
Karl Jensen on at

Like (0)

Report

Hello,

Were you able to find a method to address this with a pre or post eConnect procedure?

Thanks!

Was this reply helpful? Yes No
tsmithappolis 5 on at

Like (0)

Report

Is there a way to address this with eConnect procedure? We have 2 customers with the same issue.

Was this reply helpful? Yes No