The XML element named 'BAPI_TRANSACTION_COMMIT' from namespace 'urn:sap-...

[Former Member]

I got the error message below when added "BAPI_TRANSACTION_COMMIT" to proxy in ASP.NET with SAP .NET Connector 2.0

The XML element named 'BAPI_TRANSACTION_COMMIT' from namespace 'urn:sap-com:document:sap:rfc:functions' references a method and a type. Change the method's message name using WebMethodAttribute or change the type's root element using the XmlRootAttribute.

[reiner_hille-doering]

Do not add BAPI_TRANSACTION_COMMIT to your proxy, as it already exists as built-in method "CommitWork". Use this one instead.

[Former Member]

I need "COMMIT WORK AND WAIT"

[reiner_hille-doering]

Please see my response at the end of thread

[Former Member]

Hello Reiner,

When calling CommitWork() without having RFC permissions on the correct function group CommitWork() seemed to report no error whereas BAPI_TRANSACTION_COMMIT threw up an exception violation.

There is no documentaiton on what CommitWork() returns (true = error or false = error?)

Where can I go to read up on this behaviour, also is there any sort of guide or examples that I can reference to learn more about how errors are raised (or not raised) as well as to read more about CreateAsyncs, CreateQRFC, CreateTRFC, ProxyType and MAPBapiExceptions.

Does the version 1.0 document still apply?

[reiner_hille-doering]

Sorry for the missing documentation thing: Yes: CommitWork() catches the exception internally and transforms it to the boolean return, so "false" means error.

The rest of what you ask should be nicely documented. The docu is contained as VS integrated help, both reference and overview.