Describing SAP Ariba 2408 Release Features

• Applicable Products
  • SAP Ariba Sourcing
  • SAP Ariba Contracts
  • SAP Ariba APIs
  • SAP Ariba developer portals
  • SAP Ariba Strategic Sourcing Suite
• User Type
  • Buyer
  • Supplier
• Enablement Model
  • Customer configured

This feature allows buyers to engage and negotiate contractual terms with suppliers involved in a guided sourcing project during the commercial negotiation phase or after an initial assessment. The pre-award negotiation process enables buyers to define the necessary terms and conditions of their sourcing requirement using a baseline contract. The baseline contract serves as the foundation for suppliers to bid and subsequently enables buyers to negotiate with the selected suppliers.

Buyers can create or update a baseline contract from the guided sourcing interface or using open APIs included in the Contract Workspace Management APIs. A baseline contract can be associated with a guided sourcing project at any stage until the project is awarded.

To negotiate with suppliers participating in the guided sourcing project, buyers can create supplier contracts. A supplier contract is a copy of the most recent baseline contract that is published. It contains the header data and documents, including the Main Agreement and the Contracts Line Items Document (CLID), from the baseline contract.

Suppliers participating in the guided sourcing project can download the legal contract document (Main Agreement) attached to the baseline contract associated with the project. The legal contract document enables suppliers to review the terms and conditions outlined by the buyer user before submitting their bid response.

Buyers can publish a guided sourcing project depending on the status of the associated baseline contract. A guided sourcing project can be published only when the associated baseline contract meets the following conditions:

• It is in the Published state.
• It is inactive because its state changed to Expired or Closed.
• It is deleted.

After the guided sourcing project is awarded, buyers can update the baseline contract and the corresponding supplier contract with the awarded line item information.

• Your site must have guided sourcing enabled.
• Your site must have SAP Ariba Contracts integrated with SAP Ariba Sourcing.
• Your administrator must enable the Application.ACM.EnablePreAwardNegotiationInGuidedSourcing ICM parameter.
• If you create a baseline contract using open APIs, it must be associated with a valid guided sourcing project.
• To create supplier contracts in a guided sourcing project, the following conditions must be met:
  • The status of the baseline contract associated with the guided sourcing project must be Published.
  • The guided sourcing event must be in one of the following phases: Published, Monitor, Pending Selection, Review responses, Open, or Paused.

• This feature is applicable to guided sourcing projects of type Single event only. Guided sourcing projects of type Full project containing subprojects of type Single event that are configured for pre-award negotiation are not valid.
• Only one active baseline contract can be associated with a sourcing project. To associate a new baseline contract with a sourcing project that already has an associated active baseline contract, buyers must first change the status of the existing baseline contract to Closed or Expired before associating the new baseline contract.
• A baseline contract is not available for sourcing awards when buyers choose to add awarded line items to an existing contract with a supplier.
• A baseline contract cannot be amended after it is published.
• While updating a baseline contract using open API, the following attributes of a baseline contract workspace cannot be modified: Predecessor Project (eventInternalId), Baseline Contract (baselineContract), and Supplier (supplier).
• While creating a contract workspace (procurement), if you choose to copy data from an existing baseline contract, the Baseline Contract (baselineContract) attribute is not copied to the new contract workspace.

The Contract Workspace Modification API now supports the following new objects that buyers can include in the request body for creating or updating a baseline contract:

• baselineContract - A flag indicates whether the contract workspace is a baseline contract. When set to true, it is created as a baseline contract.
• eventInternalId - The predecessor sourcing project ID to associate with the baseline contract. Buyers must provide a valid predecessor sourcing project ID when baselineContract is set to true.

A new option Associated Contracts is added to the More actions menu in guided sourcing events. Selecting this option brings up the Associated Contracts page, as shown in the following screenshot.

Buyers can find the following information under the Baseline Contracts section:

• Document Title - The title of the baseline contract.
• Contract Status - The status of the baseline contract in SAP Ariba Contracts.If you have integrated your SAP Ariba instance with Icertis Contract Intelligence (ICI) for SAP Ariba Solutions, this column appears as Contract Status (ARIBA).
• Contract Status (ICERTIS) - (Optional) The status of the agreement created in ICI in correspondence to baseline contract. This field appears only if you have integrated your SAP Ariba instance with ICI.
• SAP Ariba ID - The unique identifier of the baseline contract. Buyers can choose the ID to navigate to SAP Ariba Contracts and review the baseline contract.
• Icertis ID - (Optional) The unique identifier of the corresponding agreement created in Icertis Contract Intelligence (ICI) for SAP Ariba Solutions. This field appears only if you have integrated your SAP Ariba instance with ICI.
• Effective Date - The effective date set for the baseline contract.
• Expiration Date - The expiration date of the baseline contract.
• Update - An option to sync the baseline contract with line item information updates from the sourcing event.

