on ‎2014 Jan 17 2:47 PM
Hi All,
I created 2 message processing rules. One with processing type as Transaction and another as category. Message Name was marked as * in both the cases. < as shown >
When the input was received in MII, message monitor showed that the messages were hitting the rule with category definition. Does it gets any advantage/preference over transaction processing type?
,
Same is seen in below scenario as well:
MessageName is same in both rules below. But the input always seems to hit the categorized rule.
Note: SAP MII 14.0
Any thoughts..
Have a nice day!!
Thanks/Regards
Ruchir
Request clarification before answering.
Hi Ruchir,
I tried your scenario and found that this is how MII behaves.
If there are 2 messages with same name and same message type and with processing type as category and other one as transaction, then the one with 'Category' processing type will always get processed and not the transaction one.
You will find that if you delete the message with type 'category', then the one with 'transaction' will start getting executed.
Another point to consider is that this is only because you have SAME 'message name' AND 'message type' for both your processing rules.
Instead, if you had a different 'message type' OR the 'message name', then they will both be considered unique and then whatever is the processing rule created, will get applied.
I am also curious to find out that how did you manage to save a processing rule with same message name and same message type? When I tried it, the system did not let me save it.
Regards,
Rutika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ruchir,
a recent SAP notes can also provide some light on your question:
1872559 - message listener performance
It point to also some consideration in regards to picking either Category or Transaction Processing type.
A personal architecture would be:
1. if when triggered, it has to be reflected directly and immediately in a destination system and without having a very high volume; then use Transaction processing.
ex: This can be the case for a production order or something like that as long as they are not sent by the thousands,
This can also be the case for a message sent from another MES system or plant system or MII, etc...
2. For everything else, Category:
- Master Data, ex: Material which can be batch updated
- Transactional data with a very high volume: ex production orders for a month after an MRP run.
Hope it helps,
Arnaud
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.