SAP Fiori UX Design and Build Challenge May Procure 2 Maintain. Simple. Efficient. Delightful.

Transcription

1 1 Simple. Efficient. Delightful. Background This application is mainly targeted for Manufacturing Industry, where it is important to prevent any production loss due to machine downtime. In such cases, Preventive Maintenance plays a critical role. More specifically, this application is useful for any manufacturing plant where these two SAP products are already in place - SAP Plant Maintenance for creating Maintenance Orders in ERP system - SAP Supplier Relationship Management (SRM) for procurement of Indirect Materials In SAP technical language we refer to the above scenario as Plan Driven Procurement or PDP. It is a quite commonly used SRM implementation strategy for CPG industry, Pharma Industry, etc. The Basic Document Flow in such scenario is like this Step 1: The plant Maintenance Manager creates Plant Maintenance order in IW31 transaction in ERP. Step 2. System generates a Purchase Requisition for this PM order, in order to request for Procurement of goods and services to carry out the maintenance activity. Step 3: With the help of Plan Driven Procurement configuration, the details of the Purchase Requisition are read by the SRM system and a shopping cart is generated in SRM system. Step 4: Based on the approval workflow guidelines of the organization, the Shopping Carts are approved and these get converted into a Purchase Order. Step 5: The purchase order output is sent to the vendor and the copy of Purchase Order is transmitted to ERP system. Step 6: After receiving the Purchase Order, vendor supplies the material to the plant. Step 7: With the help of goods and services supplied by Vendor, the maintenance activity is carried out. We understand and accept that different user groups will have different business needs in such a work environment and a single application might not be suitable for everyone. In the present context, the specific group of customers which will benefit the most will be the Maintenance Managers who are the head of indirect procurement for Maintenance Operations. This application will not only make the overall process more efficient, but this will also simply their system interaction by providing all the necessary information on a single screen, thus eliminating the need of logging into multiple transactions and reducing the training cost.

2 2 Persona User Experience Journey In her current role, Radha needs to perform the following activities quite frequently. Search for incomplete PM orders for her plant Check for PM orders which have not been marked Technically Complete (TECO) in the latest PM report for Incomplete Orders, in ERP system Identify Red, Yellow and Green Status Orders Red Those PM orders, for which Shopping Cart has not been generated Need to check in SRM backend system in BBP_PD transaction Yellow Those PM orders for which Shopping Cart is generated but not yet approved Need to check in SRM Portal Green Those PM orders for which Purchase Orders have been created and have been sent to Vendors Can check in either SRM or in ERP system Red Create ticket with IT support if SC has not been generated Yellow Send reminder for SC approval to the approvers Green Follow up with vendors if required

3 3 Accordingly, her User Experince Journey can be described as outlined below - In the above example, the Red dots represent the pain points and the Blue dots represent important milestones and decision points. Mock up This is the rough Mock Up to present the idea what all information should be displayed

4 4 SAP Web IDE App The OData design is based on the local EDMX schema in the IDE The Mock Data is maintained for the metadata file Screen elements are modified to suit the design

5 5 The initial screen shows all PM orders which are yet to be completed. User may filter for his/her plant if required

6 6 User can click and see the details of the Red, Yellow and Green status PM orders. Moreover, with the help of the buttons at the bottom of the screen, the necessary notification can be sent to IT helpdesk, SC approvers or the Vendor.

7 7 Conclusion 1. User centric / Role-based Focussed on the specific user group and scenario provide only that information which is relevant for the user for this paritcular activity. 2. Simple / Intuitive As compared to the original process in which user has to access so many SAP transactions and screens in multiple SAP systems, this Application provides the simplified view in a single screen. No specific user training is required for the user. 3. Efficient User saves a lot of time in performing the activity which used to take twice the amount of time earlier + Organization saves a lot on training cost. 4. Delightful Due to the Fiori like look and feel, ease of use, less chance of error, intuitive and user focussed application User feel delighted, because he/she feels that someone is thing from his/her point of view and cares about the specific things which he/she needs and cares.