Unexpected event in event management

[former_member636423]

We have an Z event which is not configured as an expected event.The requirement is that this event should behave as an expected event whence posted. For this issue to be resolved we followed 2 ways:

Approach 1:

Use trackeemodify table from BAPI /SAPTRX/BAPI_EH_ADDEVENTMSG_02.With this approach, the event was being created as expected but the same event was posted as unexpected.

Approach 2:

Use BAPI /SAPTRX/BAPI_EH_ADD_EE but I guess this is marked as obsolete.

Can experts throw light which is the best way to resolve this issue.

[butschbacher]

Hi Smriti,

yes you can also create Expected Events without Planned Date/Time and Location.

In EE Profile set Check Location as "Do not check". If you the send later the actual event it should be processed as Expected Event.

Best regards,

Steffen

[smriti1988]

Hello Experts

We have a scenario where Actual events are coming via Interface to SAP EM system for reporting. These events as per their nature are expected but our current system doesn't allow me to plan these events (as I have no visibility on dates and location of these events) so how should I handle this situation.

1. One way is I declare these events as Unexpected in SAP EM but in this situation I will not have a reason code for this because in nature they are not unexpected

2. Is there a way to declare this event as Expected but without date or location ??

Please help!

[rafael_cano_perez]

Hi Indraneel.

I don't know which system is connected to EM as the business process system. Depending on the system, the following process changes.

For an event to be considered as an expected event, it has to be in the expected event table of the the event handler, as Steffen points.

Expected events come from business process milestones, this means that there is some kind of expected event extractor that runs in the context of the business process system, when the business entity ( document ) is saved, that extracts a table of event ids, with dates and location ids, and sends it to EM. Your Z event has to be in this table.

When this table arrives to EM, it goes through a mapping process using the expected event mapping profile. Your Z event has to be here as well. If your Z event was not in the original extracted expected events list, it can also be mapped to a standard event in the table.

At the end, your Z event would be in the expected event table, and when the event gets reported, depending on location requirements set in the mapping profile, it will behave as a reported expected event.

Hope it helps. Regards, Rafael

[butschbacher]

This can only work when the expected event was created before. EM looks up in the EE table if it does not find it there it will be recognized as unexpected event. Maybe you can explain the scenario here.

Best regards,

Steffen