Purchase Order Processing – Add Line Item
Scott Hardman asked 7 years ago
Purchase Order Processing – Add Line Item
In trying to configure a map to handle PO Receiving Transaction Entry for GP, I am having trouble adding multiple line items to the work entry. As far as I can see it is a requirement to provide the create receipt map and include the ReceiptType [POPTYPE] by the error being reported.
However this prevents me from adding line items to an existing receipt as the create receipt map expects a new Receipt Number [POPRCTNM] for each record.
This inspired me to select the Update Existing checkbox in the hopes I could update an existing record. This also yields no result and ends in error.
I am unsure if this is expected behaviour, if so, it makes creating the receipt number with multiple line items very difficult as the Add Line Item map will always conflict with the Create Receipt map and vice versa unless I create a new receipt for every line item. This of course defeats the purpose of multiple line items.
If anyone else has overcome this issue or has experienced similar errors relating to node requirements, I would like to know how you did it.
Thanks
In trying to configure a map to handle PO Receiving Transaction Entry for GP, I am having trouble adding multiple line items to the work entry. As far as I can see it is a requirement to provide the create receipt map and include the ReceiptType [POPTYPE] by the error being reported.
Node taPopRcptHdrInsert not found in POPReceivingsType. The element node is required for this transaction type.
However this prevents me from adding line items to an existing receipt as the create receipt map expects a new Receipt Number [POPRCTNM] for each record.
This inspired me to select the Update Existing checkbox in the hopes I could update an existing record. This also yields no result and ends in error.
Error Number = 8053 Stored Procedure= taPopRcptLineInsert Error Description = Input variable contains a duplicate document (POPRCTNM)
Node Identifier Parameters: taPopRcptLineInsert
POPTYPE = 1
POPRCTNM = RCT0023028
ITEMNMBR = J30013090
Related Error Code Parameters for Node : taPopRcptLineInsert
POPRCTNM = RCT0023028
<taPopRcptLineInsert>
<UpdateIfExists>1</UpdateIfExists>
<QTYSHPPD>10</QTYSHPPD>
<VNDITNUM>J30013090</VNDITNUM>
<AUTOCOST>1</AUTOCOST>
<Purchase_IV_Item_Taxable>3</Purchase_IV_Item_Taxable>
<receiptdate>04/04/2016</receiptdate>
<POPRCTNM>RCT0023028</POPRCTNM>
<ITEMNMBR>J30013090</ITEMNMBR>
<VENDORID>100732</VENDORID>
<POPTYPE>1</POPTYPE>
</taPopRcptLineInsert>
“
I am unsure if this is expected behaviour, if so, it makes creating the receipt number with multiple line items very difficult as the Add Line Item map will always conflict with the Create Receipt map and vice versa unless I create a new receipt for every line item. This of course defeats the purpose of multiple line items.
If anyone else has overcome this issue or has experienced similar errors relating to node requirements, I would like to know how you did it.
Thanks
Answers
Mark Anderson Staff answered 7 years ago
This error occurs when you have the data grouped wrong in the map. You need to have your key fields set and the transaction node grouped so that it only occurs once in every document you send to eConnect.
If you run the map to file and open up one of the records it generates, you should be able to see if that header node is there at all, or is present too many times and then adjust your mapping accordingly.
If you run the map to file and open up one of the records it generates, you should be able to see if that header node is there at all, or is present too many times and then adjust your mapping accordingly.
Scott Hardman replied 7 years ago I think the problem is that the data I want to return throughout the detail line destination, only exists in the header source. So I can not add the required data in each line. or it can not group them all together.
The second issue still comes back to entering the line data map, I can not update the receipt lines after the receipt create has occurred. This leaves me in the same predicament as explained above.
Scott Hardman answered 7 years ago
I think the problem is that the data I want to return throughout the detail line destination, only exists in the header source. So I can not add the required data in each line. or it can not group them all together.
The second issue still comes back to entering the line data map, I can not update the receipt lines after the receipt create has occurred. This leaves me in the same predicament as explained above.
The second issue still comes back to entering the line data map, I can not update the receipt lines after the receipt create has occurred. This leaves me in the same predicament as explained above.
Patrick Roth Staff answered 7 years ago
Scott,
In almost every map (but POP & SOP for sure) you are required to send in the “header” node.
The reason for this is that creating a line (the purchase receipt line) doesn’t automatically create the header piece- you bring that in yourself via that node. So it is a required element.
So in your mapping, you map the lines first and then the header to create a complete document.
“I think the problem is that the data I want to return throughout the detail line destination, only exists in the header source. “
Why not? Your data sources would contain the information for both header and lines regardless since all of the source data gets connected together in one homogenous resultset essentially.
So the thought of Mark’s reply is typical of your “node xxxx not found” is somewhat typical of a grouping issue in that depending on how you choose it you get multiple “headers” created in the XML which puts the “headers” in an Items collection which eConnect won’t parse. And wouldn’t work right anyway even if it did.
Or you have a restriction that filters it out.
or you just didn’t map it.
“The second issue still comes back to entering the line data map, I can not update the receipt lines after the receipt create has occurred. This leaves me in the same predicament as explained above”
As far as this goes, the purchase receipt nodes in eConnect do not allow updates the purchase order documents – just inserts if memory serves.
We can tell because in the map lines there is not “update if exists” or “update existing” map item to set to true/false.
If you run:
sp_help taPopRcptHdrInsert
you won’t see anything type of parameter like that.
If you run the same:
sp_help taUpdateCreateCustomerRcd
You will see a param for: @I_vUpdateIfExists
which will tell us that proc supports updates. the pop receipt one doesn’t have it and so does not support updates.
If you have further issues or questions on this, please open a support case.
In almost every map (but POP & SOP for sure) you are required to send in the “header” node.
The reason for this is that creating a line (the purchase receipt line) doesn’t automatically create the header piece- you bring that in yourself via that node. So it is a required element.
So in your mapping, you map the lines first and then the header to create a complete document.
“I think the problem is that the data I want to return throughout the detail line destination, only exists in the header source. “
Why not? Your data sources would contain the information for both header and lines regardless since all of the source data gets connected together in one homogenous resultset essentially.
So the thought of Mark’s reply is typical of your “node xxxx not found” is somewhat typical of a grouping issue in that depending on how you choose it you get multiple “headers” created in the XML which puts the “headers” in an Items collection which eConnect won’t parse. And wouldn’t work right anyway even if it did.
Or you have a restriction that filters it out.
or you just didn’t map it.
“The second issue still comes back to entering the line data map, I can not update the receipt lines after the receipt create has occurred. This leaves me in the same predicament as explained above”
As far as this goes, the purchase receipt nodes in eConnect do not allow updates the purchase order documents – just inserts if memory serves.
We can tell because in the map lines there is not “update if exists” or “update existing” map item to set to true/false.
If you run:
sp_help taPopRcptHdrInsert
you won’t see anything type of parameter like that.
If you run the same:
sp_help taUpdateCreateCustomerRcd
You will see a param for: @I_vUpdateIfExists
which will tell us that proc supports updates. the pop receipt one doesn’t have it and so does not support updates.
If you have further issues or questions on this, please open a support case.
Shaun answered 7 years ago
I had the same problem, and found that you can automatically get the next receipt number by using the “Additional Column” button at the top of the destination window.
From there, create a new GP Rolling Column.
Set the Series to Purchase Order Processing, and the Document Type to Receipt number.
Now go back to your mapping, and change Receipt Number drop down list from Source Column to GP Rolling Column, and select the new column.
Voila.
From there, create a new GP Rolling Column.
Set the Series to Purchase Order Processing, and the Document Type to Receipt number.
Now go back to your mapping, and change Receipt Number drop down list from Source Column to GP Rolling Column, and select the new column.
Voila.
Charles Allen replied 6 years ago I found that using a single column in my source column I could group on solved the issue instead of selecting all header columns for the grouping, which is what you’d do in Integration Manager. In my source data I have a POPRCTNM column. Even though I’m not mapping it, I used it for the grouping.