on 09-05-2007 6:55 PM
To all that have made changes to the SBO_SP_TransactionNotification Stored Procedure, please be aware the the object-code is now nvarchar(20), [Actually been that since SBO2004, but SAP have made changes that get errors to surface].
Problem is that Addons using User Defined Objects can't save their data in SBO2007 and later versions of 2005 if there are incorrect code in the SBO_SP_TransactionNotification (Not taking care of that the code might be alphanumeric)
Here is a PDF describing the problem (written because many people tend to get the error at the moment because of the SAP change):
http://www.b1up.net/pdf/The%20SBO_SP_TransactionNotification%20Problem.pdf
Thanks a lot, Rasmus, for sharing the description of the problem - and the solution with the community!
Regards,
Frank
PS: I hope you don't mind that I will make this thread "sticky" - i.e. appear on the first page always - for a week or so?!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
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.