Approval - RootITUp Order Analysis

Within this guide you are going to learn about the central Approval - RootITUp Order Analysis workflow in Matrix42. This workflow implements the default approval workflow for all bookings correlating to a S4Hana articles. There are four possible outcomes during approval :

1. The booking is directly approved. The provisioning of the booking can continue without any further approving entity.
2. The booking is to be approved by the IT. Before a provisioning of the booking can take place, the IT has to approve the booking.
3. The booking is to be approved by the privileged users. The group of privileged users is depending on the recipient and the service. Before a provisioning of the booking can take place, one of these users has to approve the booking. (For managers, only the first user is prompted for approval)
4. The approval is faulty. The workflow crashes.

Concepts

The main concepts introduced are the notion of beyond privileged and privileged users. A user is beyond privileged, if a membership for the Service Catalog - adesso Group - Beyond group is given within Matrix42. It is important to note, that a booking for a beyond service can only be approved by a beyond privileged user.

When we use the parent notion, a traversal along a hierarchical structure is meant.

Workflow

The workflow starts by determining the users that are beyond privileged and relative to the service privileged. To decide who is allowed for the approval of a standard service the total order amount is used. The free amount is configurable and decides which bookings need no approval, as they are cheap enough.

Example

To visualize the effect, examples for beyond and standard service ordering are supplied below.