sap ariba applications q2 2019 release guide

CONFIDENTIAL2019-04

SAP Ariba Applications Q2 2019 release guide

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

Feature enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7SM-11786: API enhancements related to supplier IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SM-11786: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8CP-10389: Field names and descriptions for reportable fields extracted by the SAP Ariba Operational Reporting API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9CM-1223: SAP Ariba APIs to update and fetch status of lookups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Workflow for the Lookup upload API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Workflow for the Lookup status API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

SAP Ariba Procurement solutions features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13SINV-5980: Support for ‘U’ (Unknown) account assignment category for service items. . . . . . . . . . . . . . 13

SINV-5980: Workflow overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17SINV-5980: User tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Data import changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17cXML changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

CP-10715: Display order confirmation review task in the To Do list of purchasing managers. . . . . . . . . . . .19Information for administrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

CP-9209: Create and manage requisitions using Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20CP-9209: Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21CP-9209: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21CP-9209: Information for users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22CP-9209: User tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

OPCCC-564: Asynchronous remittance import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35OPCCC-565: Asynchronous receipt import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36OPCCC-592: Enhanced charge reconciliation for purchasing card orders. . . . . . . . . . . . . . . . . . . . . . . . 37OPCCC-610: Support for customizing user profile change request approval flows to add additional approvers when users add or change groups in their user profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37OPCCC-645: Import of generic addresses for SAP integrated sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Import Addresses data import task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39CM-1048: Support for determining catalog item prices dynamically. . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Workflow for support for determining catalog item prices dynamically. . . . . . . . . . . . . . . . . . . . . . . 41CM-1048: Use case scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41How to create price lookup keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

CM-4106: Catalog filename-based filtering of catalog data extraction in JSON format. . . . . . . . . . . . . . . 43SB-7208: New Spot Buy network seller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2 C O N F I D E N T I A LSAP Ariba Applications Q2 2019 release guide

Content

How to add a buyer email address for Walmart orders through Spot Buy. . . . . . . . . . . . . . . . . . . . . .44GB-2965: Add approvers and watchers without editing requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

GB-2965: User tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45GB-3223: Guided buying can show multiple validation policy violations during check out . . . . . . . . . . . . 47GB-4536: Display warnings from the Validating and enriching API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47SINV-6042: Evaluated receipt settlement (ERS) and automatic invoicing for service items. . . . . . . . . . . 48

SINV-6042 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49SINV-6042: Workflow to procure service items flagged for ERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50SINV-6042: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50User tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52SINV-6042: Information for administrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54SINV-6042: cXML changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

SINV-6221: Links to eForms in invoice documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Options for eForm linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

SINV-6857: Enhancements to accounting export and import for invoices. . . . . . . . . . . . . . . . . . . . . . . . 57Worksheet validation for accounting distributions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58SINV-6857: Site configuration options for accounting export and import for invoices. . . . . . . . . . . . . 62

SINV-7199: Goods receipt-based invoice verification without ship notice IDs. . . . . . . . . . . . . . . . . . . . . .62Workflows for goods receipt-based invoice verification for invoices without ship notice IDs. . . . . . . . . 63SINV-7199: Site configuration options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SAP Ariba Strategic Sourcing and Supplier Management solutions features. . . . . . . . . . . . . . . . . 66OPCCC-483: Support for custom relationships between fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Workflow for setting up custom relationships between fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68How to deactivate relation entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Data import task for establishing a relationship between two fields. . . . . . . . . . . . . . . . . . . . . . . . . .69Data import task for mapping values in one field to values in another field. . . . . . . . . . . . . . . . . . . . . 69

SS-3414: Enhanced envelope bidding with improved team control for access. . . . . . . . . . . . . . . . . . . . . 70SS-3451: Update live events from Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

How to update published events from an Excel document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72SS-890: Support header-level integration fields in Import Sourcing Project requests. . . . . . . . . . . . . . . . 74

SS-890: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75SS-9766: Send participant responses to event questions in award data . . . . . . . . . . . . . . . . . . . . . . . . . 76

Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77SSR-594: ERP integration for article variant and single article creation. . . . . . . . . . . . . . . . . . . . . . . . . 79

How to add a single article from SAP Ariba Sourcing to an external ERP. . . . . . . . . . . . . . . . . . . . . . 80How to add an article variant from SAP Ariba Sourcing to an external ERP. . . . . . . . . . . . . . . . . . . . . 81

DMS-7175: Ability to get quotes on entire BOM in product sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82DMS-7175: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83User tasks for ability to get quotes on entire BOM in product sourcing. . . . . . . . . . . . . . . . . . . . . . . 84

DMS-7183: Default 100% AML split for parts with one AML supplier. . . . . . . . . . . . . . . . . . . . . . . . . . . 86DMS-7183: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

SAP Ariba Applications Q2 2019 release guideContent C O N F I D E N T I A L 3

DMS-7303: Enhanced product sourcing UI tables for material and BOM views. . . . . . . . . . . . . . . . . . . . 88DMS-7303: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89User tasks for enhanced product sourcing UI tables for material and BOM views. . . . . . . . . . . . . . . . 93

DMS-7977: Ability to use reserve price, conditional visibility of questions, and multi-currency support for large-capacity events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

DMS-7977: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Workflow for large-capacity events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99User tasks for ability to use reserve price, conditional visibility of questions, and multi-currency support for large-capacity events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

DMS-8450: Product Sourcing dashboard data table filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106DMS-8450: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

DMS-8513: Ability to have UOM in product sourcing simple RFx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108DMS-8962: Product Sourcing user interface enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

DMS-8962: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109DMS-9020: Ability to import Material Group information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

DMS-9020: Changes to the existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111DMS-9022: Ability to access Material 360 View without using Product Sourcing dashboard. . . . . . . . . . 112

DMS-9022: Changes to the existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113DMS-9209: Custom fields enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

How to map custom fields for getting quotes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114How to create an event template with custom fields for getting quotes. . . . . . . . . . . . . . . . . . . . . . .115How to create an event template with custom fields for PIR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Custom fields in export pricing updates web service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117Custom fields in outbound PIR messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

DMS-9523: BOM hierarchy and BOM split export enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . .120DMS-9523: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

SC-5081: Mass application of conditions in an assembled contract document. . . . . . . . . . . . . . . . . . . . 121How to mass-apply conditions in an assembled contract document. . . . . . . . . . . . . . . . . . . . . . . . .121

Bulk-loading conditions with Microsoft Excel import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Using predefined and custom fields when you bulk-load conditions in a Contract Workspace template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

SC-5088: Manage individual redlining changes inline in Enhanced Contract Authoring. . . . . . . . . . . . . .129SC-5088: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

SC-5103: Increase the 100 MB attachment and document size limitation for contracts to 2 GB. . . . . . . .130SC-5159: Mass upload contract documents to multiple workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . 131

SC-5159: Administrator interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133How to mass upload contract documents to multiple workspaces by using the project mass edit utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133How to view the status of mass upload of contract documents to multiple workspaces. . . . . . . . . . . 134How to mass upload contract documents by using the edit template option. . . . . . . . . . . . . . . . . . .135

SC-3299: Commodity price escalation management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138


Content

Administrator Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140User Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

ARI-4402: Risk exposure configuration moved to UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144ARI-4402: Administrator interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145How to select data sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147How to set category weights and thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147How to define values and risk exposures for fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

ARI-4598: Enhanced workflow for sending questionnaires in control-based engagement risk assessment projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

ARI-4598: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151ARI-4598: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152How to send assessment questionnaires for a control-based engagement risk assessment project (enhanced workflow). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

ARI-4666: Increased variability in risk exposure measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156ARI-4946: Ability to upload status and expiry dates of offline risk assessments. . . . . . . . . . . . . . . . . . . 157

ARI-4946: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Risk assessment status data import file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

ARI-5268: Support for analytical reporting on control-based engagement risk assessment projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Analytical reporting for control-based engagement risk assessment projects. . . . . . . . . . . . . . . . . . 163ARI-5268: Changes to reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

ARI-5428: New Risk Control Summary report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176How to run the Risk Control Summary report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

ARI-5531: Risk control mappings based on inherent risk screening scores. . . . . . . . . . . . . . . . . . . . . . .178ARI-5531: Changes to data import and export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

ARI-5567: Presentation of Korean-language adverse media in SAP Ariba Supplier Risk. . . . . . . . . . . . . . 181SM-11787: Enhancements to supplier request duplicate checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

How duplicate checks work in submitted supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

SAP Ariba Applications Q2 2019 release guideContent C O N F I D E N T I A L 5

Feature enablement

Features are enabled by default unless specified otherwise. When action is required to enable a feature, the information is in the "Enabling this feature" section.


Feature enablement

APIs

SM-11786: API enhancements related to supplier IDs [page 7]

CP-10389: Field names and descriptions for reportable fields extracted by the SAP Ariba Operational Reporting API [page 9]

CM-1223: SAP Ariba APIs to update and fetch status of lookups [page 10]

SM-11786: API enhancements related to supplier IDsDescription

Products: SAP Ariba Supplier Lifecycle andPerformanceSAP Ariba Supplier Information and PerformanceManagement (new architecture)

Audience: Buyers

Enablement: Customer enabled or configured

This feature introduces the following enhancements to the Supplier Data API, the Supplier Data API with pagination, and the External Approval API for Sourcing and Supplier Management:

Enhancement Applicable APIs

Ability to retrieve data for specific suppliers. Supplier Data APISupplier Data API with Pagination

Ability to retrieve supplier IDs associated with questionnaires, tasks, and supplier management projects so that results returned by the API can be mapped back to third-party systems.

External Approval API for Sourcing and Supplier Management

Prerequisites

You must be registered with the SAP Ariba developer portal and have access to the applicable APIs.

Changes to existing functionality

See SM-11786: Changes to existing functionality [page 8].

SAP Ariba Applications Q2 2019 release guideAPIs C O N F I D E N T I A L 7

SM-11786: Changes to existing functionality

Changes to the Supplier Data API and the Supplier Data API with Pagination

In the request body posted by the searchSuppliers endpoint (Supplier Data API) and vendors endpoint (Supplier Data API with Pagination), a new name:value array allows you to filter request output by one or more specific suppliers:

Name:value array Valid values

smVendorIds One or more valid SM vendor IDs for suppliers in your site, separated by commas.

The following request body retrieves questionnaire titles, IDs, and types for two specific suppliers in JSON format:

{ "outputFormat":"JSON", "withQuestionnaire": true, "smVendorIds": ["S1004848","S1004834"] }

Changes to the External Approval API for Sourcing and Supplier Management

The supplier key in the body of all responses for the GET method for External Approval API endpoints now includes supplier IDs. In addition to the existing smVendorId name:value pair, it includes a new s4SystemId name:value pair that specifies a unique identifier that SAP Ariba assigns to the supplier. It also includes a new vendorIds array that lists sourcesystem:id name:value pairs for any IDs assigned to the supplier in different domains, including:

sourcesystem Description

buyersystemid The S4 organization system ID for the supplier, which is automatically generated by SAP Ariba. If a supplier is subsequently synchronized to an integrated ERP system, the ERP vendor ID is copied to this source system.

duns D-U-N-S number

networkid Ariba Network ID

sourcingnetworkid Ariba Network ID related to fulfillment relationship

sap An SAP ERP system

oracle An Oracle ERP system

psoft A PeopleSoft ERP system

For example:

"supplier": { "S4SystemId": "ACM_12345", "smVendorId": "S12345678", "name": "ABC, Inc.",


APIs

"vendorIds": [ { "sourceSystem": "buyersystemid", "id": "123456789" }, { "sourceSystem": "duns", "id": "987654321" }, { "sourceSystem": "networkid", "id": "5678901234567" }, { "sourceSystem": "sap", "id": "123456789" } ] },

CP-10389: Field names and descriptions for reportable fields extracted by the SAP Ariba Operational Reporting API

Products: SAP Ariba APIs

Audience: Buyers

Enablement: Automatically on

Previously, reports in JSON format extracted by the Operational Reporting API did not include field names (or labels) and descriptions for fields containing procurement data.

Starting with this release, reportable data extracted by the Operational Reporting API include field names and descriptions to provide more information about the fields containing procurement data. This enhancement is available in reports extracted for the following transactions:

● Requisitions● Purchase orders of the following types:

○ Direct orders○ Copy orders○ ERP orders

● Receipts

Additional references

See Operational reporting API for procurement for information about extracting reports on procurement data using the Operational Reporting API.


CM-1223: SAP Ariba APIs to update and fetch status of lookupsDescription

Products: SAP Ariba Procurement solutions

This feature is available only in sites enabled for managing catalogs using the content management system (CMS).

Audience: Buyers

Enablement: Customer configured

The API set provided by this feature enables your application to update existing lookups in SAP Ariba solutions by uploading new lookup files. It also enables you to fetch the status of lookups from SAP Ariba solutions. The following APIs are available:

Lookup upload API uploads lookup files to the content management system (CMS) in SAP Ariba solutions to update existing lookups

Lookup status API fetches the status of lookups from the content management system (CMS) in SAP Ariba solutions

NoteThis API set does not create new lookups in SAP Ariba solutions.

Prerequisites

Before you can use this API set, you must

● Complete the onboarding process on the SAP Ariba developer portal● Ensure that your application conforms to expected OAuth authentication. Only applications approved by the

SAP Ariba APIs administration can execute OAuth authentication.See the Authentication section of the SAP Ariba developer portal documentation for details.

● Configure the oAuth client ID in your SAP Ariba solution.When you create the client application in the Open API portal, an OAuth client ID is generated after SAP Ariba reviews and approves your application. You must then navigate to Catalog Administration Catalog Content Manager Open API Auth ID in your SAP Ariba solution and update the OAuth client ID.

● Create one or more lookups in the content management system (CMS) in SAP Ariba solutions.After a first version of a lookup is activated, you can use the lookup upload API to update it.


APIs

Workflow for the Lookup upload API

This API enables your application to upload lookup files to the content management system (CMS) in SAP Ariba solutions to update existing lookups.

1. The client application sends a POST request to update a specific lookup, with the lookup file attached as part of the request.The following is a sample POST request:

'/lookup?lookupname=testlookup1' (a lookup file needs to be attached with this request). Sample Curl request (generated by Postman) to :curl -X POST '/lookup?lookupname=testlookup1' -H 'apikey: 4a13afxxxxetc' -H 'authorization: Bearer c26d7-yyyy-zzzz-etc' 'cache-control: no-cache' -H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' -H ' -H 'realm: ' -F [email protected]" We have not provided any curl request

2. The SAP Ariba solution sends a response to this request indicating whether the file upload was accepted or not. It also returns a unique ID for the lookup version if the import was successful.The following is an sample response from the API:

{ "lookupname":"testlookup1", "message":"Lookup File Accepted", "id":"39994868-7d97-4b3d-9008-dfac45bfcc95"}

Workflow for the Lookup status API

This API enables your application to get the status of a specific lookup in the SAP Ariba solution. This API can be used to check whether a lookup file has been successfully activated, or if it failed parsing or validation.

1. The client application sends a GET request to fetch the status of a specific lookup. The request contains the lookup name and unique ID of the version.The following is a sample request:

'/lookup?lookupname=testlookup1&id=39994868-7d97-4b3d-9008-dfac45bfcc95

2. The SAP Ariba solution sends a response to this request by providing the status of the lookup version. Status can be any one of the following: Parsing, Active, Failed, or Deactivated. The status also captures the last modified time of the lookup version.The following is an sample response from the API:

[ { "lookupname": "testlookup1", "lastmodifiedtime": "2017-11-17 11:56:05", "status": "Active", "id": "39994868-7d97-4b3d-9008-dfac45bfcc95" } ]

If the GET request contains only the lookup name and not the unique ID of the lookup version, then the response contains statuses of all versions of that lookup. Sample response is as follows:

[ { "lookupname": "testlookup1", "lastmodifiedtime": "2017-11-03 14:10:59", "status": "Deactivated", "id": "00c74c8f-7ce2-4060-acd4-6fb2e525cf44" }, { "lookupname": "testlookup1", "lastmodifiedtime": "2017-11-17 11:36:06", "status": "Deactivated", "id": "078f96b3-5bf5-4fa1-8105-8fce9c741e41" },


{ "lookupname": "testlookup1", "lastmodifiedtime": "2017-09-21 17:29:17", "status": "Deactivated", "id": "1f65f5bd-3ed5-4456-a2fe-c1fbcee29b32" }, { "lookupname": "testlookup1", "lastmodifiedtime": "2017-11-17 11:56:05", "status": "Active", "id": "39994868-7d97-4b3d-9008-dfac45bfcc95" }]


APIs

SAP Ariba Procurement solutions features

SINV-5980: Support for ‘U’ (Unknown) account assignment category for service items [page 13]

CP-10715: Display order confirmation review task in the To Do list of purchasing managers [page 19]

CP-9209: Create and manage requisitions using Microsoft Excel [page 20]

OPCCC-564: Asynchronous remittance import [page 35]

OPCCC-565: Asynchronous receipt import [page 36]

OPCCC-592: Enhanced charge reconciliation for purchasing card orders [page 37]

OPCCC-610: Support for customizing user profile change request approval flows to add additional approvers when users add or change groups in their user profile [page 37]

OPCCC-645: Import of generic addresses for SAP integrated sites [page 38]

CM-1048: Support for determining catalog item prices dynamically [page 40]

CM-4106: Catalog filename-based filtering of catalog data extraction in JSON format [page 43]

SB-7208: New Spot Buy network seller [page 43]

GB-2965: Add approvers and watchers without editing requests [page 45]

GB-3223: Guided buying can show multiple validation policy violations during check out [page 47]

GB-4536: Display warnings from the Validating and enriching API [page 47]

SINV-6042: Evaluated receipt settlement (ERS) and automatic invoicing for service items [page 48]

SINV-6221: Links to eForms in invoice documents [page 55]

SINV-6857: Enhancements to accounting export and import for invoices [page 57]

SINV-7199: Goods receipt-based invoice verification without ship notice IDs [page 62]

SINV-5980: Support for ‘U’ (Unknown) account assignment category for service itemsProducts: SAP Ariba Buying and Invoicing (integrated with SAP ERP)

SAP Ariba Buying (integrated with SAP ERP)

Ariba Network

Audience: Buyers having access to SAP-integrated sites

Integrated suppliers and suppliers having access to SAP Ariba Buying or SAP Ariba Buying and Invoicing

Enablement: Contact SAP Ariba to enable

SAP Ariba Applications Q2 2019 release guideSAP Ariba Procurement solutions features C O N F I D E N T I A L 13

It is often a case that buyer users while creating requisitions are not certain of the appropriate account assignment category to which a line item’s expenditure is to be assigned. In such cases, users randomly assign an account assignment category for the line items to be able to submit their requisitions. This often leads to accounting mismatch errors when account assignment category information on service sheets and invoices do not match with orders.

Starting with this release, users can choose U (Unknown) as the value for the Account Assignment field for service line items on requisitions. The value U (Unknown) corresponds to the definition of Unknown account assignment category in SAP ERP and SAP S/4HANA. Users can specify this value only for line items that have item category as D (Services).

If the value for the Account Assignment field for line items is U (Unknown), the buying solution does not perform validations for account assignment category and allows users to submit their requisitions. The buying solution triggers validations only when buyer or supplier users submit service sheets to ensure that they replace the value U (Unknown) with the appropriate account assignment category values. For sites that are not configured to trigger validations for accounting information on service sheets, or if the service sheet process is not mandatory, the buying solution triggers validations for Account Assignment field values when users submit invoices.

With this feature, the buying solution can also be configured to default the account assignment category value from the first line to the other consecutive lines in service sheets created by supplier users. When this feature is enabled, the Account Assignment field of only the first line in the service sheet is editable. Any changes made to this field value in the first line will be propagated to the rest of the lines, and all associated accounting field values are also reset. Supplier users can still edit the other accounting-related fields. However, in certain cases where the accounting information in the service sheet is inherited from the associated purchase order, you may want to restrict supplier users from editing the accounting information. A site configuration option is available to configure this functionality.

Prerequisites

● Customer administrators must define the Unknown account assignment category in the AccountCategory.csv file used by the Import Account Categories data import task and then import the file. For more information, see Data import changes [page 17].

● By default, suppliers are not allowed to edit accounting information for line items on service sheets on Ariba Network after they punch in to add items on service sheets. If you require suppliers to replace the Unknown account assignment category value with the appropriate values, your site must be configured to allow suppliers to edit accounting information for line items on service sheets. For help with this configuration, please contact SAP Ariba Customer Support.

● The new transaction rule Require suppliers to provide account assignment information must be enabled on Ariba Network to ensure that suppliers while submitting service sheets replace the value U (Unknown) with the appropriate account assignment category values.If this transaction rule is enabled, Ariba Network rejects cXML service sheets that do not contain the appropriate account assignment category. Therefore, integrated suppliers working with buyer organizations that do not use SAP Ariba Buying or SAP Ariba Buying and Invoicing as their buying solution must collaborate with their buyers to ensure that cXML service sheets sent to Ariba Network contain the appropriate account assignment category.For more information about configuring transaction rules, see the Ariba Network buyer administration guide.

● Your site must be configured to enable supplier users to edit accounting fields while they add shopping cart items to service sheets during punch in from Ariba Network. SAP Ariba sets this option for you.

14 C O N F I D E N T I A LSAP Ariba Applications Q2 2019 release guideSAP Ariba Procurement solutions features

SINV-5980: Workflow overview

SINV-5980: Workflow for support for ‘U’ (Unknown) account assignment category for service items (service sheet-based invoicing) [page 15]

SINV-5980: Workflow for support for ‘U’ (Unknown) account assignment category for service items (PO-based invoicing without service sheets) [page 16]

SINV-5980: Workflow for support for ‘U’ (Unknown) account assignment category for service items (service sheet-based invoicing)

The following is a high-level workflow of an ordering process for service items specified with the Unknown account assignment category in which invoices are created based on processed service sheets:

1. A buyer completes the following tasks:○ Creates a service requisition.○ (If the user is not certain about the account assignment category value for a service item) Edits the

accounting information for the service line item and chooses the Account Assignment field value as U (Unknown).

○ Submits the requisition for approval.2. The SAP Ariba solution creates a service purchase order after it is fully approved.3. The supplier starts the activities required to fulfill the service.4. If the buyer creates service sheets, the following steps apply:

1. The SAP Ariba solution validates the Account Assignment field value on the service sheet and flags errors for line items that have U (Unknown) as the account assignment category value.

2. The buyer user replaces the U (Unknown) value for the Account Assignment field with appropriate account assignment category values and then submits the service sheet.

3. All approvers in the approval flow for the service sheet complete their approvals in the SAP Ariba solution.4. The buyer creates an invoice based on the approved service sheet.

5. If the supplier submits service sheets, the following apply:○ For sites that do not allow suppliers to edit accounting information on service sheets, the SAP Ariba

solution does not validate the Account Assignment field for line items for which the account assignment category value is specified as U (Unknown). In this case, buyers while approving supplier-submitted service sheets are forced to replace the U (Unknown) value with the appropriate account assignment category values.

○ For sites enabled to allow suppliers to edit accounting information on service sheets, the following steps apply:1. The SAP Ariba solution validates the Account Assignment field value on the service sheet and flags

errors for line items that have U (Unknown) as the account assignment category value.2. The supplier punches in to the SAP Ariba solution (SAP Ariba Buying or SAP Ariba Buying and

Invoicing) to replace the Unknown value with appropriate values for the required line items. The supplier then submits the service sheet.

3. All approvers in the approval flow for the service sheet complete their approvals in the SAP Ariba solution.


The supplier creates an invoice based on the approved service sheet.

SINV-5980: Workflow for support for ‘U’ (Unknown) account assignment category for service items (PO-based invoicing without service sheets)

The following is a high-level workflow of an ordering process for service items specified with the Unknown account assignment category in which PO-based invoices are created without creating service sheets:

1. A buyer completes the following tasks:○ Creates a service requisition.○ (If the user is not certain about the account assignment category value for a service item) Edits the

accounting information for the service line item and chooses the Account Assignment field value as U (Unknown).

○ Submits the requisition for approval.2. The SAP Ariba solution creates a purchase order after the requisition is fully approved.3. The supplier starts the activities required to fulfill the service.4. If the buyer creates PO-based invoices, the following steps apply:

1. The SAP Ariba solution validates the Account Assignment field value on the invoice and flags errors for line items that have U (Unknown) as the account assignment category value.

2. The buyer user replaces the U (Unknown) value for the Account Assignment field with appropriate account assignment category values and then submits the invoice.

3. The SAP Ariba solution auto-generates a service sheet.4. All approvers in the approval flow for the service sheet complete their approvals in the SAP Ariba solution.

5. If the supplier submits a PO-based invoice, the following apply:○ For sites that do not allow suppliers to edit accounting information on invoices, the SAP Ariba solution does

not validate the Account Assignment field for line items for which the account assignment category value is specified as U (Unknown). In this case, buyers while approving supplier-submitted invoices are forced to replace the U (Unknown) value with the appropriate account assignment category values.

○ For sites enabled to allow suppliers to edit accounting information on invoices, the following steps apply:1. The SAP Ariba solution validates the Account Assignment field value on the invoice and flags errors

for line items that have U (Unknown) as the account assignment category value.2. The supplier punches in to the SAP Ariba solution to replace the Unknown value with appropriate

values for the required line items. The supplier then submits the invoice.3. All approvers in the approval flow for the invoice complete their approvals in the SAP Ariba solution.



User interface changes

User interface changes (SAP Ariba Buying and SAP Ariba Buying and Invoicing)

If specified in the accounting information section for line items, documents, such as requisitions, contracts, orders, service sheets, and invoices now display U (Unknown) as the value for the Account Assignment field. The value U (Unknown) corresponds to the Unknown account assignment category in SAP ERP and SAP S/4 HANA. Further, the corresponding email notifications for requisition approvals now include this value for the Account Assignment field.

Buyer administrator user interface changes (Ariba Network)

On the Default Transaction Rules page, Ariba Network displays a new rule named Require suppliers to provide account assignment information. By default, this rule is unchecked.

SINV-5980: User tasksHow to specify Unknown account assignment category for a line item on a requisition [page 17]

How to specify Unknown account assignment category for a line item on a requisition

Procedure

1. Open the requisition in which you want to specify the Unknown account assignment category for a line item.2. Click Edit.

3. Select the line item you want to edit and click Actions Edit Details .

The Line Item Details page appears.4. In the Accounting - by Line Item section, select U (Unknown) for the Account Assignment field.

5. Click OK.

Data import changesThe Import Account Categories data import task now supports the Unknown account assignment category.


The following is a sample of the AccountCategory.csv file used by this task in which the Unknown account assignment category is identified by the letter "U".

"UTF-8" KNTTP,FAUS1,KNTTX"A","----------**-----------+--------.-----------------*...-...............","Asset""F","---------..-------.-------------.-----------------+-..-...............","Order""K","---------+.---------------------.-----------------+-..-...............","Cost center""P","-----------.------.-------------.-----------------+-..-...............","Project" "U","------------------------------------------------------...............","Unknown"

cXML changes

cXML changes for purchase orders

The cXML of service orders sent to Ariba Network do not include the <Distribution> attribute for line items that have account assignment category value as Unknown.

cXML changes for service sheets

The cXML of service sheets include the <Distribution> attribute for line items that include account assignment category value. The following is a sample code snippet of the cXML of a service sheet containing the <Distribution> attribute:

<Distribution> <Accounting name="Default"> <AccountingSegment id="0000002100"> <Name xml:lang="en-US">Cost Center</Name> <Description xml:lang="en-US">ID</Description> </AccountingSegment> <AccountingSegment id="0000445000"> <Name xml:lang="en-US">GL Account</Name> <Description xml:lang="en-US">ID</Description> </AccountingSegment> <AccountingSegment id="100"> <Name xml:lang="en-US">Percentage</Name> <Description xml:lang="en-US">Percentage</Description> </AccountingSegment> </Accounting> <Charge> <Money currency="MXN">100</Money> </Charge></Distribution>


CP-10715: Display order confirmation review task in the To Do list of purchasing managersProducts: SAP Ariba Buying and Invoicing

SAP Ariba Buying

Audience: Buyers


Previously, for sites enabled for the enhanced order confirmation feature, the To Do list of members of the Purchasing Manager group did not include order confirmation review tasks even though they were eligible to review and accept supplier-proposed changes in order confirmation documents.

Starting with this release, the buying solution can be configured to ensure that order confirmation review tasks are displayed in the To Do list of users belonging to the Purchasing Manager group or any child groups assigned to the Purchasing Manager group.


See Purchasing guide for procurement professionals for information about managing change orders based on the enhanced order confirmation feature

Enabling this feature

This feature is available for all customers with the applicable solutions but requires customer steps to enable it. For information about how to enable and configure this feature, see the administrator topics.

Information for administrators

Customer administrator must enable the following self-service parameter:

Application.Procure.AddOCReviewInToDoListOfUserGroups

The Application.Procure.AddOCReviewInToDoListOfUserGroups parameter specifies the user groups that can also view the Review Order Confirmation tasks in their To Do lists, apart from the preparers and requesters of the associated requisitions.

NoteThe groups that can be selected for this parameter is the Purchasing Manager group or any child groups assigned to the Purchasing Manager group.


The default setting of this parameter is an empty list, meaning that only the To Do lists of the preparers and requesters of the associated requisitions can include view the Review Order Confirmation tasks.

CP-9209: Create and manage requisitions using Microsoft ExcelProducts: SAP Ariba Buying

SAP Ariba Buying and Invoicing

Audience: Buyers


Certain businesses handle large-sized requisitions that consist of several line items. Routine tasks, such as creating and updating requisitions become complex particularly if there are a varying mix of accounting combinations to be managed for line items on such large requisitions.

This feature enables users to take advantage of the functionalities available in Microsoft Excel workbooks to define the structure of requisitions in the offline mode and then import the Excel file in the buying solution to create, update, or cancel requisitions. Users can also perform bulk import operations to create, update, or cancel multiple sets of requisitions put together as Excel workbooks in a ZIP file format. In addition, users can export an existing requisition to their systems in Excel format and use it as a template to make changes to existing requisitions or create new requisitions by importing the Excel file.

Requisitions imported in Excel format are processed asynchronously in the buying solution meaning that such tasks are performed in the background and might take a few minutes to complete especially for ZIP files consisting of large number of Excel files. The buying solution assigns a job ID for each import operation using which users can track the status of the upload operation. Users can perform other tasks in the buying solutions and later check for the progress of the upload operation on the Upload History screen.

Prerequisites

See CP-9209: Prerequisites [page 21].


See CP-9209: Changes to existing functionality [page 21].

Information for users

See CP-9209: Information for users [page 22].


User tasks

See CP-9209: User tasks [page 31].

CP-9209: Prerequisites

● Users who import or export requisitions must have membership of the Import Requisitions group.● The maximum number of line items per requisition (including split accounting lines and tax lines) that can be

successfully imported using an Excel spreadsheet depends on the limit configured for your site. To configure the required limit, contact your Designated Support Contact and have them log a service request. An SAP Ariba Customer Support representative will follow up to configure your site accordingly.

● A ZIP file consisting of Excel workbooks for multiple requisitions must not include a directory structure.● In the default configuration, change orders are not allowed by importing requisitions in Excel format. To enable

this functionality, contact your Designated Support Contact and have them log a service request. An SAP Ariba Customer Support representative will contact you to enable it on your site.

● The Excel template has three sheets named Requisition Header, RequisitionDetail, and RequisitionSplitAccounting.

RememberDo not rename the worksheets in the Excel template. Excel templates with renamed worksheets might cause errors during import.

CP-9209: Changes to existing functionality

Functional changes

Previously, administrator users were allowed to create, update, or cancel requisitions using CSV files, web services, or cXML posts. With this release, members of the Import Requisitions group can create, update, or cancel requisitions by importing requisition data in Excel files.

New user group

This feature introduces a new Import Requisitions group. Members of this group can import and export requisitions using Excel spreadsheets.

NoteMembers of the existing Purchasing Agent group can also import and export requisitions using Excel spreadsheets.



With this feature enabled, the following are the changes to the user interface:

● When a user clicks Create Requisition on the dashboard, the SAP Ariba solution provides the following options to create or update a requisition:○ Manually on the user interface○ By uploading requisition data in an Excel workbook

● Requisitions include a new button named Excel Export. By clicking on this button, members of the Import Requisitions group can download an existing requisition in Excel format. After making the appropriate changes to the Excel file, users can re-import the file to update the requisition by clicking the Excel Import button.

