Actions

Time windows support the following actions:

Time Shifting

Time windows allow you to shift the time that a day starts. The Dutch railway company, for example, decided that for their schedule, the night from Friday to Saturday is still Friday. Saturday starts at 6 AM. Therefore, they want to specify that a job that is submitted for Friday 4 AM, actually runs on Saturday 4 AM. This can be achieved by using the OffsetTimeOfDay attribute of time window elements. Note that the start time of jobs will only be modified when  OffsetTimeOfDay → Scheduled Start Time . For example, if the Dutch railway schedule a job for execution at midnight with a time window, which has anOffsetTimeOfDay set to 6 AM, the job will actually run the following day at 6AM.

Day Shifting

Calendar time windows are normal time windows with the restriction that they do not specify times; they are always open for the whole day. They allow you to shift days forward or backward. This allows you to compensate public holidays or when the last day of the month falls a Sunday, for example. You can compensate for that by shifting a process a few working days forward or backward. This works by comparing two time windows, the reference is the main time window, if an open day of that time window is closed in the Shift time window, then the process is shifted forward or backward according to a third time window. The second (Shift) time window specifies when to shift (when the Shift time window is closed), the third (Stride) time window, defines the stride of the shift (n number of open days), the number of steps to move (n) is defined in the main time window.

For example, your process runs on the last day of the month, when this is a weekday (Mon-Fri). When the last day of the month is a Saturday, Sunday or public holiday, you want to shift that process to the preceding workday.

You create three calendar time windows, the first is closed on Public Holidays and is named TW_Closed, the second is open Monday to Friday and is named TW_WeekDay, the third is your main time window named TW_Cal, it is open on the last day of the month, when an open day in TW_Cal is closed in TW_Closed then we shift the process to the preceding open day in TW_WeekDay.

Another example, your process runs on the 3rd workday of every month according to the FR factory calendar in your SAP system.

You create 3 calendar time windows. A time window that is always closed, named PR1_NEVER. A PR1_FR time window, which is defined by the period function SAP_FactoryCalendar, it will need the following parameters: calendar=PR5 FR. SAP CPS will use that time window to move forward according to the factory calendar. A time window PR1_3RD_WORKDAY with a time window element "on the last day of the month" and the shift condition "If an open day is closed during PR1_NEVER then shift this day forward to the 3rd following open day in PR1_FR". See the step-by-step example below for this.

Calendar time windows have the following restrictions:

On the calendar time window:

On elements of a calendar time window:

Calendar time windows are evaluated in the time zone of the job. The time zone of the job is the time zone specified in the submit wizard. When the job was submitted from RedwoodScript, without specific time zone, the central server time zone is used for the job time zone.

Time Window Preview

In the preview pane of a time window, a calendar displays the current month and the days and time the currently selected time window is open. It shows the time of the current day by default but different days, months, and years can be selected. It shows a blue bar when a time window is open, a light blue bar when a time window opens and a white bar when the time window is closed. This can help fine tune a time window and can help you make sure you have made no mistakes when you created the time window.

The time scale below the calendar shows the time of the currently selected day the time window is open,

An overview table is displayed on the right-hand side and gives you an overview over all the times and dates of the current month the time window opens and closes.

When you use restrictions, for example from Monday to Tuesday, and the from value comes after the to value, the process server will automatically wrap. The following list illustrates the behavior:

(this month) to 5 (next month)''

Finding Time Windows

You can search for time windows using filters and the Search Time Windows box on the Time Windows tab. This box is known as the intelliSearch box lndocated under your username on the top right-hand side of the user interface. Filters allow you to specify a list of objects with static criteria. IntelliSearch allows you to specify complex queries in a simple way using prefixes. Prefixes are used to specify which property you are searching in and have short and long syntaxes. For example, if you want to display all time windows with the term import in the comment, you would use the search criteria as follows:

c:import

You can search more than one property, as follows:

c:import n:Bi

See the Advanced Object Search for more information.

The following table illustrates the available prefixes for time windows:

Deleting Time Windows

You can only delete time windows when no other objects relate to them. For example, if there are jobs that have run with the time window, the time window cannot be deleted until all jobs that ran with it have been deleted. You can see all jobs that relate to the time window in Related Objects in the lower detail pane and on the show page.

The table in related objects contains three columns:

Security

You can grant privileges on two levels, Access and Admin; a privilege granted on Admin level allows the grantee to grant the privilege to other users. These privileges can be granted system-wide, per partition or isolation group.

If you have the security module, which requires the Module.Security license key, you have an additional Security tab on the time window. It allows you to specify which users can access, edit, and delete the time window.