Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Odd issue when importing PO's using eConnect

Posted on by 75,730

I have a routine that imports PO's via eConnect. It works fine 99% of the time. Every now and then one comes across reporting this error.

9184 Document is currently being edited by another user.

How can this be possible since I am importing a new PO?

Categories:
  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Odd issue when importing PO's using eConnect

    This happens totally randomly and the import process does POs in mass. Less than 0.1% of the time this happens. Trying to catch this will be very difficult.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at
    RE: Odd issue when importing PO's using eConnect

    could you run a SQL trace while running the import process to try figure out what happens right before the error comes up ?

    www.eonesolutions.com/.../

    dynamicsgpland.blogspot.com/.../trace-database-triggers-using-sql.html

    Are you using straight eConnect calls or the MSMQ services ?

    community.dynamics.com/.../using-the-econnect-incoming-and-outgoing-services-with-msmq

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Odd issue when importing PO's using eConnect

    The PO numbers come from a database in a linked server. There is no way that a PO can exist in GP and in this other database until they are brought over to GP. All POs start in this external database. In eConnect all import routines are set to update if they already exist in GP so this makes this even stranger.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at
    RE: Odd issue when importing PO's using eConnect

    Richard,

    You say "PO Number is supplied from an external database".. what do you mean by this ?

    Are you using any lookup to grab the next PO number or does the numbering differ completely from the setup in GP ?

    If a lookup is used with the eConnect SP's to grab the next number, it could be conflicting with a new PO that is just created by another user as suggested by Josh..

    Otherwise, I'd double check some of the PM table to check if there isn't already the same document number used in the past.

    PS: what tools are used to process the import to eConnect ?

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Odd issue when importing PO's using eConnect

    The PO number is supplied from an external database to eConnect so that would not be what is causing this.

  • Suggested answer
    Josh Page Profile Picture
    Josh Page on at
    RE: Odd issue when importing PO's using eConnect

    When you are running the integration, are there users in GP?

    It's possible that if EConnect and a user in the PO entry window "grab" the same next PO number at about the same time you could see that error message.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans