What would be the 5 top issues in SAP EM Space?

[Former Member]

Kindly highlight the major challenges we face in SAP EM Space today and how they can be overcome. I went through many discussions, but could not find any answers. Please share any relevant links or posts. Thanks in Advance.

[Former Member]

Hi Swosti,

There were plenty of discussions that were related to not only performance and also in design perspective.

1. Service sizing is major challenge and that would have major performance issue once it is go-live, because when we discussed with client that would have given some estimate but end up somewhere when we went live.

E-g Initial design for server sizing to handler one million events per day, later the actual event would show as double or triple the count.  I had a recent bad experience with one of design and it took 3 weeks of discussion with multiple team, how encountered.

2. Overall architecture design of SAP EM space with SAP and Non-SAP systems.  Most of the client performance issue with third party application client because we don't have control on them and those were poorly integrated to SAP EM sometimes.

3. Try to avoid Event Handler Set in design.

4. Effective design of queue management instead of having one queue per process.

5. Avoid using custom Business Process Types and use Standard SAP EM BPT.

6. Try to avoid one event handler for end to end business process for example - OTC, P2P or H2R.

7. If client SO/DLY/SHP business process holds more than 20 line items then optimized coding require to avoid event handler lock.

8. If any third party sends tons of events per sec in peak hours, then try to use Buffer message concept and process later time those events.

Regards

GGOPII

[Former Member]

Thanks Gopi for the detailed answer!!

[Former Member]

Hi Swosti,

It depends on the implementations and how they are designed. I would say one should design properly and ask right questions before designing.

Somethings to keep in mind.

1) Performance

2) Queues running slow

3) Integration

4) Designing EM for purely track, trace and handling exceptions rather than for reporting purpose. It's not a reporting tool but can be used as one.

5) Designing rulesets efficiently ( most critical for performance )

6) Avoid duplication of events across multiple EH types unless required. Sometimes user training is required here to help them understand what event is relevant for what EH type and using webui links to navigate to different EH type to see the events.

Thanks,

Vishnu

[Former Member]

Thanks Vishnu. These points make lot of sense.