You’re offline. This is a read only version of the page.
455
An inquiry on a document came up with no results, but, I have the printed document. I am seeing the data in the SQL database.
*This post is locked for comments
If the sales records exist in the SOP30200 and SOP30300 tables then when you try to enter the same invoice number back into Sales Transaction entry you will get a message stating that the invoice already exists in history and will not be able to enter it. Can you find this document in the RM Key Master table? (RM00400). There is a broken link here somewhere and you need to find the missing link.
Rosemary, do you have any 3rd party products that integrate with SOP? As you note, it is unusual to find a corrupt record that has been printed.
Are you able to pull the document up in Receivables Posted Transaction Maintenance?
The check links was run, but access to the document number is still not avaialble, I would probably need to re-enter. I can understand a document beng locked if a session ends abnormally, but this was a document which was printed.
Thanks very much all the input.
Check Links does exactly as it name implies. It will look for any broken links between related tables. Sometimes it fixes things and some times it does not. It all depends on what the underlying problem is. Make sure you do a backup first as it can delete records.
I have not done the Check Links as yet, would the procedure recover the document? Is this guaranteed?
Hi Rosemary,
You mentioned previously that you could see the transaction in SQL, where? Do you have access to the SearchOnAllDB stored procedure so you can search for it across the database or are you just checking the SOP tables. Perhaps you can find it in the smartlists and let us know which one? If you can find it in a smartlist try clicking it to see if you can open it in an enquiry screen. If it errors, then we know if you have a problem.
Rosemary -
The most common reason for an 'incomplete' or orphaned record would probably be related to connectivity - a power surge or anything that interrupts the connection between the workstation and the server. Great Plains is a 'fat' client - each workstation that has GP installed has the actual 'code' installed on it. Thus - lots of connection occurs between SQL Server and GP Workstation. This causes incomplete processes from time to time.
Microsoft acknolwedges this and builds in data integrity tools.
In your case - have you tried Check Links? The Check Links is a data integrity utility that looks for data inconsistencies and tries to correct them. Check Links is a data altering process - it should be done only after a complete database backup and done while system access is limited or null.
I just recently had to delete (via SQL) 2 sales records for a client of mine in their database. Both records were missing the Customer ID and therefore, were considered 'orphan' or bad records.
Hope this helps...........
yes
You sure the transaction is not a Receivables invoice or been created through Invoicing accidently?
The document is historical, but, what can cause an orphaned record?
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,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (