on 02-09-2012 6:40 AM
Hi all,
I encountered this problem of a client of ours after updating MSSql 2008 where some of the PO details were missing and also affects the amount of the POs.
.
Although the document is still 'Open-Printed', but the printout details which was printed before was different compared to the PO details now. And I would think maybe because of the update we had yesterday.
What could possibly gone wrong with this problem?
Just wanna know why. 'Cause maybe I could get an idea on how to restore all the original PO details without restoring the database or editing further the PO.
Thanks ahead for the responses!
Hi,
What do you mean by after updating SQL? As you are aware the altering tables of SBO
may loss your SAP support.
More details please.
Thanks.
Clint
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Drei_FTconsultant,
If you have backup of Live Database before updating SQL then Uninstall SQL server and Reinstall upgraded version of SQL then restore your Live Database its very easy way to achive your task....
upgrading SQL with DB its compleceted....
Thanks,
Srujal Patel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please clarify for after updating MSSql 2008. Have you upgraded your SQL Server?
Thanks,
Gordon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
We updated the MSSQL 2008 from 10.0.1600 to 10.0.5500 for the reason that a server bug occurred. I found this solution on this forum. (http://forums.sdn.sap.com/thread.jspa?threadID=1881193)
Now after the update. The existing POs were now missing some details which was previously created. I checked their printouts which was prior to the update that all details are present.
We also haven't made any alterations on the details whatsoever even on the MSSQL.
So I wonder would the update of MSSQL really cause the missing details? Correct me if I'm wrong.
We could have done a test run for the update before applying the update to be safe. However, the issue needs to be resolved ASAP. Anyways, let me know your thoughts on this.
Thanks!
Hi,
Please follow the suggestion of Srujal Patel.
Try the following :
1. Leave the SQL server original version. Dont upgrade yet.
If already upgraded uninstall and restore original version.
2. Backup live database, then detach your database.
3. Upgrade your SQL Server.
4. After upgrading is done. Restore your live database.
5. Then test.
Thanks.
Clint
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.