on 06-30-2008 1:53 PM
Hello guys,
I have just probed the new SBO_SP_PostTransactionNotice functionality which comes with SBO 2007A version (or SBO 2005 A EhP 2).
It is very useful, if you want to build advanced functionalities, for instance calling an external program which will add transactions in the system (using DI API or DI Server). This is not possible with SBO_SP_TransactionNotification as you will conflict with SBO inner work (system transaction which is not yet commited/rollbacked)
Unfortunately, I have noticed that it is not possible to run simple queries (SELECT) in SBO_SP_PostTransactionNotice as we can do with SBO_SP_TransactionNotice. This is a pity as this is so handy! I was wondering why is this forbidden (as I can't see how doing it could be a possible threat to the system).
Has anybody found a way around this limitation?
Regards,
Cyril
Dear Cyril,
The documentation regarding the SBO_SP_TransactionNotification procedure
can be found in the following link:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e991e2b9-0901-0010-0395-ef5268b00aaf
It is also possible to download documentation regarding the DI Event
Service, a .NET library that leverages on SBO_SP_TN and provides an
easier and safer way of getting notified on changes in the Database. It
can be found in:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/53cefa6a-0a01-0010-cd8e-e7c189cb6519
Regards
Arshdeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
96 | |
10 | |
9 | |
5 | |
3 | |
3 | |
3 | |
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.