‎2010 Jun 03 2:45 PM
what will happen when system crashes in middle of Bi session
and also in call ransaction please let me know
‎2010 Jun 03 2:59 PM
Hi,
For some theoritical knowledge about this there is a concept called check points in Relation database, you can go through that.
the bdc session method is always synchronous, so the process will get rolled back.
Im not sure about the asynchronous mode in call transaction.
Wait for experts opinion.
‎2010 Jun 03 2:59 PM
Hi,
For some theoritical knowledge about this there is a concept called check points in Relation database, you can go through that.
the bdc session method is always synchronous, so the process will get rolled back.
Im not sure about the asynchronous mode in call transaction.
Wait for experts opinion.
‎2010 Jun 03 4:41 PM
Farha, I dont know what is a "Bi" session.
But if the system crashes in between a BDC session, the effect will be similar to what will happen when a user is doing the transaction online.
When the transaction to which the BDC is done, does a commit action, the BDC will end. Before the commit if the system crashes then your BDC data will not be updated in the system. If the system crashes after the commit is completed, then your data will be updated.
Standard SAP transactions make updates in subroutines or functions "on update task". So, an update task is created. But the data is not updated in the system. You can see the update tasks in SM13. Once the transaction issues a "Commit" statement, all the update tasks are executed. If the system crashes during this process, the update tasks will show as failed in sm13. Basis or support team need to re-execute those tasks manually to complete the data update.
Salai.
‎2010 Jun 03 5:15 PM
Hi Sivaprakash,
What about the asynchronous mode in CTU method ?
Thanks,
Keshav