Name: Creating Self-Service RFQ in Guided Buying in SAP Ariba
Uploaded: 2023-12-6
Duration: 240 s
Description: The video presents an overview of the tactical sourcing scenarios available in guided buying and the steps to creating a self-service RFQ.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>The video presents an overview of the tactical sourcing scenarios available in guided buying and the steps to creating a self-service RFQ. </div></div></div></div>

Creating Self-Service RFQ in Guided Buying in SAP Ariba

This video focuses on tactical sourcing scenarios available in the guided buying capability. The tactical sourcing process starts in guided buying with a request form. These forms are created by guided buying administrators who also create the supplier policies that determine which scenario is triggered by the form and what will be the involvement of the sourcing team if any is required. The first scenario is the self-service. Here the user filling in the form is fully in charge of the process. They will submit the RFQ for bidding and then choose which supplier they will be buying from. Then, there is the low-touch scenario, where the casual user fills in the request, but once they submit it, the RFQ will first go to the sourcing team. A sourcing specialist will publish the RFQ for the suppliers to bid. Once bidding is over, the casual user selects the awarded supplier in guided buying. Finally, we have the high-touch scenario. Here, the casual user submits the request in guided buying, which will be forwarded to the sourcing team. This is the scenario where the process is entirely handled by the procurement department, with them creating an event or a sourcing request. For this scenario, awarding is performed in SAP Ariba Sourcing, and guided buying displays the results. This video demonstrates the self-service scenario. In guided buying, we use the Language Services Request Form to ask for translation services. We require a translation from English into French for a document of about 35 pages. The tactical sourcing scenarios we have in guided buying are triggered by two pieces of information the casual user enters in the request form. One of them is the estimated price and the other is whether the form will be sent to at least one preferred supplier. Because we haven't specified anything in those fields yet, the language policy displayed is high touch for now. Let us now invite the preferred supplier to the RFQ and then in the Estimated Amount enter $250 USD. Since the estimated price we entered is below the threshold that the guided buying administrator has set for a self-service scenario, the system knows that the request can be sent to the supplier directly. In order to do so, we select the Request Quotes button at the top of the page. We can now see that the request was created and submitted to the supplier. They will be able to find it in their SAP Business Network account. Let us now focus on accepting supplier quotes. To manage their RFQs, a casual user will have to go to the Your Requests tab in guided buying. This is the place where they can see all the RFQs they have submitted and the different stages the RFQs are at within the tactical sourcing process. Because this is a self-service scenario, the casual user can immediately see the quotes and award. In this example, we have a quote of 200 US dollars from Translation Works. We choose Accept Quote and then Award. On the next page, we see that the system has automatically generated a purchasing requisition linked to this RFQ. This request will be submitted to the approvers specified by the approval process the administrators have set up for requests in SAP Ariba Buying. The last thing to do is to submit the request for approval. This concludes our video on self-service tactical sourcing scenario.