Finance | Project Operations, Human Resources, ...

Integrating Sales Orders with GP Web Services vs. Econnect

(1) Share

Report

Posted on by Jeffrey A

210

Hi - we are a highly transactional company that experiences significant issues with our GP environment specifically related to integrating our sales orders from our ecommerce platform using GP Web Services. I don't recall the exact reason we chose web services over econnect or another option but I am now trying to understand the best option that will allow us to integrate orders faster into GP than we are today.

I am really looking for some advice from others that have experience the same issue at one point and what they did to improve the time it takes to integrate; we see significant increases in volume for a very short periods of time and need to figure out how GP can handle those peak periods without seeing what we call the backup and que of orders waiting in line to integrate.

We currently are running on GP2015.

Thank you,

Jeffrey

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (7)

Answers (0)

Almas Mahfooz 11,009 User Group Leader on at

Like (0)

Report

What issues you are having in using web services?

Was this reply helpful? Yes No
Jeffrey A 210 on at

Like (0)

Report

It really comes down to the speed at which we can integrate orders into GP. We find ourselves with a backed up que during the peak time which then also causes timeouts, etc...

I am essentially trying to understand the fastest way to integrate sales orders.

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

It may be worth looking at eConnect over Web Services to see if it is more efficient for the sales orders you're integrating into Dynamics GP and resulting in a backed up queue during peak times, causing timeouts.

Another option(s) you can potentially look at is:

--Schedule the integrations to not run during peak hours, instead running them during off-business hours and/or maybe when users are at lunch, i.e. a slower part of the day.

--If the sales orders contain a large volume of total orders and/or number of items contained per order, in each integration run, you may look at breaking the integrations into smaller chunks, so, for example, instead of sending through 1000 sales orders in one shot, have it do 4 runs of 250 orders each, to see if that goes through more smoothly and not get backed up so much.

--Make sure users aren't posting in Dynamics GP the same time the integrations are being run, as the posting process sometimes locks several tables the integrations may also need, thus causing delays.

That being said, depending on the integration code being passed through Web Services to create the sales orders, you may already be using eConnect procedures to do so.

Let us know if you have any questions.

Thanks

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report

I'm curious as to the volumes of sales transactions you are dealing with, per hour min at peak times?

I would expect eConnect to work for you assuming SQL server has been maintained well.

Tim

Was this reply helpful? Yes No
Jeffrey A 210 on at

Like (0)

Report

Hi Tim - sorry for the delay on this as its been a while....

When at peak, we are trying to integrate 8500 orders per day. During peak hours of a 3 hour period, we are looking at 2,000-3,000 orders to integrate. Our current setup is just not handling that; we are seeing an hour plus back up in que trying to come in.

We have 6-8 simultaneous processes running at the same time to help with the flow but that just isn't working.

I am thinking that GP just cannot handle that volume in the timeframe or that web services is inadequate too but after all the digging I have done, I don't think econnect would be sufficient either.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (0)

Report

I'm not sure I'd have anything more that I could give, as you may just be running into a limitation of the application in general.

Having 3-5 Web Services processes running really isn't helping, as it is all going to the same SQL Server instance/database, thus that could be causing a bottleneck to occur.

The same could be said for using eConnect procedures outside of Web Services, the procedures that eConnect use are still going to be calling the same tables and inserting/updating, pretty much as Web Services is doing, thus using the same SQL instance and databases.

I'm not sure if anyone on these forums has more practical information they could share, with experience of a similar issue.......

I do know we have seen bottleneck type issues like this, with high volume of integrations which the 8500+ orders a day/13,000 to 16,0000 lines would definitely fall under.

The recommendation is usually eConnect, as that is calling straight stored procedures, but again, I don't know if it would be able to handle the volume for the same reasoning mentioned above.

Thanks

Was this reply helpful? Yes No
Jeffrey A 210 on at

Like (0)

Report

Thank you very much for your reply! Huge help.

Do you know if there is someone that I can connect with regarding seeing these bottleneck type issues before? We have a lot invested in GP and would like to know anything I can from anyone who has been part of these bottlenecks to find out what ended up happening…..

Thank you!

Was this reply helpful? Yes No