(Individual) Software Order
This guide details the process for an individual within a company to order software, including how the order is managed and processed within the systems.
Overview
Walkthrough
- Starting the Order: An employee begins the process by choosing software items for delivery. If the employee is responsible for an office, a notification shows up to confirm that this is an individual order.
- Order and Booking Approval: Once the order is created, it undergoes an approval process. This is governed by a workflow called "Approval - RootITUp Order Analysis". The software items in the order (referred to as bookings) must be approved to move to the next step.
- Processing Steps:
- The order is registered in the order management system and is considered complete when an "OrderRegistered" event is noted.
- Each software item is then added to a purchasing basket in the system. This step is finalized when a "BasketItemRegistered" event occurs.
- A decision-making ticket regarding existing stock is created in a category called "StockDecision," which is customizable.
- Decision on Stock: After the ticket is accepted, the employee makes a decision about the current stock while closing the ticket.
- Handling a Negative Stock Decision (when there’s not enough existing stock):
- A new ticket is created under "PreApproval" for ordering new software licenses.
- Each software item is confirmed in the system, marked complete when a "BasketItemConfirmed" event happens.
- Once all items are confirmed, a purchase request is initiated in S4Hana.
- The IT Procurement team approves the purchase requisition.
- The purchase request is automatically turned into a purchase order by a purchasing job in SAP S4Hana.
- The initial ticket is moved to the "Software Provisioning" category.
- Upon successful delivery of the software by the supplier, the IT team confirms the delivery and records the goods receipt in S4Hana.
- Handling a Positive Stock Decision (when existing stock is sufficient):
- Items are deregistered in the system, marked complete when a "BasketItemDeregistered" event occurs.
- A ticket is created under "Software Provisioning" for the handling of the existing stock.
- Final Step: The workflow then waits for the closure of the software provisioning ticket.