By Steve Endow
This is a pretty obscure eConnect issue that had me puzzled for several minutes.
I'm working on an upgrade of a client's existing eConnect integration. One component of the integration involves updating existing SOP Orders in Dynamics GP.
When the integration code submits the order update to eConnect on my development server, I get this error:
Error Number = 110 Stored Procedure= taSopLineIvcInsert Error Description = Item number/location code does not exist in inventory
Node Identifier Parameters: taSopLineIvcInsert
SOPNUMBE = TEST001
SOPTYPE = 2
LNITMSEQ = 16384
Related Error Code Parameters for Node : taSopLineIvcInsert
LOCNCODE =
NONINVEN = 0
ITEMNMBR = E100
![]()
![]()
![]()
This is a pretty obscure eConnect issue that had me puzzled for several minutes.
I'm working on an upgrade of a client's existing eConnect integration. One component of the integration involves updating existing SOP Orders in Dynamics GP.
When the integration code submits the order update to eConnect on my development server, I get this error:
Error Number = 110 Stored Procedure= taSopLineIvcInsert Error Description = Item number/location code does not exist in inventory
Node Identifier Parameters: taSopLineIvcInsert
SOPNUMBE = TEST001
SOPTYPE = 2
LNITMSEQ = 16384
Related Error Code Parameters for Node : taSopLineIvcInsert
LOCNCODE =
NONINVEN = 0
ITEMNMBR = E100
The item is setup properly in GP and it is assigned to the correct inventory site, as it is on the existing order.
For reference, here is the relevant XML that is being submitted to eConnect.
< ?xml version="1.0" encoding="utf-8"? >
< eConnect >
< SOPTransactionType >
< taSopLineIvcInsert_Items >
< taSopLineIvcInsert >
< SOPTYPE >2< /SOPTYPE >
< SOPNUMBE >TEST001< /SOPNUMBE >
< CUSTNMBR >108404< /CUSTNMBR >
< DOCDATE >2016-04-10< /DOCDATE >
< LOCNCODE / >
< ITEMNMBR >E100< /ITEMNMBR >
< AutoAssignBin >1< /AutoAssignBin >
< UNITPRCE >0< /UNITPRCE >
< XTNDPRCE >0< /XTNDPRCE >
< QUANTITY >0< /QUANTITY >
< FUFILDAT >2016-03-24< /FUFILDAT >
< ACTLSHIP >2016-03-24< /ACTLSHIP >
< QTYCANCE >0< /QTYCANCE >
< QTYFULFI >1< /QTYFULFI >
< ALLOCATE >0< /ALLOCATE >
< UpdateIfExists >1< /UpdateIfExists >
< QtyShrtOpt >2< /QtyShrtOpt >
< /taSopLineIvcInsert >
< /taSopLineIvcInsert_Items >
Notice that the LOCNCODE value is blank. Since the location code (site ID) isn't being updated or changed, it isn't being sent into the order update. I would assume that eConnect would just update the item and figure out the existing site ID for the item.
But that doesn't seem to be the case.
After checking my order, my item setup, my site setup, and everything else I could imagine, I assumed that there was some default Site ID that was missing in my dev environment.
After searching for a while, I found that in my development environment, where I'm testing with the Fabrikam company, there is a SOP default site of WAREHOUSE.
When I changed that default Site ID to match the site ID of the item on the order being updated, the error went away.
I realized that my test inventory item was only setup for one test site, and was not setup with the WAREHOUSE site ID. I added the item at my test site and that resolved the issue as well.
So, it seems that when updating an order, if the LOCNCODE value is not sent to eConnect, the item must be assigned to the default site under SOP Setup.
Steve Endow is a Microsoft MVP for Dynamics GP and a Dynamics GP Certified IT Professional in Los Angeles. He is the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.
