Michal’s Tips: SXMB_MONI vs FEH/ECH vs AIF
In this article I will try to present the main differencies between 3 SAP technologies which are used in SAP integration projects on the SAP backend systems (like ERP, SCM, etc.) for handling interface related errors:
a) SXMB_MONI – standard monitor for proxy messages
b) FEH/ECH – Forward error handling, Error and Conflict Handler – standard SAP tool for enterprise service error solving
c) AIF – Application Interface Framework – additional tool from SAP for interface monitoring
A similar comparision was already done in this article – POV: FEH or AIF or Custom Error Handling – but since then there have been some significant changes in some of those technologies so I believe it’s worth to do the comparision once more.
|
FEH/ECH |
AIF |
SXMB_MONI |
|||
|
|
|
|||
|
|
Works for outbound asynchronous services |
Works for outbound asynchronous services |
|||
|
|
Works for inbound synchronous services |
Works for inbound synchronous services |
|||
| Works for outbound synchronous services | Works for outbound synchronous services | ||||
| SAP Standard services use ECH | Needs to be customized (no coding required) | SAP Standard services use SXBM_MONI | |||
| Payload editor | Payload editor | Payload editor based on XML | |||
| Manual restarting | Manual restarting | Manual restarting | |||
| Automated error resolution based on error type | Very limited automated restarting | Very limited automated restarting | |||
| Alerting, Notification | Alerting, Notification also based on content of the message | Alerting, Notification | |||
| SXMB_MONI – integration – links | SXMB_MONI – integrated | ||||
| Data search on the basis of message attributes | Data search on the basis of message attributes from indexed tables | ||||
| Usage of tips and hints | Usage of tips and hints | ||||
| Authorization concept with payload attributes usage | |||||
| Framework for implementing error handling – only | Framework for implementing all kinds interfaces (IDOC, WS, etc.) | ||||
| IDOC monitoring in the same tool (look and feel) | |||||
| Own runtime for processing other types of integrations (file, etc.) | |||||
| Simple navigation from error to the field level | |||||
| Value mapping tables are the AIF standard objects | |||||
| Grouping of interface based on defined criteria | |||||
| Message mapping tool for additional mapping | |||||
| Versions of interfaces | |||||
| Customizable application tabs (with own objects) | |||||
| Does not link to the documents | Customized links to documents | Does not link to the documents | |||
| Licence cost – free | Licence cost – Seperate Licence | Licence cost – free |
I hope some of you can use this information to determine what kind of error handling tool do you need in your projects.
Thanks Michal for sharing the difference.
Hi Michal,
Thanks for the information.
Request you to provide bit more information on "FEH/ECH".
Regards
Ankita
Thanks Michael for your insights.
Do you know if you can conditionally assign error handling for an organization unit branch? like in PPO where you can assign business users to fix business related errors?
Which tool is the best for this?
Hi Erik,
with AIF you can assign error handling to any kind of data you have in the message (like plant, company code etc.) if this is something you're looking for,
Regards,
Michal Krawczyk