Provisioning - RootITUp Booking Processing

DEPRECATED!

Within this guide you are going to learn about the central Provisioning - RootITUp Booking Processing workflow in Matrix42. This workflow implements the general order management process. Each booking for a S4Hana article should by default be provisioned using this workflow.

Workflow

The workflow starts by determining the relevant booking information including the article name, article quantity, pricing, payment cycles. Importantly, the information can be overwritten using

• the booking form filled out by users ordering a special (software / hardware) service or
• the service form configured for a welcome day service.

After determining further information relevant for ordering, the workflow determines the type of the order using the cost center of the order. The IT-Procurement cost center encodes a company order. The encoding of the order type was achieved in this way because the shopping cart allows for no (out-of-the-box) extension of order attributes.

Importantly, a smartphone service has two variants configured using a service form. A contracted and an uncontracted variant. If the user should receive an additional mobile contract (and mobile phone number), the contracted service variant is used when ordering.

The purple activities display the communication with the OrderManagementService. The workflow registers the order and the booking, after it determined all relevant ordering information.

Inventory Check Ticket

A software service results in a inventory check ticket, before any communication is done with S4Hana. Should stock be successfully reserved, no ordering is required within S4Hana. The booking is therefore deregistered.

Provisioning TIcket

Depending on the order type, service type and basket item type tickets are created within Matrix42. Importantly, at creation they are created in a way they are not visible to the normal service desk users. After creating the ticket, the booking is confirmed.

The workflow waits until the booking is in an ordered state. Only then is the provisioning ticket dispatched into the desired category. This category depends on the type of ticket and is e.g. overwritten for welcome day laptops.

The last step is to wait for the closing of the provisioning ticket, if required.

Disclaimer

In the production environment a small workaround was implemented for Dortmund. If a booking is done with delivery to Dortmund for a currently still stocked service, the booking is deregistered and a hardware output ticket is created.