Skip to Content

User defined message search criteria on ECC

Hi Experts,

I have configured UDMS-user defined message search under ECC (for message search in MONI) using T-code: SXMS_LMS_CONF and while defining extractors, I have selected both check boxes.

1. Extract during message processing

2. Extract with external Job

As per my knowledge, 1st option indexes all messages which are processed after we activate filters.

2nd option is used to index previous messages which are processed before defining filter.

For me 2nd option is working fine (I can search old messages which are indexed using a program:  SXMS_EXTRACT_MESSAGES).

But 1st option is not working. I have created filters yesterday and activated also, but couldn't able to trace today messages using user defined search.

Please help in this regard.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 01, 2014 at 01:53 PM

    Hi Experts,

    Could you please provide some input on above issue ....

    What I observed is ,selecting check box: "Extract during message processing" is not indexing currently processing messages.

    For achieving this, I have to schedule a job again with program name as: SXMS_EXTRACT_MESSAGES to index messages.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      From SAP Note.  1600078


      Most problems occur because you use the communication components or partners as the filter criteria in the filter even though you want the system to index only certain interfaces. In this situation, you must always set the components or partners to "*".
      If you specify components or partners, you must consider how indexing of messages runs technically. If indexing is called at runtime, the system executes it at the start of the Integration Engine and at the end of the Integration Engine; this means that the value that the components or partners have at this point is definitive. For example, if you have defined a receiving component, this is not set at the start of the Integration Engine (except in special cases) and this is why the filter does not select the message. It also has no effect at the end because the message contains the receiving interface after the mapping. If you call the test function of transaction SXMS_LMS_CONF, the filter is used on each individual persistent version of the message (the same process as when indexing via a job). If the message is made persistent directly before the mapping, the sender interface exists there and the receiving component or partner is set. Therefore, the filter described above would be active here. As a result, this function is better defined to check the XPath than the filter criteria.

      Check if you put  * in the receiver component.