You’re offline. This is a read only version of the page.
The company I am currently working in is has Sales Order Processing Setup configured to Track Voided Transactions in History.
A user has reported a voided order still showing up on an open order report. When I investigated the order I noticed it still resides in the SOP10100 and SOP10200 tables. The VOIDSTTS column is set to 1 and it has a value for TRXSORCE.
I have tried running check links for the sales module and Reconcile - Remove Sales Documents (Remove Completed Documents) for the individual order number. The order still has not moved to history.
Any suggestions on what I can try or investigate next?
*This post is locked for comments
Great News Steve,
Don't forget to mark the question as answered, so it will benefit others in the future :-)
Just wanted to post here what I finally did in case anyone reading is interested. After running several tests in a test environment I ended up setting VOIDSTTS to 0 and TRXSORCE to <blank> in SOP10100. Next I deleted the entry for the same TRXSORCE value in the SOP30100. GP then allowed me to void the document through the client and it moved to history. I did notice the void journal did not pop up until I closed the window as described by Kirk earlier in this thread. I am pretty confident the inconsistency was cause by the original user who processed the void. I will be doing some further training to avoid this in the future.
WOW! Thank you Leslie, this is indeed a wonderful tool. I have found this value only exists in SOP10100 and SOP30100. I have also determined it is not allocating any quantity. I think it will be safe to continue with the plan to clear the VOIDSTTS and TRCSORCE columns using SQL then delete the order via GP.
steve,
When I run into things like this, the first thing I normally do is to search the entire database for the document string. I use a FREE tool called APEXSQL search. It's FABULOUS and FREE! By using this tool I can easily identify all of the tables including the document of question. I typically have to end up adjusting something in SQL and the APEX Search tool will give you a lot of confidence that there isn't some speck of data that will come by and bite you in the rear. If you do any SQL work, it's a must have for any consultant.
Kind regards,
Leslie
Hi Steve
If you have inventory, and this order had inventory on it, you may need to run reconcile against your inventory. Check to see if anything is "allocated" and if so, if it is a valid record.
Cheers
Heather
I have restored to a test company and set the VOIDSTTS field back to 0. When I attempt to pull up the sales transaction, it says "This document has been posted". But it cannot be found in the Posted Transactions window. I decided to try and also set the TRXSORCE to <blank>. Once I did this I was able to pull up the sales transaction entry and delete the record. The only thing that concerns me is where that TRXSORCE may be referenced. If the order never truly posted anywhere then the number may not show up anywhere. I guess check links would catch it if it were a problem.
Have you tried to set the VOIDSTTS field value back to 0 and try to delete the Sales Order from within GP..
As you said, Checklinks and reconcile didn't produce any significant result, so try that.
Take a full backup first of your company DB and set the flag back to 0.
Then see if you can delete in GP or Void it another time..
I've seen cases in 2013 where a posted SOP document would not set the void status, tough it was voided properly in GP, and showing as such in the inquiry window, but in the table, the value would still be 0.
It only exists in the SOP10100 and the SOP10200. No entries found in any of the other tables you have listed in your script. At this point having the log of it in history isn't even that important. The order is tiny in relation to most our other sales. I just need to get it out of the work tables. What are the potential ramifications of just deleting the 1 record each of the SOP tables?
Hi Steven,
Have you checked if the voided SO shows up in the historical tables too ? that would be SOP30200 & SOP30300..
I use the following script to check the data against a specific SOP document
use XYZ
declare @inv as varchar (21)
declare @cust as varchar (15)
set @inv = 'INV000872'
set @cust = '%'
print @inv
select sopnumbe, custnmbr, cstponbr, docdate, voidstts,prstadcd, * from sop10100
where sopnumbe like @inv and custnmbr like @cust --and voidstts = 0
select * from sop10200
where sopnumbe like @inv --and custnmbr like @cust
select sopnumbe, custnmbr, cstponbr, docdate, voidstts,prstadcd,* from sop30200
where sopnumbe like @inv and custnmbr like @cust --and voidstts = 0
select * from sop30300
where sopnumbe like @inv --and custnmbr like @cust
select * from sop10106
where sopnumbe like @inv
select * from sop10107
where sopnumbe like @inv
Unfortunately this did not work. We opened and closed the window and no journal printed. We also tried to pull up the order but it just says it is voided.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (