Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Roy B on Aug 25 at 11:13 AM Hi Lou,
I have seen SAP lose data, but I agree with you that it is very rare. If you are using document number range buffering and the system crashes the numbers in the buffer get lost which can cause you problems with consecutive numbering. Therefore in Italy (and other countries where consecutive numbering is a legal requirement) it is recommended to turn buffering off. Also I did once see an incident where a system crashed in the middle of a posting, so we had a one-sided entry. We had to get SAP in to fix the tables in that case. But in all these cases we have not lost all trace of a posted document. Sometimes the system can be slow so it reports (say, in FB03) that a document number does not exist when it has not yet been updated. Usually logging off and on again gives it enough time to update and then the document appears normally, but all of the cases I have mentioned are seldom seen.
Rgds, Roy B.
| | | ---------------Original Message---------------
From: Louis Corato
Sent: Saturday, August 25, 2012 12:32 AM
Subject: Missing Vendor Line Item
The one thing you should know is that it's extremely rare (if ever) that SAP "loses" data. I've never seen it in 16 years of working in SAP. I've had users tell me SAP created a document and then lost it, only to realize an update failed. If that happens, the user gets a notice sent to their SAP inbox about it, which they usually ignore. I've never seen it actually drop data without any notice.
So look in the user's SAP office inbox for a possible update failure, and definitely ensure that the item was actually posted and not just parked.
- Lou |
| Reply to this email to post your response. __.____._ |   _.____.__ |
