I looked into using this adapter a few years ago, and back then, transactions were not supported. The reason given was that “the adapter uses the partner WSDL and the APIs support only single sObject.” In simpler words, the adapter talks to SalesForce.com via web service calls and each web service call only acts on a single object/table. Once a call is done, it’s done. It has no relationship to future calls.
I’m not sure if things have changed since then. If they haven’t, a common work-around for an issue like this is to insert into the detail table first and then the header. This is done because the data consumers normally query the header table first so by the time the header record is inserted, you already know the detail records succeeded. You will still have the issue that if, for example, the header record fails, you will want to rollback the detail changes. Unfortunately, in that case, your only choice may be to perform a delete (assuming you did an insert earlier) and hope it works.
#Adapters-and-E-Standards#webMethods#Integration-Server-and-ESB