● The Manage menu on the dashboard includes a new option named Upload History. This option enables users to view the status of a single requisition or multiple requisitions uploaded using the job ID on a new window named Upload History.The Upload History window provides the following information:○ The unique job ID assigned to an Excel file for a single requisition or the job ID assigned to a ZIP file

consisting of multiple Excel files.○ The time when a requisition was created.○ The file name for the uploaded Excel or ZIP file.○ The status of the upload operation. The status can be Pending, Processed, Completed, Completed with

Errors, or Failed.○ Details of errors if an upload operation failed or completed with errors.

CP-9209: Information for users

Important notes to consider when importing Excel spreadsheets:

● If the imported spreadsheet does not contain a value for the Operation field in the requisition header worksheet, a new requisition is created.

● You can only import a spreadsheet to create a new requisition or to modify an existing requisition that is in the Composing or Submitted state. If you import a requisition corresponding to a purchase order that is in the Ordered state, a new version of the requisition is created.

● If the imported spreadsheet contains a UniqueName and no new version exists for the requisition, the spreadsheet completely replaces the existing requisition.

● If the original requisition has been changed and a new version exists (in Composing state), a spreadsheet import does not allow changes to the following fields:○ On the requisition header sheet: Supplier○ On the requisition line item information sheet: Full Description, Supplier, Supplier Part Number, Supplier

Auxiliary Part ID, Unit of Measure, and Unit Price (for catalog items)● When creating requisition line items from a catalog in the user interface, the visibility of catalog items can be

controlled based on purchasing unit filtering of suppliers or catalog view constraints. This prevents users from adding items to a requisition they are not allowed to add. However, when users import a requisition and the requisition Excel spreadsheet includes such items, that requisition is processed successfully.


Fields that cannot be exported

Reviewers, please confirm if there are fields that are not exported.

About the requisition workbook format

Your SAP Ariba solution provides sample Microsoft Excel spreadsheets specific to ERP variants as a starting point to create new requisitions. The sample worksheets are located along with the documentation on SAP Ariba Connect. For information about how to download a sample worksheet, see How to download an Excel workbook template for requisitions from SAP Ariba Connect [page 31].

A typical Excel requisition workbook includes a requisition header sheet, a requisition item details sheet, and an accounting information sheet.

The following table lists the sheets in the requisition workbook.

Sheet name Description

Requisition Header Defines header-level information for a requisition.

RequisitionDetail Describes line-item information.

RequisitionSplitAccounting

Specifies accounting information for the line items.

NoteYou must not rename the sheets on an Excel workbook to make sure errors do not occur when you upload the file to create or update a requisition.

Related Information

Requisition header sheet [page 23]Requisition line-item details sheet [page 25]Accounting information sheet [page 29]

Requisition header sheet

This sheet contains requisition header information. In the Excel template, the sheet containing this information is named as Requisition Header.


Column Description

PreparerUniqueName The unique internal identifier of a user who creates a requisition.

RequesterUniqueName The unique internal identifier of a user that appears in the On Behalf Of field on the requisition.

SAPPlantUniqueName (Applicable for SAP ERP) The unique ID of the plant to which an item is to be shipped.

DefaultLineItem.ShipTo.UniqueName (Applicable for PeopleSoft ERP and Generic ERP)

The unique identifier for the Ship to address.

ERPRequisitionID The ID assigned to a requisition in the external ERP system from which the requisition is imported.

HoldTillDate The date until which processing of a fully approved requisition is withheld. Post-approval processes do not start until the specified Hold Until Date is reached.

ImportedHeaderCommentStaging A comment added at the header level of a requisition.

ImportedHeaderExternalCommentStaging A flag that shows whether a comment is external or not. If set to true, the comment will be visible to the supplier.

IsServiceRequisition Specifies whether a requisition is a service requisition.

IsShared Specifies whether a requisition is a team requisition.

IsTeamReceived Specifies whether a line item is enabled for team receiving.

LineItems Specifies the number of line items on a requisition.

Operation This field can contain one of the following values:

● New: Specifies that a new requisition must be created.

● Update: Specifies that a requisition must be updated.

● Cancel: Specifies that a requisition must be cancelled.

NoteIf this field is left blank, the buying solution considers this operation as a new requisition import.

OriginatingSystem The name of the external system from which a requisition is imported. If this field is left blank, the default is Imported. This value can be used to search for requisitions on the user interface.

OriginatingSystemReferenceID The ID of the external system from which a requisition is imported.

PreparerPasswordAdapter The password adapter of the user specified in the Preparer field on a requisition.

RequesterPasswordAdapter The password adapter of the user specified in the On Behalf Of field on a requisition.

ValidityEndDate The validity end date for a limit line item on a requisition.

ValidityStartDate The validity start date for a limit line item on a requisition.


Column Description

WorkOrderID Applicable for requisitions based on a workorder. Refers to the ID of the work order against which the requisition is created.

Name The title of a requisition.

DefaultLineItem.DeliverTo The user to whom a line item needs to be delivered.

DefaultLineItem.NeedBy The Need By date for a line item.

CompanyCode.UniqueName (Applicable for SAP ERP) The name of the SAP company code a user is mapped to.

BusinessUnit.UniqueName (Applicable for PeopleSoft ERP)

The business unit associated with a requisition.

Preparer.UniqueName The unique internal identifier for the preparer of a requisition.

Requester.UniqueName The unique internal identifier for the user on behalf of whom a requisition is created. Typically, the preparer and requester of a requisition is the same user. If a preparer creates a requisition for someone else, the requester is the user for whom the requisition is created.

UniqueName The unique ID of a requisition. Example: PR123.

Requisition line-item details sheet

This sheet contains information about line items on a requisition. This information is described in the RequisitionDetail sheet in the Excel template.

Column Description

AllowUsersToEditUnitPrice Indicates whether users are allowed to edit the unit price of line items on service sheets. This field can contain the value as Yes or No.

Line_Number The unique serial number for a requisition item.

Quantity The quantity for a line item.

DeliverTo The user name to whom the line item needs to be delivered.

CompanyCode (For SAP ERP) The unique internal identifier for the SAP company code.

Need_By_Date The date by which the item is required.

SplitAccountingType The type of split accounting, such as percentage, quantity or amount for the item.

Account_Assignment The unique internal identifier of the account assignment category for a line item.

ChargeAmount The total charge amount for a line item.

ChargeType The unique internal identifier for a charge type applied on a line item.


Column Description

BillTo The unique identifier for the Bill To address.

Commodity_Code The commodity code of the item.

Account_Type The type of account associated with the commodity code of a line item.

CommonCommodity_Code The UNSPSC commodity code for the line item.

Currency The currency applicable for the item.

PriceUnit The unit of measure for the unit price.

Unit_Of_Measure Unit of measure for the item.

ShipTo The unique identifier of the Ship To location.

Supplier The name of the supplier.

Supplier_Location The supplier location for the line item.

Domain The name of the domain for the system commodity code.

ExpectedValue.Currency.UniqueName The currency for the expected amount for a service item.

TaxCode The tax code defined in the external ERP system.

TaxCodeCountry The tax code applicable for a country.

Item_Category (For SAP ERP) The unique internal identifier for an item category in SAP ERP. An item category describes the characteristics and attributes of an item and controls the processing of the item. Examples of item categories include Material (for material goods) and Service (for services).

OverallLimit.Currency.UniqueName The currency of the overall limit for a line item.

Purchase_Group The unique identifier for a purchase group associated with a line item.

SAPPlant (For SAP ERP) The unique identifier for the plant to which the items are to be shipped. A plant is an operational unit within a company code.

Purch_Org The unique identifier for the purchasing organization associated with a line item.

Item_Description Description of the line item.

ItemPartNo Unique part number of the line item.

ItemAuxPartId Unique part auxiliary ID of the item.

ManPartNo The manufacturer's part number for the item.

BuyerPartNumber The buyer's part number for the item.

ContractId The ID of the contract associated with a line item.

UnitConversion The ratio used to convert the ordered unit to the price unit. The unit price is based on the price unit quantity and the price unit.

Unit_Price Unit price of the item.


Column Description

PriceUnitQuantity The quantity corresponding to the unit price of the item specified by the supplier. The unit price is based on the price unit quantity of the item.

PriceBasisQuantity The item quantity that the quoted unit price is based on. For example, the unit price might be 2 USD for a quantity of 10 but 3 USD for a quantity of five.

PriceBasisQuantityDesc The description that provides the details of pricing when an item’s unit price is determined using the quantity based pricing method.

PricingDescription The user-specified description for quantity-based pricing. Buyers can use the field to store any information on the unit conversion calculation.

DiscountAmount The total discount amount for a requisition. This value is calculated by adding discounts for all line items on a requisition. Discounts are indicated by negative values.

ERP_ITEM_NO The line number of the corresponding line item on the requisition in the external ERP system.

ExpectedValue.Amount The amount a service is expected to cost.

ServiceChild Indicates whether an item is a child item associated with a service parent item.

ItemType The value representing the line item type category, such as normal, composite, or item.

OriginatingSystemLineNumber The line item number in the external system from which the requisition is imported.

OriginatingSystem The ID of the external system from which a requisition is imported.

OverallLimit.Amount The maximum amount a service is expected to cost.

OverallLimit.ApproxAmountInBaseCurrency The approximate maximum amount a service is expected to cost in the base currency.

OverallLimit.ConversionDate The currency conversion date for a service line item for which an overall amount limit is specified.

ParentLineNumber The unique serial number for the parent service line item.

PaymentTerms The unique identifier of the payment terms.

ExpectedAmount The expected amount for a service item.

ExpectedAmountCurrency The currency for the expected amount for a parent line item.

MaximumAmount The maximum amount for a service item.

MaximumAmountCurrency The currency for the maximum amount for a parent line item.

IsServiceRequisition An indicator that specifies whether a requisition is flagged as a service requisition. This field can contain the value as Yes or No.


Column Description

IsShared An indicator that specifies whether a requisition is flagged as a team requisition. This field can contain the value as Yes or No.

IsTeamReceived An indicator that specifies whether a requisition is flagged for team receiving. This field can contain the value as Yes or No.

Operation Indicates whether a new requisition is to be created or an existing requisition is to be updated or deleted. The Operation column can include one of the following values:

● New: To create a new requisition.

NoteIf you do not specify any value for this field, the buying solution considers this operation as a new requisition import.

● Update: To edit an existing requisition.

● Cancel: To cancel or delete a requisition.

RequiresServiceEntry Specifies whether service sheets are required to record details of services performed by suppliers.

ServiceEndDate The end date of a service.

ServiceStartDate The start date of a service.

UniqueName The ID of the requisition. For example, PR123.

Contact_Id The ID of a contact person at the supplier location for the item.

ConversionDate The date on which the currency for a line item was converted.

ExpectedValue.ApproxAmountInBaseCurrency The approximate amount for a line item in the base currency.

Facility The location or any other logical entity that helps maintain multiple cross-references for a buyer part number.

ServiceChild Indicates whether a line item is a child line associated with a parent line item. This field can contain the value as Yes or No.

IsTaxOrDiscountLine Indicates whether a line item is a tax or a discount line item. This field can contain the value as Yes or No.

ItemType The value representing the line item type category. This field can contain the value as 1 (for normal item) or 2 (for composite item).

TaxAmount The amount of tax for a line item.

ERPRequisitionID The ID assigned to a requisition in the external ERP system.

Delay_Purchase_Until The date until which purchase of a line item must be delayed.

Amount The amount for a line item.

PreparerPasswordAdapter The password adapter of the preparer of the requester.

RequesterPasswordAdapter The password adapter of the requester of the requester.


Accounting information sheet

This sheet contains split accounting information. In the Excel template, the sheet containing this information is named as RequisitionSplitAccounting.

Column Description

SubNumber (Applicable for SAP ERP) The unique internal identifier of an asset line item.

NumberInCollection The line number of the split accounting. The line number must be unique for each split per line item.

Percentage (Applicable if split accounting type is specified as percentage) The percentage assigned to a split.

ProcurementUnit The unique internal identifier of a purchasing unit.

Quantity (Applicable if split accounting type is specified as quantity) The quantity of a split.

Amount.Amount (Applicable if split accounting type is specified as amount) The amount assigned to a split.

Currency The currency for the amount specified in the Amount field.

BusinessUnit.UniqueName (Applicable for Generic ERP)

The unique internal identifier of a business unit for a split.

Company.UniqueName (Applicable for Generic ERP) The unique internal identifier of a company for a split.

Project.UniqueName (Applicable for Generic ERP) The unique internal identifier of a project.

Region.UniqueName (Applicable for Generic ERP) The unique internal identifier of a region.

SubAccount.UniqueName (Applicable for Generic ERP) The unique internal identifier of a sub-account.

Department.UniqueName (Applicable for PeopleSoft ERP)

The unique internal identifier of the department for a split.

GL_Business_Unit (Applicable for PeopleSoft ERP) The unique internal identifier of the general ledger business unit for a split.

Location_Code (Applicable for PeopleSoft ERP) The location of the general ledger business unit for a split.

Product (Applicable for PeopleSoft ERP and Generic ERP) The unique internal identifier of the product for a split.

Statistics_Code (Applicable for PeopleSoft ERP) The unique internal identifier of the statistics code for a split.

Account The unique internal identifier of the account for a split.

CompanyCode (Applicable for SAP ERP) The unique internal identifier of the company code for a split line item.

Network (Applicable for SAP ERP) The unique internal identifier of the network for a split.

ActivityNumber The unique internal identifier of an Activity Number.

Asset.UniqueName (Applicable for SAP ERP) The unique internal identifier of an asset.

CostCenter (Applicable for SAP ERP) The unique internal identifier of the cost center for a split line item.

GeneralLedger (Applicable for SAP ERP) The unique internal identifier of the general ledger for a split line item.


Column Description

InternalOrder (Applicable for SAP ERP) The unique internal identifier of an internal order.

Network.UniqueName (Applicable for SAP ERP) The unique internal identifier of the network for a split line item.

WBSElement (Applicable for SAP ERP) The unique internal identifier of a WBS element.

Error messages for failed requisition import

The following table lists the error messages that are displayed when requisitions imported in Excel format fail:

Error message Cause

Importing service requisitions using Excel workbooks is not supported.

This feature does not support importing of service requisitions using Excel.

The preparer of the requisition and the logged in user do not match. The preparer of a requisition must be the same user who imports the Excel file.

The name of the user specified as the preparer in the Excel file and the logged in user who actually imports cannot be different, meaning that you as the preparer of a requisition cannot import an Excel file on behalf of another preparer.

Requisition was not created in the SAP Ariba solution because requisition {Requisition ID} with OriginatingSystemReferenceId {ID} already exists.

NoteOriginatingSystemReferenceId refers to the ID of the external system from which a requisition is imported. This field might not contain a value if a requisition is imported locally.

This error occurs if a user tries to create a new requisition using an Excel file in which the ID of an existing is specified. To successfully create new requisitions, the UniqueName column in the Excel file must be left blank.

Requisition {Requisition ID} with OriginatingSystemReferenceId {ID} could not be processed in the SAP Ariba solution because the current status of either the requisition or the associated orders does not support the import operation.

The ability to import requisitions depends on the status of an exisiting requisition or the associated orders. For example, you cannot import a requisition to perform an update operation if the requisition is in the Approved state in the buying solution and the corresponding order is in the Ordering state.

Could not perform the update operation for requisition {Requisition ID} with OriginatingSystemReferenceId {ID} as this requisition is incorrectly associated with one or more orders in the SAP Ariba solution.

The existing requisition is not associated with the appropriate purchase orders.

{Requisition ID} (OriginatingSystemReferenceId: {ID}) has one or more active amendments associated with it. Requisition could not be created in the SAP Ariba solution.

Applicable for sites enabled for creating simultaneous amendments for requisitions. The import operation fails if there are one or more in-process amendments for a requisition.

Requisition {Requisition ID} with OriginatingSystemReferenceId {ID} could not be canceled in the SAP Ariba solution due to unexpected errors.

The cancel operation fails when system errors occur. Contact your administrator for help.


Error message Cause

Requisition {Requisition ID} with OriginatingSystemReferenceId {ID} cannot be canceled because either the user does not have the required permissions or a new version of this requisition exists with errors generated in the external system.

This error occurs in one of the following cases:

● The user who performs the import operation does not have membership of the appropriate group to be able to cancel requisitions.

● A revised version of the requisition exists in the buying solution.

CP-9209: User tasks

Downloading a Microsoft Excel workbook template for requisitions [page 31]

How to create, update, or cancel requisitions by importing data in a Microsoft Excel file [page 32]

How to track the status of uploaded requisitions [page 33]

How to export a requisition in Excel format [page 34]

How to update a requisition using Excel import [page 34]

Downloading a Microsoft Excel workbook template for requisitions

How to download an Excel workbook template for requisitions from SAP Ariba Connect [page 31]

How to download an Excel workbook template for requisitions from the SAP Help Portal [page 32]

How to download an Excel workbook template for requisitions from SAP Ariba Connect

Procedure

1. Go to http://connect.ariba.com and log in. If you do not have a User ID and Password for SAP Ariba Connect, contact your SAP Ariba account executive.

2. On the Home page, click Product Information and Documentation.

The Resources, Documentation, Known Issues, Release Updates page appears.

3. On the left pane, click Procurement and Invoicing Documentation .

The Procurement and Invoicing Documentation page appears.4. Click Ordering and invoicing and download the Excel templates for requisitions.


http://help.sap.com/disclaimer?site=http%3A%2F%2Fconnect.ariba.com

How to download an Excel workbook template for requisitions from the SAP Help Portal

Prerequisites

Most of the documentation on the SAP Help Portal requires signing in with an S-user (SAP-user) ID. For more information about getting an S-user ID, see everything you need to know about S-User IDs .

Procedure

1. Go to the SAP Help Portal.

2. On the Home page, click Technology Platform and then click SAP Ariba SAP Ariba Procurement solutions .

The SAP Ariba Procurement solutions page appears.3. Under the References section, click Sample requisition and download the Excel template for requisitions.

How to create, update, or cancel requisitions by importing data in a Microsoft Excel file

Prerequisites

● Ensure that you have defined the required data in the Excel workbook template. For information about the fields defined in the Excel template, see About the requisition workbook format [page 23].

● Ensure that you have specified the appropriate values for the columns in the Excel file:○ The UniqueName column specifying the ID of a requisition must be blank if you want to create a new

requisition. If you want to update a requisition, this field must specify the ID of the requisition.○ The Operation column must include one of the following values:

○ New: To create a new requisition.

NoteIf you do not specify any value for this field, the buying solution considers this operation as a new requisition import.

○ Update: To edit an existing requisition.○ Cancel: To cancel or delete a requisition.

● To perform bulk import operations to create, update, or cancel multiple sets of requisitions, ensure that you define requisitions in separate Excel workbooks and put them together in a ZIP file format.


https://help.sap.com/viewer/p/SAP_Ariba

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sapanalytics.cloud%2Fresources-s-user-id%2F

https://help.sap.com/viewer/p/SAP_Ariba

Context

If you have a requisition defined in an Excel spreadsheet, you can upload it to create a new requisition. SAP Ariba recommends that you first create a requisition template, export it, and use this as the template to build up your requisition details for import.

Procedure

1. On the dashboard, click Create Requisition .2. Under What would you like to create?, click Upload Requisition.3. Click Browse to locate the Excel file. After you have identified the path to the file, click OK.

A requisition is created, and data imported using the Excel file is displayed on the requisition.4. Make any necessary modifications and click Submit.

The buying solution displays a job ID. Save the ID to track the status of the upload operation.

Next Steps

Check the status of the upload operation on your dashboard using the job ID. For more information, see How to track the status of uploaded requisitions [page 33].

How to track the status of uploaded requisitions

After you upload an Excel file for a single requisition or a ZIP file for multiple requisitions, the buying solution assigns a job ID for the upload operation. You can use the job ID to find whether or not the upload action was successful.

Context

The history for uploaded requisitions display one the following statuses:

● Pending: Indicates that upload operation is not complete.● Processing: Indicates that the upload operation is complete but creation of requisition is under process.● Completed: Indicates that requisitions are created successfully.● Completed with Errors: Indicates partial success, wherein, some requisitions were created successfully and

there were errors for the remaining.● Failed: Indicates that no requisitions could be created.


Procedure

1. On the dashboard, click Manage Upload History .2. On the Upload History window, enter the job ID, and click Search.3. Find the appropriate upload operation corresponding to the job ID and review the details.

How to export a requisition in Excel format

You can use the export functionality to download a requisition in Excel format. If required, you can edit the Excel file and import it again to update the requisition.

Procedure

1. In the My Documents content item on your dashboard, click the ID for the requisition.2. Click Excel Export.3. Click Open to open an Excel version of the requisition on your browser.

Click Save to save the Excel version of the requisition in its current form.

Related Information

How to update a requisition using Excel import [page 34]

How to update a requisition using Excel import

You can open a requisition and choose to update it by importing data in an updated Excel workbook.

Procedure

1. Open the appropriate requisition.2. If required, export the requisition in Excel format and make the necessary changes in the Excel file. For more

information about exporting a requisition in Excel format, see How to export a requisition in Excel format [page 34].○ The Operation column in the Excel file must include one of the following values:

○ Update: To edit an existing requisition.


○ Cancel: To cancel or delete a requisition.

3. Click Excel Import.4. Click Browse to locate the Excel file. After you have identified the path to the file, click OK.

○ The buying solution displays a job ID. Save the ID to track the status of the upload operation.○ If the inport operation is successful, the requisition is updated, and data imported using the Excel file is

displayed on the requisition.

Related Information

How to track the status of uploaded requisitions [page 33]

OPCCC-564: Asynchronous remittance importDescription

Products SAP Ariba Buying and Invoicing

SAP Ariba Invoice Management

Audience Buyers

Enablement Customer configured

Asynchronous remittance import applies to customers who have integrated their SAP Ariba Procurement solutions with their SAP back-end system through the SAP Ariba Cloud Integration Gateway. Remittance information can be imported from SAP back-end systems using the new web service remittance import task in SAP Ariba Buying and Invoicing or SAP Ariba Invoice Management. This task can be configured for use with SAP Ariba Cloud Integration Gateway.

Remittance information is a summary statement that provides details about a payment transaction that has been made. For example, a remittance statement might list all invoices included in a payment, the payment method used, bank information, discount information, and amount paid.

Each supplier location must have its own remittance location. When generating a payment request, SAP Ariba Procurement solutions use the remittance location associated with that supplier location. You cannot associate multiple supplier locations with the same remittance location, but you can associate multiple remittance locations with the same supplier location.

Prerequisites

Before using this feature, ensure the following:

● Support for the SAP Ariba Cloud Integration Gateway is enabled in your solution, and the corresponding parameter is turned on.


● Support for asynchronous integration events for the web service channel in SAP Ariba Cloud Integration Gateway is enabled in your solution.

Administrator interface changes

The Integration Manager workspace will have the new Import Remittances web service to import the remittance information from SAP back-end systems.

NoteThe end point URL for the new web service task must be configured in the buying solution from SAP Ariba. Customer administrators must enter the URL in the Integration Manager page.

OPCCC-565: Asynchronous receipt import

Description


SAP Ariba Buying

Audience Buyers

Enablement Customer configured

Asynchronous receipt import applies to customers who have integrated their SAP Ariba Procurement solutions with their SAP back-end system through the SAP Ariba Cloud Integration Gateway. Goods receipts can be imported asynchronously from SAP back-end systems using the new Import Receipts from an External Application Asynchronously web service data import task in buying solutions from SAP Ariba. This task can be configured for use with SAP Ariba Cloud Integration Gateway. This is different than the existing web service real-time receipt import task, which imports receipts in a synchronous manner.

Prerequisites

Before using this feature, ensure the following:

● The Realtime receipts import feature is enabled on your site.● Support for the SAP Ariba Cloud Integration Gateway is enabled in your solution, and the corresponding

parameter is turned on.● Support for asynchronous integration events for the web service channel in SAP Ariba Cloud Integration

Gateway is enabled in your solution.



The Integration Manager workspace will have the new Import Receipts from an External Application Asynchronously web service to import receipt information from SAP back-end systems.

NoteThe end point URL for the new web service task must be configured in the buying solution from SAP Ariba. Customer administrators must enter the URL in the Integration Manager page.

OPCCC-592: Enhanced charge reconciliation for purchasing card ordersDescription


SAP Ariba Buying

Audience Buyers

Enablement Contact SAP Ariba to enable

This feature enhances the charge reconciliation process for purchasing card orders by enabling reconciliation when only the purchasing card number is available in the imported charge (in the Charge.csv file). Previously, for charge reconciliation for purchasing card orders, both the purchasing card number and the order number were required in the Charge.csv file. The order number was used to find a matching purchase order in the buying solution from SAP Ariba. With this enhancement, even if the Charge.csv file does not have the order number, the buying solution will find the most recent purchasing card order corresponding to the purchasing card number.

OPCCC-610: Support for customizing user profile change request approval flows to add additional approvers when users add or change groups in their user profileDescription


SAP Ariba Buying


Audience Buyers


This feature allows customers to request SAP Ariba to use standard customization to customize user profile change request approval flows. This customization enables the addition of approvers to user profile change request approval flows when new groups are added to the user profiles, or when groups already added to the user profiles are changed.

OPCCC-645: Import of generic addresses for SAP integrated sites

Description

Products: SAP Ariba Buying and InvoicingSAP Ariba BuyingSAP Ariba Invoice Management

Audience: Buyers


This feature applies to customers who have integrated their SAP Ariba Procurement solutions with their SAP back-end system. Generic addresses can be imported from SAP back-end systems using the new Import Addresses data import task in SAP Ariba Procurement solutions.

The imported addresses can be used as shipping addresses or billing addresses in approvable documents. You can also import ad hoc addresses created by users in the SAP back-end system to avoid creating the same ad hoc addresses inSAP Ariba Procurement solutions. The imported ad hoc addresses will be available only to the users who created them.

Each address imported by the task will be associated with a specific company code. After you import the addresses, and they are available in your SAP Ariba Procurement solutions, you must run the existing Import Plant to Purchase Organization Mapping task to map the addresses to the corresponding purchasing organizations. This step ensures the imported addresses can be used when creating approvable documents. Alternatively, you can contact SAP Ariba Customer Support to enable a parameter that will ensure the imported addresses can be used without running the Import Plant to Purchase Organization Mapping task.

Prerequisites


The Import Addresses page data import task is available.


Changes to data import and export

● Import Addresses data import task [page 39]

Integration with external systems

The new data import task can be used to import addresses from SAP back-end systems using the SAP Ariba integration toolkit. It can also be run from the user interface of your SAP Ariba Procurement solutions.

To use this feature for address import, you must configure the Import Addresses task for use with the SAP Ariba integration toolkit.

Import Addresses data import task

The new Import Addresses task uses a CSV file to import generic address information from SAP back-end systems. The CSV file has the following columns:

Columns Description

CreatorStaging.UniqueName For ad hoc addresses, the unique identifier of the user who created the address.

CreatorStaging.PasswordAdapter The password adapter for the user who created the ad hoc address.

UniqueName The unique identifier of the address.

Name The name of the address.

Line1sLine12Line13

The street address lines.

PostalCode The ZIP code.

City The city.

StateStateCode

The state and state code.

Country The country.

ShipTo If set to True, the address is available only for ShipTo addresses.

BillTo If set to True, the address is available only for BillTo addresses.

PurchasingUnit If defined, the address is available only for the defined purchasing unit.


CM-1048: Support for determining catalog item prices dynamicallyDescription

Products: SAP Ariba Buying

SAP Ariba Buying and Invoicing

SAP Ariba Catalog

Audience: Buyers


This feature enables catalog managers to define different prices for a CIF catalog item based on different values of a mapped entity configured as a price lookupkey. The price of the item displayed in the catalog search results and item details pages is determined dynamically based on the business scenario and the value of the mapped price lookup entity. For example, if you define different prices for different regions, the price of the item to be displayed is determined by the region that the user is associated with.

Catalog managers can define different fields as the price lookup entities for the following different scenarios where catalog search is performed:

Scenario/Context Description

Catalog home page search (outside the context of a requisition)

User performs catalog search directly from the Catalog dashboard and there are no items in the cart. If the cart contains items that had been added previously but not checked out, then the context is a requisition scenario.

Requisition User in the process of creating a requisition from the Home dashboard clicks

Create Requisition and navigates to the catalog home page.

User performs catalog search directly from the Catalog dashboard and there are one or more items in the cart that had been added previously but not checked out.

NoteThe functionality provided by this feature is applicable only to the requisition and catalog home page search scenarios.

A new key, pricekey attribute for the PriceConfiguration CIF field has been introduced to enable this functionality. The following is an example of a PriceConfiguration field value with the pricekey attribute:

[{"articleprice"=[{"priceType"=net_customer;"priceKey"="3000";"priceamount"=800;"pricecurrency"=USD;"pricefactor"=1};{"priceType"=net_customer;"priceKey"="4000";"priceamount"=320;"pricecurrency"=USD;"pricefactor"=1}]}]

[{"articleprice"=[{"priceType"=net_customer;"priceKey"="3000";"priceamount"=800;"pricecurrency"=USD;"pricefactor"=1};{"priceType"=net_customer;"priceKey"="4000";"priceamount"=320;"pricecurrency"=USD;"pricefactor"=1}]}]


In this example, the price of the item is $800 USD if the value of the mapped price lookup entity is 3000 and is $320 USD if the value of the entity is 4000.

Administrator tasks

● How to create price lookup keys [page 42]

Workflow for support for determining catalog item prices dynamically [page 41]

CM-1048: Use case scenario [page 41]

How to create price lookup keys [page 42]

Workflow for support for determining catalog item prices dynamically

Configuring different prices for different values of a price lookup key involves the following high-level steps:

1. A catalog manager, based on the requirement, identifies the field to be used as the price lookup key and contacts the SAP Ariba Customer Support representative to configure the field to be available for selection when creating price lookup keys.If a new custom field is to be created, then the catalog manager contacts an SAP Ariba Customer Support representative to create the required field and configure it accordingly .

2. The catalog manager then navigates to Catalog Manager Catalog Views Add Price Lookup Key and creates the required price lookup key.

3. CIF catalogs with relevant prices are loaded to the SAP Ariba solution.4. A user performs a search for catalog items.

The prices of the items to be displayed are determined dynamically based on the context of the catalog search and the value of the field defined as the price lookup key.

CM-1048: Use case scenario

The following use case scenario illustrates how to specify different prices for an item based on the different values of the mapped price lookup entity and how the price of the item to be displayed during catalog search is determined dynamically.

Consider a business scenario where users procure items for Region A and Region B and the the price of the catalog item is dependent on the region that it is being procured for.

Catalog managers can define two different prices for an item; one for Region Aand the other for Region B and configure the Region field as the price lookup entity. When a user in the process of procuring items for Region A performs a catalog search, the price of the item defined for Region A is fetched dynamically and displayed.

When creating price lookup entities,SAP Ariba recommends that catalog managers define the same field as the price lookup entity for both the User and Requisition classes. This is to ensure that the same price is displayed to users when they search for items outside the context of a requisition or from within the context of a requisition.


Defining different prices for an item for different regions and configuring the Region field as the mapped price lookup entity involves the following high-level steps:

1. The catalog manager navigates to Catalog Manager Catalog Views Add Price Lookup Key and configures the Region field in the User and Requisition classes as the price lookup key.

2. The catalog manager then creates and loads a catalog with different prices for items defined in the PriceConfiguration field.Consider the following PriceConfiguration field value for this example:

[{"articleprice"=[{"priceType"=net_customer;"priceKey"="Region A";"priceamount"=800;"pricecurrency"=USD;"pricefactor"=1};{"priceType"=net_customer;"priceKey"="Region B";"priceamount"=320;"pricecurrency"=USD;"pricefactor"=1}]}]

In this example, the price of the item is $800 USD if the Region value is Region A and is $320 USD if the region is Region B.

3. A user in the process of procuring items for Region A searches the catalog for the specific item.4. Since the user is procuring for Region A, the SAP Ariba solution displays $800 USD as the price of the item.

How to create price lookup keys

You can define the fields available in the User and Requisition classes as price lookup keys. SAP Ariba recommends that you define the same field as the price lookup key for both the classes.

Procedure

1. On the dashboard, click Manage Core Administration .

2. Select Catalog Manager Catalog Views .3. Click the Add Price Lookup Key tab.4. Click Add Price Lookup Key to add a new price lookup key.5. Select the class that you want the price lookup to be based on. For example, select Requisition if you want to

create a price lookup key based on the fields available in the requisition class.

The Add Price Lookup Key page displays the list of available fields that can be selected as the price lookup entities. Custom fields that are configured to be selected as the price lookup entities are also displayed.

6. Identify the field that you want to specify as the price lookup entity and click Select.7. Click Add Price Lookup Key to add the field as the price lookup key.


CM-4106: Catalog filename-based filtering of catalog data extraction in JSON formatDescription

Products: SAP Ariba Catalog

Audience: Buyers


SAP Ariba Catalog sends relevant catalog data over HTTP in JavaScript Object Notation (JSON) format to external procurement systems (such as, SAP SRM) in response to full or delta catalog data extraction requests. By default, all catalog subscription data that has been validated and is available for search in the SAP Ariba Catalog user interface is available for extraction. There was no way to filter the data that is being sent based on specific catalog files

Now, catalog data that is sent from SAP Ariba Catalog can be filtered based on the associated catalog filenames. To filter data based on catalog filenames, you must specify a relevant value for the new CATALOGPREFIX parameter in the request from external procurement systems for catalog data extraction. Data from only those catalogs are extracted whose filename starts with the value speified as the CATALOGPREFIX.

A sample URL to punch in to SAP Ariba Catalog to extract catalog data from select catalog files is as follows:http://host:<port>/Buyer/downloadJson/<AN_ID>?PunchinId= <AN_ID>&UserId=<User_Id>&password=<pwd>&realm= <realm>&FUNCTION=downloadjson&CATALOGPREFIX=<keyword>

Limitations

This feature is applicable only to external procurement systems that integrate with SAP Ariba Catalog using OCI-based protocols.

SB-7208: New Spot Buy network sellerDescription

Products: SAP Ariba Buying with the Spot Buy capability

SAP Ariba Buying and Invoicing with the Spot Buy capability

Audience: Buyer



This feature allows buyers to purchase from Walmart.com through the Ariba Network seller channel on Spot Buy.

When Walmart is enabled as a network seller, it is listed as a seller in your Supplier Lists at Manage Spot Buy Administration Setup Marketplace Ariba Network , and you can turn it off as a marketplace from here by selecting the green checkbox button.

The email address input in the Buyer Options (SB Admin) helps associate the order placed to the customer’s Walmart.com account. Else end-users, when attempting to add to cart, will get an error msg. Emphasize that the Walmart.com email address needs to be the correct one to ensure customer admins can see their orders in their Walmart.com account info page.

Prerequisites

● The Ariba Network seller channel must be enabled at Manage Spot Buy Administration SetupMarketplace Ariba Network .

● You must have a Walmart account.● The buyer's email address that is associated with the Walmart account must be added under Buyer Options.

See How to add a buyer email address for Walmart orders through Spot Buy [page 44]. This is to associate orders placed through Spot Buy with the customer’s Walmart.com account. If this is not entered an error message is displayed. The Walmart.com email address entered must be correct so that administrators can see their orders on their Walmart.com account information page.

Limitations

This feature is only available in the United States.

How to add a buyer email address for Walmart orders through Spot Buy

The buyer email address associated with the Walmart account must be provided in order to associate orders with a customer.

Procedure

1. Log in to your SAP Ariba Buying solutions.

2. On the dashboard, click Manage Spot Buy Administration .

3. Select Setup Buyer Options .4. Enter the buyer email address under Walmart Account Info.


GB-2965: Add approvers and watchers without editing requestsDescription

Products: SAP Ariba Buying with the guided buying capability SAP Ariba Buying and Invoicing with the guided buying capability

Audience: Buyers


Guided buying allows users to add additional approvers and watchers to the approval flow when composing requests, which enables them to get feedback from additional employees. But, after submitting requests, users could add them only after they clicked Edit and Withdraw, which required edit permission. If they couldn't edit requests, they couldn't add additional approvers or watchers.

Now, users can add additional approvers and watchers without editing requests. Any user who can view a requests (requesters, preparers, or existing approvers) can add them and they can be added to the approval flow before or after the active approver.

Additional approvers and watchers can be added only before the approval process is complete; they can't be added after approval is finished.

Users use the same functionality to add or remove additional approvers or watchers as they do while composing requests.

As part of this improvement, the name of the approval chain has been changed from Process to Approval Flow.

GB-2965: User tasks

GB-2965: How to add additional approvers and watchers [page 45]

GB-2965: How to add additional approvers and watchers

Users can manually add or remove additional approvers and watchers to a request's approval flow.

Context

Any user who can view a request can add or remove additional approvers and watchers.

You can add or remove additional approvers and watchers when the request is in Composing or Submitted state. You can't change the list of approvers or watchers after the request reaches Approved state.


You can add approvers or watchers before or after the active approver.

NoteAn approver is anyone who has the authority to approve or deny a request. A watcher is someone who can't approve or deny a request, but who will be notified of the progress of the request.

Procedure

1. Click the options menu ( ) in the upper left corner of the page.2. Choose one of the following:

○ Click Approve requests for requests that are waiting for your approval, that you're watching, or that you recently approved.

○ Click Your requests for requests you're currently composing or have already submitted.3. Click a request that is in Composing or Submitted state.4. To add additional approvers or watchers to the Approval Flow:

a. Place your pointer on a dotted line in the approval flow. Guided buying displays a plus symbol (+) in the flow, indicating where the new approvers or watchers can be added.

b. Click the plus symbol (+) to display the Add Approval Request window.c. Select Approver or Watcher. Optionally, enter a reason for adding the additional approvers or watchers.d. Search for users or scroll down in the list until you see them.e. Click Choose beside those users.f. Click OK when done.

5. To remove approvers or watchers from the Approval Flow:a. Click the delete (X) symbol next to an approver or watcher. You can delete only users that were manually

added.b. Click Remove.

Results

Guided buying adds or removes the approver or watcher from the Approval Flow.

If you added an approver before the current approver, guided buying removes the request from the current approver's To Approve list and the added approver becomes the current approver. Then, as the request progresses through the Approval Flow, guided buying skips users who already approved it.


GB-3223: Guided buying can show multiple validation policy violations during check out Description


Audience: Buyers


Guided buying can now display multiple validation policy violations when users check out with their shopping carts. Previously, it displayed only the first policy violation found for a line item or the requisition header; additional violations didn't display, so users were unaware of them.

The Checkout page now groups policy violations by the Severity level assignment in your site's validation policy file: Error, Justification, and Info. If a line item has multiple Justification or Info policy violations, a single message displays indicating that there are multiple violations. Users can click More details to display all Justification or Info policy violations for that line item.

Only one policy violation with a Severity level of Error displays for each line item, regardless of how many errors there are. Users must resolve the error before they can continue.

If errors are found by both guided buying and SAP Ariba Buying and Invoicing, the guided buying ones display first. After the user resolves those errors, the ones found by SAP Ariba Buying and Invoicing display.

GB-4536: Display warnings from the Validating and enriching APIDescription


Audience: Buyers


The Validating and enriching approvable data in an external system API checks guided buying request data (such as budget and accounting information) against ERP data. It returns errors, errors with warnings, or just warnings. However, guided buying displayed only errors and errors with warnings, not cases when there were just warnings. But, users wanted to know about warnings and wanted guided buying to stop so they could make changes before submitting their requests.

Now, if guided buying receives warnings from the Validating and enriching approvable data in an external system API, it stops and displays them. Users see these warnings and can make changes in their requests before submitting them.


Guided buying checks request data using the Validating and enriching approvable data in an external system API after:

● A user submits a request● A users or approver edits a request● The last user in the approval graph approves a request

SINV-6042: Evaluated receipt settlement (ERS) and automatic invoicing for service items

Products: SAP Ariba Invoice ManagementSAP Ariba Buying and Invoicing

Audience: Buyers


Starting with this release, service items on requisitions can be flagged for Evaluated Receipt Settlement (ERS) and automatic invoicing. When a planned service line item is flagged for ERS, the nested level of its child lines automatically qualifies for ERS and automatic invoicing. For unplanned service items, line items on service sheets are automatically eligible for automatic invoicing if the parent service item is enabled for ERS.

In addition, the SAP Ariba solution can be enabled to allow buyer users to create correction service sheets based on processed service sheets for which invoices are created. Users can specify negative item quantities on correction service sheets (also known as negative service sheets) to adjust for excess invoiced amounts. When correction service sheets are fully approved, the SAP Ariba solution automatically creates line-level credit memos to reverse over-invoiced amounts and accumulations against purchase order limits.


See Purchasing guide for procurement prefessionals for more information about ERS.

Prerequisites

See SINV-6042 Prerequisites [page 49].

Workflow to procure service items flagged for ERS

See SINV-6042: Workflow to procure service items flagged for ERS [page 50].



See SINV-6042: Changes to existing functionality [page 50].

User tasks

See User tasks [page 52].

Information for administrators

See SINV-6042: Information for administrators [page 54].

cXML changes

See SINV-6042: cXML changes [page 54].

SINV-6042 Prerequisites

● Customer administrator must enable the self-service parameter for this feature. For information about how to enable and configure this feature, see the administrator topics.

● You must have an agreement with suppliers on the applicable conditions before you enable ERS.● Ensure that data import tasks required to enable supplier locations for ERS transactions must be complete:

○ For SAP ERP-integrated sites, the XERSY field in the PurchaseOrgSupplierCombo.csv file used by the Import Purchase Organization to Supplier Mapping data import task must be set to X.

○ For PeopleSoft and Generic ERP-integrated sites, the ERS_Flag or the ERSAllowed field (as applicable) in the SupplierLocationConsolidated.csv file used by the Import Supplier Location Data (Consolidated File) data import task must be set to Yes.

For more information about managing data for ERS using data import tasks, see the Common data import and administration guide.

● Users must have membership of the Purchasing Manager or the Invoice Manager group to be able to approve service line items for ERS transactions.

● For SAP Ariba Invoice Management, ensure that the automatic invoice creation functionality is not enabled in the ERP system to prevent creation of duplicate invoices. Similarly, for merged sites combining SAP Ariba Buying and Invoicing and SAP Ariba Invoice Management, perform the appropriate settings to ensure that automatic invoices are created either in SAP Ariba Buying and Invoicing or SAP Ariba Invoice Management.

● Customer administrators must configure the approval flows for requisitions to include the Purchasing Manager or the Invoice Manager group if a requisition includes at least one ERS item.


SINV-6042: Workflow to procure service items flagged for ERS

The following is a high-level workflow to procure service items flagged for ERS:

1. A buyer user creates a requisition for service items that need to be procured from ERS-approved suppliers.2. An approver having membership of the Purchasing Manager or the Invoice Manager group ensures that the

ERS Allowed field is set to Yes for the parent lines on the requisition and then approves the requisition.A purchase order is created after the requisition is fully approved.

3. The supplier receives the order and performs the service.4. Either the supplier or the buyer user creates a service sheet and submits it for approval.5. The SAP Ariba solution automatically creates an invoice for service items flagged for ERS after the service

sheet is fully approved.6. (For buyer-created service sheets) If necessary, the buyer user creates a correction service sheet with

reference to the invoiced service sheet to reverse over-invoiced item quantities.7. The SAP Ariba solution automatically creates a line-level credit memo after the correction service sheet is fully

approved.

SINV-6042: Changes to existing functionality

Functional changes

● Previously, ERS and automatic invoicing was supported only for material items. Now, customers can also configure their sites to allow ERS and automatic invoicing for service items. With this feature enabled, the SAP Ariba solution creates invoices automatically for service items flagged for ERS when fully approved service sheets move to the Processed state.

● Until this release, the SAP Ariba solution allowed users to create service sheets by specifying negative item quantities for items that required to be reversed. Now, the SAP Ariba solution allows users to create correction service sheets to make adjustments for over-invoiced item quantities by specifying negative values. When correction service sheets are fully approved (Processed), the SAP Ariba solution automatically creates line-item credit memos based on item quantities in the correction service sheets. For more information about creating correction service sheets, see How to create a correction service sheet [page 53].

The following are the additional changes in scenarios where service orders and service sheets consist of a mix of ERS and non-ERS items:

● Orders consisting of a mix of ERS and non-ERS items when only ERS feature is enabled:Previously, if an order consisted of both ERS and non-ERS items, invoices were created automatically when goods receipts for ERS items were fully approved. However, it was not possible to create invoices for non-ERS items on those orders. To prevent this situation, users were required to process separate orders for ERS and non-ERS items.Starting with this release, users can create manual invoices for non-ERS items and automatic invoices for ERS items based on approved service sheets for orders that consist a mix of ERS and non-ERS items. This functionality is available for both material and service items.


● Orders consisting of a mix of ERS and non-ERS items when both ERS and direct invoicing features are enabled:For sites configured to allow users to create PO-based invoices directly without first creating service sheets (also known as direct invoicing) and also enabled for ERS transactions, users can perform the following actions for a mixed order consisting of ERS and non-ERS items:○ Create service sheets for ERS items by clicking the Create Service Sheet button. With this action, the

service sheet page includes only ERS items.○ Create invoices directly for non-ERS items by clicking on the Invoice button on the purchase order. The

Invoice Entry page includes only non-ERS items from the mixed order.

NoteAlternatively, users can create direct invoices for non-ERS items by selecting mixed orders from a list of orders on the Invoice Entry page. The Invoice Entry appears by clicking Create Invoice on the dashboard.

● Service sheets consisting of a mix of ERS and non-ERS items when only ERS feature is enabled:In Ariba Network, if the Allow suppliers to include multiple parent PO lines per service sheet transaction rule is enabled, a single service sheet can include multiple service parent lines. This allows suppliers to create a service sheet by adding items under multiple parent lines. After such service sheets consisting of a mix of ERS and non-ERS items are fully approved, the SAP Ariba solution automatically generates invoices for ERS items. In addition, users can create invoices manually for non-ERS items.


See Creating and managing invoices for more information about creating invoices with reference to service sheets.


Changes for service sheets

● The Line Items table on service sheets include a new column named ERS Allowed. If flagged as Yes, it indicates that a line item is enabled for ERS.

● Service sheets associated with invoices in the Approved or Reconciling states include a new Create Correction Service Sheet button. By clicking on this button, a new page titled Correction Service Sheet appears. This page displays line items copied over from the referenced service sheet and includes negative values for the quantity and the amount values. Users can specify negative numbers less than or equal to the invoiced quantity to reverse item quantities that were invoiced.

NoteCorrection service sheets do not include the Add Items button meaning that users can neither add new line items or add back line items they delete.

● Correction service sheets include a new field named Reference Service Sheet. This field displays the ID of the service sheet based on which the correction service sheet is created.


Changes for purchase orders

● The Service Sheet tab on purchase orders also displays correction service sheets. Correction service sheets can be identified from a list of service sheets by their negative amount values.

● For sites enabled for direct invoicing, purchase orders for service items display the Invoice button while the Create Service Sheet button is disabled. However, if the ERS feature is also enabled, purchase orders display both Invoice and Create Service Sheet buttons. This allows users to create service sheets for ERS items and PO-based invoices without creating service sheets for non-ERS items.

User tasks

How to flag a service item for ERS transactions [page 52]

How to create a correction service sheet [page 53]

How to flag a service item for ERS transactions

Prerequisites

You must be a member of the Purchasing Manager or the Invoice Manager group to be able to enable or disable line items for ERS transactions.

Procedure

1. Open the appropriate requisition.2. In the Line Items section, select the check box for the appropriate service parent line item, and then select

Actions Edit .3. On the Line Item Details page, ensure that the ERS Allowed field is set to Yes.4. Click OK.


How to create a correction service sheet

Correction service sheets can be created for both ERS and non-ERS items to reverse item quantities that were inadvertently over invoiced.

Prerequisites

● The invoice corresponding to the service sheet for which you want to create a correction service sheet must be in the Approved or the Reconciling state.

● A correction service sheet includes line items copied over from the service sheet from which it is created. You cannot add new line items to a correction service sheet. Further, if you delete line items from a correction service sheet, you cannot add them back again. In a scenario where you delete all items on a correction service sheet, you can only delete the correction service sheet and create a new one, if required.

● You can create one or more correction service sheets with reference to a service sheet for which an invoice has been created. The SAP Ariba solution allows you to reverse not more than the entire quantity of a line item on the referenced service sheet. For example, let the quantity for "Item 1" on a service sheet be 10 units. If you create a correction service sheet for this item with quantity as 6 units, you can create one or more service sheets for this item for a maximum quantity of 4 units.

Context

Correction service sheets allow only negative values for item quantities. The negative value corresponds to the quantity you need to reverse. For example, you realize that the invoiced quantity of a line item on a service sheet is incorrectly specified as 20, instead of 12. You can specify -8 as the quantity for that line item on the correction service sheet to make a correction for the over-invoiced quantity.

Procedure

1. Open the service sheet against which you want to create a correction service sheet.2. Click Create Correction Service Sheet to "flip" the invoiced service sheet into a correction service sheet.

The Create Correction Service Sheet page appears.3. Enter the appropriate values for the required line items to specify the quantity that must be reversed.4. Complete other fields required to submit the service sheet and click Submit.

Results

The SAP Ariba solution automatically creates a line-item credit memo for ERS items after the correction service sheet is fully approved.


SINV-6042: Information for administrators

Site configuration options

Some of the functionality for this feature is controlled by site configuration parameters, which your administrator can set in Ariba Administrator under Customization Manager Parameters .

● Application.Procure.EnableERSForServiceItems (enabled for self-service)Determines whether invoices are generated automatically from approved service sheets for suppliers that are configured for Evaluated Receipt Settlement (ERS). If both this parameter and the Application.Procure.EnableERS parameter is set to Yes, invoices are created automatically when service sheets are fully approved (SAP Ariba Buying and Invoicing) or imported from the external system (SAP Ariba Invoice Management). In addition, users can create correction service sheets with reference to invoiced service sheets for ERS items or a mix of ERS and non-ERS items.The default value of this parameter is No.

● Application.ServiceSheet.EnableCorrectionServiceSheet (enabled for self-service)Specifies whether the SAP Ariba solution allows users to create correction service sheets with reference to invoiced service sheets.The default value of this parameter is No.

SINV-6042: cXML changes

cXML changes for purchase orders

Previously, cXMLs of purchase orders included the <Extrinsic name="Ariba.invoicingAllowed">No</Extrinsic> extrinsic at the header level. Therefore, if an order consisted of a mix of ERS and non-ERS items, all items on the order were automatically flagged for ERS.

Now, cXMLs for purchase orders include the InvoiceInstruction intrinsic at the line level for items that are flagged for ERS:

● <InvoiceInstruction value="isERS" verificationType="goodsReceipt"/> for material and service parent items

● <InvoiceInstruction value="isERS"/> for child lines nested under service parent items

With this change, if an order consists of a mix of ERS and non-ERS items, non-ERS items are not flagged for ERS.

cXML changes for service sheets

cXMLs of service sheets now include the following changes to allow users to create correction service sheets:

● <Extrinsic name="operation">Reverse</Extrinsic>:The extrinsic name with operation as Reverse indicates a correction service sheet for negative quantity.


● <DocumentReference payloadID="<PayLoadID>"/>:<PayLoadID> refers to the payload ID of the referenced service sheet based on which the correction service sheet is created.

SINV-6221: Links to eForms in invoice documentsDescription

Products: SAP Ariba Buying and Invoicing


Audience: Buyers


Organizations using eForms can customize invoices and invoice reconciliation documents so users can link to a related eForm. Approvers reviewing the invoice can then click the eForm link to view the eForm, giving them the information they need for informed approval.

For example, suppose the following:

● Your organization has a supplemental form (an eForm) that's required for disputes.The dispute eForm has its own approval process, separate from that of the invoice documents.

● The IR document is customized to include a field called Dispute Document ID, used to add a link showing the associated dispute document.

In this scenario, for any disputes that occur, the invoice agent finds the Dispute Document ID field on the IR document and can pick the relevant dispute document from the chooser. The IR document now contains a link to the appropriate dispute document.


Figure 1: eForm referenced in an IR document

eForms ID fields aren't sent to Ariba Network, so suppliers don't see them.

NoteThis functionality already exists for requisitions and purchase orders.


To have this feature enabled, please have your Designated Support Contact (DSC) submit a Commercial Request with your SAP Ariba Customer Engagement Executive or Account Manager. AnSAP Ariba representative will follow up with information about SAP Ariba Services.

This feature requires a customization on your site.

Options for eForm linking [page 57]

Limitations

● This feature is for eForms, not forms created in the forms builder.● You can have eForm links added in the header of invoices and IR documents but not at the line level.● You can use this feature with invoices and IR documents created after eForm linking is implemented on your

site.● eForm ID fields are not included in cXML IR documents sent to Ariba Network.


Options for eForm linkingFollowing are a few examples of the configuration options available for adding eForm links to invoices and invoice reconciliation (IR) documents.

● The eForm ID fields on the invoice or IR document can be required or not, depending on business needs.● As with other custom fields, eForm ID fields can be configured with specific conditions that determine when

the field is visible and editable. Validity constraints can also be configured.● Depending on how the eForm ID chooser on the invoice or IR document is configured, it can include all eForm

documents of any status, all approved eForm documents, or eForm documents created by the user and the user’s subordinates. ("The user" in this case is the person who's editing the invoice or IR document.)

Note○ You can't link to withdrawn eForms. However, if an eForm is withdrawn after being linked to an invoice

document, the link is not affected. If you want to be alerted in such cases, you can configure a new invoice exception type.

○ Members of the group eForm Manager can see all approved eForm documents regardless of how the field is configured.

● Configuration options control which eForm information is revealed to users in eForm ID choosers. For example, by default, users can click the eForm ID in the chooser to view the eForm. You can have this capability turned off.

● On invoices and IR documents, up to two eForm ID fields can be made available for reporting. (You can have more than two eForm ID fields on an invoice document, but only two of them can be available for reporting.)

● eForm ID fields can be included in the Export Payment Requests data export task.

SINV-6857: Enhancements to accounting export and import for invoicesDescription

Products: SAP Ariba Buying and Invoicing


Audience: Buyers


The Microsoft Excel worksheet for exporting and importing line-level accounting distributions now uses color-coding to indicate invalid values. You can quickly identify and correct the data before importing it back into the invoice or invoice reconciliation document.

● Invalid accounting field entries have a red background.● For sites integrated with SAP ERP, the worksheet indicates which accounting fields are relevant for a line item

based on the Account Assignment field.

Worksheet validation for accounting distributions [page 58]


Prerequisites

Your SAP Ariba solution must be configured to support:

● Line-level split accounting● Export and import of accounting distributions on invoices and invoice reconciliations

For details, see SINV-6857: Site configuration options for accounting export and import for invoices [page 62].


Previously, when users exported accounting distribution information, the generated Microsoft Excel worksheet didn't indicate invalid accounting fields.

Now, the worksheet indicates invalid information with a light red background, based on the validity at the time of the export.

Previously, for sites integrated with SAP ERP, the worksheet included only the fields that were relevant based on account assignment. Now, the worksheet includes all fields. Cells in the Account Assignment column have a dropdown for changing the value.

Worksheet validation for accounting distributions [page 58]

SINV-6857: Site configuration options for accounting export and import for invoices [page 62]

Worksheet validation for accounting distributions

When you export accounting distribution information to a worksheet, the worksheet has color coding to indicate the validity of the information. For example, the worksheet shows invalid information with a light red background.

When you import the information from a worksheet, the import process validates split percentages, quantities, and amounts.


Figure 2: Excerpt of exported accounting info in an Excel worksheet

The color coding in the worksheet reflects all data validation done in the SAP Ariba solution, such as account field dependencies and any defaulting configured in the SAP Ariba solution.

Color coding to indicate validity and editability

The following table explains the meaning of the colored cells in the accounting distribution worksheet.


Cell color Meaning

Red Invalid value.

The worksheet also uses red to show:

● Split percentages that don't add up to 100. If you correct the percentages, the cell color changes accordingly.

● Splits that reference different account assignments for the same line item (standard for SAP ERP). If you correct the account assignments so they're all the same, the cell color changes accordingly.

NoteIf you type account assignments in the worksheet instead of using the dropdown, press Enter or the down-arrow key to commit the change. If you sim

ply click in a different cell instead of pressing one of these keys, only the current cell changes color. The other account assignment cells don't change until you refresh them (by double-clicking, for example).

Blue Either:

● A column header.● A value that's the same for all splits of a line item. For ex

ample, if the item quantity is 8, all splits have 8 in the Item Quantity field.

NoteDon't edit Item Number or Item Type.

White A cell for a given accounting distribution that you can edit individually.

Gray (on sites integrated with SAP ERP) The cell is irrelevant (inactive) for the specified accounting distribution. For details, see the following section, "Applicable fields based on SAP ERP account assignment."

Applicable fields based on account assignment

For sites integrated with SAP ERP, you can select account assignments from a dropdown in the Excel worksheet, as shown in the previous figure.

Depending on the account assignment for an accounting distribution, some account-related fields are applicable and others are not. The worksheet uses a gray background to indicate cells that don't apply based on the value in the Account Assignment field. These cells are inactive cells. The values in inactive cells aren't editable in the SAP Ariba solution, so entering values and importing them from the worksheet has no effect.


The cells that do pertain to the account assignment are active cells. Active cells are editable in the SAP Ariba solution, so you can import values from the worksheet.

If you change an account assignment, the worksheet updates which cells are active and inactive.

Table 1: Example of active and inactive fields for account assignments in standard SAP variants

Account assignment Active fields Inactive fields (gray cells)

A (Asset) Asset Number

Sub-number

GL Account

Cost Center

Project/WBS

Internal Order

F (Order) GL Account

Internal Order

Cost Center

Project/WBS

Asset Number

Sub-number

K (Cost Center) GL Account

Cost Center

Internal Order (optional for K)

Project/WBS

Asset Number

Sub-number

P (Project) GL Account

Project/WBS

Cost Center

Asset Number

Sub-number

Internal Order

Validation and error messages during import

When you import accounting distribution information from a worksheet, the import process displays an error for the following:

● Split percentages that don't add up to 100 if accounting is split by percentage● Split quantities that don't add up to the total item quantity if accounting is split by quantity● Split amounts that don't add up to the total item amount if accounting is split by amount

Correct the errors in the worksheet before importing.


SINV-6857: Site configuration options for accounting export and import for invoicesSome of the functionality for this feature is controlled by site configuration parameters, which your administrator can set in Ariba Administrator under Customization Manager Parameters .

The following existing parameters are prerequisites for using the enhancements to accounting export and import. Both parameters must be set to Yes before you can use this feature.

Application.Procure.AllowAccountingExportAndImport (enabled for self-service)In sites enabled for split accounting (Application.Approvable.AllowSplitAccounting is set to Yes), this parameter specifies whether export and import of accounting distributions is allowed on requisitions, service sheets, invoices, and invoice reconciliations. If set to Yes, users can export accounting distributions to a Microsoft Excel file, add or modify accounting information, and import the updated accounting information from the file. The default is No.

Application.Approvable.AllowSplitAccounting (enabled for self-service)Enables or disables split accounting on line item level. If set to Yes, users can create accounting distributions on line level in requisitions, service sheets, invoices, and invoice reconciliation documents. The default value is Yes.

SINV-7199: Goods receipt-based invoice verification without ship notice IDsDesciption

Products: SAP Ariba Invoice Management

Audience: Buyers


Buyers can now use goods receipt-based invoice verification without requiring suppliers to add ship notice IDs to invoices. For invoices without ship notice IDs, buyers can allow automatic matching to receipts based on the corresponding purchase order.

For general information about goods receipt-based invoice verification, see the topic "Goods receipt-based invoice verification" in the Invoicing and payment process guide.

Workflows for goods receipt-based invoice verification for invoices without ship notice IDs [page 63]

Prerequisites

Enable goods receipt-based invoice verification (set the parameter Application.Procure.EnableGRBasedInvoice to Yes).


Limitations

If a quantity variance exception is raised after the invoice is matched to receipts for the same PO, the only way to resolve it is to manually match any additional receipts to the invoice.


Previously, the only way invoices were automatically matched to receipts was based on ship notice ID. Therefore, suppliers invoicing for items requiring goods receipt-based invoice verification had to include a ship notice ID on the invoice. The ship notice ID on the invoice had to match the ship notice ID the buyer had added to the receipt. If an invoice came in without a ship notice ID, a No Matching Receipts Found exception was raised.

With this feature, invoices that don't have a ship notice ID are matched to receipts associated with the same purchase order. The No Matching Receipts Found isn't raised.

NoteBuyers must still provide a ship notice ID on receipts for items requiring goods receipt-based invoice verification. If suppliers include a ship notice ID on the invoice, the IDs still must match the ship notice ID in the corresponding receipt in order for automatic matching to happen.

Administrator tasks

To use this feature, set the parameter Application.Invoicing.MatchReceiptToInvoiceWithoutShipNotice to Yes.

SINV-7199: Site configuration options [page 65]

Workflows for goods receipt-based invoice verification for invoices without ship notice IDs

The following workflows illustrate how invoices are matched to receipts when the invoice doesn't include a ship notice ID.

These workflows apply to sites that allow invoices without ship notice IDs to be automatically matched to receipts based on purchase order. The SAP Ariba solution matches the invoice to the receipt for the same purchase order. If there are multiple available receipts, they are picked in the ascending order based on when the receipts were created.


Basic flow

1. The buyer sends the supplier an order for items marked for goods receipt-based invoice verification.2. The buyer receives the items and creates a receipt that includes a ship notice ID.3. The supplier sends an invoice for the items.4. The SAP Ariba solution checks the invoice for a ship notice ID.5. If the invoice doesn't include a ship notice ID, the SAP Ariba solution looks for a receipt for the purchase order

that's referenced on the invoice, and matches the invoice to that receipt.6. The SAP Ariba solution raises quantity variance or price variance exceptions as appropriate.

When the invoice comes in before the receipt is created

1. The buyer sends the supplier an order for items marked for goods receipt-based invoice verification.2. The supplier sends an invoice for the items. The invoice doesn't include a ship notice ID.3. Upon receiving the invoice, the SAP Ariba solution looks for but doesn't find a matching receipt.4. The SAP Ariba solution raises a No Matching Receipts Found exception against the invoice because the

receipt doesn't exist yet.5. The buyer creates a receipt for the order. The receipt includes a ship notice ID.6. The SAP Ariba solution matches the invoice to the receipt and clears the No Matching Receipts Found

exception.

When there are multiple receipts for the purchase order that's referenced on the invoice

1. The buyer sends the supplier an order for an item marked for goods receipt-based invoice verification. The quantity of the item is 100.

2. The buyer receives 20 of the items and creates a receipt. The receipt includes a ship notice ID.3. The buyer receives 20 more of the items and creates a receipt. The receipt includes a ship notice ID. (The ship

notice ID can be either the same as or different from the one on the previous receipt.)4. The supplier sends an invoice for 30 of the items. The invoice doesn't include a ship notice ID.5. The SAP Ariba solution matches the invoice to both receipts, matching a quantity of 20 for the first receipt and

a quantity of 10 for the second receipt.

When a quantity variance exception is raised after the invoice is matched to receipts for the same purchase order

1. The buyer sends the supplier an order for an item marked for goods receipt-based invoice verification. The quantity of the item is 100.

2. The buyer receives 20 of the items and creates a receipt. The receipt includes a ship notice ID.3. The supplier sends an invoice for 30 of the items. The invoice doesn't include a ship notice ID.


4. The SAP Ariba solution matches the invoice to the receipt.5. A Receipt Quantity Variance exception is raised.6. The buyer receives 20 more of the items and creates a receipt. The receipt includes a ship notice ID. (The ship

notice ID can be either the same as or different from the one on the previous receipt.)7. The SAP Ariba solution continues to match the invoice to the first receipt only. It doesn't automatically match

the invoice to the second receipt. The invoice reconciliation document still has a Receipt Quantity Variance exception.

8. The buyer manually matches the second receipt to the invoice.9. The SAP Ariba solution clears the Receipt Quantity Variance exception.

SINV-7199: Site configuration options

Some of the functionality for this feature is controlled by site configuration parameters, which your administrator can set in Ariba Administrator under Customization Manager Parameters .

Application.Invoicing.MatchReceiptToInvoiceWithoutShipNotice (enabled for self-service)

On sites enabled for goods receipt-based invoice verification, this parameter determines whether invoices must include ship notice IDs in order to be matched to receipts automatically. (Goods receipt-based invoice verification is on if the parameter Application.Procure.EnableGRBasedInvoice is set to Yes.)

● When this parameter is set to No, automatic matching of invoices to receipts is based solely on ship notice ID. Invoices without a ship notice ID are not matched to receipts.

● When set to Yes, invoices without ship notice IDs are matched to goods receipts based on purchase order.


SAP Ariba Strategic Sourcing and Supplier Management solutions features

OPCCC-483: Support for custom relationships between fields [page 67]

SS-3414: Enhanced envelope bidding with improved team control for access [page 70]

SS-3451: Update live events from Excel [page 72]

SS-890: Support header-level integration fields in Import Sourcing Project requests [page 74]

SS-9766: Send participant responses to event questions in award data [page 76]

SSR-594: ERP integration for article variant and single article creation [page 79]

DMS-7175: Ability to get quotes on entire BOM in product sourcing [page 82]

DMS-7183: Default 100% AML split for parts with one AML supplier [page 86]

DMS-7303: Enhanced product sourcing UI tables for material and BOM views [page 88]

DMS-7977: Ability to use reserve price, conditional visibility of questions, and multi-currency support for large-capacity events [page 97]

DMS-8450: Product Sourcing dashboard data table filtering [page 106]

DMS-8513: Ability to have UOM in product sourcing simple RFx [page 108]

DMS-8962: Product Sourcing user interface enhancements [page 109]

DMS-9020: Ability to import Material Group information [page 110]

DMS-9022: Ability to access Material 360 View without using Product Sourcing dashboard [page 112]

DMS-9209: Custom fields enhancements [page 113]

DMS-9523: BOM hierarchy and BOM split export enhancements [page 120]

SC-5081: Mass application of conditions in an assembled contract document [page 121]

Bulk-loading conditions with Microsoft Excel import [page 123]

SC-5088: Manage individual redlining changes inline in Enhanced Contract Authoring [page 129]

SC-5103: Increase the 100 MB attachment and document size limitation for contracts to 2 GB [page 130]

SC-5159: Mass upload contract documents to multiple workspaces [page 131]

SC-3299: Commodity price escalation management [page 136]

ARI-4402: Risk exposure configuration moved to UI [page 144]

ARI-4598: Enhanced workflow for sending questionnaires in control-based engagement risk assessment projects [page 150]

ARI-4666: Increased variability in risk exposure measurements [page 156]

ARI-4946: Ability to upload status and expiry dates of offline risk assessments [page 157]

ARI-5268: Support for analytical reporting on control-based engagement risk assessment projects [page 161]

ARI-5428: New Risk Control Summary report [page 176]



ARI-5531: Risk control mappings based on inherent risk screening scores [page 178]

ARI-5567: Presentation of Korean-language adverse media in SAP Ariba Supplier Risk [page 181]

SM-11787: Enhancements to supplier request duplicate checking [page 182]

OPCCC-483: Support for custom relationships between fields

Description

Products SAP Ariba Contracts

SAP Ariba Sourcing

Audience Buyers


Relation entries enable you to set up a relationship between two fields on an object for the purpose of ensuring valid combinations of field values, so that the values that are acceptable and available for one field depend on the value of another field.

For example, you could use relation entries to constrain the Supplier and Commodity Code fields in the Allocation Details section of a savings form to a set of allowed combinations.

You can set up one-to-one, one-to-many, or many-to-many relationships using relation entries. You can set up relationships between the Supplier field and the Commodity Code field, as well as custom flex master data fields in savings forms. You can set up relationships between the Supplier field and custom flex master data fields in contract workspaces.

See Workflow for setting up custom relationships between fields [page 68].


The Data Import/Export page in the Site Manager workspace of Ariba Administrator lists the following new tasks:

● Import Relations● Import Relation Entries

Administrator tasks

● How to deactivate relation entries [page 68]

SAP Ariba Applications Q2 2019 release guideSAP Ariba Strategic Sourcing and Supplier Management solutions features C O N F I D E N T I A L 67


This feature introduces the following new data import tasks:

● Data import task for establishing a relationship between two fields [page 69]● Data import task for mapping values in one field to values in another field [page 69]

Workflow for setting up custom relationships between fields

Setting up relation entries is a three-step process:

1. SAP Ariba Customer Support sets up and imports RelationType.csv to establish a generic relationship between the two fields.

2. You enter data in RelationEntries.csv to define the specific field value dependencies, following an example provided by SAP Ariba Customer Support, and import the data using the Import Relation Entries data import task.

3. SAP Ariba Customer Support writes and uploads an AML customization to define the behavior of the relationship.

How to deactivate relation entries

Context

You can deactivate relation entries to prevent their continued use.

Procedure

1. Create a RelationEntry.csv file that contains only the relation entries you want to deactivate.

2. On the dashboard, click Manage Administration .3. Click Site Manager, and then click Data Import/Export.4. On the Import tab, search for the Import Relation Entries data import task, and click Import.5. Click Deactivate, enter the location of the RelationEntry.csv file you created in step 1, and click Run.



Data import task for establishing a relationship between two fields

The Import Relations data import task establishes a relationship between two fields. It reads data from the CSV file named RelationType.csv. SAP Ariba Customer Support typically creates and imports RelationType.csv.

Following is an example of RelationType.csv. This example establishes a relationship between Supplier and Commodity Code fields in the allocation details of a savings form .

UTF8 UniqueName,Name,LeftClass,RightClassSupplierCommodityMap,Supplier to Commodity Validation,ariba.core.Supplier,ariba.common.core.CommodityCode

Data import task for mapping values in one field to values in another field

The Import Relation Entries task maps the values in one field to the values in another field. Both fields must be included in RelationType.csv. This task reads data from the CSV file named RelationEntry.csv, which depends on the CSV file named RelationType.csv.

Following is an example of RelationEntry.csv. In this one-to-many example:

● Supplier SUP_0523 is mapped to commodity codes Commodity112, Commodity113, and Commodity114.● Supplier SUP_0536 is mapped to commodity codes Commodity120, Commodity121, and Commodity122.

The combination of values in the LeftId and RightId columns establishes each relation entry as unique. You can make up these values or use existing field values. In the example that follows, the LeftKey1 and RightKey1 values are used for LeftId and RightId.

UTF8 RelationType.UniqueName,LeftId,RightId,LeftKey1,LeftKey2,LeftKey3,RightKey1,RightKey2,RightKey3SupplierCommodityMap,SUP_0523,Commodity112,SUP_0523,,,Commodity112,,SupplierCommodityMap,SUP_0523,Commodity113,SUP_0523,,,Commodity113,,SupplierCommodityMap,SUP_0523,Commodity114,SUP_0523,,,Commodity114,,SupplierCommodityMap,SUP_0536,Commodity120,SUP_0536,,,Commodity120,,SupplierCommodityMap,SUP_0536,Commodity121,SUP_0536,,,Commodity121,, SupplierCommodityMap,SUP_0536,Commodity122,SUP_0536,,,Commodity122,,


SS-3414: Enhanced envelope bidding with improved team control for accessDescription

Product: SAP Ariba Sourcing

Audience: Buyers


Envelopes control who can see participant responses in SAP Ariba Sourcing events and when the responses can be seen.

Prerequisites

To use this feature, you must set the rule Must participants improve their bids? to No. By default, this rule is set to Yes.

You can create envelopes in RFI and RFP events so that participant responses are not visible until the envelope is opened. An event typically contains multiple envelopes, and you configure project teams (groups) who are authorized to open envelope bids for each envelope.

Envelopes are opened serially. Authorized group members select which participants will advance to the next envelope; only responses from the selected participants are visible in the next envelope.

The group authorized to open the first envelope in an event (envelope 1) sees responses from all participants, then selects the participants who will advance to envelope 2. The group authorized for envelope 2 sees only responses from participants who were selected to advance from envelope 1.

As an example, you can create an event with envelope 1 that collects technical information and have the responses evaluated by a technical team, then use envelope 2 to collect commercial information to be evaluated by a business team.

A new event rule, Will teams control envelope access?, controls how envelopes are opened and how participants are selected. In previous releases, authorized group members first selected participants to advance to the next envelope opening, then opened only the envelopes of the selected participants. Now, when Will teams control envelope access? is set to Yes, authorized group members first open envelopes, then select the participants who will advance to the next envelope opening.

The default value for Will teams control envelope access? is No (authorized group members select participants to advance, then open only the envelopes of the selected participants). Although this was the behavior in previous releases, the suggested workflow below allows the authorized group to see responses before selecting participants to advance to the next envelope opening.



Workflow

● The event owner or template author sets the event envelope rule Will teams control envelope access? to Yes.

NoteFor this workflow, be sure to set this rule to Yes. The default for this rule is No. If you leave the default, the authorized group won’t be able to see responses before selecting participants to advance to the next envelope opening.

The event owner or template author configures additional envelope rules, including:○ Number of Envelopes

Each envelope is linked to one or more sections, and the envelope contains responses for all items in the sections.

○ The group or groups authorized to open each envelope.For information about all event envelope rules, see the Event rules reference guide.

● The event owner or template author ensures that the rule Must participants improve their bids? is set to No.● The event owner or template author creates sections and specifies the envelope for each section. The event

owner or template author adds questions, lots, or items to the sections.● The event owner publishes the event.● Participants submit responses and bids. Bidding closes for the event and the event state is Pending Selection.● A user in the group authorized for envelope 1 opens envelope 1. The user:

○ Opens the event and selects Actions Open Envelope in the upper right corner of the event page.○ On the Open Envelope Confirmation page, the user selects Open Envelope.

● Users in the group authorized for envelope 1 view participant responses to items in envelope 1. This is the first envelope, so responses from all participants are visible.

● A user in the group authorized for envelope 1 selects participants to advance to the next envelope (envelope 2). The user:

○ Selects Actions Choose suppliers for next envelope in the upper right corner of the event page.○ In the Choose suppliers to advance to the next envelope page, the user selects the suppliers

(participants) to advance and clicks Unseal Next Envelope.This enables users in the group authorized for envelope 2 to open the next envelope. In envelope 2, only responses from the selected participants will be visible.

● A user in the group authorized for envelope 2 opens envelope 2. Users in the authorized group can view only the responses from the participants selected to advance from envelope 1. If there are additional envelopes, a user in the group authorized for envelope 2 selects participants who will advance to the next envelope.


This feature allows you to see participants' responses before deciding whether they should advance to the next envelope opening. With previous functionality, you selected participants to advance before you saw their responses.

This feature introduces a new template rule, Will teams control envelope access? A user in the group authorized for envelope 1 issues a new command, Unseal Next Envelope, to enable users in the group authorized for envelope 2 to open that envelope.


SS-3451: Update live events from ExcelProduct: SAP Ariba Sourcing

Audience: Buyers


This feature enables you to add, edit, or delete items in a live (published) event from a Microsoft Excel document.

Limitations

● You can only update the following items:○ Content○ Participants○ Buyer Terms

You cannot update event rules or currency conversion specifications with this feature.

How to update published events from an Excel document

Prerequisites

You must be the event or project owner and a member of one of the following groups:

● Commodity Manager● Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)● Internal User● Limited Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination

Team)● Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market

Coordination Team)

Context

You can update content and participants in a published event from an Excel document.

If you make changes to the event after some or all participants have already submitted bids, you must choose what to do with the existing bids that were not already removed by your change, since some of the bids might have become invalid. For example, maybe you notice that you forgot to set a participant-specific initial value for some participants or you lowered the ceiling price on a certain lot. When you update the event, you have the option to notify the participants that you have changed the event, and you can decide to discard or keep participants’ existing responses.



Limitations● You can only update the following items:

○ Content○ Participants○ Buyer Terms

You cannot update rules or currency conversion specifications.

Procedure

1. Choose Actions Document Edit .The event wizard (editor) opens.

2. In the navigation panel on the left side of the page, select Suppliers or Contents.3. From the Invited Participants or Content page, select Excel Import.4. In Step 1 of the Import Content from Excel page, select the data you want to import.

Because you are updating a published event, your choices are limited to:○ Content○ Participants○ Buyer Terms

5. In Step 2 of the Import Content from Excel page, select Click here to open your RFP in an Excel spreadsheet (or Click here to open your Auction in an Excel Spreadsheet) to create an Excel document with the existing event information.

6. When the download completes, choose to either open the template in Microsoft Excel or save it, then open it. Edit the Excel document and save your changes.○ To add line items, create entries in the Pricing worksheet. Leave the System ID column blank.○ To delete an existing line item, locate the row with the item in the Pricing worksheet and enter Yes in the

Delete column.○ To modify an existing line item, locate the row with the item in the Pricing worksheet and change column

values. Do not change the System ID column value.○ To modify a term value for an existing item, change the value in the Pricing worksheet and the Event Terms

worksheet.7. Return to the Import Content from Excel page for simple Excel imports: Navigate to the Content page for the

event and click Simple Excel Import at the bottom of the page.8. In Step 4 of the Import Content from Excel page, select Add/Edit to Event Content (this is your only choice).9. In Step 5 of the Import Content from Excel page, select your Excel document.10. In Step 6 of the Import Content from Excel page, select Import.11. Select Exit to exit the event editor.12. From the monitor page for the event, select Update Published Event.13. Review the pending changes. Select Update.14. On the Update Event page, choose an option for handling the changes and notifications to participants.

Choose Keep and email or Do not keep, and email to enter an optional personalized message. Your personalized message will be included in the Event Edited and Republished notification.


15. Click Update Event.

Results

The system updates the event with your changes, unless you need approval before publishing an event. In that case, the system submits your updates for approval. When the appropriate person provides approval, the system updates the event with your changes.

The Event Edited and Republished notification is sent when you republish your event.

SS-890: Support header-level integration fields in Import Sourcing Project requests

Description

Product: SAP Ariba Sourcing

Audience: Buyers


This feature enables you to send the following header-level integration fields in requests for the Import Sourcing Project SOAP web service:

● External System● Company Code● Payment Terms● Purchasing Group● Purchasing Organization

SAP Ariba Sourcing validates the values against the values in the Material Master data for the external system. If award data is sent back to the external system (by selecting Actions Send Quotes to External System ), SAP Ariba Sourcing sends the values back to the external system with the award data.

Prerequisites

● Your site must be configured for material master data integration with an external system, as described in the Common data import and administration guide.

● You must set the site configuration parameter Application.ACM.ValidateERPFieldsEnabled to Yes. This is a self-service parameter; a member of the Customer Administrator group can set it in Ariba Administrator under Customization Manager Parameters .



SS-890: Changes to existing functionality

Import Sourcing Project request changes

You specify the header-level integration fields in CustomString elements in the ProjectHeaderFields element within a body of an Import Sourcing Project request.

The integration fields and corresponding elements are:

Integration field Element Valid values

External System <urn:CustomString name="ExternalSystem"> ID

Company Code <urn:CustomString name="CompanyCode"> ID or ID description

Payment Terms <urn:CustomString name="PaymentTerms"> ID or ID name

Purchasing Group <urn:CustomString name="PurchasingGroup"> ID or ID name

Purchasing Organization

<urn:CustomString name="PurchasingOrganization"> ID or ID name

For ExternalSystem, specify the ID of the External System as configured in Ariba Administrator under Master Data Manager.

For CompanyCode, specify one of the following:

● ID. ID for the value, as defined on the external system. This is usually a number. For example, 100.● ID description. ID and description for the company code, separateed by a space. The values must match

an ID and description pair defined on the external system and loaded on Ariba Administrator as master data. For example, 100 My Company North.

For all other fields, specify one of the following:

● ID. ID for the value, as defined on the external system. This is usually a number. For example, 1009.● ID name. ID and name for the value, separated by a space. The values must match an ID and name pair

defined on the external system and loaded on Ariba Administrator as master data. For example, 1009 Raw Materials Project X.

For example:

<soapenv:Body> <urn:SourcingProjectImportRequest partition="?" variant="?"> <urn:WSSourcingProjectInputBean_Item> <urn:item> : : <urn:ProjectHeaderFields> : : <urn:Custom> <urn:CustomString name="ExternalSystem">ECC01</urn:CustomString> <urn:CustomString name="CompanyCode">100 My Company North</urn:CustomString> <urn:CustomString name="PaymentTerms">0003</urn:CustomString> <urn:CustomString name="PurchasingGroup">1009 Raw Materials Project X</urn:CustomString> <urn:CustomString name="PurchasingOrganization">100 Project X</urn:CustomString>


SAP Ariba Sourcing validates the values for the Company Code, Payment Terms, Purchasing Group, or Purchasing Organization against the values in the Material Master data for the external system. SAP Ariba Sourcing verifies that the ID values match entries in the Material Master data; if a value contains both an ID and a name or description, SAP Ariba Sourcing verifies that they match an ID and name (or ID and description) pair in the Material Master data.

If award data is sent back to the external system (by selecting Actions Send Quotes to External System ), SAP Ariba Sourcing sends the values back to the external system with the award data.

New Status and Error Message values

If SAP Ariba Sourcing cannot parse values sent for the integration fields or the values do not match the Material Master data for the external system, SAP Ariba Sourcing returns the following status and error message in the Import Sourcing Project reply:

Status Error Message

-6037 Error processing ERP field

SS-9766: Send participant responses to event questions in award data Product: SAP Ariba Sourcing

Audience: Buyers


This feature improves integration between SAP Ariba Sourcing and ERP systems by including responses to event questions from awarded participants in award data.

If your site has the Award Scenario ERP Integration feature enabled and an event has an External System configured, the event owners can use the Send Quotes to External System button to send award data to the external system. SAP Ariba Sourcing sends the award data in a cXML QuoteMessage document. In previous resleases, participant responses to event questions were not included in the QuoteMessage document. (Participant responses to line-item terms were included in QuoteMessage documents.)

To send a response to an external system, the corresponding question must have a value in the ERP field mapping field. In addition, the question must have one of the following response types:

● Attachment● Date● Decimal Number● Money● Percentage



● Quantity● Text (single line limited)● Text (single line)● Text (multiple lines)● Whole Number● Yes/No (Boolean).

Limitations

● SAP Ariba Sourcing cannot send the responses with the following types:○ Address○ Certificate○ Percentage○ Production Facility

● SAP Ariba Cloud Integration Gateway does not support responses with type Attachment.● If you are using SAP Ariba cloud integration (CI), you must use version CI 9.0 or later. The CI must be

customized to handle responses with the type Attachment.


cXML changes

A QuoteMessage document sent to an external system contains responses to event questions. A response is sent as an extrinsic and is linked to its corresponding question by its name attribute, which is set to the value of the ERP field mapping field for the question. The response extrinsics are nested within a Terms extrinsic in the QuoteMessageHeader.

The following example contains a response for a question. The name attribute for the response extrinsic is "Available Now", which is the ERP field mapping field value for the corresponding question. The extrinsic contains the participant's response, Yes.

<Message> <QuoteMessage ...> ... <QuoteMessageHeader> ... <Extrinsic name="Terms"> <Extrinsic name="Available Now">Yes</Extrinsic> ...

SAP Ariba Sourcing can send the following types of question responses in award data:

● Attachment. The attachment is sent as part of a Multipurpose Internet Mail Extensions (MIME) envelope with the QuoteMessage document. The extrinsic for the response has a child Attachment element, which contains a child URL element with a content ID (Content-ID or CID) for the attachment. The corresponding attachment contains the same CID in its header.


For example, a QuoteMessageHeader contains the following elements:

<Extrinsic name="Terms"> <Extrinsic name="SupplierResponseDoc"> <Attachment> <URL>cid:0</URL>

The content ID for the attachment is 0; the MIME header for the corresponding attachment contains the following entry:Content-ID<0>For more information about attachments in cXML documents, see the cXML solutions guide.

● Date. SAP Ariba Sourcing sends the response in one of the following formats:YYYY -MM -DD Thh :mm :ss +hh :mmYYYY -MM -DD Thh :mm :ss -hh :mmWhere:○ YYYY specifies the year○ MM specifies the month○ DD specifies the day○ T is a literal value that specifies the start of the time section○ hh specifies the hour○ mm specifies the minutes○ ss specifies the seconds○ +hh :mm specifies a time zone with a positive offset from UTC (Coordinated Universal Time)○ -hh :mm specifies a time zone with a negative offset from UTC (Coordinated Universal Time)

For example:2019-05-25T00:00:00-08:00The date format is a restricted subset of ISO 8601. The “Z” time zone designator is not allowed.

● Decimal Number● Money. SAP Ariba Sourcing sends the response in the following format:

amount currencyIDWhere amount is a numeric amount and currencyID is the ID for the currency type. For example, 100 USD.

● Percentage: The response is sent with the uumeric value only (no percent sign). For example, 99.● Quantity● Text (single line limited)● Text (single line)● Text (multiple lines)● Whole Number● Yes/No (Boolean). The response is sent as Yes or No.



SSR-594: ERP integration for article variant and single article creation

Description

Products: SAP Ariba Strategic Sourcing Suite

Audience: Buyer


When your SAP Ariba solution is integrated with an external ERP through the SAP Ariba Cloud Integration Gateway, it is now possible create article variants and single articles in SAP Ariba Sourcing and send them to your ERP where they are added to your ERP master data.

Prerequisites

Your solution must be configured to connect to an external ERP through the SAP Ariba Cloud Integration Gateway. For more information, see the SAP Ariba Cloud Integration Gateway configuration guide and the SAP Ariba Cloud Integration Gateway overview guide.


When adding a line item to a sourcing event, a new option called Generic Article was added to the Category pull-down menu.

When you select this option you can select from variant-creating attributes in the item terms, and you can then add values for the attributes that you seleect. For example, for a pizza you might select 'Large' as a value for the variant-creating attribute 'Size', and 'Pepperoni' as the value for the attribute 'Type'.

User tasks

● How to add a single article from SAP Ariba Sourcing to an external ERP [page 80]● How to add an article variant from SAP Ariba Sourcing to an external ERP [page 81]

How to add a single article from SAP Ariba Sourcing to an external ERP [page 80]

How to add an article variant from SAP Ariba Sourcing to an external ERP [page 81]


How to add a single article from SAP Ariba Sourcing to an external ERP

Procedure

1. Log in to your SAP Ariba solution.

2. Select Create Sourcing Project .3. Enter the required details for the project, select the appropriate template, and click Create.

4. On the Content tab, select Add Item and add the relevant item details.5. Select Category and then select the merchandise category. For example, Cheese.6. Select the appropriate external system, then search or browse for the article category and click OK.7. Enter any required terms for the article.8. You must ensure that the Material Type and Material Number attributes are present for all line items. To add

these, select Add Term .9. Expand the term lists and select Material Type and Material Number. Then click OK.10. Enter a value for Material Type and select Done.

The Material Number field should be blank for new articles.This will be updated by the system when the article is created in the ERP and the ERP sends back the article id in the response.

11. On the Summary page of the event, select Publish.12. On the Event Published page, select the Monitor this event link.13. Select the Scenario tab at the top of the page.

14. Select Create Manual Scenario .A manual scenario can be created in any event that has either Open or Pending status.

15. Name the scanrio and select Save to save it.16. On the Current Scenarios page, select the scenario you created and select Edit.17. Click on the Master Data Creation button.

The articles in the event are displayed.18. Select the check box for the article (or articles) you wan to send to the external system and click Send Articles.

Articles have the status PENDING before they are sent. When you click on Send Articles the article status is updated to SENT in your SAP Ariba solution.

Results

The status of the article is updated to CREATED when receipt of the item is acknowledged by the ERP and the corresponding article has been created in article master data there.



How to add an article variant from SAP Ariba Sourcing to an external ERP

Procedure

1. Log in to your SAP Ariba solution.

2. Select Create Sourcing Project .3. Enter the required details for the project, select the appropriate template, and click Create.

4. On the Content tab, select Add Item and add the relevant item details.

5. Select Category Generic Article .6. Select the appropriate external system, then search or browse for the article category and click OK.7. Select variant-creating attributes in the item terms and then select the Unspecified pull-down menu to select

values for these attributes.8. You must ensure that the Material Type and Material Number attributes are present for all line items. To add

these, select Add Term .9. Expand the term lists and select Material Type and Material Number. Then click OK.10. Enter values for these fields and select Done.11. On the Summary page of the event, select Publish.12. On the Event Published page, select the Monitor this event link.13. Select the Scenario tab at the top of the page.

14. Select Create Manual Scenario .A manual scenario can be created in any event that has either Open or Pending status.

15. Name the scanrio and select Save to save it.16. On the Current Scenarios page, select the scenario you created and select Edit.17. Click on the Master Data Creation button.

The articles in the event are displayed.18. Select the check box for the article (or articles) you wan to send to the external system and click Send Articles.

Articles have the status PENDING before they are sent. When you click on Send Articles the article status is updated to SENT in your SAP Ariba solution.

Results

For variant articles, if no plant was associated with the article during article creation, the status of the article is updated to CREATED when receipt of the item is acknowledged by the ERP and the corresponding article has been created in article master data there.

For variant articles where plant was associated with the article during article creation, the status of the article is updated to PENDING PLANT ASSOCIATION when receipt of the item is acknowledged by the ERP. The variant article then moves to the CREATED state.


DMS-7175: Ability to get quotes on entire BOM in product sourcing

Description

Products: SAP Ariba Strategic Sourcing Suite product sourcing features

Audience: Buyers and suppliers


This feature enables buyers to get quote pricing for bill of materials (BOMs). Buyers can create both full and quick sourcing projects from the BOMs they manage. SAP Ariba does not restrict or limit the types of sourcing events buyers can run. Buyers can choose which part types are visible to suppliers and which part types they want to collect pricing for during sourcing events. Buyers can also choose to collect pricing for BOMs based on BOM volume.

When buyers create sourcing projects from Product Sourcing, SAP Ariba automatically transfers historic prices, quantity, supplier specific prices, and terms with supplier specific values to the sourcing project. SAP Ariba also automatically adds AML suppliers from product sourcing as invited suppliers in the sourcing project. Buyers can also search for additional materials in Product Sourcing and add those materials to their sourcing events.

Buyers can accept pricing during the event award process and that information is sent back to product sourcing.

This feature enables you to:

● Send an entire BOM to SAP Ariba Sourcing for quotes● Use volume pricing conditions● Identify the part types that are visible and quotable by suppliers● Allow bidders to bid on the identified quotable materials● Automatically assign suppliers based on assigned contract manufacturer● Get quotes for ad hoc parts in BOMs● Award supplier pricing for BOMs and assemblies● Create follow-on documents for BOMs and assemblies

Prerequisites

To view and select BOMs and materials for quote requests, you must be a member of one of the following groups:

● Materials Viewer● Materials Administrator

To create quote requests, you must be a member of one of the following groups:

● Category Manager● Commodity Manager● Customer Administrator (access to this group must be approved by SAP Ariba)● Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)



● Junior Procurement Agent● Junior Sourcing Agent● Limited Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination

Team)● Procurement Agent● Sourcing Agent● Sourcing Approver● Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market

Coordination Team)


Buyers can send one BOM, including volumes, to be quoted by the suppliers they choose. Buyers can choose the materials that are visible to suppliers and which materials suppliers are able to bid on. Buyers can see the event total and can see a BOM rollup with the pricing received.


See DMS-7175: User interface changes [page 83].

User tasks

● How to create sourcing projects from product sourcing BOMs [page 84]

DMS-7175: User interface changes

The following user interface changes have been introduced with this feature:

● Get quote button. A Get quote button is now available in the following locations:○ BOM search○ BOM advanced search○ Clicking the top BOM on the Product Sourcing tab.

The following options are available after you click Get quote:○ Using Simple RFX○ Using Sourcing Project

● Get quote popup screen. The Get quote popup screen appears after you choose Get quote Using Sourcing Project . There are two options available on the Get quote popup screen:○ Create BOM Quote


○ Material Quote● Create BOM Quote popup screen. The Create BOM Quote popup screen displays after you click Get quote.● BOM Cost Rollup term. The BOM Cost Rollup term is now available in sourcing events created from BOMs in

product sourcing. The BOM Cost Rollup term determines the cost, which is based on the original BOM you chose to get quotes on.

● View Rollup link on the Content tab in the event monitoring interface. The View Rollup link is available in sourcing events created from BOMs. Click View Rollup to view the BOM rollup with the pricing received.

Create BOM Quote popup

The following fields are available on the Create BOM Quote popup screen:

Field Description

Name Enter the name of the BOM quote you are creating.

Description Enter a description of the BOM quote you are creating.

Visible Part Types Choose the part types you want to make visible to suppliers during the sourcing event.

Quotable part types Choose the part types for which you want suppliers to submit pricing.

Volume Choose Yes to include BOM volume data in your event.

Volume Type Appears when you choose Yes in the Volume field. Choose the volume type you want to use in your sourcing event.

User tasks for ability to get quotes on entire BOM in product sourcing

How to create sourcing projects from product sourcing BOMs [page 84]

How to create sourcing projects from product sourcing BOMs

Prerequisites

To view and select BOMs for quote requests, you must be a member of one of the following groups:

● Materials Viewer● Materials Administrator

To create quote requests, you must be a member of one of the following groups:



● Category Manager● Commodity Manager● Customer Administrator (access to this group must be approved by SAP Ariba)● Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)● Junior Procurement Agent● Junior Sourcing Agent● Limited Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination

Team)● Procurement Agent● Sourcing Agent● Sourcing Approver● Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market

Coordination Team)

Context

Before you create a sourcing project, SAP Ariba recommends that you:

● Define all of the project’s requirements and make sure that the available templates meet those requirements. You might need to ask your template administrator to create additional templates.

● Determine if you want to create a full project (one or more sourcing events, with full project management feature, including task management) or a quick project (a single sourcing event).

● Select the appropriate template for your project.● Consider the supplemental documents you want to include in the project.

Procedure

1. Click the Product Sourcing dashboard tab.2. Complete one of the following actions to display parent BOMs:

○ Click one of the BOM action tiles. The data table automatically filters to display BOMs according to the action tile you selected.

○ Enter a BOM name or ID in the search box and click the search icon.○ Click Advanced Search. On the Advanced Search page, enter one or more BOM IDs, separated by spaces.

3. Select the parent BOM for which you want supplier quotes and click Get quote Using Sourcing Project .4. On the Get quote popup screen, choose BOM Quote.5. Click Continue.6. On the BOM Quote popup screen, enter a name for your BOM quote.7. Optionally, complete the following fields on the Create BOM Quote popup screen:

○ Description.○ Visible Part Types. Choose the part types you want to make visible to suppliers during the sourcing event.○ Quotable part types. Choose the part types for which you want suppliers to submit pricing.


○ Volume. Choose Yes to include BOM volume data in your event. When you choose Yes, the Volume Type field displays.

8. Click Done.The Create Sourcing Project page displays.

9. On the Create Sourcing Project page, enter a name and description for your event.

You can enter an unlimited number of characters in the Name and Description fields. Other fields might limit you to 255 characters.

10. Choose one of the following options:

○ Choose Full Project. A full project can contain multiple sourcing events and includes all project management features.

○ Choose Quick Project. A quick project is a single sourcing event.11. If you choose to create a quick project, choose the event type that you want to create from the Event Type pull-

down menu. The event type controls the display of event templates, which are different for each event type.12. Select a value for the Test Project field. In most cases, No is the appropriate value. Specify Yes if you are

creating a project for internal testing or training.

NoteYou cannot change the test project setting after you have created a project.

13. Specify values for the remaining sourcing project fields; see the Event management guide for information about these fields.

14. Select a template for the project. The templates that are available depend on the project information you have entered and the user groups you belong to.

15. Answer any questions shown. The questions are determined by the project template.16. Click Create.

Next Steps

For more information about creating sourcing projects and events, see the Event management guide.

DMS-7183: Default 100% AML split for parts with one AML supplier

Description


Audience: Buyers




This feature automatically assigns a 100% AML split to any item that has only one Approved Manufacturer List (AML) supplier.

Limitations

Once the AML split is assigned, it is not updated again if the following happens:

● The existing AML supplier is removed and a new AML supplier is added● The AML split is manually removed for any month


See DMS-7183: Changes to existing functionality [page 87]

DMS-7183: Changes to existing functionality

● The Materials with missing AML splits action tile has been renamed to Materials with incorrect or missing AML splits. The action tile shows items with an overall split that is less than or more than 100%.For example, an item with a 70% AML split for Supplier A, and a 30% split for Supplier B, is removed. A new AML supplier, Supplier C, is added. The system automatically assigns a 100% AML split to Supplier C. If Supplier A (70% split) and Supplier B (30% split) are later added back, the item appears in the Materials with incorrect or missing AML splits action tile. The AML splits must be manually fixed to equal 100%.

● If a new AML supplier is added to an item where there was previously only one AML supplier and this feature was not enabled, the AML split stays empty and requires a manually entered split.

● A newly added plant is automatically assigned a 100% AML split when there is one AML supplier for an item across multiple plants.

● If a plant changes, and is later added back to the same item, the AML split is added back with the plant.For example, an item with 18 months of AML splits for Plant A is changed to Plant B in the current month. The next month, it changes from Plant B back to Plant A. The Materials with incorrect or missing AML splits action tile shows the 17 months for Plant A. The missing month for Plant B is not included.

This feature runs on a scheduled task that updates every two hours.


DMS-7303: Enhanced product sourcing UI tables for material and BOM views

Description


Audience: Buyers

Enablement: Automatically on for new deployments. Existing customers must contact SAP Ariba to enable.