Buyers can create a baseline contract by selecting the Create Baseline Contract option.

The Supplier Contract panel contains two tabs, as displayed in the screenshot, below:

Under the Contracts tab, buyers can find the following information related to the supplier contracts created in the event:

• Supplier - The name of the supplier.
• Document Title - The title of the supplier contract.
• Contract Status - The status of the supplier contract.
• Contract Status (ICERTIS) - (Optional) The status of the agreement created in Icertis Contract Intelligence (ICI) for SAP Ariba Solutions in correspondence to baseline contract. This field appears only if you have integrated your SAP Ariba instance with ICI.
• SAP Ariba ID - The unique identifier of the supplier contract. Buyers can choose the ID to navigate to SAP Ariba Contracts and review the supplier contract.
• Icertis ID - (Optional) The unique identifier of the corresponding agreement created in Icertis Contract Intelligence (ICI) for SAP Ariba Solutions. This field appears only if you have integrated your SAP Ariba instance with ICI.
• Effective Date - The effective date set for the supplier contract.
• Expiration Date - The expiration date of the supplier contract.
• Update - An option to update a supplier contract with awarded line item information. This option is available only after a guided sourcing event is awarded.

Under the Creation History tab, buyers can find the following information:

• Supplier - The name of the supplier.
• Created On - The date and time when the supplier contract creation request was initiated.
• Status - The status of the contract creation request.
• Error Message - Details of the error encountered, if any, while creating a supplier contract.

A new page Review Legal Contract is added to the Event Details page. This page appears under the Checklist group after the step where suppliers review and accept the prerequisites outlined by the buyer, as shown in the following screenshot.

The Review Legal Contract page is available to suppliers when the following conditions are met:

• A baseline contract is associated with the event that they have chosen for participation.
• The baseline contract has a legal contract document added to it.
• The baseline contract is published.

• Applicable Products
  • SAP Ariba Strategic Sourcing Suite
• User Type
  • Buyer
  • Supplier
• Enablement Model
  • Automatically on

This feature introduces support for basket lots with linked items in supplier alternative bids.

You can link a line item that already exists in a guided sourcing event with a basket lot, creating a basket lot with linked items (also known as a prepack). A copy of the linked item is added to the lot, and this remains linked to the source line item outside the lot, so any changes that are made to the price term in the line item outside the lot are also reflected in the line item copy inside the lot.

When you link an item to a lot, a copy of the line item that already exists outside the basket lot is added to the lot. The line item copy inside the lot is linked to the source line item so that any changes that are made to the price term in the line item outside the lot are also reflected in the line item copy inside the lot.

The quantity term is the only term that is editable for item copies within the lot. The value of every other term is copied over to the copied item within the lot and cannot be edited in the copy. If an initial value was set for quantity in the source term, that is copied with the lot in the first instance, but this can be edited in the item copy.

• Your site must have guided sourcing enabled and you must be a member of the Category Buyer group.
• For article master functionality, your site must have Category Attribute Hierarchy enabled.

Basket lots with linked items are now supported in supplier alternative bids.

If the template that your sourcing event is based on is configured for basket lots with linked items (also known as prepacks), you can use the following procedure to link items that exist already in an event to a basket lot:

1. Open a guided sourcing event for editing. If the event is published, choose the More actions icon in the upper-right corner of the event page and select Event options → Edit event.
2. Go to the Items that need quotes panel and select the More icon for the lot to which you want to link an item and select Link item.

   The Select Basket Items popup opens.

3. Select the item that you want to link to the lot and select Save.

A member of the global Template Creator group or the template project’s Template Creators team group must add a basket definition within the event template using the following procedure:

1. Select Manage → Templates.
2. On the Documents tab, select the name of the sourcing template in which you want to configure linked items and choose Action → Open.
3. Select the template document in the Documents area and select View Details.
4. On the Definitions tab, do one of the following:
   • If there is no basket lot in the template and you are adding one, select Add → Lot and go to step 5.
   • If you are editing an existing basket lot of type Basket - Bid at Lot level, compete at Lot level (collect item pricing post bidding), select the basket lot name, choose Edit, and then go to step 6.
5. In the Lot Type field, select Basket - Bid at Lot level, compete at Lot level (collect item pricing post bidding).
6. Select Yes in the Link Items field.

   The following screenshot illustrates steps 5 and 6: