This blog post shows some tips and tricks around the SAP Analytics Cloud Calendar. The intention is to educate about features and functionality and simplify modelling your planning process!
Tip #1 – Reopen closed tasks
Sometimes things do not happen as desired. To make an example: During a revenue planning period a business department notices planning has to be performed again for a certain region (here: Plan
Region EU West). There can be many reasons - circumstances of business can change fast and plan values have to be adopted accordingly to ensure accuracy of planning. However, planning of the
Region EU West has already been performed during the planning period and the calendar task is already closed. How can we deal with such scenarios?
Closed tasks can be discontinued tasks or tasks reached with a certain end state (such as
Canceled,
(Partially) Accomplished. Closed tasks do not incorporate any active participation anymore. Indeed, closed tasks can be
reopened using the side panel. This will open the closed tasks and assignees of the corresponding event will be notified. This initiates the workflow of the task the same way as it would have been set to active for the first time after creation. Planning activities for
Region EU West can be performed once again.
In fact, composite tasks already implicitly use the reopen mechanism as part of the workflow between assignees and reviewers. Imagine the reviewer (part of a review round) rejects the submission of the assignee. Then the task itself will be reopened for the assignee, too. The Assignee will receive a notification that the previously submitted task has been reopened to further work on the deliverable. Of course, the assignee will be notified if a previous submission has been reopened as part of the rejection of the reviewer. Below a screenshot of the notification via email.
Tip #2 –Conversion of a process to a task and vice versa
SAP Analytics Cloud calendar provides us a flexible modelling environment. A process can be converted to a General Task. By selecting a certain process and clicking the conversion button of the toolbar we can initiate the conversion. If child events are attached to the process the system will provide a warning informing the user that child events (of the selected process) will be detached. That makes perfectly sense because a general task cannot be used to model hierarchical structures but rather an event mapping a business task to a workflow component.
How to initiate conversion of
Process to
General Task:
Result:
The same button can be used the other way around, too. We can also convert a
General Task to a
Process. This can be achieved by selecting the desired task and clicking the conversion button. In this case, the
General Task (here:
Plan EU West) will be remodeled to a
Process and furthermore a child event (here:
General Task with the same name
Plan EU West) will also be created. The system informs me before the conversion and also provides me a nice overview of how the conversion will look like in the system!
How to initiate conversion of
General Task to
Process:
Result:
Note, we performed the conversion within the process tree hierarchy. We converted a
General Task to a
Process within the overarching process element
A sample revenue process.
Tip #3 – Shorten/extend due date in UI
The Gantt view of SAC’s calendar provides a nice and easy to use visualization to consume and modify timeframes of modeled planning processes. The duration of a process and/or event can be adjusted by dragging the bars of the respective event.
If the user selects a process and adjusts duration, then the user will be prompted to apply the change also for child events. The duration of the child events will be adjusted based on the
ratio of change. To make an example: if we double the duration of the process, the duration of all child events will be doubled, too. If we cut the duration by half of the original duration, duration of child events will be cut to half, too.
Check out more enablement material
here!