Events act as markers within your iFlow, defining where processes start, end, handle errors, or respond to time-based triggers. Each has precise behavior and restrictions.
Start Message: Starting point of the main Integration Process
Initiates the flow by receiving messages from different senders. It connects the sender adapter to the integration flow.
End Message: Ending point of the main Integration Process
Completes the flow and sends data back to the trigger point after processing is done.
Start Event: Starting point of the Local Integration Process
To start a local process within the integration.
End Event: Ending point of the Local Integration Process
To end a local process within the integration
Error Start Event: Starting point of the Exception Subprocess
It catches errors in the main flow or local process to handle exceptions effectively
Error End Event: Ends the exception subprocess when an error occurs, ensuring proper error management, by either ending the subprocess or helping you connect with a Receiver.
If an exception occurs during the processing sequence which has been handled in an Exception Subprocess, the message status displayed in the message processing log is Failed.
Timer: Triggers the iFlow on a scheduled basis, useful for fetching delta records or periodic data from systems when there is no external trigger.
Questions:
❓What happens if the Timer hasn’t finished processing a message before the next scheduled interval?
Ans: If the Timer starts processing a message and it’s not done before the next interval, the Timer skips that next interval.
❓Does Timer support daylight saving?
Ans: Yes
Note: If you want the events to happen at a specific time, with no relation to the specific time of the day during daylight saving, select a time zone that doesn’t support daylight saving.
❓Which time standard doesn’t support daylight saving?
Ans: CoordinatedUniversal Time (UTC) is a time standard that isn’t adjusted for daylight saving.
❓Can I use a timer in a Local Integration Process?
Ans: No
❓In case there are 2 Integration Processess in an Integration Flow, can I use a timer in both?
Ans: Yes
Terminate Message: Stops the further processing of the iFlow when a specific condition is met. The flow status in monitoring will reflect as “Completed.” For example, you have defined specific values on the payload. If the payload doesn’t match those values, the process is terminated.
The message status displayed in the message processing log is Completed, because it has terminated the message successfully.
Questions:
❓Can you use a Terminate Messgae in an Exception Subprocess?
Ans: No
❓By default, what are the events in an Exception Subprocess?
❓Even in case an exception occurs during the processing sequence which has been handled successfully in an Exception Subprocess, you want the message status to be displayed as Failed , then what do you use?
Ans: 1. Use an Error End event. OR
2. Use an Escalation End Event (sets a message status to Escalated in that case).
Escalation End Event: In case the message qualifies one of these categories,
Escalation Event : Routing condition has not been met.
Receiver not reachable : Receiver could not be reached, because it is temporarily down or not accessible (for example, due to overload or maintenance work).
Receiver not found : Receiver could not be found because the URL points to a non-existent resource (for example, HTTP 404 error).
Not authenticated to invoke receiver : Receiver could not be called because authentication has failed (for example, HTTP 401 error).
Not authorized to invoke receiver : Receiver could not be called because of insufficient permissions (for example, HTTP 403 error).
Receiver tries to redirect : Receiver could not be reached (HTTP 302 error).
Internal server error in receiver : Internal server error occurred in the receiver system (for example, HTTP 500 error).
Others – not further qualified : Escalation category has not been further qualified.
💡If Escalation End Event is in main Integration Process, then Escalated
💡If Integraion Process is calling local integration process, and Escalation End Event is in local integration process, then main flow message will be Completed
💡In case of Synchronous Exchange Pattern, the message will be marked as Escalated
💡In case of Asynchronous Exchange Pattern, no exception will be raised, and the message status will be Escalated
💡If used within an Exception Subprocess, the message processing stops, and the message status will be Escalated. This is regardless of whether the exception subprocess is used in the main Integration Process or a Local Integration Process
A quick summary as generated by AI:
Events act as markers within your iFlow, defining where processes start, end, handle errors, or respond to time-based triggers. Each has precise behavior and restrictions.Start Message: Starting point of the main Integration ProcessInitiates the flow by receiving messages from different senders. It connects the sender adapter to the integration flow.End Message: Ending point of the main Integration ProcessCompletes the flow and sends data back to the trigger point after processing is done.Start Event: Starting point of the Local Integration ProcessTo start a local process within the integration.End Event: Ending point of the Local Integration ProcessTo end a local process within the integrationError Start Event: Starting point of the Exception SubprocessIt catches errors in the main flow or local process to handle exceptions effectivelyError End Event: Ends the exception subprocess when an error occurs, ensuring proper error management, by either ending the subprocess or helping you connect with a Receiver.If an exception occurs during the processing sequence which has been handled in an Exception Subprocess, the message status displayed in the message processing log is Failed.Timer: Triggers the iFlow on a scheduled basis, useful for fetching delta records or periodic data from systems when there is no external trigger.Questions:❓What happens if the Timer hasn’t finished processing a message before the next scheduled interval?Ans: If the Timer starts processing a message and it’s not done before the next interval, the Timer skips that next interval.❓Does Timer support daylight saving?Ans: YesNote: If you want the events to happen at a specific time, with no relation to the specific time of the day during daylight saving, select a time zone that doesn’t support daylight saving.❓Which time standard doesn’t support daylight saving?Ans: CoordinatedUniversal Time (UTC) is a time standard that isn’t adjusted for daylight saving.❓Can I use a timer in a Local Integration Process?Ans: No❓In case there are 2 Integration Processess in an Integration Flow, can I use a timer in both?Ans: YesTerminate Message: Stops the further processing of the iFlow when a specific condition is met. The flow status in monitoring will reflect as “Completed.” For example, you have defined specific values on the payload. If the payload doesn’t match those values, the process is terminated.The message status displayed in the message processing log is Completed, because it has terminated the message successfully.Questions:❓Can you use a Terminate Messgae in an Exception Subprocess?Ans: No❓By default, what are the events in an Exception Subprocess?❓Even in case an exception occurs during the processing sequence which has been handled successfully in an Exception Subprocess, you want the message status to be displayed as Failed , then what do you use?Ans: 1. Use an Error End event. OR2. Use an Escalation End Event (sets a message status to Escalated in that case).Escalation End Event: In case the message qualifies one of these categories,Escalation Event : Routing condition has not been met.Receiver not reachable : Receiver could not be reached, because it is temporarily down or not accessible (for example, due to overload or maintenance work).Receiver not found : Receiver could not be found because the URL points to a non-existent resource (for example, HTTP 404 error).Not authenticated to invoke receiver : Receiver could not be called because authentication has failed (for example, HTTP 401 error).Not authorized to invoke receiver : Receiver could not be called because of insufficient permissions (for example, HTTP 403 error).Receiver tries to redirect : Receiver could not be reached (HTTP 302 error).Internal server error in receiver : Internal server error occurred in the receiver system (for example, HTTP 500 error).Others – not further qualified : Escalation category has not been further qualified.💡If Escalation End Event is in main Integration Process, then Escalated💡If Integraion Process is calling local integration process, and Escalation End Event is in local integration process, then main flow message will be Completed💡In case of Synchronous Exchange Pattern, the message will be marked as Escalated💡In case of Asynchronous Exchange Pattern, no exception will be raised, and the message status will be Escalated💡If used within an Exception Subprocess, the message processing stops, and the message status will be Escalated. This is regardless of whether the exception subprocess is used in the main Integration Process or a Local Integration Process A quick summary as generated by AI: Event TypeRole / DescriptionTypical UsageMessage StatusStart MessageEntry point for the main iFlow, connected to sender adapterMain process begins when a message arrivesProcessing/Further StepsEnd MessageExit point for main iFlow, sends processed data to receiverFinal output after integration logicCompleted/SentStart EventEntry for local process within an iFlowStarts sub-processes, not connected to sender adapterProcessingEnd EventEnd for local integration processConcludes local sub-processCompletedError Start EventEntry for exception subprocess (error handling)Catches errors in main/local process for custom handlingFailed/EscalatedError End EventEnd of exception subprocess, status ‘Failed’Concludes error handling, updates logFailedTimerTriggers iFlow based on schedule, not on message arrivalPeriodic data fetch, no external triggerProcessing/SkippedTerminate MessageImmediately stops processing upon meeting condition, status ‘Completed’Conditional logic (e.g., terminate if payload invalid)CompletedEscalation End EventMarks message as ‘Escalated’ for exception/routing issues (see list below)Use for: routing failure, receiver unreachable, auth issues, HTTP errorsEscalated Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