The SAP Ariba Strategic Sourcing Suite solutions package includes the Product Sourcing dashboard. Your Product Sourcing dashboard might be based on the default dashboard template, or it might be based on a template created by someone in your organization.

The Product Sourcing dashboard displays BOM and material related information and links you can use to perform tasks. Previously, the Product Sourcing dashboard displayed BOM and material related information in both fixed and dynamic columns. Dynamic columns were used to capture AML splits, contracted pricing, and estimated pricing.

The following enhancements have been made to the BOM and materials tables on the Product Sourcing tab:

● Users now enter material pricing, AML splits, and lead time for one or more suppliers on the Item Information page. Previously, users entered material pricing, AML splits, and lead time directly in the materials table on the Product Sourcing tab.

● Users now enter BOM split percentages on the Enter BOM Splits page.● Assignment information and RFx terms are now displayed with material information.● Users can copy pricing, AML splits, and lead time for one or more suppliers.

For more information about the Product Sourcing dashboard, see the SAP Ariba product sourcing guide.

Prerequisites

The information and tiles displayed on your dashboard depend on your group membership:

● If you are a member of the Materials Viewer group, you see information about materials and materials assigned to you.

● If you are a member of the Materials Manager group, you see information about BOMs. You also see information about materials, such as materials for which you need to assign owners (materials that do not have owners assigned).





User tasks

● How to update estimated pricing for materials [page 93]● How to complete splits for materials with missing AML splits [page 94]● How to add estimated lead time values to materials [page 95]● How to complete missing BOM splits [page 96]


The following pages have been introduced with this feature:

● Item InformationThe Item Information page has the following tabs:○ Pricing / Splits○ Assignment info○ RFx

● Enter BOM SplitThe Enter BOM Split page has the following tabs:○ BOM Split - Buyers can enter BOM splits for each item group on the BOM Split tab. Each item group is

displayed in an expandable section.○ Assignment info - Buyers can view assigned contract manufacturers and programs for the materials.

The following Product Sourcing dashboard user interface items have been introduced with this feature:

● View / edit item info action menu link. Click to access the Item Information page and enter enter estimated pricing, split details, and view information about the material.

● View/Edit BOM split button. Click to access the Enter BOM Split page and enter BOM split percentages.


Item Information page

The following image describes the location of elements on the Item Information page:

1. Click to return to the materials table on the Product Sourcing dashboard.2. Shows the name of the action tile you clicked to filter the list of materials. Click to search for materials by ID or

name. You can also scroll through the list of available materials. Click a material ID to access the corresponding Item Information page.

3. Information about the material is displayed in the header. You can choose to update pricing and splits for all suppliers or a single supplier by choosing the corresponding value from the Supplier pull-down menu.

Field Description

Material ID The ID of the material.

Material Name The name of the material.

Programs The program to which the material is assigned. A link displays when a material is assigned to multiple programs. Click the link to view a list of all the assigned programs in a popup.

Contract MFR The contract manufacturer to which the material is assigned. A pull-down menu displays when materials have been assigned to multiple contract manufacturers. Choose the contract manufacturers for which you want to edit material information.



Field Description

Supplier The supplier to which the material is assigned. A pull-down menu displays when materials have been assigned to multiple suppliers. You can choose to edit material information for all suppliers or individual suppliers by choosing the corresponding value from the Supplier pull-down menu.

Costing Level Indicates whether the costing level has been set for the material. SAP Ariba automatically sets the costing level at the assembly level if you receive a quote, or if pricing exists, either estimated or contracted. Buyers can manually override the automatic settings and SAP Ariba will not change manual updates to the costing level.

4. Item Information page tabs.

Page tabs Description

Pricing / Splits Enter estimated pricing and split details on this tab.

Assignment Info View item assignment information on this tab, including assignment type, ID, and name.

RFx View simple RFx event terms associated with the material.

5. Enter estimated pricing, split percentages, and estimated lead time. Click the Copy icon in the estimated price textbox to copy the price to another estimated price textbox. A message is displayed showing the copy status.

6. Click Export to Excel to export pricing information to Excel spreadsheet. You can enter price for materials missing pricing. Additionally, you can edit the estimated pricing for materials with pricing information. After the updates, click Import from Excel to import the Excel spreadsheet.


Enter BOM Split page

The following image describes the location of elements on the Enter BOM Split page:

1. Click to return to the BOM table on the Product Sourcing dashboard.2. Click Selected BOMs to filter selected BOMs by ID or name. You can also scroll through the list of selected

BOMs. Click a BOM ID to access the corresponding BOM on the BOM split page.3. Information about the BOM is displayed in the header. You can choose to update splits for all suppliers or a

single supplier by choosing the corresponding value from the Supplier pull-down menu.

Field Description

Parent BOM ID The ID of the parent BOM.

Parent BOM Name The name of the parent BOM.

Contract MFR The contract manufacturer to which the material is assigned. A pull-down menu displays when materials have been assigned to multiple contract manufacturers. Choose the contract manufacturers for which you want to edit material information.

4. BOM Split page tabs.


Pricing / Splits Enter estimated pricing and split details on this tab.




Assignment Info View item assignment information on this tab, including assignment type, ID, and name.

5. Click to expand and minimize item groups.6. Information about the item, including the ID, name, and material owner.

7. Enter estimated pricing, split percentages, and estimated lead time. Click the Copy icon in the estimated price textbox to copy the price to another estimated price textbox. A message is displayed showing the copy status.

User tasks for enhanced product sourcing UI tables for material and BOM views

How to update estimated pricing for materials [page 93]

How to complete splits for materials with missing AML splits [page 94]

How to add estimated lead time values to materials [page 95]

How to complete missing BOM splits [page 96]

How to update estimated pricing for materials

SAP Ariba allows you to update the estimated pricing for parts without AML suppliers assigned to it. You can also update or enter the estimated pricing for materials with missing pricing.

Prerequisites

Users must be a member of the Materials Manager or Materials Viewer group to add an estimated price to a part they own. You must be the material owner to edit or enter the estimated price.

Context

You can enter, or update estimated pricing from the following action tiles on Product Sourcing dashboard:

● Materials with owners● Materials without owners● Materials with missing prices● Materials with missing AML splits


Procedure

1. Click the Product Sourcing dashboard tab.2. Click the Materials with owners, Materials without owners, Materials with missing prices, or Materials with

missing AML splits action tile.3. Click the item ID for the material you want to edit.4. Click View / edit item info.

SAP Ariba displays the Item Information page.5. Do one of the following to enter estimated pricing:

○ In the materials list, enter the estimated price for the material in the textbox.○ Click Export to Excel to export pricing information to an Excel spreadsheet. You can enter price for

materials missing pricing. Additionally, you can edit the estimated pricing for materials with pricing information. After the updates, click Import from Excel to import the Excel spreadsheet.

○ Click the copy icon in the estimated price textbox to copy the price to another estimated price textbox. A message is displayed showing the copy status.

6. To view material assignment information, click Assignment Info.7. To view simple RFx event terms, click RFx.

Results

The updated pricing information is available in the user interface.

If you use the Import from Excel feature, the Excel file will be processed by a scheduled task that runs multiple times an hour. The import page contains an Import requests area with the following status information:

● A dropdown to select the time period for the status information (Last 7 days, Last month, All).● A button to Refresh the status information.● A status information table with the following columns:

○ User ID: ID of the user who submitted the data import.○ Type: Type of data import.○ File: Name of the file submitted.○ Start Date: Time and date the data was submitted.○ End Date: Time and date the data import completed.○ Elapsed Time: Time elapsed between the import submittal and the import completion.○ Status: Status of the data import.

How to complete splits for materials with missing AML splits

Prerequisites

Users must be a member of the Materials Manager or Materials Viewer group to enter split percentages for materials they own.



Context

There are two types of splits:

● Approved Manufacturer List (AML) - splits across every item and contract manufacturer● BOM - splits between item groups in a particular BOM

The action tiles that are available to you depend on the dashboard tabs that are available to you and your user permissions.

Procedure

1. Click the Product Sourcing dashboard tab.2. Click the Materials with missing AML splits action tile.

You can click Export to Excel to add your split percentages in a spreadsheet and then click Import from Excel.3. Click the item ID for the material you want to edit.4. Click View / edit item info.

SAP Ariba displays the Item Information page.5. Enter the split percentages in the Split % field.

NoteYou must be the owner of the material to add split percentages.

How to add estimated lead time values to materials

Buyers can find materials that have no lead time and enter an estimated lead time for them in the parts database.

Prerequisites

You must be a member of the Materials Manager, or Materials Viewer group to add an estimated lead time.

Procedure

1. Click the Product Sourcing dashboard tab.2. Do one of the following:

○ Click the Materials with missing lead time tile.


NoteThe Materials with missing lead time tile shows the materials that do not have a value for estimated lead time or lead time.

○ Click any materials tile.3. Click the item ID for the material you want to edit.4. Click View / edit item info.

SAP Ariba displays the Item Information page.5. Enter a value in the Estimated lead time (in days) field.

You can export and import the estimated lead time values using the Export to Excel and Import from Excel buttons.

You can also enter the estimated lead time value when creating a new material.

How to complete missing BOM splits

Prerequisites

Users must be a member of the Materials Manager or Materials Viewer group to enter split percentages for materials they own.

Context

There are two types of splits:

● Approved Manufacturer List (AML) - splits across every item and contract manufacturer● BOM - splits between item groups in a particular BOM

The action tiles that are available to you depend on the dashboard tabs that are available to you and your user permissions.

Procedure

1. Click the Product Sourcing dashboard tab.2. Do one of the following:

○ Click a BOM ID or BOM name and choose View BOM details. Then click BOM split and double-click the split percentage field to make it editable.

○ Click the BOM item groups without 100% split action tile. Select the BOM IDs for which you want to enter split percentages and click View / Edit BOM split info.

You can also click Export to Excel to add your split percentages in a spreadsheet and then click Import from Excel to upload your updates.



SAP Ariba displays the Enter BOM Split page.3. Do one of the following to enter BOM split percentages:

○ Enter split percentages in the Split % field.○ Click Export to Excel to export the BOM split detail information to an Excel spreadsheet. You can enter

split percentages directly in the Excel spreadsheet. After you make your updates, click Import from Excel to import the Excel spreadsheet.

○ Enter a split percentage in a Split % field and then click the copy icon in the Split % textbox. The Split % value you entered is copied to the remaining periods. A message is displayed showing the copy status.

NoteYou must be the owner of the material to add split percentages.

4. If you selected multiple BOMs, you can click Selected BOMs to navigate to the other BOMs you selected and enter split percentages.

DMS-7977: Ability to use reserve price, conditional visibility of questions, and multi-currency support for large-capacity eventsDescription

Products: SAP Ariba Strategic Sourcing Suite

SAP Ariba Sourcing

Audience: Buyers and suppliers


Contents for large-capacity events are accessed using Excel spreadsheets and are not directly visible in the user interface. Event managers create and edit contents using Excel spreadsheets, and participants submit responses using Excel spreadsheets. Event managers must also use Excel spreadsheets when allocating items in manual award scenarios for large-capacity events or selecting items in optimization scenarios for large-capacity events.

For more information about large-capacity events, see the Event management guide.

This feature includes the following enhancements to large-capacity event functionality:

● Ability for buyers to set reserve prices● Ability for buyers to define visibility conditions for questions● Ability for participants to select their bid currency from a list of currencies associated with the large-capacity

event


Limitations

Large-capacity events have the following limitations:

● Custom formulas are not supported. The rule Can project owner create formulas is set to No and is not visible.

● The values for calculated terms are shown on the Pricing worksheet, but the formulas for calculated terms are not shown on the Pricing worksheet. The formulas are shown only on the Terms worksheet.

● Matrix terms are not supported. Values are not summed up (rolled up) for matrix terms.● Buyers cannot configure initial bids for participants. You cannot set the Initial Bid option for participants and

the Set Participant-specific Values option is not available.● Grading and scoring is not supported. You cannot assign scoring points or grade suppliers.● Envelope bidding is not supported. You cannot create envelopes. The Envelope Rules section is not present in

templates for large-capacity events.● Conditional event content is only supported for regular questions. You cannot create event conditions or set

visibility conditions for prerequisite questions. Large-capacity events can contain up to 50 questions with visibility conditions.

● Participants cannot submit responses that include attachments. Questions with the Answer Type set to Attachment are not supported.

● Information about individual line items is not sent to SAP Ariba Analysis for reporting. For large-capacity events, a summary of the items is sent to SAP Ariba Analysis.



User tasks

● How to create large-capacity RFPs [page 101]● How to submit prices and responses for large-capacity RFPs [page 104]


User interface changes for buyers

The following user interface changes have been introduced for buyers:

● The Currency Rules area is now visible in RFP templates when the rule Capacity type for the event is set to Large. The following rules are displayed in the Currency Rules area:○ Allow participants to select bidding currency - When set to Yes, this rule allows participants to select the

currency in which they place their bids from a list of currencies associated with the event. Participants can only select the currency for lots and line items.



○ Show currency exchange rates to participants - This rule appears only if you chose to allow participants to select the bidding currency. If you select Yes, a currency exchange rate table appears on the Event Details page. A read-only version of the currency exchange rate table appears on the Currency Conversion worksheet in the event content Excel file.

● The Currency Conversion worksheet now appears in large-capacity event spreadsheets when currency rules are configured. This worksheet lists the conversion rate for all the currencies in your SAP Ariba system converted to the currency for this event. You can change the exchange rates, but you cannot add currencies that are not defined in your SAP Ariba Sourcing solution.

● The Reserve field is now editable in the Item Terms area.● The Reserve Price column is now available on the Pricing worksheet.● The market feedback rule Show reserve price to all participants is now configurable in large-capacity events.

If buyers want to communicate the reserve price to a participant, they can choose Yes. The alternative choice is to only let participants see the reserve price after they have met it.

● Buyers can now create visibility conditions for regular questions. Is this a prerequisite question to continue with the event? must be set to No. You cannot create event conditions or set visibility conditions for prerequisite questions.

● The Conditions worksheet now appears in the event content Excel file. Event questions with visibility conditions appear on the Content worksheet.

● The Visibility Condition column now appears on the Content worksheet.

User interface changes for suppliers

The following user interface changes have been introduced for suppliers:

● Participants can now select the currency in which they place their bids from a list of currencies associated with the event.

● The Reserve Value column now appears in all worksheets that contain line items.● When an event contains conditional event questions, a Conditional Questions link now appears in the event

checklist in the left pane of the event console.● The Conditional Questions page only displays content after the event opens and participants accept the

bidder agreement. Participants must answer all required conditional questions before they can download event content and submit responses. After participants submit their responses, the Conditional Questions page becomes read-only. If participants edit their response, values on the Conditional Questions page becomes editable.

● Conditional questions now display in the Excel response spreadsheet. Conditional questions appear on worksheets that contain content with visibility condition questions.

● Participant answers to conditional questions are displayed in the Answer column. The Answer column appears on worksheets that contain content with visibility condition questions. Values in the Answer column are locked and cannot be changed.

Workflow for large-capacity events

● An event manager creates an RFP using a template for large-capacity events.


● The event wizard opens. The event manager optionally adds participants from the Suppliers page in the event wizard. Alternatively, the event manager can add suppliers by entering the suppliers on the Participants worksheet of the Excel file used for adding line items in the next step.

● On the Contents page, the event manager creates an Excel template with the needed line-item terms by:○ adding one or more sample line items with the desired terms in the field-based user interface○ generating and downloading an Excel file (a template) from the sample data

● The event manager adds items to the Pricing worksheet of the Excel template. The event manager can also specify terms, event participants, line item participants, reserve price, and rules in the Excel template.

● Optionally, the event manager can add currency exchange rates on the Currency Conversion worksheet and define visibility conditions for questions on the Conditions worksheet.

● The event manager uploads the edited Excel template to the event and the file is validated and submitted for processing. It can take several minutes for the file to be processed. A page with the processing status opens. The event manager can return to the dashboard. SAP Ariba sends an email notification to the event manager when the file is processed. If the event manager remains logged in, they also receive an instant notification when the file is processed. Event managers cannot update any event components (contents, rules, or participants) while the Excel file is being processed. If the event manager attempts to update the event or start the event wizard while the Excel data is being processed, the processing status page opens.

● The event manager completes specifications for the event and publishes the event.● When the event is open, the participants:

○ complete event prerequisites○ answer conditional questions on the Conditional Questions page○ download the event contents to an Excel file○ edit the Excel file and add responses○ upload their edited Excel file

● The uploaded response file is validated and submitted to a queue for processing. Response files are processed in the order they are submitted. It can take several minutes for the file to be processed. The participant receives an email notification when the file is processed. If the participant remains logged in, they also receive an instant notification when the file is processed.

● Response files are accepted until the event closes. If the event closes and response files have been submitted but not processed, the event remains Closed (no additional responses are accepted and the time remaining is 00:00:00) but does not change to the Pending Selection state until all responses that were submitted before the event closure time are processed.

● If the RFP contains lots that require lot reconciliation, or lots with the lot type Basket - Bid at Lot Level, Compete at Lot Level (collect item pricing post bidding), the suppliers must download, edit, and submit Excel files for lot details responses.

● The event manager can view participants' bids by generating a bid report, such as a Full Bid Report. The event manager can create bid reports at any time. For example, the event manager can generate a bid report while the event is open to monitor the event, or when the event is in the pending selection state to evaluate bids for awards.

● After the event closes and is in the pending selection state, the event manager creates scenarios for awards. For manual scenarios, the event manager downloads an Excel file, edits the file to specify award amounts, and uploads the edited Excel file. The event manager must also use an Excel file when creating an optimization scenario if the event manager wants to select a subset of the event items for the scenario.



Best practices for large-capacity events

● Tell your participants to allow additional time to generate, view, edit, and submit bids. Tell participants to not wait until the closing minutes of an event to submit bids.

● If you are editing a large-capacity event that already has contents, ensure that you editing the most recent contents by clicking the Download content button.

● To get accurate Rank and bid information in an event report, generate the report after the event closes.

User tasks for ability to use reserve price, conditional visibility of questions, and multi-currency support for large-capacity events

How to create large-capacity RFPs [page 101]

How to submit prices and responses for large-capacity RFPs [page 104]

How to create large-capacity RFPs

Prerequisites

● Your site must have a template for large-capacity RFPs.● You must be a member of one of the following groups:

○ Category Manager○ Commodity Manager○ Customer Administrator (access to this group must be approved by SAP Ariba)○ Event Administrator (access to this group must be approved by the SAP Ariba Market Coordination Team)○ Junior Procurement Agent○ Junior Sourcing Agent○ Limited Event Administrator (access to this group must be approved by the SAP Ariba Market

Coordination Team)○ Procurement Agent○ Sourcing Agent○ Sourcing Approver○ Sourcing Project Administrator (access to this group must be approved by the SAP Ariba Market

Coordination Team)


Context

LimitationsYou cannot use the user interface to search for and add item master data directly to large-capacity events. You can search for and add the items to a standard-capacity event and export the contents to Excel. Then, add the Excel rows with item master data to an Excel file for the large-capacity event.

Procedure

1. If the RFP does not already exist, create it.

a. In Common Actions, click Create Sourcing Project .b. On the Create Sourcing Project page, enter a name and description for your event.

You can enter an unlimited number of characters in the Name and Description fields. Other fields might limit you to 255 characters.

c. If you want to copy another project, choose the project or event you want to copy from the Copy from Project pull-down menu. The option Do you want to copy project groups that were not in the template, from the project being copied? appears at the bottom of the page. Select Yes to import the project groups defined in the project or event you are copying.

SAP Ariba Sourcing automatically sets the event type and template to match the project or event you are copying. You can then modify the data you have copied.

d. If you are an SAP Ariba Sourcing Pro user, select the project type (Full Project or Quick Project).A full project can contain one or more sourcing events and includes additional project management features. If you select Full Project, you complete the creation of the full project, then create the RFP by navigating to the Documents area of the project and selecting Actions Create Event .If you select Quick Project, select RFP in the Event Type field.

e. Select a template for the large-capacity RFP (or full project, if you are creating a full project to contain your RFP event).

f. Click Create.2. If the event is not already open, click the event name in the Documents area and choose Open.3. In the event wizards, enter values on the Rules, Team, and Suppliers pages. Continue to the Contents page.4. If this is the first time you are adding content, you will see an Enter sample data area. Enter sample data to

create an Excel template with the format required by SAP Ariba Sourcing. Add at least one line item with the terms you want to use so the template contains entries for the terms. If you want sections or questions in the event, add at least one section or question.

NoteThe items you add here are in the sample data only; they are not added to the line items document until you export them to an Excel file and import them into the event.

By default, the maximum number of sample items must be less than 50.



a. Choose Add Line Item .b. In the Add Item page, enter a name for the item.c. Optional: Add a description. Specify the commodity, bidding rules, and any access control restrictions.d. Enter values for terms, such as Price, Quantity, and Reserve.e. To add more terms for the line item, click the Add button in the bottom left corner of the Item Terms area

and choose Term. On the Add Terms page, select a previously defined term from the Available Terms tab. Alternatively, open the New Term tab to define a new term.

f. Optional: Click Add Participants to add specify event participants for this line item.g. Click Done.

h. Optional: If you want to have sections in your event, add at least one section. Choose Add Sectionand complete the information for the section. If you want to have other non-item content in your event, such as questions, add at least one instance of the content by clicking Add and choosing the appropriate content type, such as Question. Specify information for the additional content and click Done.

i. Optional: If you want to add conditional questions to your event, choose Add Question and complete the information for the section. Is this a prerequisite question to continue with the event? must be set to No. You cannot create event conditions or set visibility conditions for prerequisite questions. Click none next to the Visibility Conditions attribute. Choose Create Condition. The Create Condition dialog box lists all available questions that you can use to build a condition. Specify information for the additional content and click Done.

5. Click Download content to generate an Excel template for the event. When SAP Ariba has finished generating the template, a browser dialog box opens with access options for the template file. Click Open or Save.

6. Open the Excel template and edit it according to the instructions on the Design Instructions worksheet in the template. Add items on the Pricing worksheet. Leave the System Id column blank.

7. Save the Excel file on your file system.8. Click Import Content.

The Import Content from Excel page opens.9. Select the type of event data you want to import, such as Contents.10. Select how you want to import the content (add to the content or replace the existing content).11. Select your Excel document with the event content (browse for the file, enter the file path, or drop a file icon in

the drag-and-drop box).12. Click Import.


SAP Ariba checks the Excel file for errors. If the file contains errors, you will see the message The Excel import request failed. Click the Download file with error details link. Open the file and go to the Error worksheet to view the errors.

If the Excel file is valid, a Status for pending content change page opens that shows the status of your Excel import request and a progress bar.

You do not have to keep this page open while your import request is being processed; you can click Return to dashboard. When your Excel import has been processed, you can return to the event wizard by clicking edit event. The Content page contains a section that lists the number of items, sections, and questions loaded.

How to submit prices and responses for large-capacity RFPs

A large-capacity RFP can contain up to 10,000 items. To view the items, you generate an Excel document with the contents; to submit responses, you edit and upload the Excel document.

Context

We recommend that you allocate time for processing the Excel document. All responses submitted before the event closing time are processed before a buyer can create awards for the event. However, we recommend that you submit your responses much earlier than the event closing time.

Procedure

1. If you are not already viewing the event, open the Events table for a buyer.2. Click the event name in the Events table.

Complete any event prerequisites.3. View the contents of the Introduction section. The Introduction section contains instructions posted by the

buyer and any documents that you should download and review. If the buyer attached documents, you can click the document title to download the file.

4. If the event contains conditional questions, a Conditional Questions link appears in the event checklist in the left pane of the event console. You must answer all required conditional questions before you can download event content and submit responses.After you submit your response, the Conditional Questions page becomes read-only. You cannot edit answers to conditional questions in the event content Excel spreadsheet.

5. If the View Contents and Submit Response page is not open, go to the event checklist in the left pane and click View Contents and Submit Response.

6. Click Generate Content to generate an Excel spreadsheet with the event contents.When SAP Ariba has finished generating the Excel spreadsheet, a Download contents link is displayed.

7. Click Download contents.8. Save the content to your computer.



9. Edit the spreadsheet in Microsoft Excel.

Review the instructional worksheets and note the background colors that indicate which cells are required, optional, or read-only.

On the Other Content worksheet, enter your responses. Indicate your intent to bid on an item by changing the value in the Intend to Respond column from No to Yes.

10. Save the edited Excel spreadsheet to your computer.11. Return to the View Contents and Submit Responses page. Select your edited Excel spreadsheet (browse for

the file, enter the file path, or drop a file icon in the drag-and-drop box).12. Click Submit response.

Processing a large response can take up to 30 minutes depending on the event size and the other responses being processed. You do not have to keep this page open while your response is being processed. After your response is processed, you'll receive an email notification. If you are logged in to SAP Ariba Sourcing, you will also receive an instant message.

13. If submitted bids for lots that require reconciliation (lots for which you must submit item prices after the event closes, or Basket - Bid at Lot Level, Compete at Lot Level (collect item pricing post bidding) lots), return to the event page after the event closes.

14. Click Enter Lot Details.The View Contents and Submit Response page opens.

15. Click Generate Content to generate an Excel spreadsheet with the event contents.When SAP Ariba has finished generating the Excel spreadsheet, a Download contents link is displayed.

16. Click Download contents.17. Save the content to your computer.18. Edit the spreadsheet in Microsoft Excel.

On the Other Content worksheet, enter prices for the individual items in the lot.19. Save the edited Excel spreadsheet to your computer.20.Return to the View Contents and Submit Responses page. Click Browse and locate your edited Excel

spreadsheet.21. Click Submit response.

SAP Ariba checks the Excel file for errors. If the file contains errors, you will see the message The Excel import request failed. Click the Download file with error details link. Open the file and go to the Error worksheet to view the errors.

If the Excel file is valid, it is submitted for import. You can close this page while your file is being processed. You'll receive an email notification when processing is complete. If you are logged in to SAP Ariba Sourcing, you will also receive an instant message.

If you submit a valid Excel file before the event closes but processing is not complete when the event closes, the buyer must wait to for your file to be processed before the buyer can create awards for the event.


DMS-8450: Product Sourcing dashboard data table filtering

Description


Audience: Buyers


Product Sourcing dashboard action tiles enable users to quickly filter material and BOM data. When users click an action tile, the data table shows the items that meet the criteria defined by the action tile, such as Materials without owners. Users can further refine items in the data table by clicking a column filter icon and entering data in the search box.

Previously, users needed to enter search terms in the column filter and click Filter to further refine items in the data table. Now, SAP Ariba automatically filters items in the data table as users type in the column filter search box. For example, when users type AAA in the Item Id column filter search box, SAP Ariba automatically filters the data table to only display items that contain AAA in the ID. Users can apply multiple columns filters at the same time.

For more information about the Product Sourcing dashboard, see the SAP Ariba product sourcing guide.

Prerequisites

The information and tiles displayed on your dashboard depend on your group membership:

● If you are a member of the Materials Viewer group, you see information about materials and materials assigned to you.

● If you are a member of the Materials Manager group, you see information about BOMs. You also see information about materials, such as materials for which you need to assign owners (materials that do not have owners assigned).

Limitations

Data table instant filtering is not available on the:

● Advanced Search page.● View BOM table in the context of a BOM quote.● Compare BOM popup.







● Column filter icons now indicate when items in the data table have been filtered by a search term.

○ SAP Ariba displays the following column filter icon when filtering is off:

○ SAP Ariba displays the following column filter icon when filtering is on: ● Column filter search boxes now display a Done button. Users can click Done to close the search box after

entering a search term.● To remove column filtering, users can delete the text in the search box or click (X) in the search box.

Instant data table filtering is available for the following material action tiles:

● Material with Missing Prices● Material with Missing AML Splits● Material with Owners● Materials without Owners● My pinned materials● All materials● New materials● Materials with Missing Lead Time

The following material data table columns instantly filter items as users type:

● Item Id● Item Name● Category● Programs● Contract MFR● Owner● Supplier● Part Type

Instant data table filtering is available for the following BOM action tiles:

● BOMs Missing Contract MFRs● BOMs Missing Programs● BOMs without 100% Split● Total BOMs● Active BOMs● New BOMs● All BOM Item Groups● Assemblies


The following BOM data table columns instantly filter items as users type:

● BOM Id● BOM Name● Programs● Contract MFR● Owner

DMS-8513: Ability to have UOM in product sourcing simple RFxDescription


Audience: Buyers


Unit of measure (UOM) and quantity for a material can now be sent into a sourcing event from a simple RFx. This allows suppliers to see what unit of measure (each, gallon, and so on) they are making quotes for.

NoteThis feature does not affect the full sourcing project.


When the Quantity term is added to simple RFx, a default quantity of 1 and the UOM for the item are sent to the sourcing event for material quotes.

UOM and quantity can be exported using the export pricing updates web service.

For more information about simple RFx, and the export pricing updates web service, see the SAP Ariba product sourcing guide.


The web service includes the following changes to the elements in the body of the previous web service:

● ItemList now includes UOM.● RFXCustomTermList no longer includes UOM, Quantity, and Currency.● RFXStandardTermList now includes UOM, Quantity, and Currency.



DMS-8962: Product Sourcing user interface enhancementsDescription

Products SAP Ariba Strategic Sourcing Suite Product Sourcing features

Audience Buyers

Enablement Automatically on

This feature is a collection of enhancements for the Product Sourcing user interface. The enhancements are made to the Product Sourcing dashboard, Advanced Search page, Compare BOM page and alert messages.

The following enhancements have been made to the Product Sourcing user interface:

● You now have the option of exporting only selected Bill of Materials (BOMs), materials, or items from the BOM or material table. Previously, in the Product Sourcing dashboard, all the entries listed in the table would be exported to a spreadsheet. This enhancement makes it feasible to export only the required entries, thus making it easier to handle the Excel spreadsheet.

● You can view the current month pricing in a pop-up window that is displayed, when you hover over the Item name in the material table on the Product Sourcing dashboard. Alternatively, you can also click the Item name to view the pricing.

● Previously, in the Advanced Search page you would click Go to Dashboard button, which reloads theProduct Sourcing dashboard. You can now click Back to navigate to the Product Sourcing dashboard.

● The alert messages displayed when a task is successful close automatically. Previously, an alert or error messages had to be closed manually.

● You can click the icon the change the columns displayed in the Compare BOM page.● Previously, you could select BOMs from the same BOM table for comparison. You can now select BOMs from

different BOM tables or search results and click Add to compare for comparison. The selected BOMs are added for comparison and banner is displayed at the top of the page, which gives information about the number BOMs selected. You can choose which of the two BOMs you want to compare from the list.




The following are the user interface enhancements:

● In the Product Sourcing dashboard, you can select the items in the data table to export and click Export to Excel to export items to a spreadsheet. You can also filter the items by the Item name and export the filtered items to Excel. If you click Export to Excel without selecting any items, all the items in the table are exported to the spreadsheet.


This functionality is available in the following Product Sourcing dashboard tiles:○ BOMs without 100% split○ Materials with owners○ Materials without owners○ Materials with missing prices○ Materials with missing AML split

● A new pop-up window is added to view the current month pricing for items in the material table. You can click View/edit item to display the Item detail page.The following image shows the pop-up window:

● In the Advanced Search page, a Back button is added to return to the Product Sourcing dashboard.● The alert messages displayed close automatically.● In the Compare BOM page, a settings icon is added, which helps filter the columns you want to display in the

BOM compare tables.● A new Add to compare button is added to all BOM list tables. This enables you to select two or more BOMs

from two different BOM tables or from the search results and add the BOMs for comparison. A banner is displayed on the top of page which gives information about the number of BOMs selected. When you click the banner, a pop-up window is displayed with the list of selected BOMs. You can select which of the BOMs you want to compare and click Compare 2 BOMs.

DMS-9020: Ability to import Material Group information

Description

Products SAP Ariba Strategic Sourcing Suite Product Sourcing features

Audience Buyers




This feature enables buyers to import material group information from the ERP system and making it available in SAP Ariba Strategic Sourcing Suite. You can now include material group information, while creating a simple RFX or sourcing project. This feature allows suppliers to view the material group for which they are quoting prices. SAP Ariba imports the material group information through the material master integration from the ERP system. The import request is processed by a regularly scheduled task that runs once a week.

On the Product Sourcing dashboard, you can click icon and select Material Group column to add to the data tables. In the BOM details page, you can click icon to add the t Material Group column to the data table. Each material group is associated with a one material. When buyers create simple RFX or full sourcing projects from Product Sourcing, SAP Ariba automatically transfers material group information to the sourcing project.

NoteThe sourcing project template used to create the simple RFX should have material group enabled.

