Integration fails with "document already exists"

(0) Share

Report

Posted on by Community Member Microsoft Employee

I'm trying to expand a working integration which imports transactions as sales orders from a business partner. Some of these transactions are orders with new products not in our system. We don't maintain inventory. We don't really even care about the products except that we can't bill the invoices without them. I am trying to add in a part integration to run prior to the sales order integration to deal with new parts. I'm running into multiple problems with this approach because the part integration doesn't set up default sites or vendors - even though we use static values. :S

Anyway, I tried running the part integration (and it worked) but the sales order got hung up in the batch and wouldn't post with the other three orders (with pre-existing parts). I was finally able to use the Document Setup to delete the sales order and clear the batch AND I was able to finally get the part deleted back out to try again. The part came in fine (so far), but in trying to re-integrate the one order, I keep getting the error "document already exists" and the integration fails.

I've looked through the SOP tables for any sign of the original order number (invoice numbers are assigned as the orders integrate) and can't find it. Can someone point me to how I can get this sales order into the system?

Thanks!

*This post is locked for comments

All responses (4)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration fails with "document already exists"

Thanks, Leslie, but the first two items are already set. As we use the Integration primarily for one vendor (yet others exist), I can not endorse the third option at this time.

And I am using eConnect. (I looked at the standard one and there is literally zero difference, however.)
Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration fails with "document already exists"

As I posted above, I've already looked in the SOP tables for both current and historical transactions. The other problem is that it isn't the SOPNUMBE that is causing the problem - those are generated dynamically upon integration. I believe it is the original document number.
L Vail 65,271 on at

Like (0)

Report

RE: Integration fails with "document already exists"

Hi,

You might want to look at a couple of SOP settings. On the Sales Order Processing Setup window, there is a checkbox "Prices not Required in Price List". You might want to check that box.

In the SOP Setup Options window, make sure the Enter Non-Inventoried Items box is checked:

If you are not using anything except the Item Master table in inventory, you might just want to turn the module off. You can do that in the Registration window, just uncheck the box next to Inventory Control:

Also, if you are using Integration Manager, be sure to look at the eConnect Adapter options. If you can use the eConnect Adapter, the integration runs incredibly fast because it is using the SQL stored procs instead of running a macro. You do not even need the workstation installed on the machine running the integration, nor do you need GP to be launched. You can also use command line code to put IM on a schedule.

Kind regards,

Leslie
Community Member Microsoft Employee on at

Like (0)

Report

RE: Integration fails with "document already exists"

The error indicates the document exists in system - check SOP10100 and SOP30200 table of GP company database if there the order still exits in database :

select * from sop10100 where sopnumbe = 'Order number'

select * from sop30200 where sopnumbe = 'Order number'

This should confirm if you delete actually deleted the orders.

Cheers!