avatar image
Former Member

Transformation interface modified at runtime.

Dear All,

Very lot error with text:

Error in the SAP kernel

The current ABAP program "CL_SXMLP_DATA_ST======

  terminated because the ABAP

processor detected a system error.

Transformation "/1SAI/SASB161BBECC42B3BF61048=XT" was modified at program

  runtime. This can cause

inconsistencies.

Program "/1SAI/SASB161BBECC42B3BF61048=XT" uses interface version

  20150622151939.

Program "/1SAI/TASF5FC3E4D51137A5EFC42=XT" uses interface version

  20150622151529.

Internal mode was started at 20150622151825.

Transformation of always different.

Reset WSIL caсhe not help.


Help to solve.

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jun 22, 2015 at 12:26 PM

    Hi Alex,

    Can you please let us know about the error by providing screen shots for better understanding of the issue.

    Also, please make sure you are asking in the right forum.. 🤪

    Regards

    Vishnu

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Alex,

      The dump screen shot which you have shared, is this from ECC system?

      If yes, then this comes under ABAP forum.

      And this forum is for SAP PI middle ware related issues/queries. Please post your query related to SAP XI/PI.

      Can you please post your query in ABAP forum for helpful replies.. 🤪

      ABAP Development

      Regards

      Vishnu

  • avatar image
    Former Member
    Jun 22, 2015 at 06:24 PM

    Hi Alex,

    From the given inputs, what I can say is, there is involvement of an XSLT mapping which is trying to deserialize the input XML structure.

    This means that the time stamp at which the XML structure got created is getting removed from the message header.

    This is the work of the XSLT mapping here.

    Now, from the error log, it seems that as the source XML message (payload) arrived, the XSLT mapping which takes the help of proxy program, was not able to deserialize(remove timestamp) the payload. The reason seems to be that due to some unknown reason the proxy program ran a bit late.

    In that case, note that here correct deserialization depends upon the sync in the timestamp at which the XML payload arrives and the timestamp at which the proxy program runs.

    So, in my opinion, it is a temporary issue. Please resend the message and check if the error still persists.

    Regards,

    Souvik

    Add comment
    10|10000 characters needed characters exceeded

Skip to Content