Changes to the existing functionality

See DMS-9020: Changes to the existing functionality [page 111].

DMS-9020: Changes to the existing functionality

Buyers can now import the material group information from the ERP system through the material master integration.

User Interface changes

The following are the user interface enhancements:

● The Material Group column can be added to the data tables. You can click icon or icon and add Material Group column to the data tables. The Material Group column is available in the following dashboard tiles and user interface data tables:○ Materials with owners○ Materials without owners○ Materials with missing prices○ Materials with missing AML splits○ Advanced Search page○ BOM details page○ Material 360 page

● A new popup is displayed when you click Material Group. The pop-up displays Material Group ID and Material Group.


Data export

You can export material information as a part of web services export or you can use Excel export functionality. When exporting using web services, the following material group fields are exported:

● materialGroupId● materialGroupDesc

You can also use Export to Excel functionality to export material group information from the Materials with owners, Materials without owners, Materials with missing prices, and Materials with missing AML splits dashboard tiles or the BOM details page.

DMS-9022: Ability to access Material 360 View without using Product Sourcing dashboard

Description

Products SAP Ariba Strategic Sourcing Suite

Audience Buyers


This feature enables you to access the Material 360 View page when the Product Sourcing tab is not enabled. A new user group Item360 Viewer group is introduced for this feature. You can add the Item360 Viewer group to users who need access to Material 360 View page, but do not have permission to view the Product Sourcing tab. You can access the Material 360 View page from the event details page only if you are aasigned to the Item360 Viewer group. You can view the Sourcing activity, PIR activity, and Contract activity in the page.

Prerequisites

● You must have Product Sourcing enabled for you site.● You must add Item360 Viewer group to users to access the Material 360 View page.

Changes to the existing functionality

See DMS-9022: Changes to the existing functionality [page 113].



DMS-9022: Changes to the existing functionality


● A new user group, role, and permission hierarchy is added:○ Group: Item360 Viewer○ Role: Item360 Viewer○ Permission: Item360Viewer

● You can click in the Content section on the event details page to access the material 360 page.

DMS-9209: Custom fields enhancements

Description


Audience: Buyers

Enablement: Automatically On

Custom product sourcing fields can now be added to:

● The export pricing updates web service● Purchase information records (PIRs) sent to SAP ERP● Get quote for simple RFx or sourcing project

Custom fields are new fields that are mapped in product sourcing to item material master data from SAP ERP.

You can now add custom fields as terms in the line item for sourcing projects and BOM quotes. The term is populated with the value from the custom field in product sourcing. Custom fields can be sent in outbound PIR messages and added to the web service.

Prerequisites

A member of the Integration Admin group must review and accept the data definition changes for this feature.

Limitations

You can only search for custom fields on the Custom Field Mapping page.



Custom fields appear with their values from the item on the Content page of the sourcing event.


A new column, Include in Quote, is added to the dashboard for Custom Field Mapping in the Product Sourcing Manager area on the Administration tab.

A new field, Include in Quote, is added to the Add Record to Table popup for creating custom terms located in Custom Field Mapping in the Product Sourcing Manager area on the Administration tab.

A new field, External Field Mapping is added to the Edit Term page in the sourcing event template.

Administrator tasks

● How to map custom fields for getting quotes [page 114].● How to create an event template with custom fields for getting quotes [page 115]● How to create an event template with custom fields for PIR [page 116]


● Custom fields in export pricing updates web service [page 117]● Custom fields in outbound PIR messages [page 119]

How to map custom fields for getting quotes

Prerequisites

You must be a member of one of the following groups:

● Materials Administrator● Customer Administrator (access to this group must be approved by SAP Ariba)



Context

When you map item material master data received from SAP ERP to custom (new) product sourcing fields for items in BOM and material lists, you can choose to have the custom field included in simple RFx and sourcing events.

Procedure

1. Go to Custom Field Mapping located in the Product Sourcing Manager area on the Administration tab.2. Click Add.3. Choose true for Include in Quote.4. Make your choices from the remaining dropdowns in the Add Record to Table popup.

The Field ID should match the External Field Mapping value of the term in SAP Ariba Strategic Sourcing.

See the SAP Ariba product sourcing guide for more details on the remaining dropdowns in the popup.5. Click Submit.

Results

You can see a list of the custom mappings by clicking Search on the Custom Field Mapping page.

If you selected true for the Display In UI option, a user viewing a materials table can see the field and value by clicking the table menu in a material data table, showing the column Custom fields, then clicking View in the Custom fields column.

How to create an event template with custom fields for getting quotes

Prerequisites

To create or edit templates, you must be a member of one of the following:

● Customer Administrator group (access to this group must be approved by SAP Ariba)● Template Creator group● Template Creators group on the Team tab of the template project

The custom fields should already be mapped. For information on mapping custom fields, see the SAP Ariba product sourcing guide.


Context

Custom fields that are enabled to be included in quotes can be added to event templates.

Procedure

1. On the dashboard, click Manage Templates .2. From the Documents tab on the Templates page, click the dropdown next to Sourcing Templates.3. Select an RFP template and choose either Open or Copy.4. Before publishing the template, go to the Content tab.5. Edit the Line Item.

6. If the custom term is not in the Item Terms table, click Add Term and do one of the following:

○ Add the term from the Available Terms tab.○ Add the term on the New Term tab.

7. Select the term and click Edit.8. Verify the External Field Mapping value matches the value of the Field ID for the custom term in product

sourcing. Change the value if it does not match.

The predefined term with the correct mapping and data type must be in the template for the term to be created in the event.

See the SAP Ariba product sourcing guide for information on the Field ID when creating maps for custom fields.9. Return to the template project page when you have configured the template fields as needed.

10. Choose Properties and then Action Publish .

Results

You can now create events with custom fields and their values using the published template.

How to create an event template with custom fields for PIR

Prerequisites

To create or edit templates, you must be a member of one of the following:

● Customer Administrator group (access to this group must be approved by SAP Ariba)● Template Creator group● Template Creators group on the Team tab of the template project



The custom fields should already be mapped. For information on mapping custom fields, see the SAP Ariba product sourcing guide.

Context

Custom fields that are enabled to be included in outbound PIR messages can be added to event templates.

Procedure

1. On the dashboard, click Manage Templates .2. From the Documents tab on the Templates page, click the dropdown next to Sourcing Templates.3. Select an RFP template and choose either Open or Copy.4. Before publishing the template, go to the Content tab.5. Edit the Line Item.

6. If the custom term is not in the Item Terms table, click Add Term and do one of the following:

○ Add the term from the Available Terms tab.○ Add the term on the New Term tab.

7. Select the term and click Edit.8. Verify the External system field mapping for PIR: value matches the value of the Field ID for the custom term

in product sourcing. Change the value if it does not match.See the SAP Ariba product sourcing guide for information on the Field ID when creating maps for custom fields.

9. Return to the template project page when you have configured the template fields as needed.

10. Choose Properties and then Action Publish .

Results

You can now send custom fields and their values in outbound PIR messages using the published template.

Custom fields in export pricing updates web service

The Export Pricing Updates web service has a new element, CustomFieldsList.

An ItemInfo element contains a CustomFieldsList element if the URL for the export web pricing updates requests included an object=CustomFieldsList parameter or the object parameter was omitted. The CustomFieldsList element contains a list of custom field IDs, names, types, and values.

The CustomFieldsList element contains 0 or more CustomFields elements. Each CustomFields element specifies an assignment of a custom field ID, custom field name, type, and custom field value. There is a


CustomFields element for each assignment that was added or changed within the time range specified in the URL for the export pricing updates web service.

Each CustomFields element contains the following child elements:

CustomFieldId ID of the custom field.

CustomFieldName Name of the custom field.

Type The custom field type. The type can be string, numeric, or boolean.

CustomFieldValue The value of the field from product sourcing.

Active An Active attribute shows the element's object is active.

LastModified A LastModified attribute shows the date and time the element's object was last modified.

Unique Identifier

The values of the following elements together identify a unique data set:

● ItemId● CustmFieldValue

Example

<CustomFieldsList> <CustomFields> <ItemId>AC1000-222</ItemId> <CustomFieldId>cf123</CustomFieldId> <CustomFieldName>custom123</CustomFieldName> <Type>string</Type> <CustomFieldValue>ABC</CustomFieldValue> <LastModified>2019-05-11T09:44:54Z</LastModified> <Active>true</Active> </CustomFields> <CustomFields> <ItemId>AC1100-333</ItemId> <CustomFieldId>cf234</CustomFieldId> <CustomFieldName>custom234</CustomFieldName> <Type>string</Type> <CustomFieldValue>BCD</CustomFieldValue> <LastModified>2019-05-11T09:44:54Z</LastModified> <Active>true</Active> </CustomFields> . .</CustomFieldsList>



Custom fields in outbound PIR messages

Outbound PIR messages (PIR data sent to SAP ERP) now include custom fields from sourcing projects and simple RFx events.

The PIRFetchResponse message has been enhanced to include CustomFields.

The outbound PIR message sends all custom fields, custom field IDs, and custom field values from product sourcing to SAP ERP if they are mapped to be included in the quote, and they are on the event template.

Each CustomFields element contains the following child elements:

CustomFieldId ID of the custom field.

CustomFieldValue The value of the field from product sourcing.

CustomFields in XML

<xs:complexType name="CustomFields"> <xs:sequence> <xs:element name="CustomFieldId" type="xs:string"/> <xs:element name="CustomFieldValue" type="xs:string"/> </xs:sequence> </xs:complexType>

Example

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns2:PIRFetchResponse xmlns:ns2="http://ariba.com/s4/dms/schema/pir"> <ns2:ERPId>SAPERP1</ns2:ERPId> <ns2:RealmId>s4All-18</ns2:RealmId> <ns2:PIRInfo> <ns2:LineItemData> <ns2:AwardNumber>AANwAJcQwQE3n</ns2:AwardNumber> <ns2:ItemNumber>LINE1533676609122</ns2:ItemNumber> <ns2:MaterialNumber>AC10000-222</ns2:MaterialNumber> <ns2:VendorNumber>2000002</ns2:VendorNumber> <ns2:MaterialGroup>FPP_PROGR</ns2:MaterialGroup> <ns2:CreationDate>20190128</ns2:CreationDate> <ns2:UnitOfMeasure>EA</ns2:UnitOfMeasure> <ns2:CustomFields> <ns2:CustomFieldId>ABC</ns2:CustomFieldId> <ns2:CustomFieldValue>15</ns2:CustomFieldValue> </ns2:CustomFields> </ns2:LineItemData> . . . </ns2:PIRInfo> </ns2:PIRFetchResponse> </SOAP-ENV:Body>


</SOAP-ENV:Envelope>

DMS-9523: BOM hierarchy and BOM split export enhancementsDescription


Audience: Buyers


Exporting large BOMs from the BOM Details page may take some time for SAP Ariba to process. Now, when buyers export a large amount of BOM hierarchy and BOM split data from the BOM Details page, SAP Ariba processes the request in the background. When SAP Ariba completes processing the export request, buyers receive a message on the Product Sourcing dashboard. Buyers can download the BOM hierarchy and BOM split data export directly from the message.

Prerequisites

BOM data must be loaded through an integration, before they can be managed in SAP Ariba Strategic Sourcing Suite. BOM management functionality is only available for SAP Ariba Strategic Sourcing Suite buyers.

You must be a member of the Materials Manager or Materials Viewer group to view and export BOM details.



DMS-9523: User interface changesThe following user interface changes have been introduced with this feature:

● When buyers click Export to Excel on the BOM Details page for BOM hierarchy and BOM split data, SAP Ariba displays a confirmation message at the top of the screen indicating that the export request was successfully submitted.

● After SAP Ariba processes the export request, the notification bell icon ( ) on the Product Sourcing

dashboard indicates that a new notification is available ( ).



● Buyers can click the notification bell icon ( ) to view their list of notifications. Buyers can click Download in the notification list to download the corresponding BOM hierarchy and BOM split data export Excel file.

SC-5081: Mass application of conditions in an assembled contract document

Description

Product: SAP Ariba Contracts

Audience: Buyers


You can use a Microsoft Excel document to associate conditions with clauses or sections in a Main Agreement or Contract Addendum (called an assembled contract document). You can use conditions to include clauses or sections in assembled contract documents based on the value of project header fields. For example, you could include a clause with United States environmental regulations in a Main Agreement if the Regions project header is United States.

You can also bulk-load conditions into a Contract Workspace template. See Bulk-loading conditions with Microsoft Excel import [page 123].

How to mass-apply conditions in an assembled contract document

Prerequisites

You must be able to add documents to a project template. For example, members of the Template Creators group and members of the Templates team can do this. You must have Enhanced Contract Authoring enabled to use this feature.

Context

The first step is to export the conditions file from the assembled contract document. Make any updates to the file, including adding conditions, and then import the updated file.


Procedure

1. Open a Contract Workspace template.2. Upload a Main Agreement or Contract Addendum document.3. In the Outline View tab, on the Actions menu, under Condition mapping, click Export.4. Examine the exported conditions file and prepare any changes.

The conditions file is an Excel file that contains two sheets.

The first sheet, ConditionMapping, maps clauses or sections to conditions. This sheet includes these columns:

○ Internal Id: Unique identifier for a section or clause in an assembled contract document. These internal IDs are generated when you export the conditions file. Clause internal IDs start with "Doc" and section internal IDs start with "WS".Conditions are applied based on the internal ID only; the order of the content in the file does not matter.

NoteInternal IDs change from version to version of the same document. Before you import a conditions file into a document, make sure that you have applied conditions to a freshly exported conditions file from the same version of the document.

○ Section Title/Clause Text: Either a section title or the text of a clause in an assembled contract document. You can apply conditions to either clauses or sections.

○ Compound Type: Enter Any of, All of, None of, or Never matches, which apply to the conditions referenced in the Conditions column. For each of these compound types, you must use the appropriate number of conditions, as follows:○ Any of: 0 or more conditions○ All of: 2 or more conditions○ None of: 1 or more conditions○ Never matches: exactly 0 conditions

NoteThe compound type cannot be blank.

NoteNever matches means to remove the section or clause from the document.

○ Conditions: Entry in the Unique Name column in Conditions, the second sheet in the conditions file. You can separate multiple conditions by using the vertical bar (|).

○ Update Condition: Enter true or false. True means to update the Conditions and/or Compound Type on that row; false means to leave them as is. When you initially export the conditions file, the Update Condition column is set to false for all rows.

The second sheet, Conditions, defines conditions and includes two columns:

○ Unique Name: The unique name of the condition, which you enter into the Conditions column in the ConditionMapping sheet.

○ Expression: The condition itself; for example (OR ((Region)is equal to(China))).



NoteThe expressions on the Conditions sheet are for reference only. You cannot re-import them.

For more information on creating conditions, see "How to make clauses conditional" in the Contract authoring guide, which describes how to associate conditions with one clause in a document. For details about the syntax of conditions, see the Project template guide.

5. To import the conditions file, return to the Outline View tab, navigate to the Condition mapping area, and click Actions Import . Browse to the location of the file you want to import.

The import may not happen in real time. Click the Refresh Status button if it appears.6. After the import, check the Status column, which will show one of these values:

○ In Progress: The import process is in progress.○ Completed: The import process successfully completed processing all the records (rows) in the Excel file.○ Completed with errors: The import process completed processing all the records (rows) in the file, but

there are errors in the Error Log.○ Failed: The import process failed. It did not process the entire set of records in the file.

7. If necessary, click View Details in the Error Log column to see any errors.

If you see only one row (the header row), there are no errors.

Bulk-loading conditions with Microsoft Excel importYou can use a text-based syntax in Microsoft Excel to bulk-load conditions. Conditions can be either simple expressions or compound expressions composed of other compound expressions and/or simple expressions.

Prerequisites

You must be able to add documents to a project template. For example, members of the Template Creators group and members of the Templates team can do this. You must have Enhanced Contract Authoring enabled to use this feature.

To bulk-load conditions, first export conditions from the Conditions tab of a Contract Workspace template. Then, in the exported spreadsheet, put the expressions in the Conditions spreadsheet in the Expression column:


Change to existing functionality

This feature adds the Export and Import menu items to the Actions button next to the conditions on the Conditions tab of a Contract Workspace template.

Workflow

The workflow for bulk-loading conditions is separate from the workflow described in How to mass-apply conditions in an assembled contract document [page 121]. The syntax for writing conditions is different from the syntax described in that topic. However, as is true for the other workflow, it is helpful to create conditions, export them, make changes, and then re-import the Excel file.

For example, if you want to create different conditions based on region and department, you can create one condition in the template, export the condition, cut and paste in Microsoft Excel to make the changes you want, and then re-import the conditions. When the conditions are imported, they appear on the Conditions tab of the Contract Workspace template.

How to create the text-based syntax for conditions

In the user interface, you can create a compound expression like the following:

For details on how to create conditions in the user interface, see the Project template guide.



Each of these three lines is a simple expression that evaluates to true or false. You can link these three lines by choosing All Are True, Any Are True, or None are True.

● All Are True is like using "and" between the simple expressions. The compound expression using All Are True evaluates to true only if all three simple expressions are true.

● Any Are True is like using "or" between the simple expressions. The compound expression using Any Are True evaluates to true if any one of the three simple expressions is true.

● None Are True is like using "not...and not...and not" between the simple expressions. The compound expression using None Are True evaluates to true only if none of the simple expressions is true.

Using All Are True, the compound expression shown above can be written as: (AND(((Region)is child of(EMEA))((Commodity)is in list(unspsc:5310|unspsc:5311))((Client)is equal to(300)))). This is the syntax for Excel import.

NoteUse the unique names of the fields instead of their localized user interface labels. For example, Regions from the UI becomes Region, andDepartments becomes Client.

In properly indented format, the expression above looks like this:

● The outer parentheses, shown in yellow, are the root parentheses of the compound expression. These parentheses enclose the entire expression.

● The next set of parentheses, shown in turquoise, are the compound expression parentheses. These parentheses enclose all child expressions, simple and compound.

● The next set, shown in green, are the simple expression parentheses.● Finally, the innermost set, shown in gray, are the field name or field value parentheses. Both field names and

field values must be enclosed in parentheses.

Parentheses must be in matched sets. Unmatched parentheses cause an error. Note that there are no separators between expressions.

To easily write this syntax, start with the basic format:

(AND ( ))


Write the simple expressions one at a time. First write:

(AND ( ((Region) is child of (EMEA)) ) )

Then write the Commodity line:

(AND ( ((Region) is child of (EMEA)) ((Commodity) is in list(unspsc:5310|unspsc:5311)) ))

Use unique lookup keys for field values. Use a colon in case of multiple lookup keys. For example, above, unspsc:5310 represents the Clothing commodity in the UNSPSC domain. The vertical bar (|)separates multiple field values.

Fields can be of the following types: Boolean (true/false), Date, Decimal Number, Double (decimal), Group (unique name), Integer, Money, Multiline Text (String), Percentage, String, Text (String), Text Multiple Select (multiple strings), URL Link (String), User (unique name), and User Multiple Select.

NoteFor the date, use the concise date format that corresponds to your locale; for example, MM/DD/YYYY for the US locale. For another locale, you may need to use DD/MM/YYYY or whatever your standard date format is.

Predefined fields that can be used include Commodity, Region, Client, Supplier, and Organization. For a complete list of the predefined fields, and for information about custom fields, see Using predefined and custom fields when you bulk-load conditions in a Contract Workspace template [page 126].

Some data field values must match specific values in the system, such as values for regions or commodity codes. For these field types, use an export task to find out what the specific values should be. If you can't access the necessary export task, contact your Customer Administrator.

Using predefined and custom fields when you bulk-load conditions in a Contract Workspace template

When you use Microsoft Excel to bulk-load conditions into a Contract Workspace template, you can use both predefined and custom fields.

The table below shows the names of the predefined fields to use when you are bulk-loading conditions into a Contract Workspace. In the Excel file, use the unique name listed in the first column below, not the user interface name listed in the second column.

If your site uses custom fields and you want to generate unique names from the user interface names, add the prefix cus_ and remove any spaces from the user interface name. For example, a custom field with the user interface name Purchasing Order Amount has the unique name cus_PurchasingOrderAmount. You can get the unique names of fields by first exporting conditions as described in Bulk-loading conditions with Microsoft Excel



import [page 123]. If a condition is defined on a field, you'll see the unique name of the field in the spreadsheet as part of the expression for that condition.

Unique name User interface name

Active Active

AdhocSpendUsers Ad hoc Spend Users

AffectedParties Affected Parties

AgreementDate Agreement Date

AllowAdhocSpend Allow Ad hoc Spend

AmendmentReason Amendment Reason

Amount Contract Amount

arb_CompanyCode Company Code

arb_DocumentCategory Document Category

arb_DocumentType Document Type

arb_PaymentTerms Payment Terms

arb_PurchasingGroup Purchasing Group

arb_PurchasingOrganization Purchasing Organization

AutoRenewalCount Auto Renewal Count

AutoRenewalInterval Renewal Interval (in months)

BaseLanguage Base Language

BeginDate Start Date

BusinessSystem External System

Client Departments

Commodity Commodity

ComplexSpendAmount Total Approved Amount

ComplexSpendAvailableAmount Available Amount

ComplexSpendReleaseApprovers Release Approvers

ComplexSpendReleaseCreators Release Creators

ContractCreationSupplierClassification

Minimum supplier status for contract creation

ContractId Contract ID

ContractIntegrationSupplierClassification

Minimum supplier status for contract integration with ERP

ContractPublishingSupplierClassification

Minimum supplier status for contract publish

ContractStatus Contract Status

DisplayStatus Status

EffectiveDate Effective Date



EndDate End Date

EngagementRequestId Engagement Request Project

ExpirationDate Expiration Date

ExpirationTermType Term Type

ExpiringEmailRecipients Expiration Email Recipients

ExpiringReminderBegin Email Notification

ExpiringReminderFrequency Expiring Reminder Frequency

ExternalPublishVersion External Publish Version

HierarchicalType Hierarchical Type

InternalId ID

IsComplexSpendWorkspace Combined Spend

IsEvergreen Is Evergreen

IsInProjectTemplate Is In Project Template

MaxAutoRenewalsAllowed Maximum number of Renewals

NoticeDate Notice Date

NoticeEmailRecipients Notice Email Recipients

NoticePeriod Notice Period (in days)

NoticeReminderBegin Notice Email Notification

NoticeReminderFrequency Notice Reminder Frequency

Origin Origin

OriginalExpirationDate Original Expiration Date

Owner Owner

ParentAgreement Parent Agreement

ProcessStatus Process Status

ProposedAmount Proposed Contract Amount

ProposedIncrementalAmount Proposed Incremental Amount For Approval

Region Regions

RelatedId Related ID

SelectLineItemToSendExternalSystem Enable Select Line Items To Send External System

Status Project State

Supplier Supplier

TimeCreated Time Created

TimeUpdated Time Updated

UserGroups User Groups

UserPermisssions User Permissions




Workspace Workspace

SC-5088: Manage individual redlining changes inline in Enhanced Contract Authoring

Description

Products: SAP Ariba Contracts

Audience: Buyers


This feature allows users to accept or reject individual modifications to a document while reviewing a red-lined document that has been uploaded to SAP Ariba Contracts.

Context:

Buyers often work with multiple suppliers on contracts and need to update documents in the contract workspaces such as the main agreement or the contract addendum. Buyers author the existing main agreement or addendum by downloading and making additions or adding clauses from the clause library. Buyers can also modify these documents as part of negotiation via the negotiation tasks. When the other parties or suppliers propose changes, buyers might want to review each change individually within SAP Ariba Contracts while uploading (by browsing or via drag and drop) or at the time of negotiation and review tasks.

Previously, when a new document was uploaded, buyers were shown the number of changes and the suggested additions and deletions. Buyers could choose Process Changes to accept the changes, or Reject Changes to reject the changes. Buyers could then save the document as a new version or replace the current version of the document.

With this feature, the Process Changes and Reject Changes options are renamed to Process All Changes and Reject All Changes, respectively. Two new options, Process Change and Reject Change, are added to allow buyers to go through each change individually and accept or reject it.

Prerequisites

You must have Enhanced Contract Authoring enabled to use this feature.

This feature requires the “ActiveX Removal” feature and the “Drag And Drop” feature. To enable these features, have your Designated Support Contact log a service request. An SAP Ariba Customer Support representative will follow up to complete the request.



● SC-5088: User interface changes [page 130]

SC-5088: User interface changes

Previously, when a new document was uploaded, buyers were shown the number of changes and the suggested additions and deletions. Buyers could choose Process Changes to accept the changes, or Reject Changes to reject the changes. Buyers could then save the document as a new version or you can replace the current version of the document.

With this feature, the Process Changes and Reject Changes options are renamed to Process All Changes and Reject All Changes, respectively. Two new options, Process Change and Reject Change, are added to allow buyers to go through each change individually and accept or reject it.

SC-5103: Increase the 100 MB attachment and document size limitation for contracts to 2 GB

Description


Audience: Buyers


This feature allows users of SAP Ariba Contracts to upload attachments with a maximum size of 2 GB for contracts.

Previously, you could upload attachments and documents with a maximum size of 100 MB for contracts.

Now, you can upload attachments and documents with a maximum size of 2 GB for contracts. The supported document types are Word documents (.doc, .dot, .docx), Excel documents (.xls, .xlt, .xla, .xlsx), and .zip files.

NoteWhen you select the document and upload it, the progress bar screen displays the following message for large documents: "Note that if the file being uploaded is of a larger size, it may take time to upload depending on the network bandwidth. Do not go back or close the window, else upload will be terminated. It may take multiple hours to upload a file of size 2GB".



NoteIf the file you upload exceeds the maximum file size for indexing (104857600 bytes), the file will get uploaded, but keyword searches cannot be performed.


This feature is disabled by default. To enable this feature, have your Designated Support Contact (DSC) submit a Service Request (SR). An SAP Ariba Customer Support representative will follow up to complete the request. SAP Ariba configures the following to enable this feature on your site:

● Application.ACM.FileUploadMaxSize: The value of the parameter is in bytes. This parameter must be set to 2147483647.

● Application.ACM.BackgroundProcessAttachmentSize: The value of this parameter is in bytes. This parameter must be set to 2147483647.

SC-5159: Mass upload contract documents to multiple workspaces

Description


Audience: Buyers


This feature allows users to add one or more contract documents to multiple workspaces simultaneously using the project mass edit utility or the edit template option. The new documents are addded to the selected contract workspaces in the root folder of the Documents tab.

NoteEditing a template and publishing a new version does not affect any contract workspaces created with the previous version of the template by default. However, SAP Ariba Contracts has an option for updating a contract workspace created from an updated template when the project owner amends the contract workspace. If your site does not support upgrading template versions in contract workspaces, contact SAP Ariba Customer Support.

Context:

New contract documents may sometimes be needed to be added to multiple workspaces. For example, a new law may require the addition of new documents to all contract workspaces for suppliers in a particular region.


Alternatively, multiple contract workspaces created from a single template may need to be updated to reflect new requirements – for example, secondary data processors to be added to IT contracts.

Previously, you could only add contract documents to multiple workspaces individually. You also could not simultaneously add documents to or update multiple contract workspaces created from a single template.

With this feature, contract administrators can add new documents by choosing the Document document type, and upload the documents individually or as a single .zip file containing multiple contract documents. Contract administrators can also choose to add new contract documents to a contract workspace template, and propagate the addition to all the active contract workspaces created from that template.

Prerequisites

The ability to upload one or more contract documents to multiple workspaces simultaneously is controlled by group membership.

● Members of the Mass Edit Administrator group can access the mass edit admin option.● Members of the Project Mass Edit Administrator group can access the new Upload Document(s) option and

can select the workspace(s) to upload their contracts documents to.

NoteAssign users to the Project Mass Edit Administrator group with extreme caution; membership in this group circumvents access controls to provide mass edit capabilities. Members of the Project Mass Edit Administrator group can use the project mass edit feature to search for and edit any project of any type, regardless of any access control restrictions. The only projects that members of this group cannot search for or edit are deleted projects.

Limitations

If the workspace is in Published status, any upload of contract documents triggers the creation of an Amendment amendment, and the relevant amendment tasks are re-triggered.

NoteUsers of the Project Mass Edit Administrator group must use this feature with caution and must ensure that the affected project owners are aware of the change to their workspaces (as the project owners may have disabled the automatic notifications).


● SC-5159: Administrator interface changes [page 133]



SC-5159: Administrator interface changes

The Project Manager Mass Edit Projects option in Ariba Administrator includes a new check box, Upload Document(s), in the Select Fields to Update option. A single document can be uploaded as it is, or multiple documents can be zipped together and uploaded as a single .zip file.

How to mass upload contract documents to multiple workspaces by using the project mass edit utility

Prerequisites

You must be a member of the Project Mass Edit Administrator group.

NoteAssign users to the Project Mass Edit Administrator group with extreme caution; membership in this group circumvents access controls to provide mass edit capabilities. Members of the Project Mass Edit Administrator group can use the project mass edit feature to search for and edit any project of any type, regardless of any access control restrictions. The only projects that members of this group cannot search for or edit are deleted projects.

Context

The project mass edit utility enables you to edit multiple projects at once.

Procedure

1. In Ariba Administrator, choose Project Manager Mass Edit Projects .2. Select the projects you want to edit.

a. Select the Contract Workspace (Procurement) project type from the Project Type pull-down menu.b. To search for matching text in text-based project fields (such as the Title, Description, and Owner fields),

enter text in the unlabeled text box.c. To search for matches in specific project fields, click the + button to add a field filter.

The search utility adds the most commonly used field filter. To change the field filter, click the field’s pull-down arrow, and select a different field.

The search fields available depend on the type of project selected.


For additional information about specifying search criteria, see the Searching, completing tasks, and other common user actions guide.

Click Reset to reset all the search criteria except the Project Type field. You can only search for and edit one project type at a time.

By default, a field filter with no value specified matches any value in that field (like a wildcard). To to match empty values in a field, choose Options Match Empty Values from the upper-right corner of the search page. The Match Empty Values option is valid for all fields except the title field, and for all field data types except Boolean. For more information, see the Using and customizing the dashboard guide.

3. Click Search.4. Select the check boxes for the contract workspaces you want to edit and click Add.

Projects you edit appear on the projects to update page.5. Click Next.6. Click Select Fields to Update. The page displays the fields that can be edited.7. Select the check boxes for the Update Document(s) field, and click OK.8. Upload the contract document that you want to add to the workspace. If you have more than one contract

document, zip all the contract documents and upload a single .zip file. The zipped files are extracted and added to the workspace individually.

9. Click Next.10. Click Select Project Groups Fields. The page displays the project groups that can be edited.11. Select the project groups you want to update and click Next.12. Click Next.

The Review Edits page opens with a summary of the projects selected for editing and the fields and project groups to be edited.

13. To submit the mass edit changes, click Update.

The Mass Edit Wizard status page appears. SAP Ariba sends you a notification email when your mass edit changes are complete, with the mass edit report attached.

How to view the status of mass upload of contract documents to multiple workspaces

All changes made during a mass edit are captured both in an Excel report, one per mass edit, and in the audit trail on the History tab of each updated project. If an error occurs during the mass edit process, changes to the project that encounters the error are rolled back.

Context

You can view the status of mass uploading contract documents to multiple workspaces by using the project mass edit utility.



Procedure

1. In Ariba Administrator, select Project Manager Mass Edit Status .2. Click View details to view the changes made during the mass edit process in an Excel report.

NoteIf errors occurred during mass edit of a project, the errors are saved and displayed when the mass edit process is complete.

If the contract documents were uploaded successfully, the workspaces in the Published status are amended and moved to the Draft status. Other statuses remain the same.

How to mass upload contract documents by using the edit template option

Prerequisites

To create or edit project templates, you must be a member of the global Template Creator group or the template project’s Templates Creator team.

Context

To edit a template, the template status must be Draft. If you have published a template, you must create a new, draft version of the template to edit. When you are done editing a template, you must publish the template to make the changes affect subsequent projects created using the template.

Procedure

1. On the dashboard, click Manage Templates .2. Locate the template you want to edit. Click the template name and select Open.3. Navigate to the Overview tab of the template.

4. In the Properties pane, select Actions Template New Version . You can modify and add contract documents to the template.Open the workspaces associated with the template, and verify that the contract documents are added to the workspaces. You can choose to trigger a load of these documents to all contract workspaces. All the added documents will be loaded to the workspaces, that is, you cannot add three documents to the template and choose to trigger a load of only two of them.


5. Choose Actions Publish on the Overview tab.

