2025 Dec 04 11:34 AM - edited 2025 Dec 04 11:37 AM
Hi I’m wondering how to set periodic timer event for Integration Suite.
That condition is trigger the iFlow in every month every week in certain day but except national holiday or company holiday.
I found a similar case in SAP community in following link.
But I need to do more for customers request for restricting the trigger for national holiday or company holiday.
Please somebody give me your knowledge for guiding me for this area.
Thank you for in advance.
Sincerely
T.N
Request clarification before answering.
In SAP Integration Suite, the standard timer event does not support an arbitrary list of dates (like holidays) out-of-the-box. It is designed to run on a repetitive schedule, e.g., defined days of the week or month.
For your use case - triggering an iFlow periodically while excluding national or company holidays a two-step approach is recommended:
Use the standard timer for the base schedule
Configure the timer to run on the relevant weekdays (e.g., Monday–Friday).
This handles the majority of your scheduling needs (roughly 80%).
Filter out holidays using externalized parameters and Groovy scripting
Maintain a configurable parameter (e.g., in the Integration Flow’s properties) containing all holiday dates. The dates can be comma-separated in a consistent format, such as US date format or your company standard.
Add a Groovy script at the start of the iFlow that checks the current run date against this holiday list.
If the date matches a holiday, the script can stop further execution; otherwise, processing continues as usual.
This approach allows the iFlow to run on all weekdays but only process data on valid business days, and it keeps the solution flexible. You can update the holiday list for the next year - or even several years ahead - without modifying the interface design
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @taao19710316 ,
In SAP Integration Suite, the standard timer event does not support an arbitrary list of dates (like holidays) out-of-the-box. It is designed to run on a repetitive schedule, e.g., defined days of the week or month.
For your use case—triggering an iFlow periodically while excluding national or company holidays—a two-step approach is recommended:
Use the standard timer for the base schedule
Configure the timer to run on the relevant weekdays (e.g., Monday–Friday).
This handles the majority of your scheduling needs (roughly 80%).
Filter out holidays using externalized parameters and Groovy scripting
Maintain a configurable parameter (e.g., in the Integration Flow’s properties) containing all holiday dates. The dates can be comma-separated in a consistent format, such as US date format or your company standard.
Add a Groovy script at the start of the iFlow that checks the current run date against this holiday list.
If the date matches a holiday, the script can stop further execution; otherwise, processing continues as usual.
This approach allows the iFlow to run on all weekdays but only process data on valid business days, and it keeps the solution flexible. You can update the holiday list for the next year—or even several years ahead—without modifying the interface design
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.