| Feature Name & Description |
2019 Release Availability |
Automatically On |
Customer Enabled/ Customer Configurable |
Contact SAP Ariba To Enable |
Learn More |
Filter tiles by user's job function [GB-4109]
You can now configure tiles in guided buying so they are filtered by users' Job Function setting in addition to the existing Purchasing Unit setting. Tiles that have a Job Function are visible only to users who have that same Job Function. You can assign multiple Job Function settings per tile. Tiles that have no Job Function are visible to all users. |
Q4 |
|
 |
|
 |
Map header-level RFQ form fields to sourcing projects [GB-4185]
You can now configure guided buying RFQ form fields to map data to header-level fields in the Overview tab in SAP Ariba Sourcing events. Previously, guided buying could send only line-level data to SAP Ariba Sourcing. This mapping capability includes standard data, master data, and custom fields. |
Q4 |
|
|
|
|
Require lower-level commodity codes in requests [GB-6089]
With this feature, users can now be required to choose lower level commodity codes when completing line item forms, RFQ forms, or non-PO invoices. |
Q4 |
|
|
|
|
Support for lean services procurement in Guided Buying [GB-6188]
This feature introduces the lean services procurement process as an integration scenario with SAP S/4HANA Cloud solution. Lean services in SAP S/4HANA can be planned lean services or limit items for unplanned lean services. This release supports only planned lean services in guided buying integrated with SAP S/4HANA Cloud. It involves creation of service requisitions in Guided Buying and creation and processing of follow-on documents such as purchase orders, service entry sheets, goods receipts and invoices in S/4HANA. Users can monitor the progress of procurement by reviewing the status of follow-on documents created in SAP S/4HANA by viewing the entries recorded in the history of the service requisition. |
Q4 |
|
|
|
|
Improved guided buying navigation controls [GB-6228]
Guided buying has enhanced the way users navigate through the application. New, more modern navigation controls and other improvements make it easier and more intuitive to use guided buying. They're part of the larger effort to make the user interface consistent with other SAP applications and to comply with the SAP Fiori 3.0 design standard. |
Q4 |
|
|
|
|
Sending accounting splits, comments, and custom fields on requisitions to SAP S/4HANA [GB-6238]
Starting with this release, line-level comments, accounting split information (accounting distributions), and custom fields are sent to SAP S/4HANA when users submit requisitions for approval. After requisitions move to the submitted state, these details are also included in the corresponding requisition created in SAP S/4HANA. |
Q4 |
|
|
|
|
Enhancements to guided buying validation policies
Guided buying validation policies were originally meant to validate only transactional data, so they used information from only the request itself. Now, validation policies can include other form data, such data from master data fields, and supplier data from SAP Ariba Supplier Lifecycle and Performance, such as qualification status and preferred levels. This new information allows customers to develop validation policies that check more of the data provided by users. |
Q3
|
|
|
|
|
Additional session information available for use in form field conditions
Guided buying forms designers can use new fields that provide user session information in form field conditions. Use them to provide users greater responsiveness and personalization in forms. |
Q3
|
|
|
|
|
Guided buying maps data of type master data
Guided buying can now map any data of type master data that form designers include using Data source chooser fields. This new capability maps complex data containing object type and lookup values and it can allow you to avoid requiring users to enter data twice. |
Q3
|
|
|
|
|
New look for guided buying header
Guided buying has adopted the SAP Fiori principal theme in the header banner, header banner icons (such as menu, shopping cart, and notification), and search bar. While the header banner has changed, the functionality and use of guided buying has not changed and remains familiar to users. |
Q3
|
|
|
|
|
Add approvers and watchers without editing requests
Users can now add additional approvers and watchers without editing requests. The Approval Flow allows users to add additional approvers or watchers in the Your requests and Approve requests area. |
Q2 |
|
|
|
see release guide |
Guided buying can show multiple validation policy violations during check out
The Checkout page now shows multiple policy violations and groups them by the Severity level configured for your site. |
Q2 |
|
|
|
see release guide |
Ability to cancel requests and POs in guided buying
Now, users can cancel requests and POs in guided buying without punching in to a separate service. They can enter the reason for canceling and choose whether to send the reason to the supplier. In addition, they can copy canceled line items to new requests for future purchases, which is an easy way to make changes, such as switching suppliers. |
Q1 |
|
|
|
|
RFQ information inclusion in requisitions and purchase orders
Now, guided buying includes this information in the requisition and purchase order data models. It identifies the RFQ ID and line number, the quote ID and line number, whether the line items comes from a request form or an RFQ, and the touch flow that was used (self-service or low touch/high touch). |
Q1 |
|
|
|
|
