Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

.NET Connector XML naming conflict problem

The error I am getting seems to be a similar type to the error patched in OSS Note 506603 ( I have installed this patch already, as I was having XML naming conflict problems ). After installing the patch there are still some naming problems.

I create a proxy with three methods:

Bapi_Alm_Notif_Create

Bapi_Alm_Notif_Save

Bapi_Transaction_Commit

I create the proxy using:

SAPProxy1 proxy = new SAPProxy1(connectionString);

and I get the following error ( due to a naming conflict )

System.InvalidOperationException: Method SAPClient.CommitWork can not be reflected. ---> System.InvalidOperationException: 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.

NOTE: I can workaround this issue by changing the following lines in the SAPProxy1.cs file ( adding _RENAMED)

RequestElementName = "BAPI_TRANSACTION_COMMIT_RENAMED",

ResponseNamespace = "urn:sap-com:document:sap:rfc:functions",

ResponseElementName = "BAPI_TRANSACTION_COMMIT.Response_RENAMED")]

Former Member
replied

Let me just mention that you shouldn't add BAPI_TRANSACTION_COMMIT to your poxy but use the builtin CommitWork() instead. That the builtin version doesn't have the Wait parameter is by intention (see the corresponding discussions).

The workarround mentioned only works for RFC and not for Soap.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question