Editing a template and publishing a new version does not affect any contract workspaces created with the previous version of the template by default. However, SAP Ariba Contracts has an option for updating a contract workspace created from an updated template when the project owner amends the contract workspace. If your site does not support upgrading template versions in contract workspaces, contact SAP Ariba Customer Support.

NoteDocuments do not have versions within a particular version of a template. However, if you make changes to a document in a subsequent version of a template, the original version of the document is retained in the previous template version.

SC-3299: Commodity price escalation management

Description


Audience: Buyers


Feature IDs associated with this feature: SC-5090, SC-5148, SC-5149, SC-5062, SC-5128, and SC-3307.

This feature allows you to create and maintain escalation clauses within your contract workspace to periodically adjust the pricing of purchased components based on market changes to the prices of the specified base materials. SAP Ariba Contracts allows you to create and apply escalation clauses in your contracts and synchronize escalation terms with related contracts.

Context:

The prices of commodities vary based on various factors such as the demand for the materials, changing economic climate across the globe, or random market fluctuations. If the items you intend to procure contain raw materials whose prices fluctuate, you might incur a loss if the market prices of the raw materials differ greatly from the price you set for them. By adding escalation clauses into your contract workspace, you can mitigate potential risk from market fluctuations.

You can configure which commodity markets the pricing fluctuations of commodities must be checked against.

NoteYou can associate a Contract Line Item with more than one commodity escalation clause.



Prerequisites

You can manage commodity price escalation clauses, but must have Contracts Line Items Document enabled to apply them.

To administer commodity escalation clauses, you must be part of the Commodity Escalation Administrator group.

Workflow for commodity price escalation management

The following is a sample worflow showing how a buyer incorporates escalation clauses into the contract with a supplier.

● The buyer notes that a part to be sourced from a supplier is made of two metals.● The buyer discusses escalation clauses with the supplier. The buyer can create two escalation clauses and link

both of them to a single part.● The composition percentage of the metals in the part is taken into account while updating the price of the part.

That is, if the escalation clause specifies the price per pound of the metal but the part contains only 5 grams of that metal, then the price of the part is updated accordingly based on the formula configured by the buyer when the prices of the metals change.

● When the Contract Line Item Document (CLID) is opened, the updated metal and total prices are reflected in it.

Support for multiple currencies in escalation clauses

The following is a sample worflow showing how a buyer incorporates multiple currencies in escalation clauses.

● The buyer notes that a part to be sourced from a supplier is made of a certain material, such as copper.● The buyer procures the part in USD currency, but is located in Europe. So the buyer creates an escalation

clause for copper and specifies the price in EUR currency.● If the buyer created a formula that uses the price of copper to calculate the total price for the part, then the

total price calculation is triggered when the prices of copper is updated. The total price calculation occurs after the price of copper is converted from EUR to USD.


● Changes to existing functionality [page 138]● SC-3299: User interface changes [page 138]

Administrator tasks

● How to access the commodity escalation manager [page 140]


● How to create a new escalation clause [page 141]● How to add or update prices in an escalation clause [page 141]● How to view contracts associated with a particular commodity escalation clause [page 142]

User tasks

● How to add or link a commodity escalation clause to a CLID [page 143]● How to add a formula to a commodity escalation clause in a CLID [page 143]

Commodity escalation reporting reporting fact

● Commodity escalation reporting fact [page 139]


Previously, if the prices of base materials used in a component changed due to market fluctuations, the prices of the corresponding purchased components were not updated.

Now, you can add a commodity escalation clause and link the clause to a line item that comprises a base material. In the commodity escalation clause, you can specify a global market from which to source the escalated price of a base material, and add a formula to calculate the total price of the commodity. When the price of the base material changes, the price of the commodity is updated in the CLID based on the formula.

SC-3299: User interface changes

The Manage Administration includes a new option, Commodity Escalation Manager Escalation Clause Configuration . Selecting this option opens a new page, Commodity Escalation Clause Management, which lists the available escalation clauses.

The line item page includes a new field, Commodity Escalation Clause, which displays a list of available escalation clauses.

This option is available only to users who are part of the Commodity Escalation Administrator group.



Commodity escalation reporting fact

This fact tracks escalation and de-escalation of commodity prices as they fluctuate based on market phenomena.

About Commodity escalation reporting fact

This reporting fact is available in:

● SAP Ariba Contracts

Source of Data

The Commodity escalation reporting fact contains data from contracts.

Level of Data

Commodity escalation reporting fact data is loaded at the line level, meaning that there is one record per escalation clause.

Frequency of Data Loads and Data Retention

Your site queues a new data load six hours after the completion of the previous load. Because of interruptions to data loads and staggering in data load queues, it might take longer than six hours for new data to be available in reports. It generally does not take longer than ten hours. SAP Ariba retains the data for the duration of the subscription unless otherwise required by law. For more information about data retention in SAP Ariba cloud solutions, see the Solutions description guide.

Access Control

All SAP Ariba Contracts users who have permission to run reports have access to Commodity escalation reporting fact data.

Typical Uses

● Users can learn how many clauses are being used or linked to a line item.


● Users can learn which clauses are being used or linked to a line item.● Users can filter a report based on each commodity escalation clause.● Users can learn how many contract workspaces are being used by one or more commodity escalation clauses.

Related Prepackaged Reports

No prepackaged reports are built on the Commodity escalation reporting fact.

Commodity escalation reporting Content

This section includes information about the measures in this fact. For information about other field content, see the Ariba Reporting Field Dictionary.

Pre-Defined Measures:

Measure Description

Count The number of line items using the escalation clause.

Multi-Fact Relationships

The new Commodity escalation reporting fact has no multi-fact relationships.

Administrator Tasks

How to access the commodity escalation manager

Context

You can open the commodity escalation manager to search for, edit, or manage commodity price escalation clauses and also add or view prices.



Procedure

Navigate to Manage > Administration > Commodity Escalation Manager > Escalation Clause Configuration. The Commodity Escalation Clause Management page lists the available escalation clauses. On this page, you can search for, create, edit, or manage escalation clauses and also add or view prices.

How to create a new escalation clause

Context

You can create a new commodity price escalation clause.

Procedure

1. Navigate to Manage > Administration > Commodity Escalation Manager > Escalation Clause Configuration. The Commodity Escalation Clause Management page lists the available escalation clauses. On this page, you can search for an escalation clause or add or view prices for a commodity.

2. Click the Create New button to add a new escalation clause. Note that you can create more than one escalation clause for a commodity term. For example, you can create more than one escalation clause for the commodity Aluminium, specifiying different frequencies (that is, the time interval or intervals in which the prices of the commodity term will be available). time interval when new prices for the commodity term will be available

3. Specify details for the escalation clause, such as the title, commodity name, frequency, the exchange rate set to be used, market (the exchange market from which the prices of this commodity must be derived), currency, unit of measurement, the tolerance, and whether the tolerance is by percentage or by value.

How to add or update prices in an escalation clause

Context

You can add or update prices in an escalation clause.


Procedure


2. From the list of escalation clauses, identify the escalation clause you wish to edit, and click the Action button. By default, the price for a newly created escalation clause is 0.

3. Click Edit to edit the escalation clause or Add Price to add a price in the escalation clause. If you click Add Price, a new page opens with a Commodity Price section, on which you must specify dates for the Valid From and Valid To fields and specify the new price in the Price field.

4. Click Save. You can verify that the price you specified for the commodity term shows in the Commodity Price for that column in the Commodity Escalation Clause Management page.

How to view contracts associated with a particular commodity escalation clause

Context

You can view contracts associated with a particular commodity escalation clause.

Procedure


2. From the list of escalation clauses, identify the escalation clause you wish to edit, and click the Action button.3. Click View Contracts to view the contracts associated with the escalation clause.

The Commodity Definition page opens. The page displays details about the commodity escalation clause and the contract items associated with the clause.

4. On the Contract Items tab, click the number (for example, 2) displayed under the No.Of Line Items column.

The contracts associated with the commodity escalation clause are displayed.

User Tasks



How to add or link a commodity escalation clause to a CLID

Context

Procedure

1. Navigate to your contract workspace.2. Click the Documents tab.3. Select the Contract Line Items Document (CLID) to which you want to add a commodity escalation clause.

Alternatively, right-click the document and click Line Items Document to create a new CLID and add line items to it.

4. Select the line item to which you want to add a commodity clause.5. In the Commodity Escalation Clause field, select the commodity escalation clause that you wish to add to the

contract workspace from the list of available commodity escalation clauses.6. Click Done. When the price for the commodity changes, you can verify that your contract workspace displays

the updated price for the commodity in the CLID and that the updated price is used to re-calculate any formula terms that use the commodity.

How to add a formula to a commodity escalation clause in a CLID

Context

Procedure

1. Navigate to your contract workspace.2. Click the Documents tab.3. Navigate to and open your Contract Line Items Document (CLID).4. In the Add to Currently Selected section, search for or select the commodity whose escalation clause you

want to link to the CLID. Alternatively, on the line item page, choose a commodity escalation clause from the Commodity Escalation Clause chooser. The price of the item that you specified when you created the escalation clause is displayed.


5. Specify the composition (in the given unit) for the commodity.

6. Click Add Formula .7. Add a formula term. For example, you can add a formula term for the total escalated price that adds the

current price to the product of the escalated price and the composition.8. Click Done. If you added a price to a commodity for a date within the provided dates for the escalation clause,

and return to your contract workspace (user task) ,you can verify that the price for the commodity is updated in the CLID and the updated price is used to calculate the formula for the formula term.

ARI-4402: Risk exposure configuration moved to UI

Products: SAP Ariba Supplier Risk

Audience: Buyers


Note● This feature is opt-in for 90 days, after which it will become mandatory for all users.● Enabling this feature also activates the ARI-4666: Increased variability in risk exposure measurements

[page 156] feature, which changes the range used to measure risk exposure levels from 1-5 to 1-100.

This feature moves all risk configuration functionality from the risk configuration workbook directly into the SAP Ariba Supplier Risk user interface. This will allow easier risk exposure configurations without manual tracking of changes or versions.

Risk exposure configurations are now performed from the Configure risk exposure tab on the Supplier risk administration page. This screen displays the configuration history and provides access to configuration draft versions.

Here, Supplier Risk Manager users can adjust the risk exposure online, save a draft version, and activate the final version to customize risk exposure according to their risk appetite. Supplier risk users can view the current version of the risk exposure configuration.

Prerequisites

● When applying custom fields to specific suppliers it is required to create an import file assigning the fields to the corresponding supplier profile.

● You are responsible to carry over any previously customized spreadsheet-based risk exposure configurations to the user interface. See the links in Administrator tasks, below, for instructions.

● If you have custom fields, you must enter the custom data in the new interface; however, it is not necessary to reload suppliers.



Limitations

● Although multiple viewers can view a version simultaneously, only one user at at time can edit a version.● It is not possible to edit the active version directly. Instead, you can create a new draft, make your changes, and

make the new draft active.


See ARI-4402: Administrator interface changes [page 145].

Administrator tasks

● How to select data sources [page 147]● How to set category weights and thresholds [page 147]● How to define values and risk exposures for fields [page 149]

ARI-4402: Administrator interface changes

This feature introduces the following new UI pages:

Configure risk exposure landing page

This page displays two tables:

● Risk exposure configuration history lists the different configuration versions you have created.

Column Desription

Select Click the Action button in a row to act on the displayed version. Possible actions are○ Create new version○ Delete version○ Edit version

Active A checkmark in this column indicates that this version is the active risk exposure configuration - the values in this version currently affect risk exposure measurements.

Version number The version number.

Name The name of the version. You can use this name as a reminder of what is unique about this version, or how this version differs from previous versions, etc. For example, Added financial settings or Adjusted high settings.


Column Desription

Activated date The date when the version was activated.

Deactivated date The date, if any, when the version was deactivated.

Modified at The date when this version was most recently modified.

Last modified by The name of the person who most recently modified this version.

● Risk exposure configuration draft lists all drafts of the active configuration version.

Column Desription

Select Click the Action button in a row to act on the displayed version. Possible actions are○ Create new draft○ Delete draft○ Edit draft

Version number The version number of the draft.

Name The name of the draft, which matches the name of the active version in the previous list.

Modified at The date when this draft was most recently modified.

Last modified by The name of the person who most recently modified this draft.

The configuration editor

When you choose Create new version, Create new draft, Edit version, or Edit draft from an Actions menu on the landing page, the configuration editor opens, with the following tabs:

● The Data sources tab lets you specify which data sources contribute to risk exposure measurements.● The Category weights tab lets you set the weight of each risk category in the overall risk exposure calculation,

and specify what is considered a Low, Medium, or High exposure for each category.● The Field configurations tab lets you define values and risk exposures for standard and custom fields.● The Incident types tab lists all supported incident types. Incidents are created based on media, and are

contributing factors to all risk domains. This information is provided for reference only; no settings or changes can be made to these values.

● The Audit tab tracks changes made to the version of the configuration currently being viewed. It identifies the user who made each change, and includes the date and time of the change. This information is provided for reference only, and cannot be changed.

The configuration editor contains the following buttons on all tabs:

● Save saves your work.● Cancel exits the editor and returns to the Configure risk exposure landing page without saving your work.● Activate saves your work and makes the current version the active version.

To change the name of the version you are editing, click the pencil icon next to the current name, at the top of the screen.



How to select data sources

This topic describes how to select that data sources that contribute to risk exposure measurements.

Prerequisites

You must have the Supplier Risk Manager group to select data sources.

Context

The Data sources tab lists the data sources available for selection. Selected sources contribute to risk exposure measurements, and unselected sources do not. Sources are categorized as follows:

● Default sources are available for all SAP Ariba Supplier Risk customers.● Licensed sources are risk data providers that become available for selection only after you sign a license with

them.

Procedure

1. To enter the configuration editor, navigate to the Configure risk exposure tab on the Supplier risk administration page, then choose Create new version, Create new draft, Edit version, or Edit draft from an Actions menu on the landing page.

2. Click the Data sources tab.3. All default data sources are initially selected. Unselect those you wish to exclude. At least one data source must

remain selected.4. To save your work, click Save.5. Optional. To set this as the active configuration, click Activate.

How to set category weights and thresholds

This topic describes how to set the relative weights for each risk category in the overal risk exposure measurement, and how to define what risk exposure levels are considered High, Medium, and Low in each category.

Prerequisites

You must have the Supplier Risk Manager group to set category weights and thresholds.


Context

On the Category weights tab, the Category weight settings section contains controls that allow you to specify the relative weight each risk category will have in your risk exposure measurements. The weight percentage for each risk category defines how much it contributes to the overall potential risk exposure calculation.

The Risk level settings section allows you to set minimum and maximum threshholds for each risk category. These thresholds determine what risk exposure levels are considered High, Medium, and Low.

The Test your settings section allows you to enter risk exposure levels for a hypothetical supplier to see the resulting overall potential risk exposure and risk level that would be assigned to that supplier with those risk exposure levels. You can compare results based on your settings, the SAP Ariba default settings, and the current settings in your site.

Procedure


2. Open the Category weights tab.3. In the Category weight settings section, specify the relative weight of each risk category in one of the

following ways:

○ For each category, adjust the green slider left to reduce the category weight or right to increase the category weight.

○ For each category type a percentage weight in its Contribution to overall exposure (%) field. Total weigth must equal 100%.

The Contribution to overall exposure graph displays the relative weights visually.e4. In the Risk level settings section, for each risk category, define what constitutes a Low exposure by entering

the desired exposure in the Low risk less than column. For each risk category, define what constitutes a High exposure by entering the desired exposure in the High risk more than column.

The Risk level distribution graph to the right displays exposure lower than the minimum as Low in blue, exposure between the two thresholds as Medium in yellow, and exposure above the maximum as High in red.

5. Optional. Test your settings in the Test your settings section by entering risk exposure levels for a hypothetical supplier.

6. Click Save to save your work.7. Optional. Click Activate to make this your active configuration.



How to define values and risk exposures for fieldsThis topic explains how to define values and risk exposures for standard and custom fields.

Prerequisites

You must have the Supplier Risk Manager group to edit standard or custom fields.

Context

On the Field configurations tab, you can define values and risk exposures for default and custom fields.

The Standard fields table lists the fields included in the original risk exposure settings provided for a default data source; they use a set of pre-defined values. You can edit the following standard fields:

Field Description

Risk Category The risk category.

Field type The data type of supported values for the field.

Field value The list of permissible values for the field, in a comma separated list. Each value in the list must conform to the type specified in Field type.

Weight Determines the emphasis for each field within the risk calculations for the category.

Threshold order Determines whether greater emphasis should be given to higher or lower risk exposures, based on the thresholds set in the Less than and Greater than fields.

● Riskier to safer means that High exposure levels have more impact, Medium exposure levels have medium impact, and Low exposure levels have low impact in exposure calculations.

● Safer to riskier (the default value) means that Low exposure levels have greater impact, Medium exposure levels have medium impact, and High exposure levels have lower impact in exposure calculations.

Less than Allows you to set the lower threshold. Values below this threshold are considerd Low for risk calculation purposes.

Greater than Allows you to set the upper threshold. Values above this threshold are considered High for risk calculation

Licensed fields available for risk exposure are displayed with default settings. The default settings can be changed by the customer.

Custom fields are not included from a default or licensed source. These fields are added by the customer. You can have up to 15 custom fields.

To configure a custom field, follow these steps:

NoteIf you configure custom fields, you must create a supplier input file. This file includes the suppliers and data elements that you defined in the configuration settings.


Procedure


2. Click the Field configurations tab.3. Click a checkbox in the Custom fields list and enter the custom field name in the Name field. This name can be

up to 25 characters long.

This field name will appear as a contributing factor on the risk exposure tile of the supplier profile under the risk category you assigned.

4. Fill in the remaining columns as per the column descriptions for standard fields, above.5. To save your work, click Save.6. Optional. To set this as the active configuration, click Activate.

ARI-4598: Enhanced workflow for sending questionnaires in control-based engagement risk assessment projectsDescription


Audience: Buyers


This feature introduces an enhanced workflow for sending assessments in control-based engagement risk assessment projects. By default, the owner of the Send Assessments To Do task completes the task to send all internal and external assessments once, and the project automatically sends all applicable assessments to default recipients. The enhanced workflow for sending assessments allows the To Do task owner to:

● Select the assessments to send and send assessments in multiple rounds, including separate rounds for internal assessments before selecting a supplier and external assessments after selecting a supplier.

● Review the default recipient for each assessment and select a different recipient as needed.● Select a supplier for the engagement after sending at least one assessment, when the engagement request is

no longer editable.

Prerequisites

Control-based engagement risk assessment projects must be enabled in your site.

To send assessments for a control-based engagement risk assessment project, you must be an owner of the send assessments To Do task in the project.



To submit an engagement request with no supplier selected, you must enable the configuration parameter Application.SR.AllowOptionalSupplier in your site.


See ARI-4598: Changes to existing functionality [page 151].


See ARI-4598: User interface changes [page 152].

User tasks

● How to send assessment questionnaires for a control-based engagement risk assessment project (enhanced workflow) [page 153]

ARI-4598: Changes to existing functionality

This feature introduces significant changes to functionality of the send assessments To Do task and to the ability to select a supplier after submitting the engagement request in control-based engagement risk assessment projects.

Changes to the send assessments To Do task

In the default, simple workflow, the task owner starts the send assessments To Do task on the engagement page once to send all assessments in a single operation, after which the task is automatically marked complete and the next task in the control-based engagement risk assessment workflow starts. The project sends all available assessments automatically to the default recipients. This workflow provides a streamlined, single-action mechanism for sending assessments. However, if an assessment cannot be sent when the task is completed, there is no way to send it at a later time. For example, if there is no supplier selected for the engagement, or if the selected supplier does not have a contact, completing the send assessments To Do task does not send any external assessments. After the assessments are sent, there is no way to edit the supplier request to add a supplier to the engagement and then resend the external assessments. Starting the task does not show which assessments it sends. The task owner must make sure that all assessments can be sent before completing the task. If the engagement includes external assessments and there is no supplier selected for it, the task owner must recognize this fact and edit the engagement request to add a supplier to it before sending assessments.

In the enhanced workflow, the task owner can start the send assessments To Do task as many times as desired to send different assessments in different rounds until all available assessments are sent, and can specify the


recipients for each assessment before sending it. In a given round, they can only send the assessments that eligible for ending at that time. For example, if there is no supplier selected for the engagement, external assessments are not eligible for sending in that round. If the engagement's required controls include both internal and external assessments, the task owner can send one or more rounds of internal assessments before selecting the engagement supplier. If the engagement request is still editable (because the task owner has not yet sent any assessments), the task owner selects the supplier by editing the engagement request. If the engagement request is no longer editable (because the task owner has already sent at least one round of assessments), the task owner can add a supplier directly on the send assessments page. The send assessments To Do task remains open until all available assessments have been sent, at which point it closes automatically. If all of the engagement's required assessments were already sent as part of other control-based engagement risk assessment projects, the task owner simply marks the send assessments To Do task complete to start the next task in the control-based engagement risk assessment workflow.

Changes to the ability to select a supplier after submitting the engagement request

If the ability to select a supplier after submitting the engagement request is enabled in your site, users with the appropriate permissions can add a supplier to the engagement up until assessments are sent by editing the engagement request.

In the default send assessments workflow, once the send assessments To Do task owner sends all assessments by completing the To Do task once, it is no longer possible to add a supplier to the engagement, since the engagement request is no longer editable.

In the enhanced send assessments workflow, the send assessments To Do owner can add a supplier to the engagement after sending at least one internal assessment by using the Set/Update Supplier area of the send assessments page.

ARI-4598: User interface changes

This feature introduces a new page for sending assessments, which the owner of the send assessments To Do task sees when they start the task. This page includes the following areas:

● Risk Assessments, which lists all of the required assessments for the engagement, including both those that were sent in a previous engagement risk assessment project and those that must be sent for the current engagement, with their names, visibility (external or internal), date sent (for previously-sent assessment), and assignee (recipient).○ If any of the required assessments must be sent for the current engagement risk assessment project:

The task owner can select eligible assessments to send and can specify a different recipient here. Assessments that are not currently eligible for sending show in the list but are not selectable. For example, if a supplier is not selected for the engagement yet, external assessments are not currently eligible for sending, and assessments that were already sent in a previous engagement risk assessment project are never selectable. After the task owner has sent an assessment for the current engagement, it is also no longer selectable. Once the task owner has sent all available assessments for the engagement, send assessments page closes and the send assessments To Do task updates to completed automatically

○ If all of the required assessments for an engagement were already sent as part of previous engagement risk assessment projects: The task owner sees the list of required assessments and their



recipients, grayed out since they are not selectable, and a Mark complete button that they must click to complete the To Do task manually.

● Set/Update Supplier, which the send assessments task owner can use to select the engagement supplier. This area only shows when the current engagement risk assessment project includes required controls with external assessments, no supplier was selected in the engagement request, and the engagement request is no longer editable. If the send assessments task owner has not yet sent any assessments, the engagement request is still editable, and they must edit the request to add a supplier instead.

How to send assessment questionnaires for a control-based engagement risk assessment project (enhanced workflow)

Assessment questionnaires gather evidence of risk control effectiveness for an engagement from suppliers and internal stakeholders. If you are responsible for sending assessments to recipients and your site uses the enhanced workflow, you can send them in one or more rounds to the recipients of your choice.

Prerequisites

To send assessment questionnaires for a control-based engagement risk assessment project, you must be the owner of the To Do task for triggering the evidence and control process in the project.

To select which assessments to send, send assessments in more than one round, and choose assessment recipients, the enhanced send assessments workflow must be enabled in your site.

Context

The required assessment questionnaires for a control-based engagement risk assessment project are determined by its applicable controls, which are in turn determined by the answers the requester provided to questions in the engagement request. When you start the send assessments To Do task, the send assessments page shows a list of all of the assessments that are required for the current control-based engagement risk assessment project.

Assessments are modular supplier management questionnaires, each of which might have its own approval flow. After a recipient has submitted answers to a modular supplier management questionnaire (either as a standalone questionnaire or as part of another control-based engagement risk assessment), and those answers have been approved, the assessment questionnaire is approved until it expires (if ever). You can only send assessments that are new, have expired, or are expiring (a notification of pending expiration has been sent). If the assessment questionnaire was already sent to the recipient and either the recipient has not yet responded, the response is in approval, or the response has been approved and the questionnaire is still in Approved status, you do not sent it again.

You can send all available assessments at once, or select specific assessments to send in different rounds. For example, if your site allows requesters to submit engagement requests with no supplier selected and the required controls for an engagement use both internal and external assessments, you can send internal assessments in one or more initial rounds, then select a supplier and send external assessments. The engagement request remains editable until you send at least one assessment, and at that point you can add a supplier to the engagement by


editing the request if needed. After you send at least one assessment, the engagement request is no longer editable, but you can still add a supplier to the engagement from the send assessments page if needed.

The send assessments page shows all of the assessments required for the engagement for informational purposes. When choosing which assessments to send at a given time, you can only select those assessments that are currently available for sending. An assessment is not available for sending if:

● There is no supplier selected for the engagement yet. You cannot send external assessments for engagement-level controls until you select a supplier for the engagement, since there is no recipient. You also cannot send either external or internal assessments for vendor- or service-level controls until you select a supplier for the engagement, since those controls can be effective for a supplier across multiple engagements and there no way to tell whether the associated assessments were sent in another engagement risk assessment project until you select the supplier. To send these assessments, select a supplier for the engagement.

● The supplier selected for the engagement does not have any contacts. You cannot send any external assessments to a supplier with no contact. To send the assessments, add a contact to the supplier in their 360° profile or contact your administrator so that they can add a contact to the supplier using data import.

● There is a supplier selected for the engagement, but the assessment was already sent in another engagement risk assessment project and it is not now expiring or expired.

The send assessments To Do task remains open until you have sent all of the available assessments, after which it automatically completes.

The list of required assessments includes the name of the default recipient for each assessment. Before you send an assessment, you can change its recipient as follows:

Questionnaire visibility Default recipients Other available recipients

External The primary supplier contact (for new questionnaires) or the supplier contact who previously submitted the questionnaire (for completed questionnaires).

Any other contact associated with the supplier.

Internal Members of the questionnaire project Internal Recipient project group or, if that project group is empty or is not present in the project, members of the Project Owner project group in the engagement risk assessment project where the internal assessment was sent. The default recipient is the entire project group.

Members of the questionnaire project Internal Recipient project group or, if that project group is empty or is not present in the project, members of the Project Owner project group in the engagement risk assessment project where the internal assessment was sent. You can select one or more individual recipients from these project groups.

If all required assessments for the current engagement were already sent in previous engagement risk assessment projects, you must mark the send assessments To Do task complete so that the control-based engagement risk assessment process can move to the next step.

Procedure

1. Perform one of the following actions:

○ Click the link in the To Do task email notification to open the engagement page.○ From the Engagement Requests tile on the Supplier Risk dashboard or in a supplier 360° profile, click the

In Progress tile, locate the engagement, and click its name.



2. In the Pending Tasks lists, for the To Do task to send assessments, click Start.

The send assessments page opens. It includes a list of the required assessments for the engagement, with their visibility type, assignee (recipient), and the date that any previously sent assessments were sent. Assessments that are not currently available for sending are grayed out.

3. If all of the required assessments have already been sent, click Mark complete to complete the send assessments To Do task so that the next task in the engagement risk assessment project can start. Otherwise, proceed to the next step.

4. To send assessments for this engagement, perform the following actions:a. Check the assessments you want to send at this time. You can only check those assessments that are

currently available for sending. The assessments that you cannot send at this time are grayed out.b. (Optional) To change the default recipient, click Send to, then check one or more of the available recipients

and click OK.c. Click Send assessments.

5. (Optional) While you are sending assessments, if there is no supplier is selected for the engagement yet and you want to select one now, perform one of the following actions:

○ If you have not yet sent any assessments, edit the engagement request to add a supplier.○ If you have already sent at least one internal assessment and the engagement request is no longer

editable, in the Add/Update Supplier area of the send assessments page, search for the supplier you want to add, then click Set Supplier.

6. Continue sending assessments using the steps above until you have sent all of the required assessments that must be sent for the current engagement.

Results

If all of the required assessments were already sent in a previous engagement, once you mark the send assessments To Do task complete, that action completes the task Otherwise, once you send all of the assessments that must be sent for the current engagement, the send assessments To Do task completes automatically. In both cases, the engagement risk assessment process moves to the next step.

SAP Ariba Supplier Risk automatically sends invitations to fill out the assessment questionnaires you sent to the recipients you specified. If a questionnaire has multiple recipients, all recipients receive the invitation, and the first recipient to respond fills out and submits the questionnaire.

The Risk Assessments area of the engagement page lists all of the assessments that you have sent up to this point for the current engagement as well as all of the required assessments for the current engagement that were sent for other engagements. You can click View to the right of an assessment questionnaire to view it.

If the engagement has any controls that are open but are associated with questionnaires that have already been completed, control decision makers now see a Review button for them in the Risk Controls area of the engagement page.


Next Steps

Recipients now fill out and submit the assessment questionnaires you sent. Once they have done so, depending on how those assessment questionnaires are set up, approvers might need to approve their answers before control decision makers can review any open controls and mark them as effective or ineffective.

The external assessment questionnaires for all of the required controls in the current engagement risk assessment project, including those that were already approved and those you sent in this step, are available on the Questionnaires tile of the supplier 360° profile. Task owners and approvers can complete assigned tasks for external assessment questionnaires there or by choosing Manage My Tasks .

Internal assessment questionnaires for the required controls do not show on the Questionnaires tile. Users who have access to the engagement page can view them there. Users with the appropriate roles can view them on the Home dashboard. Approvers can approve or deny them by choosing Manage My Tasks .

ARI-4666: Increased variability in risk exposure measurementsProducts: SAP Ariba Supplier Risk

Audience: Buyers

Enablement: Contact SAP Ariba to enable.

Note● This feature is opt-in for 90 days, after which it will be

come mandatory for all users.● Enabling this feature also activates ARI-4402: Risk ex

posure configuration moved to UI [page 144]

This feature changes the range for risk exposure levels from 1-5 to 1.00-100.00.

Once this feature is enabled, existing risk exposure measurements for a profile will recalculate to the new range when a user opens the profile or when contributing factors have changed.

Default risk exposure thresholds for the new range are:

Low 1.00-29.99

Medium 30.00-69.99

High 70.00-100.00

You can change these thresholds in the risk exposure configuration interface. See How to set category weights and thresholds [page 147] for details.



ARI-4946: Ability to upload status and expiry dates of offline risk assessmentsDescription

Products SAP Ariba Supplier Risk

Audience Buyers


If you have risk-related assessments or questionnaires maintained in a system outside SAP Ariba Supplier Risk, you can make use of that data in SAP Ariba Supplier Risk by uploading header information for these external documents.

Uploading external assessment data might be helpful when:

● You are replacing a third-party system for risk due diligence processes with SAP Ariba Supplier Risk, and you want to migrate legacy risk data to the new system. You can upload the statuses of legacy risk questionnaires.

● You have legacy SAP Ariba Supplier Risk engagement risk assessment projects, and would like to migrate assessment statuses from those projects to the new control-based risk assessment projects.

● You use a shared service provider to trigger and maintain risk assessments.

Prerequisites

To import risk assessment status data in SM Administration, you must be a member of the Supplier Risk Manager or SM Ops Administrator user group.

You must already have defined modular supplier management questionnaire templates corresponding to the assessments for which you would like to import status data.

Your site must be configured for use of control-based engagement risk assessment projects, because imported risk assessment status data is used only by engagement requests created specifically from the Supplier Risk Engagement Template. This feature is not relevant to legacy engagement risk assessment projects based on the Supplier Engagement Risk Assessment Project Template.


This feature introduces a new menu item, Risk Assessment Status Data, on the File type menu in the Data import and export workspace in SM Administration.


See ARI-4946: User interface changes [page 158].



● Risk assessment status data import file format [page 159]

ARI-4946: User interface changes

The Assessment section of an engagement request can now include rows representing imported data as well as rows of information about supplier responses to questionnaires sent via the control-based engagement request. Rows representing imported data:

● Show the phrase Imported assessment status in the Assessment ID column.● Show the imported value in the Visibility column. If the import did not include a value for Visibility, the value

defaults from the corresponding Modular Questionnaire.● Show, in the Source column, the text uploaded via the Source column of the import file.

NoteDocument location URL's can be uploaded to a text field for informational purposes. From there, a user can copy a URL and paste it into a browser. For reasons of application security, uploaded URL's cannot be displayed as links.

● Do not include a View button because the actual assessment is not stored in SAP Ariba Supplier Risk.

The Control review page for a risk control on an engagement request may now show either imported assessment data, or information about the response to a questionnaire triggered by the control-based engagement request. If the assessment data was imported:

● The Source field shows the text uploaded via the Source column of the import file.● The Assessment ID field shows the phrase Imported assessment status.● The Risk Assessment area does not include a View button because the actual assessment is not stored in SAP

Ariba Supplier Risk.

ExampleImported risk assessment status data within an engagement request workflow

TipBest practice: Import corresponding risk control statuses after assessment statuses. Together, these two imports streamline incorporating offline assessments and controls into the engagement request workflow.

1. Administrator uploads risk assessment status data. Each record is for an assessment name / assessment type / supplier combination, and can include expiration date and source (text describing where to find the original assessment).

2. (Optional) Ideally, risk control statuses, corresponding to the assessments from step 1, are imported.3. Buyer creates a risk engagement request. Responses to the business details and screening questions

cause the selection of certain risk controls for the engagement.4. If an uploaded risk assessment status data record matches a required assessment identified for the

engagement request, then this imported assessment record is listed in the Assessments area of the engagement request review page.



5. Each risk control task is triggered for review once all the predecessor tasks have been completed.

NoteIf both control statuses and their related assessment statuses are imported, those control review tasks are not triggered.

○ Decisionmaker can review the imported offline assessments by using the information in the Source column. This column can be used to describe how to access the assessment outside the SAP Ariba Supplier Risk application.

○ Decisionmaker reviews risk controls. Each risk control could be either a response to a modular questionnaire, or an imported risk assessment status. Decisionmaker indicates whether each is effective or not effective.

6. Once all control review tasks are complete, an approval task assignee approves or denies the engagement.7. Later, the imported assessment status expires (based on the imported expiration date). The behavior is

similar to an expired questionnaire response: the next engagement request for the same supplier and with risk controls requiring the expired assessment triggers a notification to the supplier to update their response.

TipThe Risk Control Summary report includes both imported risk control status data and imported risk assessment status data.

ARI-5428: New Risk Control Summary report [page 176]

Risk assessment status data import file format

Risk assessment status data is information about risk assessments or questionnaires for specific suppliers that you have collected in tools or processes outside of SAP Ariba Supplier Risk control-based engagement risk assessment projects.

Importing this data allows you to reference legacy and other externally-collected risk assessment data from within SAP Ariba Supplier Risk. For example, if you are changing risk assessment tools, you may have unexpired assessments in your legacy tool; rather than asking suppliers to re-respond to new questionnaires on the same topics, you can import the statuses of these assessments.

You use the Risk assessment status data import task in SM Administration to import risk assessment data into your site. The task reads from a CSV file that contains the following fields:

Field Description Required?

ASSESSMENT_NAME This must map to the Title of an already defined Modular Questionnaire.

Yes

ASSESSMENT_TYPE Questionnaire type for the modular questionnaire as defined in the Name field of your site's Questionnaire Type master data.

Yes


Field Description Required?

VISIBILITY Indicates whether this assessment is Internal or External.

No

ASSESSMENT_STATUS The status of this assessment. Possible values are:

● Denied● Approved

Yes

RISK_SCORE The score for this assessment. Not currently used.

No

TARGET_SCORE Target score for this assessment. Not currently used.

No

EXPIRATION_DATE Date and time after which this assessment status is no longer valid, in format yyyy-MM-dd hh24:mm:ss. For example, "2020-02-05 22:52:26". After the status expiration date, the corresponding modular questionnaire is triggered based on the assessment name and type.

No

NoteIf this is left blank, the assessment remains active indefinitely.

SM_VENDOR_ID Specifies the SM ID of the supplier. Yes

SOURCE Here you can specify the location of the original assessment.

NoteDocument location URL's can be uploaded using this text field. From there, a user can copy a URL and paste it into a browser. For reasons of application security, uploaded URL's cannot be displayed as links.

No

NoteThis column supports up to 2048 bytes; number of characters supported depends on the language and database.

CautionImport tasks do not validate for every error that might exist in the import file.

● Assessment name is validated but there is no validation reconciling other uploaded values with data already configured in the realm. Verify before proceeding that the import file contains valid supplier ID's and assessment types.

● You can also upload risk control status data (see Setting Up SAP Ariba Supplier Risk). There is no validation reconciling data uploaded for risk control status with data uploaded for risk assessment status.

The following example shows lines of a risk assessment status CSV file, as well as the mandatory header:

ASSESSMENT_NAME,ASSESSMENT_TYPE,VISIBILITY,ASSESSMENT_STATUS,RISK_SCORE,TARGET_SCORE,EXPIRATION_DATE,SM_VENDOR_ID,SOURCE Group Data Protection Policy,Evidence,External,Approved,,,,S1530626,http://filesystem/location



NoteThe related export of risk assessment status data includes only the risk assessment status data in the current realm that was previously imported. It does not include status data from supplier responses to modular questionnaires completed as part of control-based engagement risk assessment projects.

Troubleshooting

If your import does not succeed, verify the validity of the data in the import file.

● Make sure your import file includes values in all rows for the fields that are required.● If the result includes the error message Error occurred while importing assessment status data, possible

reasons include::○ Missing or invalid ASSESSMENT_NAME○ Missing SM_VENDOR_ID○ Invalid EXPIRATION_DATE

If you find that the Assessments table for an engagement request does not include an imported assessment status you expected to see there:

● Review the import file and verify that this combination of ASSESSMENT_NAME, ASSESSMENT_TYPE, and SM_VENDOR_ID was included, and that the values in those fields are correct.

ARI-5268: Support for analytical reporting on control-based engagement risk assessment projects

Description


Audience: Buyers


This feature introduces support for using existing SAP Ariba analytical reporting tools to report on information in control-based engagement risk assessment projects and issue management projects using the following new reporting facts:

● SR Project● SR Project Survey Response● SR Project Task● SR Project Task Approval Flow

Reports based on these facts can use fields to show information for control-based engagement risk assessment projects, their associated issue management projects, and tasks and questionnaires in both types of projects. They


can include engagement-specific fields from the new Supplier Risk Project Information dimension, such as Engagement Risk Status.

Users with the appropriate permissions can create analytical reports, or run public analytical reports created by others, to analyze information about your organization's control-based engagement risk assessment activity and to extract data to help meet regulatory requirements. Using existing analytical reporting capabilities, they can pivot, drill down, slice and dice, and filter data on the report pivot table and can export report contents to Microsoft Excel or CSV files.

Prerequisites

Control-based supplier engagement risk assessment projects must be enabled in your site.

Existing SAP Ariba Supplier Risk user groups, such as Supplier Risk User, Supplier Risk Manager, Supplier Risk Engagement Requestor, and Supplier Risk Engagement Governance Analyst, do not have any analytical reporting permissions. To run, create, or publish analytical reports, SAP Ariba Supplier Risk users must also belong to a user group that grants them those permissions. For details on the global user groups that grant analytical reporting permissions, see the Strategic Sourcing and supplier management group descriptions.

Limitations

This feature does not include prepackaged reports based on any of the four new facts. Customers must create their own reports.

This feature does not support reporting on assessment modular supplier management questionnaires and their tasks.

.

User tasks

● Analytical reporting for control-based engagement risk assessment projects [page 163]

Changes to reporting

See ARI-5268: Changes to reporting [page 165].

Analytical reporting for control-based engagement risk assessment projects [page 163]

ARI-5268: Changes to reporting [page 165]



Analytical reporting for control-based engagement risk assessment projects

You can use SAP Ariba analytical reports to analyze questionnaire content, project, project task, and approval or review activity in control-based engagement risk assessment projects and their associated issue management projects.

You can create reports based on the following reporting facts to see data on engagement risk assessment and issue management projects, tasks, and questionnaires:

Use this fact... To see this data...

SR Project Control-based engagement risk assessment projects and issue management projects.

You can analyze project activity by project owner (the person who created the project), project start and end dates, engagement commodities, regions, and departments, engagement request status, which issue projects are associated with specific engagement risk assessment projects (primary source ID) or risk controls (secondary source ID), and so on.

SR Project Task The tasks in control-based engagement risk assessment projects and issue management projects.

In reports based on this fact, you can analyze task activity by type, task status, task start and end dates, on time or late tasks, task owner, engagement request status, which issue tasks are associated with specific engagement risk assessment projects (primary source ID) or risk controls (secondary source ID), and so on.

SR Project Task Approval Flow The details for approval and review flows in approval and review tasks in engagement risk assessment and issue management projects. It is particularly useful for identifying bottlenecks in approval processes.

In reports based on this fact, you can analyze approval and review activity by task names, start dates, end dates, the names of associated projects, approvers by name or group, the dates on which task nodes become active and approvers have acted, any comments they provide during approval, engagement request status, and so on.


Use this fact... To see this data...

SR Survey Response All questionnaires in control-based engagement risk assessment projects and in issue management projects, including the engagement request business details and inherent risk screening questionnaires in engagement risk assessment projects and issue details forms in issue management projects..

In reports based on this fact, you can analyze questionnaires by respondent, questionnaire (survey), associated project, response (response, multiple-value response, or response commodity, question, region, or department), question, engagement request status, and so on.

NoteAnalytical reporting on the modular supplier management questionnaire projects used as assessment questionnaires in control-based engagement risk assessment projects is not supported.

You must have the appropriate permission to run or create analytical reports. The following table provides a quick reference for where to find information about SAP Ariba analytical reporting:

To do this... See...

Run a report that you or another person at your organization has created

Running analytical reports

TipTo see the reports that other people in your organization have created and made publicly available, choose

Manage Public Reports .

Create an analytical report Creating analytical reports

Understand the data that is available in different reporting facts and how multi-fact reports on any combination of SR Project, SR Project Task, and SR Project Task Approval Flow data work

Reporting fact reference

Learn which user groups grant reporting permissions Strategic sourcing and supplier management group descriptions

Keep in mind the following tips when running or creating analytical reports for control-based engagement risk assessment and issue management projects, tasks, and questionnaires:

● You can create reports that include combinations of SR Project, SR Project Task, and SR Project Task Approval Flow data. You cannot create reports that combine SR Survey Response data with data from other reporting facts.

● Every analytical report must include at least one measure (data field), which you add in the first step of the reporting wizard.

● If you want a report that simply lists all of the data in rows, add fields to the Detail Fields area of the pivot layout and check Show detail fields in report. On the report pivot table, you can also switch between detail and aggregate views by clicking the data menu.



● The second step of the report wizard shows available hierarchy fields by default. To see all available fields, including flat (non-hierarchical) fields, click Available Hierarchies and choose Available Fields. Some fields that are important for reports on control-based engagement risk assessment projects, such as Engagement Request Status, Issue Primary Source ID, Issue Secondary Source ID, and Response, only show on the Available Fields list.

● Use the Issue Primary Source ID field to see the control-based engagement risk assessment projects associated with issue project, task, approval flow, or questionnaire (survey response) data in issue management projects created at the engagement level. Use the Issue Secondary Source ID field to see the risk controls associated with issue project, task, approval flow, or questionnaire (survey response) data in issue management projects created during control reviews. These fields only show data where applicable. For example, if an issue management project was created at the engagement level, it shows an Issue Primary Source ID but no Issue Secondary Source ID. Engagement risk assessment projects, tasks, and questionnaires never include this data.

● If you are not sure which fields you want to add to a report, add them as page fields. Once you have run the report, you can move page fields into the report from the Field Browser, as well as moving fields between rows, columns, and the Field Browser.

● Every analytical report includes at least one date filter. Typically, the larger the date range you choose, the larger the report.

ARI-5268: Changes to reporting

This feature introduces one new reporting dimension and four new reporting facts for data in control-based engagement risk assessment projects and their associated issue management projects.

Supplier Risk Project Information dimension

The Supplier Risk Project Information dimension includes the following fields:

Field Description

Engagement Request Status The status of the control-based engagement risk assessment project.

Issue Primary Source ID For issue project, task, and questionnaire content data in issue management projects created against engagements as a whole, the ID of the associated control-based engagement risk assessment project.

Issue Secondary Source ID For issue project, task, and questionnaire content data in issue management projects created against risk controls, the ID of the associated risk control.

Project Id The ID of the engagement risk assessment project or issue management project.

These fields are available in reports based on the following facts:

● SR Project● SR Project Survey Response


● SR Project Task● SR Project Task Approval Flow

SR Project reporting fact

The SR Project fact contains data about control-based engagement risk assessment projects and their associated issue management projects.

About SR Project


● SAP Ariba Supplier Risk

Source of data

The SR Project fact contains data from control-based engagement risk assessment projects and their associated issue management projects..

Level of data

SR Project data is loaded at the header level, meaning that there is one record per project.

Frequency of data loads and data retention


Access control

SR Project data is not subject to reporting data access control.



Typical uses

You can create reports based on the SR Project fact to:

● See all of your organization's control-based engagement risk assessment activity in one report, including how long those projects are open.

● Analyze control-based engagement risk assessment project activity by requester (project owner), status, commodity, region, department, and so on.

● Analyze issue management activity by itself or in relationship to associated engagement risk assessment projects.

Fact Name content



Measure Description

Duration The amount of time between the project start and end date in days.

Project Count The number of projects.


The following table shows multi-fact relationships for the new SR Project fact with join fields for each fact combination.


This fact... Joins at these [fields]... With these facts [and fields]...

SR Project [Project Id] ● Contract Request (Procurement) (Parent) [Project Id]

● Contract Request (Sales) (Parent) [Project Id]

● Contract Workspace (Internal) (Parent) [Project Id]

● Contract Workspace (Procurement) (Parent) [Project Id]

● Contract Workspace (Sales) (Parent) [Project Id]

● General Contract Workspace (Parent) [Project Id]

● Project (Parent) [Project Id]● Project Group [Project Id]● Project Task [Project Id]● Sourcing Project (Parent) [Project

Id]● Sourcing Request (Parent) [Project

Id]● SPM Project (Parent) [Project Id]● SQM Project (Parent) [Project Id]● SR Project (Parent) [Project Id]● SR Project Task [Project Id]● SR Project Task Approval Flow

[Project Id]● Supplier/Customer [Project Id]● Task Approvals[Project Id]

Contract Request (Procurement) [Project Id] SR Project (Parent) [Project Id]

Contract Request (Sales) [Project Id] SR Project (Parent) [Project Id]

Contract Workspace (Internal) [Project Id] SR Project (Parent) [Project Id]

Contract Workspace (Procurement) [Project Id] SR Project (Parent) [Project Id]

Contract Workspace (Sales) [Project Id] SR Project (Parent) [Project Id]

General Contract Workspace [Project Id] SR Project (Parent) [Project Id]

Project [Project Id] SR Project (Parent) [Project Id]

Project Group [Project Id] SR Project [Project Id]

Project Task [Project Id] SR Project [Project Id]

Sourcing Project [Project Id] SR Project (Parent) [Project Id]

Sourcing Request [Project Id] SR Project (Parent) [Project Id]

SPM Project [Project Id] SR Project (Parent) [Project Id]

SQM Project [Project Id] SR Project (Parent) [Project Id]

Supplier/Customer [Project Id] SR Project [Project Id]




Task Approvals [Project Id] SR Project [Project Id]

SR Project Survey Response reporting fact

The SR Project Survey Response fact contains data from questionnaires in control-based engagement risk assessment projects and their associated issue management projects.l

About SR Project Survey Response



Source of data

The SR Project Survey Response fact contains data from all survey documents in control-based engagement risk assessment and issue management projects, including:

● Engagement request business details questionnaire (in control-based engagement risk assessment projects)● Engagement request inherent risk screening questionnaire (in control-based engagement risk assessment

projects)● Issue details form (in issue management projects)

Level of data

SR Project Survey Response data is loaded at the line level, meaning that there is one record per survey content item (question, section, and so on).




Access control

SR Project Survey Response data is not subject to reporting data access control.

Typical uses

You can create reports based on the SR Project Survey Response fact to:

● See which engagement risk assessment or issue management projects provide specific answers to specific questions.

● Quickly identify the engagement risk assessments associated with issues that have specific levels of severity or probability based on the answers to severity or probability questions in the issue details form.

● Analyze engagement risk assessment activity by the commodities, regions, and departments specified in the engagement request business details questionnaire.

SR Project Survey Response content



Measure Description

Average Grade The average grade for the content.

Average System Grade N/A

Average Target The average target grade for the content.

Average Value The average value of the content.

Average Weight The average weight assigned to the content during scoring.

Quantitative Count Average An average count of the content.

NoteCurrently, SAP Ariba Supplier Risk only supports grading in the engagement request inherent risk screening questionnaire.



SR Project Task reporting fact

The SR Project Task fact contains data on tasks in all control-based engagement risk assessment projects and their associated issue management projects.

About SR Project Task



Source of data

The SR Project Task fact contains data from tasks control-based engagement risk assessment projects and their associated issue management projects..

Level of data

SR Project Task data is loaded at the header level, meaning that there is one record per task.



Access control

SR Project Task data is not subject to reporting data access control.

Typical uses

You can create reports based on the SR Project Task fact to:


● See all of your organization's control-based engagement risk assessment task activity in one report, including task owners and task durations.

● Identify bottlenecks in your control-based engagement risk assessment process.● See which users in your site are approving engagement requests, analyzing and resolving issues, sending

assessments, and performing other key engagement risk assessment activities.

SR Project Task content



Measure Description

Avg Duration The average amount of time between when the task started and when it was completed in days.

Task Count The number of tasks.


The following table shows multi-fact relationships for the new SR Project Task fact with join fields for each fact combination.


SR Project Task [Project Id] ● Contract Request (Procurement) [Project Id]

● Contract Request (Sales) [Project Id]

● Contract Workspace (Internal) [Project Id]

● Contract Workspace (Procurement) [Project Id]

● Contract Workspace (Sales) [Project Id]

● General Contract Workspace [Project Id]

● Project [Project Id]● Sourcing Project [Project Id]● Sourcing Request [Project Id]● SPM Project [Project Id]● SQM Project [Project Id]● SR Project [Project Id]




[Document Id] ● Document [Document Id]

[Task Name] ● SR Project Task Approval Flow [Task Name]

● Task Approvals [Task Name]

Contract Request (Procurement) [Project Id] SR Project Task [Project Id]

Contract Request (Sales) [Project Id] SR Project Task [Project Id]

Contract Workspace (Internal) [Project Id] SR Project Task [Project Id]

Contract Workspace (Procurement) [Project Id] SR Project Task [Project Id]

Contract Workspace (Sales) [Project Id] SR Project Task [Project Id]

Document [Document Id] SR Project Task[Document Id]

General Contract Workspace [Project Id] SR Project Task [Project Id]

Project [Project Id] SR Project Task [Project Id]

Project Task [Project Id] SR Project Task [Project Id]

Sourcing Project [Project Id] SR Project Task [Project Id]

Sourcing Request [Project Id] SR Project Task [Project Id]

SPM Project [Project Id] SR Project Task [Project Id]

SQM Project [Project Id] SR Project Task [Project Id]

SR Project [Project Id] SR Project Task [Project Id]

Task Approvals [Project Id] SR Project Task [Project Id]

SR Project Task Approval Flow reporting fact

The SR Project Task Approval Flow task contains data on approval and review tasks in control-based engagement risk assessment projects and their associated issue management projects.

About SR Project Task Approval Flow




Source of data

The SR Project Task Approval Flow fact contains data from approval and review tasks control-based engagement risk assessment projects and their associated issue management projects..

Level of data

SR Project Task Approval Flow data is loaded at the header level, meaning that there is one record per task.



Access control

SR Project Task Approval Flow data is not subject to reporting data access control.

Typical uses

You can create reports based on the SR Project Task Approval Flow fact to:

● Audit who approves which nodes in an approval flow, and when those approvals occur.● Determining where an approval flow stalled, providing accountability for each node.● Audit who reviews engagement requests or associated issues.

SR Project Task Approval Flow content





Measure Description

Task Count The number of tasks.


The following table shows multi-fact relationships for the new SR Project Task Approval Flow fact with join fields for each fact combination.


SR Project Task Approval Flow [Project Id] ● Contract Request (Procurement) [Project Id]

● Contract Request (Sales) [Project Id]

● Contract Workspace (Internal) [Project Id]

● Contract Workspace (Procurement) [Project Id]

● Contract Workspace (Sales) [Project Id]

● General Contract Workspace [Project Id]

● Project [Project Id]● Sourcing Project [Project Id]● Sourcing Request [Project Id]● SPM Project (Parent) [Project Id]● SQM Project (Parent) [Project Id]● SR Project [Project Id]

[Task Name] ● Project Task [Task Name]● SR Project Task [Task Name]

Contract Request (Procurement) [Project Id] SR Project Task Approval Flow [Project Id]

Contract Request (Sales) [Project Id] SR Project Task Approval Flow [Project Id]

Contract Workspace (Internal) [Project Id] SR Project Task Approval Flow [Project Id]

Contract Workspace (Procurement) [Project Id] SR Project Task Approval Flow [Project Id]

Contract Workspace (Sales) [Project Id] SR Project Task Approval Flow [Project Id]

General Contract Workspace [Project Id] SR Project Task Approval Flow [Project Id]



Project [Project Id] SR Project Task Approval Flow [Project Id]

Project Task [Task Name] SR Project Task Approval Flow [Task Name]

Sourcing Project [Project Id] SR Project Task Approval Flow [Project Id]

Sourcing Request [Project Id] SR Project Task Approval Flow [Project Id]

SPM Project [Project Id] SR Project Task Approval Flow [Project Id]

SQM Project [Project Id] SR Project Task Approval Flow [Project Id]

SR Project [Project Id] SR Project Task Approval Flow [Project Id]

Task Approvals [Task Name] SR Project Task Approval Flow [Task Name]

ARI-5428: New Risk Control Summary reportDescription


Audience: Buyers


This feature introduces a new Risk Control Summary report, which is a Microsoft Excel file that contains information on the risk controls required in all of the control-based engagement risk assessment projects in your site. The report includes basic information on the controls such as ID, name, type, status owner, and decision maker, as well as information on the associated assessment questionnaires, such as ID, name, status, and expiration date, if any. Users with the appropriate permissions can export this file from your site to analyze your organization's use of different risk controls in engagement risk assessments and to help meet regulatory requirements.

Prerequisites

Control-based engagement risk assessment projects must be enabled in your site.

To generate the Risk Control Summary report, you must be a member of the Supplier Risk Manager, Supplier Risk Engagement Governance Analyst, or Supplier Risk Engagement Expert group.



Changes to the user interface

This feature adds a menu item, Risk Control Summary, to the Report name dropdown menu in the User settings and configuration Reports area.

User tasks

● How to run the Risk Control Summary report [page 177]

How to run the Risk Control Summary report

The Risk Control Summary report provides an overview of the risk controls required in your organization's control-based engagement risk assessment projects.

Prerequisites

To run the Risk Control Summary report, you must be a member of the Supplier Risk Manager, Supplier Risk Engagement Governance Analyst, or Supplier Risk Engagement Expert group.

Context

The Risk Control Summary report is a Microsoft Excel file with the following fields:

● Engagement Id● Engagement Name● Vendor Id● Supplier ● Project Owner● Requested by● Requested On● Engagement Status● Risk Type● Control Id● Control Name● Control Owner● Decision Maker● Control Status● Control Expiry


● Control Status Imported, which is a flag indicating whether the control status was set manually by a review (False) or using a control status data import (True)

● Control Assessment Id● Control Assessment Name● Control Assessment Status● Assessment Expiration● Visibility● Assessment Status Imported, which is a flag indicating whether the assessment status derived from a

modular supplier management questionnaire (False) or was set using an assessment status data import (True)

Procedure

1. On the Supplier Risk dashboard, click User settings and configuration.2. In the left-hand navigation bar, click Reports.3. On the Report name dropdown menu, choose Risk Control Summary.4. Click Generate report.

ARI-5531: Risk control mappings based on inherent risk screening scores

Description


Audience: Buyers


This feature introduces a new field, InherentRiskScore, in the engagement control mapping CSV file that defines which risk controls are required for a control-based engagement risk assessment. Previously, you could map commodities, regions, departments, and the answers to inherent risk screening questions to required risk controls. Now, you can also use the new InherentRiskScore field to trigger control requirements for an engagement based on its inherent risk by mapping controls to the inherent risk score generated by the engagement request inherent risk screening questionnaire.

You can trigger control requirements based only on the inherent risk score, or based on a combination of inherent risk score and commodities, regions, or departments. If you trigger control requirements based only on the inherent risk score, requesters can create requests without specifying commodities, regions, and departments while still triggering control requirements, and those engagement risk assessments can proceed to completion.



Prerequisites

Control-based supplier engagement risk assessment projects must be enabled in your site.

To import engagement control mapping master data in Ariba Administrator, you must be a member of the Customer Administrator group.

You must set up scoring for the inherent risk screening questionnaire survey document in the Supplier Risk Engagement Template so that it generates an inherent risk score. For details, see Setting up SAP Ariba Supplier Risk.


See ARI-5531: Changes to data import and export [page 179].

ARI-5531: Changes to data import and export

This feature introduces several changes to the EngagementControlMapping.csv master data file for defining which risk controls are required for an engagement based on some combination of engagement commodities, regions, and departments, answers to conditional questions in the engagement request inherent screening questionnaire, and now the inherent risk score of the inherent risk screening questionnaire.

This feature adds the following new field to EngagementControlMapping.csv:


Field Description Required

InherentRiskScore Specifies a range of numerical inherent risk scores in the format {lowerLimit:upperLimit}; for example, a value of {50:80} maps the control to inherent risk scores from 50 to 80.

The range is inclusive, meaning that scores that match the lower limit and the upper limit, as well as all scores in between, all trigger the control. If there are overlaps in the ranges in different mappings, scores that match the overlapping value trigger all mapped controls. For example, if you map one control to {50:60} and another control to {60:70}, a score of 60 triggers both controls.

You can use a wildcard (*) to define a range with either no lower limit or no upper limit. For example, if you map a control to {80:*}, scores of 80 or above trigger the control, with no defined upper limit.

No

This feature also changes the requirement for values in the CommodityCodes, Departments, Regions, ConditionAnswers, and ConditionQuestions fields in EngagementControlMapping.csv. Values in the CommodityCodes, Departments, and Regions fields are required to trigger controls from engagement requests where the requester specifies a commodity, region, and department in the business details questionnaire. In mappings where you leave these fields blank, the mapped controls are only triggered from engagement requests where the requester does not specify a commodity, region, and department in the business details questionnaire. You can leave the ConditionAnswers and ConditionQuestions fields blank in mappings that include a value in the InherentRiskScore field and vice versa, or you can use all three.

These changes mean that you have the option to trigger controls based on any of the following mapping combinations:

● Only the inherent risk score (this mapping only triggers controls if the requester does not select commodities, regions, and departments in the engagement request business details questionnaire)..

● The engagement commodities, regions, and departments and the inherent risk score.● The engagement commodities, regions, and departments and answers to conditional questions in the inherent

risk screening questionnaire.● The engagement commodities, regions, and departments; answers to conditional questions in the inherent risk

screening questionnaire; and the inherent risk score.

The system triggers mapped controls as follows:

● If the requester selects values for commodity, region, and department in the engagement request business details questionnaire, the system identifies the mappings that match the selected values. The system then



evaluates each of those mappings to see if the engagement request matches the conditional question answer or inherent risk score range values (or both) specified in the mapping, and triggers those controls that are mapped to all matching values.

● If the requester does not select values for commodity, region, and department in the engagement request business details questionnaire, the system identifies mappings that include inherent risk score range values but no conditional question and answer values and triggers those controls that match the engagement request inherent risk score.

The following example shows lines of the EngagementControlMapping.csv file, as well as the mandatory header:

UTF-8 CommodityCodes,ConditionAnswers,ConditionQuestions,ControlIds,Departments,Description,InherentRiskScore,Regions,UniqueName43232305;43232306;43232307,Yes,Q_ID_1,Critical_data_element,CLAIM,,,USA,Group data protection policy 432323,Yes,Q_ID_1,Critical_data_element,,,{*:50},,Group data protection policy

ARI-5567: Presentation of Korean-language adverse media in SAP Ariba Supplier RiskProducts: SAP Ariba Supplier Risk

Audience: Buyers


This feature adds the Korean language to the list of languages in which adverse media articles may be presented in SAP Ariba Supplier Risk. The complete list of languages is

● Chinese (Simplified)● English● German● Italian● Korean● Portuguese● Russian● Spanish


SM-11787: Enhancements to supplier request duplicate checking

Description

Products: SAP Ariba Supplier Lifecycle andPerformanceSAP Ariba Supplier Information and PerformanceManagement (new architecture)

Audience: Buyers


This feature introduces the following enhancements to default and custom duplicate checks for existing suppliers during the supplier request process:

● Case insensitive matching● Improvements to matching accuracy and consistency● Display of match score, ordering of potential duplicate suppliers based on score, and other user interface

enhancements in the internal supplier request form and the approval workflow for both external and internal supplier requests

These enhancements increase the likelihood that if a supplier already exists in your site's vendor database, any duplicate supplier requests are identified either before they are submitted or before they are approved, preventing the creation of duplicate vendor records.

Prerequisites

Custom duplicate check based on questions in supplier requests is an optional feature and must be enabled in your site. For information on setting it up, see the Supplier management setup and administration guide.

To submit an internal supplier request and see duplicate check results on the supplier request form, you must be a member of the Supplier Request Manager group. To see duplicate check results during approval, you must be an approver for the request.

Limitations

Default duplicate checks are automatically performed on information in Address questions, but duplicate checking is not supported for Extended Address questions. Custom duplicate checking is only supported for text questions. No duplicate checks are performed against deactivated suppliers.




A new alert message for potential duplicate suppliers includes a See duplicates link. Clicking the link opens a new popup that shows potential matches, including and a new match score, which is a percentage value that expresses the closeness of the match. The popup also shows which answers in the current request match values for existing suppliers. The potential duplicate alert message shows in the following places in the supplier request workflow:

● While a requester is filling out an internal supplier request. At this point, the duplicate check runs continuously against the current information in the request form and updates the list of potential matches and match scores as the requester fills out the form.

● After the requester submits an internal supplier request. If the requester edits the request before it is approved, duplicate check updates the list of potential matches and match scores based on the edits.

● While an approver is approving an internal or external supplier request.

Match scores of 70% and below are labeled WEAK, while scores above 70% are labeled STRONG.

Information for users

● How duplicate checks work in submitted supplier requests [page 183]

How duplicate checks work in submitted supplier requests [page 183]

How duplicate checks work in submitted supplier requestsOnce a person at your company submits an internal supplier request, or a supplier submits an external supplier request, a duplicate check searches for existing suppliers that might match the request, scores the potential matches, and displays them based on specific logic.

The information in the request that contributes to the duplicate check depends on your site's configuration and the setup of your organization's supplier requests. External supplier requests and duplicate check based on custom questions are both optional features.

The supplier request duplicate check searches for existing suppliers in your site's vendor database by a combination of:

● Exact match to Dun & Bradstreet ID (D-U-N-S Number).● Strict match to the full supplier name.● At least a partial match to supplier name followed by a partial or full address match. At least a partial name

match must occur before address matching is attempted.● If your site uses custom duplicate check, partial matches to answers are also used for custom duplication

check. For custom duplicate check, the answer must match starting with the first character. If the answer contains any spaces, each space-separated word or group of characters is matched separately, and each must either fully or partially match starting with the first character.For example, if your site has an existing supplier with the value "Green Energy Corporation" in a field used for a custom duplicate check, "Green," Energy," and "Corporation" are all indexed for matching separately. Any corresponding supplier request answer that starts with "G," "E," or "C" is considered for matching, and answers such as "Gre," "Energ," and "Corp" are matched. Answers such as "Greed," "Reen," and "Gre Energion" are not matched.


The duplicate check scores these different match based on predefined logic. The score is expressed as a percentage between 0 and 100, with scores of 70% and above considered strong matches and scores of less than 70% considered weak matches.

In match scoring, a D-U-N-S Number match scores either 100% for an exact match or 0% for no match. Strict name matches score 100%, while partial name matches can vary between 0% and 100%. For matches on country, the duplicate check assigns maximum scores to exact matches but also accepts synonyms, ignoring case, and scores synonym matches based on degree of similarity to the request answer, with an exact string match scoring 100%. The duplicate check assigns a total matching score to existing, potentially matching suppliers based on all matching fields.

When the requester submits the supplier request (for internal requests only) and during supplier request approval (for both internal and external supplier requests), the duplicate check displays the top 20 matching suppliers, based on match score, in the following order:

● Exact matches (score of 100%) first.● Partial matches next, in descending order based on score.



Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP Ariba Applications Q2 2019 release guideImportant Disclaimers and Legal Information C O N F I D E N T I A L 185

www.ariba.com

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

http://www.ariba.com

https://www.sap.com/about/legal/trademark.html