web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Sales Order Integration and Next Sales Order Number

(0) ShareShare
ReportReport
Posted on by 75,854 Moderator

We just had situation with a sales order integration.  There were 5 sales orders to integrate. Prior to the start of the integration the next sales order number was 075050. The integration started and errored on the 4th sales order. The error was caused by an invalid address ID. However, other users were still entering sales orders.Sales orders 075050,075051,075052 are now in the system from the integration. A user goes to enter a new order and gets sales order number 075050, not 075053. If you look at sales order document setup, the next sales order number is 075053. I tested this with several users and the result was the same. I then had everyone exit GP, restarted the SQL service and users then went back to generate new sales orders and now they all started getting the correct sales order numbers.Has anyone else ever experiened this and, if so, how did correct the situation?

*This post is locked for comments

  • Tim Foster Profile Picture
    8,515 on at

    How were you integrating?  Integration Manager, eConnect, Macro or direct SQL?

  • Richard Wheeler Profile Picture
    75,854 Moderator on at

    Integration Manager. We see this occur 2-3 per year. We integrate 3-4 times per day. It just happened that yesterday there was this issue with an address code.

  • L Vail Profile Picture
    65,271 on at

    Richard,

    I too have seen this happen. It happens so rarely that I've never tried tracking it down. Are you using the standard adapter or the eConnect adapter?

    Kind regards,

    Leslie

  • Richard Wheeler Profile Picture
    75,854 Moderator on at

    Leslie, I am using the standard adapter. When this happens it just locks up the order process and the client simply wants to get back to work. There is no time to track it down. It must be some table or record lock issue as simply restarting SQL fixes it every time.

  • L Vail Profile Picture
    65,271 on at

    Richard,

    That's odd, you'd think the macro would act just like a user. Another mystery. Like you, if it's quick to fix and doesn't happen very often, I just fix it and move on :)

    Kind regards,

    Leslie

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans