The following is a demo that I did live at the ASUG Conference during the SRM 7.0 Overview presentation. I had a few requests for the demo, so I thought I would upload my backup screen cams here for all to access. There is no sound so I added some background in the text below.
The scenario is a contract call off for a requirement that originated from a shopping cart.
- Review and customize the Personal Objects Worklist (POWL)
- Create a shopping cart with a catalog item and a internal product master item – one item will auto PO, the other will require the purchaser to source in the Sourcing Cockpit
- Check the shopping cart status
- Manager approval
- Sourcing Cockpit to assign a source of supply to the shopping cart item that did not auto PO
- Review the contract to show the release history, including the order just created
- Create a shopping cart using the wizard design.
In the following scenario, I logged in as a purchaser for most of the steps.
Personal Objects Worklist (POWL)
In the Work Center, Purchasing Documents, the purchaser can access her Purchase Requisitions, Shopping Carts, Purchase Orders, etc. The Work Center can be customized and the purchaser already set up the documents that can be accessed in this Work Center. Furthermore, the purchaser set up queries that she frequently accesses for each of the purchasing documents. You will see the queries to the right of each document. Each query shows the number of documents that can be accessed by selecting the link; this is the number to the right of each link. When the link is selected, the documents will appear at the table in the bottom of the work center. Each time the purchaser comes to the Work Center, she can quickly access the documents and queries that she uses most often.
One of the first changes is to the view at the bottom. The purchaser selects a predefined view that makes the bottom table more appealing to her. Alternatively, the view can be used to create predefined sorts, filter, show specific fields, make calculations, and enhance the table presentation.
Define New Query
To change a query at the top of the Work Center, the purchaser selected Define New Query. In step 1, the purchaser selects the document type. This will define the query criteria in step 2. The user can use an existing query to pre-fill the criteria in step 2.
In step 2, the purchaser defines the criteria for the query. In this example, she is creating a Shopping Cart query for a particular product category.
In step 3, the purchaser names the query and assigns the query to one of the existing labels, or she can create a new label for the Work Center. As you may recall, the labels we used in the Work Center were the purchasing documents – Requisitions, Shopping Carts, Purchase Orders, etc.
When the purchaser selects the new Boards query, 25 Shopping Carts come into view. However, the view extends beyond the screen and causes the user to scroll right. We will now use the settings to change the view and reduce the number of columns (Column Selection – Remove). Next, the purchaser changes the sort for the view to sort on Shopping Cart Number. Finally, she changes the view settings to make the table display more appealing by using alternating shading and removing the grid lines. She saves the view so she can come back to the column arrangement, sort, and display when she selects the view in future sessions.
The Shopping Cart screen video highlights the new User Interface design in SRM 7.0. The floor plan (ie: UI template) for the one-page shopping cart is a Quick Activity. The objective of the Quick Activity is to provide users with a one-screen view where they can accomplish their activities as quickly as possible. Some fields are open to provide quick access and other fields, which are used less often, are a click away. This UI is targeted toward more advanced users.
By contrast, the other Shopping Cart floor plan is a Guided Activity, which is targeted toward novice or users who use the system less frequently. We will see this in another video, but the Guided Activity provides a step-by-step process flow to guide users through the process.
Create Shopping Cart
The purchaser initiates the shopping cart screen from the POWL. This is one of several ways to initiate the process. In this scenario, the purchaser will add an item to the shopping cart from the catalog (MDM Catalog 3.0). The purchaser uses the keyword search to find the product and adds the product to the MDM-Catalog cart. You’ll see in the top right a status that shows the number of items and value included in the cart. The user then checks out to transfer the catalog items to the SRM Shopping Cart. The purchaser adds an additional item from an internal product master directly into the shopping cart item table.
Note that the shopping cart including the item table view can be customized by the user to add/remove columns, and add/remove fields. In addition, the item view table can be personalized to adjust the number of rows that are visible in the table. For carts with a large number of items, the item table can be filtered to work on subsets of items.
When the purchaser selects to view the item details, notice that a tabbed window comes into view at the bottom of the screen. The tabs allow users to work in their preferred order and also reduce scrolling. In this scenario, the purchaser reviews the Sources of Supply for the items in the Shopping Cart.
Back in the POWL, the purchaser used a predefined query to display the shopping cart that she just created. The approval tab shows that the shopping cart is in the manager’s inbox waiting for approval.
A manager logs in and reviews the inbox for work items. The manager can find all items for approval in a Universal Work List (UWL). The UWL is a single entry point to all tasks, alerts, and notifications from all applications. In our scenario, the manager finds the shopping cart that needs approval, opens the shopping cart to display the details, and then approves the shopping cart. You will also notice that the manager had the option to reject or inquire for each item in the shopping cart. The inquiry option lets the manager ask questions about a particular item before approving.
First, we revisit the shopping cart so we can see how the system processed the shopping cart after approval. The purchaser checked the document history under Related Documents. For the first item, we see that the item is in the Sourcing Cockpit (status is “In Purchaser’s Worklist”). The second shopping cart item had been converted to a backend purchase order (ie: auto PO). The rest of the demo will continue with the first item in the Sourcing Cockpit.
The floor plan for the Sourcing Cockpit is Guided Activity. The objective here was to break the operational sourcing process into four quick activities. In the first step, the user selects the requirements they want to process using an extensive list of criteria. In step 2, the purchaser reviews proposed sources of supply for the list of requirements. Step 3 displays the documents to be created. Step 4 confirms that the documents were created.
In the Sourcing Cockpit, the purchaser selected a contract as the source of supply for our shopping cart. In this avi, we will review that contract.
The purchaser used the filter in the POWL to find and display the contract using the contract number. When the contract opens, you will see another UI floor plan, the Object floor plan. In the top of the window, the object is summarized, including information like document number, supplier, status, contract name, contract type, etc. Then there are a series of tabs that will change the view of the object. The Overview tab is unique because it combines elements of the other tabs into a single view. Thus, the Overview tab is designed as a Quick Activity within the Object so users can get their work done as quickly as possible on one screen. Of course users can visit the other parts of the object, but the design was for users to complete most of their work from this one screen.
We can show the contract call off for the item in our shopping cart under the Items tab and Releases. There the purchaser will find all the purchase orders for that item that were assigned to the contract.
Tracking maintains the contract history, status, versions, and change documents, and thus provides an audit trail for all contract changes. In the history, you will also see the purchase orders that have released against this contract, including the order we just created. The difference between Tracking and the Release history we viewed earlier is that Tracking will show all releases for all items in the contract.
Shopping Cart – Guided Activity
The avi opens with another version of the Personal Objects Work List (POWL). This version of the POWL doesn’t have the query links like a previous demo, but has tabs. This version of the POWL can be personalized like the one we demonstrated earlier.
When the employee selects Shop, the Guided Activity opens. In step 1, the employee can browse catalogs or other sources of product information that they are authorized to access. In this example, the employee enters a product code from a product master record. In step 2, we show how the shopping cart can be personalized using the settings. Here the employee reduced the number of shopping cart lines. Lastly, in step 3, the employee demonstrates how easy it is to hide fields in the user interface. In step 3, the employee right-clicked a field label to hide the label. The employee can bring back the field or label by right clicking the screen and selecting the user settings.