Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

DocID's get switched in SOP40200

(0) ShareShare
ReportReport
Posted on by 5

Has anyone ever experienced the 'SOPNUMBE' getting changed in the SOP40200 table when transferring to an Invoice?  The SOP40200 table looks like this before hand:

DOCID SOPTYPE SOPNUMBE
STDINV          3 STDINV0278085        
STDBK           5 STDBK0000001         
STDORD          2 STDORD825443         
RENORD          2 RENORD2297505        
RENEWAL         1 RENI701527           
STDRET          4 STDRET0026724        
STDORDW         2 STDORDW825424        
RTVORD          2 RTVORD825400         
TRNORD          2 TRNORD825352         
TRNORDW         2 TRNORDW791873        

Then somehow behind the scenes the table gets changed to:

DOCID SOPTYPE SOPNUMBE
STDINV          3 RENORD2297438        
STDBK           5 STDBK0000001         
STDORD          2 STDORD825443         
RENORD          2 RENORD2297430        
RENEWAL         1 RENI701527           
STDRET          4 STDRET0026722        
STDORDW         2 STDORDW825424        
RTVORD          2 RTVORD825400         
TRNORD          2 TRNORD825352         
TRNORDW         2 TRNORDW791873        

This has happened 3 times so far this year.  Once early March, then twice in the last week.  I've added a trigger to try and capture when this is happening and by what process, but it hasn't happened since I put it in place.

Has anyone ever seen this before?

Thanks! 

Categories:
  • Victoria Yudin Profile Picture
    Victoria Yudin 22,766 on at
    RE: DocID's get switched in SOP40200

    Jason,

    I have only seen this when there are customizations in place. Never on an out-of-the-box GP installation. Do you have any customizations/modifications around your SOP transactions? If so, that would be the first place to look.

    Unfortunately, when it's sporadic and you can't force it to happen, it's extremely difficult to track down. We've tried similar things in the past with triggers, but even knowing what user caused it to happen and when, there was nothing we were able to figure out specifically as to what they did or what they could do differently.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,494 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,309 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans