Finance | Project Operations, Human Resources, ...

eConnect taPopEnterMatchInvLine

(0) Share

Report

Posted on by Stig59

When importing using the eConnect type POPEnterMatchInvoiceType it seems that taPopEnterMatchInvLine requires the POPRCTNM value to be set before importing. Using the POPReceivingsType with the taPopRcptLineInsert it automatically sets it to the next Receipt Number. Auto-setting the next number is also the default behavior in all other eConnect types that we have used.

Does anybody know why taPopEnterMatchInvLine requires that POPRCTNM value needs to be set beforehand?

Background:

This error is returned "eConnectTraceSource Error: 735 : Create Entity produced the following exception:
Procedure or function 'taPopEnterMatchInvLine' expects parameter '@I_vPOPRCTNM', which was not supplied."

This occurs before taPopEnterMatchInvLinePre procedure is called so we are not able to get the next receipt number there either. This means that we would have to set the next receipt number already in the foreign system that generates the eConnect XML, but which normally do not have access to GP.

Any hints appreciated.

Regards, Stig

Categories:

Microsoft Dynamics GP

All responses (9)

Answers (0)

Lisa at AonC.com 3,145 on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

The 3 - Shipment/Invoice POPTYPE is the setting I was thinking may work if you were doing both a Receiving and Invoice Match.

I haven't worked with Invoice Match node at all. In reading through my old help on it, I do see this note about MultiLine coming from multiple Shipment receipts could be why the Invoice Match behaves different than the other nodes:

MultiLine You use the <taPopEnterMatchInvToShpMultiLine> XML node when you need to manually enter/match a transaction that has one item that spans multiple shipments. The <taPopEnterMatchInvToShpMultiLine> XML node allows the line to be passed to the <taPopEnterMatchInvLine> node with the first shipment to match against. Use the <taPopEnterMatchInvToShpMultiLine> XML node to allow other shipments to be added to the line that it matches. If you use multiple <taPopEnterMatchInvToShpMultiLine> XML nodes, the totals for the transaction must be immediately passed to the <taPopEnterMatchInvLine> XML node.

I'm sorry to not be able to help. :(
Stig59 5 on at

Like (1)

Report

RE: eConnect taPopEnterMatchInvLine

Hi Lisa,

thanks for your answer. I do not think that is the case, but documentation is not clear.

With ShipRCPTLNNM you pass in the POPMtchShpRcpt and ShipRCPTLNNM that you want to match to, so that part I would believe we have covered. But of course the created receipt document also needs its own receipt number and that is where we see the issue.

Are you now saying that you can use taPopRcptLineInsert to do an invoice match as well?

It does not look that way as the only valid values for POPTYPE is

Receipt type:

1=Shipment;

3=Shipment/invoice

Regards, Stig
Suggested answer

Lisa at AonC.com 3,145 on at

Like (1)

Report

RE: eConnect taPopEnterMatchInvLine

I'm late to the party on this one but could it be a miscommunication about using taPopEnterMatchInvLine to add an invoice to a document that was originally created a as a Shipment Only (where you need to pass the POP Receipt Number from that Shipment document) versus trying to do an Invoice Match (taPopRcptLineInsert)?
Stig59 5 on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

Thanks for your reply, Beat. But we are experienced users of eConnect, so yes of course we have consulted the documentation to ensure that we provide the required data as GP expects. The issue is that in this case taPopEnterMatchInvLine works differently than all other nodes (see my other reply to this post). And unfortunately this can not be read out of the documentation.

Regards, Stig
Stig59 5 on at

Like (1)

Report

RE: eConnect taPopEnterMatchInvLine

Unfortunately I think you are missing the point here. Probably because the eConnect documentation can be quite confusing.

The eConnect Schema Reference for the taPopRcptLineInsert element taPopRcptLineInsert XML node. | Microsoft Docs also states that the POPRCTNM field is required. The same goes for example for the taSopLineIvcInsert where it states that the SOPNUMBE is required - taSopLineIvcInsert XML node. | Microsoft Docs.

In both of these cases you can submit the XML without these values and GP will automatically generate this for you. We have proven that with thousands of such transactions being created. There are also other elements where this works this way, so this is the EXPECTED BEHAVIOR when that key value is not provided. And it is also the logical way for an integration to work as any source system that generates the transaction date will, and should, not have access to GP to be able to determine what the next transaction number is.

Our question is therefore WHY taPopEnterMatchInvLine does not work in the same way as all the others?

Regards, Stig
Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

Hi Stig,

did you checked the official XML schema references for the eConnect transactions?

This might help you to find the missing element:

docs.microsoft.com/.../ff623672(v=msdn.10)

and the node references for this particular transaction:

docs.microsoft.com/.../ff623943(v=msdn.10)
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

For this taPopEnterMatchInvLine procedure, if you look at the eConnect Help file, it shows that the POPRCTNM element is a required element, thus you must be giving it a value, Dynamics GP will not default a value in for you.

In your code, it shows you're not passing in a value:

<POPRCTNM></POPRCTNM>

I'd think this is why you're seeing the message:

Procedure or function 'taPopEnterMatchInvLine' expects parameter '@I_vPOPRCTNM', which was not supplied."
Stig59 5 on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

Thanks for the reply, Derek.

That is indeed the issue we faced. Since it is not in the procedure the check for this must be somewhere else. Dexterity?

For example when we create a Shipment/Invoice Receipt we provide:

<taPopRcptLineInsert>

<POPTYPE>3</POPTYPE>

<POPRCTNM></POPRCTNM>

<ITEMNMBR>SQBY189AV-0402A</ITEMNMBR>

<ITEMDESC>CADWorx Structure Professional CX CAS License Change 2020 R2 </ITEMDESC>

<VENDORID>PBS</VENDORID>

<RCPTLNNM>16384</RCPTLNNM>

<UNITCOST>4500.00000</UNITCOST>

<EXTDCOST>9000.00000</EXTDCOST>

<QTYSHPPD>2</QTYSHPPD>

<QTYINVCD>2</QTYINVCD>

<CURNCYID>GBP</CURNCYID>

<USRDEFND1>NLSTIG002</USRDEFND1>

<USRDEFND2>1</USRDEFND2>

<USRDEFND5>A1</USRDEFND5>

</taPopRcptLineInsert>

eConnect then sets the POPRCTNM value for us based on the next available receipt number.

In this case we pass in:

<taPopEnterMatchInvLine>

<POPRCTNM></POPRCTNM>

<QTYINVCD>3</QTYINVCD>

<ITEMNMBR>SQBY189AV-0402A</ITEMNMBR>

<VENDORID>PBS</VENDORID>

<RCPTLNNM>16384</RCPTLNNM>

<UNITCOST>4500.00000</UNITCOST>

<EXTDCOST>9000.00000</EXTDCOST>

<CURNCYID>GBP</CURNCYID>

<USRDEFND1>NLSTIG005</USRDEFND1>

<USRDEFND2>1</USRDEFND2>

<USRDEFND5>A1</USRDEFND5>

</taPopEnterMatchInvLine>

And we would then expect that also the next receipt number is used. This seems to be standard method for many eConnect types; for example <taSopLineIvcInsert> also allows to not pass in the SOPNUMBE.

So the question is why this would be different for taPopEnterMatchInvLine.

Regards, Stig
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: eConnect taPopEnterMatchInvLine

I don't see any error 735 in the taPopEnterMatchInvLine, but this eConnect procedure does have a I_vPOPRCTNM variable in it and it is required, for the Receipt Number.

Are you passing this variable?

Thanks