Ariba Online Help
Contents | Index | Search     
Tips   About the sourcing request process

If Ariba Enterprise Sourcing cannot match your email address with those in its database when you first connect to it, it creates a new user profile for you and randomly generates a password. It then sends you an email notification informing you of the user name and password to use when logging into Ariba Enterprise Sourcing.

If you choose a selected supplier in Ariba Enterprise Sourcing who is unknown in Ariba Contract Compliance, the Ariba Buyer Supplier Manager is notified to add the supplier to Ariba Contract Compliance. When the Supplier Manager has added the supplier, or if the set time limit for adding unknown suppliers expires before the supplier is added, you receive an email notification message.

To learn about configuring and integrating Ariba Contract Compliance and Ariba Enterprise Sourcing to source requests, see the Ariba Contract Compliance Guide. To learn more about RFX activities, see What is an RFX activity? in the Ariba Enterprise Sourcing Online Help Contents tab.

See collective negotiation for additional information about rfx activities.

Related topics

About contract sourcing requests (CSRs)

About spot purchase sourcing requests (SRs)

Sourcing request statuses

Contracts permissions

 

Ariba Contract Compliance enables authorized users to use Ariba Contract Compliance to create a request for goods or services, and then use Ariba Enterprise Sourcing to electronically solicit and manage bids from invited suppliers for providing those goods or services. After approval of the winning bids and suppliers, Ariba Contract Compliance generates the necessary documents to complete the procurement process.

If you have the permission required to work with sourcing requests, you can create a spot purchase sourcing request (SR) or a contract sourcing request (CSR) in Ariba Contract Compliance. The basic steps are similar for both SRs and CSRs, and vary mostly in how they are initiated and completed in Ariba Contract Compliance (see the process flow diagram):

In Ariba Contract Compliance

  1. Create a sourcing request. If you’re responsible for establishing a long-term contract, create a CSR. If a user submits a purchase request that contains a non-catalog item for your approval, create an SR for the non-catalog item.
  2. Submit the sourcing request for approval.
  3. When the sourcing request is fully approved, connect to Ariba Enterprise Sourcing to create a corresponding sourcing event, called an RFX activity, or simply RFX.

In Ariba Enterprise Sourcing

  1. Select a template to initiate the RFX, which is automatically populated with information from the sourcing request.
  2. Provide additional information about the RFX, launch it, and monitor bidding.
  3. When bidding ends, evaluate bids and choose selected suppliers.

In Ariba Contract Compliance

  1. For an CSR: Ariba Contract Compliance generates a draft contract request (CR), automatically populated with information from the RFX, for each selected supplier. Complete the CRs and submit them for approval. For an SR: Ariba Contract Compliance updates the original purchase request with information from the RFX and moves the purchase request through the approval process.
  2. When the CRs or purchase request are fully approved, Ariba Contract Compliance creates contracts (for the CRs) and POs (for the purchase request). Selected suppliers are notified that their bids have been accepted.
  3. Proceed with the steps related to contracts or purchase orders.

Copyright 1996 - 2004 Ariba, Inc. Legal notices.