Dynamics Community Forum Thread Details

integrating an invoice

I'm trying to integrate an invoice that has distributions and invoice line items into Great Plains using eConnect and I'm having trouble with invoice line items. I think i'm using the correct eConnect objects. They are taSopHdrIvcInsert, taSopDistribution_ItemsTaSopDistribution, and taSopLineIvcInsert_ItemsTaSopLineIvcInsert.

When i call the CreateTransactionEntity I get a response back for LOCNCODE Error Number = 106 Stored Procedure= taSopLineIvcInsert Error Description = Location code does not exist in inventory. I am passing a blank value. We don't use a default location in Great Plains.

Also, i get back an additional message that states "Error Number = 3771 Stored Procedure= taSopLineIvcInsert Error Description = Item exists as a inventoried item, NONINVEN cannot be set to 1" for an invoice line item.

I've tried setting NONINVEN to 0 but then that includes an additional message that states "Error Number = 9177 Stored Procedure= taSopLineIvcInsert Error Description = Currency/Price Level/UofM combination is not included in price list for this item". It is referring to a unit of message with the value of "Flat"

Should Great Plains have default values set to work with eConnect? Or is there a way around that if we don't use default locations, etc.?

Thanks

Categories:

Microsoft Dynamics GP

Hi ghendric,

There are required fields that need to be populated when entering a transaction in GP whether it is manually entered or brought in with an integration. In this case it sounds like this is an inventory item, so you need to provide a site or location code for the transaction, as this is a required field. With that said, I would recommend that you try to enter the transaction manually so that you can see what values are required, and then you will know what to populate on the integration. If it is a non inventory item, that you are trying to integrate, it would need to be an item number that is not an inventory item, for example if you have an item in Inventory setup as "WIDGET", you would not be able to enter a non inventory item also called 'WIDGET", so the item would need to be something different than your inventory item, if it is in-fact a non-inventory item. This is the reason that you would want to test manually keying a transaction into GP, so that you know what the values need to be for your integration file.

I hope that information helps.

Quick Links

Leaderboard