ABAP proxy error after system upgrade PI 7.11 to 7.3

[Former Member]

Dear,

We recently upgraded both our SAP PI and SAP BW systems. SAP PI 7.11 -> 7.3 SPS05 and SAP BW 3.5 to BI 7.3 SPS06.

Currently we face a problem with provider ABAP proxies. Consumer proxies are working fine.
The problem we have can be seen in SXMB_MONI: within the call adapter
step, this error is faced: "ABAP">INTERFACE_SIGNATURE_ERROR.

Details: Information about the method parameters is missing for the interface.

Knowledgde Base Article 1714297 was checked, but did not offer a solution.

Checking the proxy on the backend system results in this message: Proxy consistent.

Also, various SCN threads were consulted and proxies were regenerated and reactivated several times.

Any ideas?

Thank you.

[Former Member · Accepted solution]

Hi Dimitri...

We are facing the same problem for one of ABAP proxy code. Could you please let know in detail about the issue resolution you had done to your code ?

Thanks in advance.

Regards,

Srivatsan

[Former Member · Accepted solution]

Hi Srivatsan,

There seems to be some differences between NetWeaver 7.0 and NetWeaver 7.3, Especially for ABAP proxies, more checks are performed in the background and data is checked when entering the backend system.

We had to enhance the coding used in the section were the XML output is created.

BEFORE

    msgtyp = odocument->create_simple_element(
                            name = '<MessageType_name>'
                            parent = odocument ).

AFTER

    msgtyp = odocument->create_simple_element(

              name = '<MessageType_name>'

                           namespace = 'n0'

                            parent = odocument ).

    rc = iparser->parse( ).

    rc = msgtyp->set_attribute( name  = 'xmlns:n0'
                                       value = '<Namespace_name>' ).

Bottom line is that you need to specifiy and parse the namespace.

To be sure about the correct values for these parameters, go to the backend system, take SPROXY

and test the class. A template will be generated where test data can be filled in. Within that template, the expected header data is clearly displayed.

I hope this clarifies.

Kind regards,

Dimitri

PS: make sure you configured the specific RFC destination SAP_PROXY_ESR. More information can be found in Knowledge Base article 1759641.

[Former Member]

[ UPDATE ]

In the meantime I found out the problem is situated within the data that is pushed to the backend system. We need to provide a namespace to the message.

This code is currently used:

    msgtyp = odocument->create_simple_element(
                            name = 'n0:<MESSAGE_TYPE> xmlns:n0="<NAMESPACE>l"'
                            parent = odocument ).

But on the backend system, an error occurs and I think that not everuthing can be put in variable name.

I played around with the parameters in method CREATE_SIMPLE_ELEMENT, but unsuccessful.

Any advice on pushing the data within the correct parameters?

Thanks a lot.

[Former Member]

Problem was solved and was residing within the ABAP code.

[MichalKrawczyk]

Hi,

have a look at my blog:

http://scn.sap.com/community/pi-and-soa-middleware/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-...

maybe you have a similar issue - you can see it in the SPROXY

Regards,

Michal Krawczyk

[Former Member]

Hi Michal,

We have 1 scenario where provider ABAP proxies do work. I checked that

class on the backend system and it seems that the method is

EXECUTE_ASYNCHRONOUS, like in the old version.

When I check the method classes were we have a problem, this is the

Service Interface name, as I expected in the new version.

How can this be that we have 2 different kinds of methods on 1 and the

same system?

Regenerating the proxies provide both old and new method names. Very strange.

Kind regards,

Dimitri