Announcements
I am revisiting an old issue for one of our clients that we have never been able to capture but they claim happens. They are sitting on an SOP order and they go and generate a POP off that order. They claim, occasionally, that the quantity on the PO line will be different than the quantity on the SO line. Every time I run a DEXSQL.LOG this never happens so I cannot catch it happening. Has anyone else ever seen this type of behavior?
Hi Richard,
I have not personally seen this as an issue, but you could potentially try restoring a test company with a copy of live from the day before 'IF' the SO was in the system still that day and attempt to recreate the issue on the same sales order. The SOP60100 (SOP to POP) link table should show you the order number, PO number and the quantities on the PO that was generated, so you could see if the amounts line up there.
select * from SOP60100 where SOPNUMBE = 'XXXXXX'
There is a chance that they didn't have the correct amount on back order when they created the PO, and someone later changed the quantity on the Sales Order after the fact too.
I am guessing that it is user error that is accidentally occurring occasionally if they cannot reproduce the issue. If the issue is with code or bad data, they will be able to reproduce it at some point.
Thanks!
Isaac Olson
Microsoft Support
Isaac, thanks for the reply. This has been going on for over 10 years. I have never been able to catch and when I am there it never does this. I have shown them again how to start a DEXSQL.LOG and if need be I will turn debugging on. What they tell me they do when this happens is they first break the commitment, then delete the SOP line and reinstate the commitment. I have also told them to stop processing the next time this happens and contact me. I will remote over and take a look. My guess is that call will never come.
I am not sure that a DEXSQL.log will actually give us the answer for sure anyways. I am more curious on whether there is a bad or out of the ordinary data condition on the Sales Order that it was generated from in the first place. If they really want it fixed, I would hope that they would be willing to let you look at the data on an example before they delete the commitment, or hopefully the sales order was one that was in the system the day before and was not freshly keyed that same day as the transfer so that you could restore a test company with a copy of live that contains that exact order and try to recreate the issue.
If anyone else in the community has any ideas or has also seen this specific scenario occur frequently in their environment, hopefully they will chime in as well. Otherwise it is difficult to rule out human error, which does definitely does happen.
"How to set up a test company that has a copy of live company data ":
support.microsoft.com/.../871973
Thanks Isaac, I will plead with them to stop processing the moment this happens again and allow me to take a look.
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.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Abhilash Warrier 461 Super User 2026 Season 1
André Arnaud de Cal... 428 Super User 2026 Season 1
Subra 428
