In this post I have described how the process works to receive an inbound event message using ES, AIF and how to re-process the failed event messages.
Scenario
Abbreviation
FWO: Forwarding order
TO: Freight order / Transport order
FU: Freight unit
TU: Trailer unit
Using SAP EM Enterprise Service TrackedProcessEventNotificationCreateRequest_In events are posted in EM. SAP PO/PI service interface and interface mapping required from PI/PO end.
SAP AIF supports for event message re-processing by changing the event details such as location, event code, tracking id and date /time. Authorisation based on event tracking ID is also promising in AIF but it requires custom development in AIF.
Security roles for business users are required to re-process the error event message in AIF. Using event message tracking id, standard EM authorisation is sufficient for accessing AIF monitoring tool.
AIF Monitoring Dashboard selection screen
AIF Event Message re-processing
Data structure space from the right bottom of the AIF dashboard support for event message reprocessing by changing the event details.
Structure value turns to yellow colour by default after changing the values.
Message mapping based on master/ transactional data in AIF is easy to maintain rather than building the complex message mapping in PI/PO or any other integration tools. PI Inbound message queue can be deleted after the error as it may block the subsequent event processing.
Benefits of using AIF in EM
Event message re-processing
Tracking id mapping and custom business validations
Allowing the business user to re-process the event messages
- SAP Managed Tags:
11 Comments
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
