UC Collaborative Requisitioning Cathal O’Sullivan, Senior Product Manager, Ariba © 2011 Ariba, Inc. All rights reserved

UC

Collaborative Requisitioning

Cathal O’Sullivan, Senior Product Manager, Ariba

© 2011 Ariba, Inc. All rights reserved.


• Description Ability for the buyer to collaborate with suppliers on all requisition types

• Features Extends collaboration to catalog and non-catalog items (deployed on P2P, P2O, APC) Can enforce X Bids and a Buy on any type of requisition (deployed on P2P, P2O, APC,

Services Procurement) Quick Enablement Collaboration Request

• Benefits Buyer can negotiate with supplier on any type of requisition X bids and a buy can be enforced Suppliers no longer need to be on the Ariba Network to receive a Collaboration Request

• Examples Buyer has a standard catalog item (Widgets at $10 a unit) from Supplier XYZ. They can

collaborate with Supplier XYZ and two other suppliers on this item to see if the supplier has the item in stock and to negotiate a lower price.

© 2011 Ariba, Inc. All rights reserved. 2

Demo

• Use Case 1 Demo of Collaboration with a standard catalog item

• Use Case 2 Demo of Collaboration with a non-catalog item

• Use Case 3 Demo of Collaboration with a contracted item


Discussion

• Topic 1 Discuss what happens when the requestor is not part of

the dynamic collaboration group


Demo

• Use Case 4 Demo of Collaboration when supplier adds an item to

the requisition


Discussion

• Topic 2 Discuss a punch out supplier than can add punch out

items to the requisition


Demo

• Use Case 5 Demo of N Bids and a Buy soft stop

• Use Case 6 Demo of N Bids and a Buy hard stop


Discussion

• Topic 3 Discuss Quick Enablement Collaboration Request


Collaborative Requisitioning Using (1)

• Using Enabling

– A new permission/group has been created that allows for dynamic collaboration: AllowDynamicCollaboration.

– A new CSV file has been added that controls X Bids and a Buy. – If a Buyer wants to use QE for Collaboration Requests, they will need to customize

the Welcome Letter.– If a Buyer wants to use QE for Collaboration Requests, they will need to create

a custom PDF for their suppliers on the process that they need to follow. Requirements

– N/A Limitations

– Suppliers will only be able to edit certain fields– Understand how the process will work when a buyer wants to collaborate on

a contracted item



• Using Workflow Overview

– Changes to the approval flow compared to standard P2P and APC. There is now a concept of Pre-Collaboration, Collaboration, Post Collaboration

Changes to Existing Functionality– Not OOTB. Significant changes if the feature is enabled.

» Buyers will now be able to collaborate with suppliers on catalog and non-catalog items» Suppliers will be able to add items to the requisition» Buyer will be able to enforce X Bids and a Buy. This allows for X Bids and a Buy

to be configured on certain fields: example: commodity code» Specifies whether the user will receive hard or soft error messages» Process will be slightly different for APC customers (this is mainly because

APC does not have the concept of pre-collaboration)» Collaboration Requests can be send to suppliers who are not registered on the

Ariba Network» Buyers will be able to see View Failed Collaboration Request Welcome Letters.



• Using Changes to Existing User Interface

– Not OOTB. Significant changes if the feature is enabled:» Collaboration radio button displayed» Invited Supplier list added to screen/Supplier Location added to

the Invited Supplier list» New Collaboration tab» Bidding type added to screen» New warning messages (soft and hard) for X Bids and a Buy» New changes to Admin UI


Collaborative Requisitioning Required Action

• Action Needed Post-GA to consume the feature To enable this feature, please contact your Customer

Success Manager or Account Manager for more information on Ariba Services


Questions


“Safe Harbor” and Confidential Information Statement

This information reflects the status of Ariba solution planning as of January 2011. All such information is the Confidential Information of Ariba (per the contract between our companies), and must not be further disclosed, as stated in the confidentiality clause of that contract. This presentation contains only intended guidance and is not binding upon Ariba to any particular course of business, product strategy, and/or development. Its content is subject to change without notice. Ariba assumes no responsibility for errors or omissions in this document. Ariba shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.


UC


Cathal O’Sullivan, Senior Product Manager, Ariba

© 2011 Ariba, Inc. All rights reserved.

Documents

UC Collaborative Requisitioning Cathal O’Sullivan, Senior Product Manager, Ariba © 2011 Ariba, Inc. All rights reserved