Skip to Content
avatar image
Former Member

Monitoring events

Hi,

We are working on a scenario with TM-EM integration in place. Now landscape is that carriers will report gate in and gate out events from legacy system and then through the middleware , RFC call will be made and update events in TM. Now from monitoring perspective, in case there is any issue in the interface whereby legacy system confirmed sending out events but due to certain conditions messages did not reach TM system.

Now I have 2 questions since PI is not used:

a) How to reprocess the  failed messages send from legacy system to SAP.

b) Secondly in the middleware platform if we add a status code  as error then is there some way where using this error code, there can be some mapping with EVm messages in EM environment so that in SAP  SYSTEM, we can understand the failure of messages .

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 31, 2015 at 08:10 PM

    Hi Indraneel,

    a) How to reprocess the failed messages send from legacy system to SAP.

    You can process through SAP EM WebUI manually (copy all data from failed messages) which are failed from legacy system.  However, it is little extra effort for users or support team to process each and every time.

    If Middleware sends then you can reprocess from their system as they have monitoring tool where they can edit and resent to SAP EM/SAP TM system.  We were performing same exercise in our previous project where we connected through 3 PL (non SAP TM).

    b) Secondly in the middleware platform if we add a status code  as error then is there some way where using this error code, there can be some mapping with EVm messages in EM environment so that in SAP  SYSTEM, we can understand the failure of messages .


    We have SAP EM standard Tcode /n/SAPTRX/ER_MS_LIST, where you can see inbound event message cancel or error or warning etc.

    You can map middleware new status code to message class /SAPTRX/MSIO and add the status code to identify the error in system. However, you have to enhance BADI Interface /SAPTRX/IF_EX_BADI_MESSAGE~CHECK_MESSAGE for errors on specific codes.  This is a little bit tedious job but it can be achievable.

    Regards


    GGOPIII

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 30, 2015 at 08:07 AM

    Hi Indraneel,

    You mean to say that EM is not receiving the event info ( no RFC call ) at all due to issues in Middleware?

    a) If it is the case, then there is not much we can do here. Source system or probably middleware has to have capability to resend the missing events to EM.

    b) Even if you add a error/status code in middleware, if there is no RFC call, it will help in your monitoring in middleware but not in EM system.

    Best to explore ways to re-send the events from source itself based on middleware error codes.

    Thanks,

    Vishnu

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Indraneel,

      Request Middleware team that they can configure email id or support id to trigger email specific to SAP EM/TM event messages failures. This can be achievable in Middleware.

      Regards


      GGOPII