Skip to Content
avatar image
Former Member

Peculiar issue in Event message processing

Hi Experts,

We are facing a weird issue during the event message processing.

We have some multiple 214s coming an expected event codes reported by the carrier.

Only one of the message is processed against the expected event where as other events are registered against the event handler

as unexpected event.

So basically this is causing 2 problems:

  1. As per the expected event profile, the expected event has the "reprocessing flag" on. Then why are the multiple messages registered as unexpected event.
  2. There is a rule set activity to update TM with execution info data. This is creating an inbound queue which is failing because there is no TOR_ID in the EM structure

For both the above problems, we think that the event message is not reading the event handler data for some reason.

Any tips ?

Thanks,

Deb

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 20, 2015 at 10:58 PM

    Some context:

    This is happening very inconsistently. We faced the issue in Production and could now replicate the issue in test.

    This is happening when some event messages were sent before the event handler was created. Meaning if there is some delay in the event handler creation but messages were received before that.

    Thanks.,

    Deb

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Deb,

      this sounds strange.

      You could check here in debugger:

      class /SAPTRX/CL_EXPEV_PROCESSOR method PROCESS_MSG.

      Here are all the checks done to determine if it is expected or unexpected.

      Check here where it went wrong to find the EE.

      Best regards,

      Steffen