2006 Aug 16 6:24 PM
2006 Aug 16 6:26 PM
It's not possible to rollback after successful call transaction of SAP standard transaction. Because the transaction issues a commit work.
If this requirement is for executing the BDC in test mode, do not use save ok_code in the bdc table, instead exit ok_code and check the message table for any errors.
Regards
Sridhar
Message was edited by: Sridhar K
how can we rollback work after a call transaction?
2006 Aug 16 6:26 PM
It's not possible to rollback after successful call transaction of SAP standard transaction. Because the transaction issues a commit work.
If this requirement is for executing the BDC in test mode, do not use save ok_code in the bdc table, instead exit ok_code and check the message table for any errors.
Regards
Sridhar
Message was edited by: Sridhar K
2006 Aug 16 6:31 PM
KE,
Get out of the BDC business. SAP has.
Use BAPIs.
It eliminates upgrade issues as screens change from version to version.
2006 Aug 16 6:32 PM
i understand that the call transaction does the commit implicitly. so there is no way for the roll back. I was looking for a work around to check the file for errors in test mode. So if i have to do a test run on the input file then i need to do checks explicitly by coding. Just wanted to confirm this. As with some bapi's we can do the check and rollback - its not possible after call transaction in BDC?
2006 Aug 16 6:38 PM
There is no way to complete your needs with BDC.
Bear in mind as well, that when you run in test mode and it passes or fails... they might not be the case when you actually run the same data set "live."
2006 Aug 16 6:33 PM
Hi John our system does not have a BAPI for rebates as i see in the forum that a BAPI_AGREEMENTS is available but could not find a bapi in out system.
2006 Aug 16 6:41 PM
2006 Aug 16 6:46 PM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |