2009 Feb 11 2:29 PM
Hi,
i need to update a database table (Z) and i have to free the resource at once to not produce a deadlock situatiuon. On the other hand, i'm not allowed to do a normal commit, because this will commit all open resources without the application developper notice which may lead to unpredictable results.
Any ideas on how to archive that? First i thought shared memory might be solution but this is not really for built for many updates.
I'm open for every suggestion, sending a "message" to another report or starting threads or whatever.
Hi,
i need to update a database table (Z) and i have to free the resource at once to not produce a deadlock situatiuon. On the other hand, i'm not allowed to do a normal commit, because this will commit all open resources without the application developper notice which may lead to unpredictable results.
Any ideas on how to archive that? First i thought shared memory might be solution but this is not really for built for many updates.
I'm open for every suggestion, sending a "message" to another report or starting threads or whatever.
2009 Feb 11 3:08 PM
What about function module with an update using attribute 'Coll. run' (collective run). then start via program RSM13005
PS This option is used SAP internal only (special form of V2 update, asynchronously)
May be this helpful to you.
a®
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |