Re: EM TM process

Dipak,

TM works the same as ECC in this instance. qRFC is the traditional method used to call the 2 BAPIs that ultimately create the EH and Event messages in EM.

To give you a quick rundown on how these 2 queues work and some tips here goes...

SMQ1 - Outbound qRFC queue

1. This is where you'll find the BAPI calls to create EH and EVM
2. Configure using SMQS
   1. For Performance issues consider increasing Max connections
   2. Configure the Queue name extractor to leverage multiple queues in SMQ1 so that you can leverage the Max connections setting. i.e. If you execute a bulk transaction what you would like to see is 15-20 queues working in parallel on TM and in SAP EM, 15-20 dialog process processing the BAPI calls.
3. Performance is also affected by SAP EM processing so ensure that your Rule Set is very well structured
   1. Make use of True rules in the rule set to avoid unnecessary logic being performed
   2. Turn off task tracking and the application log
   3. Don't store history on the EH
   4. Ensure your rule set is in the sequence of most frequent events at the top and less frequent at the bottom
4. Remember that if this queue gets stuck you can just delete the entry as the corresponding BAPI will not be called in EM and the data won't exist there

SMQ2 - Inbound qRFC queue

1. This queue is used to update the table in TM called /SAPTRX/AOTREF with the EH GUID
   1. We often use this table in our relevance functions. i.e. If there is an entry already there then my object must be relevant, if not then it isn't. Using this mechanism means that you only need to do an expensive relevance check on creation and after that it's simple
   2. You can turn this entry off if you wish, in customizing
   3. Not critical for performance

Hope that helps.

Kevin