Business Cycles

BA cycles are the time frames in which you can expect the batch processes in the BA to run. For example, let's suppose that the batch processes for the Human Resources department kick off every day at 7 pm and that they must be finished by 7 am the next day. The batch processes for the Finance department kick off every day at 7:30 am and must be finished at 12:30 the same day. In this case, the Human Resources BA cycle would be 12 hours starting at 7 pm every night and ending at 7 am each morning. The Finance cycle would start at 7:30 every day and end 5 hours later the same day.

You use business area cycles to filter jobstream runs based on the cycle on which they are executed. This means that you can have BA display the jobstream run data of the Previous cycle, of the Current one or of the Next cycle (runs that are forecasted to happen in the future). BA cycles are particularly useful for organizations where different teams are assigned different time frames for batch processing.

As a BA coordinator, when you define a BA, you also assign it a cycle. This lets you create different BAs for one and the same processing batch and assign each BA a different cycle.

You add, edit and delete business areas in the web interface. However, you assign cycles to the business areas in the thick client.

Filtering Data by BA Cycles

BA uses the BA cycle information to display and filter the jobstreams that fall within a specific cycle. You can filter by the following:

Previous cycle
Current cycle
Next cycle

By filtering jobstreams by BA cycle you can see how they are performing in relation to the time frame within which they should finish.