Skip to Content

PI service - backend server proxy drops 1 element from XML but SPROXY test does provide element

We have a SAP ECC system (PI_BASIS 731) that has an ABAP server proxy implemented.

In development all works fine.
In UAT the service seems to drop 1 element from the XML response message.
When I test the proxy in the backend (SPROXY - test proxy) then that same backend does provide the full XML including the element that is dropped when making a normal call.

We have tried to transport the proxy again from development and do a regenerate in UAT.
Neither of them seem to resolve the issue.
A check proxy also reports an all OK.

Any tips on how we can correct the situation ?
Can somebody explain me where this element can be lost ?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Nov 10, 2016 at 03:06 AM


    Make sure you transported the proxy objects and repository objects to UAT system. I think check the repository objects in PIQ which is pointing to UAT contain the latest objects with the field missing?



    Add comment
    10|10000 characters needed characters exceeded

  • Nov 10, 2016 at 06:54 AM


    I checked the message definitions (PI repository) between Dvlp and UAT and they are the same.
    UAT seems to have the complete message definition.
    When executing SPROXY test then the complete message is generated in UAT. But when we make the same call (same data) using SOAPUI -> PI -> Backend then the XML response generated in the Backend seems to be missing an element.
    We notice the missing element in the Backend (SXI_MONITOR).
    I also looked at the ABAP/XML transformation programs but they seem OK and are mentioning the field in question. Besides the proxy test generates a correct XML.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 10, 2016 at 12:27 PM

    Hello Sammy,

    Can you check the XML in the receiver channel of SAP PI whether that field is present.

    If not it could be some issue of mapping or cache.

    Add comment
    10|10000 characters needed characters exceeded

    • The XML definition is OK in PI (repository).

      The missing field we can already notice in the Backend system (using SXI_MONITOR).
      So the response by the Backend is already missing the field in question before we arrive in SAP PI and any mapping that happens there.