88
CONFIDENTIAL 2019-04 Ariba Network Q2 2019 release guide © 2019 SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN

Ariba Network Q2 2019 release guide - SAP Ariba Connect

  • Upload
    others

  • View
    25

  • Download
    0

Embed Size (px)

Citation preview

CONFIDENTIAL2019-04

Ariba Network 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

SAP Ariba Supply Chain Collaboration features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6CSC-10350: Serial number visibility and reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Serial number reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How to generate serial number reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9How to view and export serial number lists in orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

CSC-11497: Quality certificate enhancements for orders, ship notices, and quality inspections. . . . . . . . . 11Buyer administrator interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Supplier user interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12cXML changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

CSC-11556: Quality Review update using email response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14How to configure quality collaboration notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15How to respond to a quality review notification by email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

CSC-11924: Quality notification enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Buyer administration user interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Supplier user interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

CSC-11928: Component consumption and component inventory enhancements. . . . . . . . . . . . . . . . . . 18Buyer user interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Supplier user interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

CSC-12187: Quality Notification mass update using Excel download/upload. . . . . . . . . . . . . . . . . . . . . . 20How to create and run a job to download quality notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21How to edit quality notifications in an Excel file that you downloaded. . . . . . . . . . . . . . . . . . . . . . . . 22How to upload changes to quality notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CSC-12649: Notification messages for ship notices that are declined or accepted with changes. . . . . . . . 24CSC-12649: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

CSC-12790: Allow integrated suppliers to send order confirmations with all item details. . . . . . . . . . . . . 25CSC-4411: Resend documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

CSC-4411: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27CSC-4411: Administrator interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27How to resend a document that was not received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

CSC-7553: Vendor upload to enable and disable SAP Ariba Supply Chain Collaboration relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

CSC-7553: Changes to reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29How to use a vendor CSV file to enable or disable SAP Ariba Supply Chain Collaboration relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

CSC-7867: Advanced packaging with handling units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2 C O N F I D E N T I A LAriba Network Q2 2019 release guide

Content

CSC-7867: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33CSC-7867: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33How to configure auto-numbering of handling units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34How to create packaging instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35How to create a ship notice with advanced packaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

CSC-8401: Ship notices by third-party online suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38CSC-8401: Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Workflow for ship notices by third-party online suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

General Ariba Network features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41SINV-5980: Support for ‘U’ (Unknown) account assignment category for service items. . . . . . . . . . . . . . 41CSC-9320: Enhanced storage location functionality for ship notices. . . . . . . . . . . . . . . . . . . . . . . . . . . 41NP-13576: Creating a correction service entry sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Buyer administrator task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Supplier task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

NP-13966: Provision to close, reopen, and delete messaging conversations. . . . . . . . . . . . . . . . . . . . . . 47Buyer and seller tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

NP-15794: Italy outbound enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50NP-15794 Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Workflow for Italy outbound enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52NP-15794 cXML changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Appendix - sample invoice cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

NP-15448: PDF based on official FatturaPA style sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Workflow for PDF based on FatturaPA style sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

NP-15461: Service entry sheet enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Buyer administrator interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Buyer administrator tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

NP-15612: Displaying rejection reasons in invoice, failed invoice, and SES reports. . . . . . . . . . . . . . . . . . 66NP-15221: Ariba Network buyer capability to opt out of or disable messaging. . . . . . . . . . . . . . . . . . . . . 67

Buyer administrator tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68NP-15657: Technical annulment of NAV invoices in Hungary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

NP-15657 Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69NP-15657 Supplier user tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

NS-5668: New Purchase Orders and Invoices tiles for standard and enterprise account users. . . . . . . . . 71NS-5668: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

NS-5695: Home page tile document limit increased from last 50 to last 200. . . . . . . . . . . . . . . . . . . . . .72NS-5695: User interface changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

NP-15094: Status tracking of CSV invoice upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73NP-15094 Changes to existing functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NP-15094 Supplier user tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

NP-13428: GRN report enhancement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77How to generate goods receipt reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

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

Additional fields added to GRN report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80CSC-12679: Planning Collaboration API for Supply Chain Collaboration. . . . . . . . . . . . . . . . . . . . . . . . . 80

Workflow for the Planning Collaboration API for Supply Chain Collaboration. . . . . . . . . . . . . . . . . . . 82How to develop an application that consumes the Planning Collaboration API for Supply Chain Collaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4 C O N F I D E N T I A LAriba Network Q2 2019 release guide

Content

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.

Ariba Network Q2 2019 release guideFeature enablement C O N F I D E N T I A L 5

SAP Ariba Supply Chain Collaboration features

CSC-10350: Serial number visibility and reportingDescription

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Automatically On

Buyers can include serial number information in the orders they send to suppliers. However, previously this information was not displayed in orders in the Ariba Network user interface. For transparancy, serial number information is now included in line item details.

There is a new serial number report template that buyers and suppliers can use to extract serial numbers from orders without opening them one by one.

Serial number cXML examples

Use the SerialNumberInfo element to specify serial numbers for a line item. Serial numbers can be specified as a list, range, or profile.

Here is an example of serial numbers specified as a list:

<SerialNumberInfo requiresSerialNumber="yes" type="list"> <SerialNumber>3482918</SerialNumber> <SerialNumber>3123333</SerialNumber> <SerialNumber>5423325</SerialNumber> </SerialNumberInfo>

Here is an example of serial numbers specified as a range (from 100,000 to 200,000):

<SerialNumberInfo requiresSerialNumber="yes" type="range"> <PropertyValue name="range"> <Characteristic domain = "minimum" value="100000"/> <Characteristic domain = "maximum" value="200000"/> </PropertyValue> </SerialNumberInfo>

Here is an example of serial numbers specified as a profile (3 to 10 numeric characters):

<SerialNumberInfo requiresSerialNumber="yes" type="profile"> <PropertyValue name="profile"> <Characteristic domain = "type" value="numeric"/>

6 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

<Characteristic domain = "minLength" value="3"/> <Characteristic domain = "maxLength" value="10"/> </PropertyValue> </SerialNumberInfo>

For more information about SerialNumberInfo, see the cXML reference guide available at http://cxml.org/ .

Prerequisites

● Buyers and suppliers that use their own cXML-enabled applications must use cXML 1.2.037 or later.

Buyer and supplier user interface changes

● Purchase Order pageIf an order contains serial numbers, click Details for a line item to view its details. The items’s serial numbers display in a section called Information on Ship Notice [Optional] > Serial Numbers.○ If serial numbers are specified as a profile or a range, they appear under Serial Numbers.○ If serial numbers for an item are defined as a list, click Details. The Items Serial Number window appears.

You can page through the list, download it in CSV format, or print it.● Serial number reports [page 7]

Supplier user tasks

● How to generate serial number reports [page 9]● How to view and export serial number lists in orders [page 10]

Serial number reports

Serial number reports contain information about lists of asset serial numbers contained in orders. When suppliers send a ship notice for an order, the buyer can require them to include unique asset serial numbers for each line item. This report helps manage those serial numbers.

Serial number report criteria

Field Description

Customer By default all customers are selected for inclusion in the report. To limit the report to spe­cific customers, click Select and then select customers for the report.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 7

Field Description

Order Number To report on an order with a specific number, enter an order number in the text box. Order numbers are case-sensitive, so PO123 is different from po123.

Order Amount To report on orders with amounts in a specified range, enter numerals in the fields. Do not enter currency symbols. Ariba Network uses your organization’s default currency. To over­ride your default currency, enter numeric values and a currency code.

Order Routing Status Select a value from the list to report on orders by routing status. To create a broad report, use the default value, Any.

Order Status Select a value from the list to report on orders by fulfillment status. To create a broad re­port, use the default value, Any.

Include active orders only By default, this option is checked, which means only active orders are included in the re­sults. To include fully shipped orders and obsolete orders, uncheck this option.

Order Date Select the range of order dates you want to include in the report. The report can be run for a period up to 12 months.

Max Results Returned Select the maximum number or records returned by the report. By default, the report re­turns up to 100 records. The report supports up to 100,000 records.

Serial number report fields

Field Description

Order # Purchase order number

Customer (in seller-created reports only) Name of the customer.

Supplier (in buyer-created reports only) Name of the supplier.

Line Number Order line number.

Quantity Ordered quantity.

UOM Unit of measure.

Serial No Serial number value.

Unit Price Unit price for the item.

Unit Price Currency Currency associated with the unit price.

Part Number Part number of the item.

Customer Part Number Part number of the item in the buyer's system.

Manufacturer Part Number Manufacturer part number.

Need by The buyer’s need-by date from the order.

Description Description of the item.

Currency The currency used for monetary amounts in the order.

Amount Amount for the item.

Order Status The fulfillment status of the order.

8 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

Field Description

Version Version specified for the ordered item.

How to generate serial number reports

If customers include serial numbers for line items in orders, you can use the serial number report template to generate serial number reports. Customers may require serial numbers on ship notices.

Prerequisites

● To generate serial number reports with data, orders must include serial numbers.● Users must belong to a role that includes the Purchase Order Report Administration permission.

Procedure

1. Click the Reports tab.2. Click Create.3. On the Report Description page, enter the following information.

○ Title—Enter a title for the report.○ Description—(Optional) Enter a report description.○ Time Zone—Choose your time zone.○ Language—Choose the language for the report.○ Report Type—Select Serial Number Report.

4. Click Next.5. Enter the following criteria:

Option Description

Customer By default, all customers are included. Click Select to select customers for the report.

Order Number To report on an order with a specific number, enter an order number in the text box.

Order Amount Enter an order amount. Do not enter currency symbols.

Order Routing Status Choose a routing status, or use the default value, Any.

Order Status Choose an order status, or use the default value, Any.

Include active orders only

Check this box to include only active orders in the results. Uncheck it to include shipped orders and obsolete orders.

Order Date Select a range of order dates. The report can be run for a period up to 12 months.

Max Results Returned Enter the maximum number or records returned by the report. The default is 100. The report sup­ports up to 10,000 records.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 9

6. Click Submit.7. After the report is processed, select it, and click Download.

How to view and export serial number lists in orders

If serial numbers are included with an order, you can view serial number details for each line item.

Prerequisites

The cXML file for the order must include serial number information.

LimitationsThe Items serial number window can display up to 500 serial numbers. If there are more than 500 serial numbers for the item, download the full list.

Procedure

1. Open an order that containers serial numbers for line items.2. For any item contained in the order, click Details.3. Find the Information on Ship Notice [Optional] > Serial Numbers section.4. If serial numbers are specified as a profile or a range, they appear under Serial Numbers.5. If the format is a list, click Details to see the list of serial numbers for the item.

The Items serial number window appears.6. Follow these steps:

a. To advance to the next page, click the icon.b. To download the list, click the Download Serial Numbers icon.c. To print the list, click the Print Screen icon.d. When you are finished, click Done.

10 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

CSC-11497: Quality certificate enhancements for orders, ship notices, and quality inspectionsDescription

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Customer configured

This feature provides the following enhancements to quality certificates for orders, ship notices, and quality inspection requests:

● Buyers can send certificate requests at the header level or at the item level. They can also specify whether each certificate is required or optional.

● On the Purchase Order page, quality certificates can now appear at the header level in the user interface.● Buyers can configure a business rule to require suppliers to attach a quality certificate to a ship notice. This

rule existed before, but it now applies to certificates at the header level or item level of ship notices.● Suppliers can now attach quality certificates at the header level or item level of ship notices.● Quality inspection documents now support optional and required certificates.

Prerequisites

● Buyers and suppliers that use their own cXML-enabled applications must use cXML 1.2.039 or later to support these quality certificate enhancements.

● Suppliers must have a trading relationship with a buyer entitled for the quality collaboration component.

Buyer administrator interface changes

See Buyer administrator interface changes [page 12].

Supplier user interface changes

See Supplier user interface changes [page 12].

cXML changes

See cXML changes [page 13].

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 11

Buyer administrator interface changes

Default transaction rules

The name of the following rule in the Order Confirmation and Ship Notice Attachment Rules list was changed to reflect that certificates can now be attached to the header of a ship notice:

Old rule New rule

Require suppliers to provide a quality certificate for line items on ship notices

Require suppliers to provide a quality certificate on ship notices

This rule is unchecked (disabled) by default. When this rule is checked, suppliers must attach required quality certificates to a ship notice.

Supplier user interface changes

Purchase Order

In the header of an order, there is a section called Quality Certificates on Ship Notice. It lists all quality certificates (required and optional) that have been attached at the header level. Quality certificates can also be attached to line items.

Ship Notice

In the header of a ship notice, there is a section called Quality Certificates. It lists all quality certificates (required and optional) that have been attached at the header level. If a file has not been attached for a certificate yet, it reads, “No attachment yet.” Quality certificates can also be attached to line items.

To attach a quality certificate to a ship notice:

1. In the Quality Certificates section of the header or a line item, click Attach file.2. Select a certificate.3. Click Choose file.4. Select the file, and click Open.5. Click Add attachment.

Quality Inspection

When you click Edit to update a quality inspection request, the Inspection details page appears. You can click Attach files Additional documents to attach multiple quality certificates (required or optional).

12 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

NoteA required certificate is indicated by an asterisk.

cXML changes

The following quality certificate enhancements are available in cXML 1.2.039 or later. For complete information about these elements and their attributes, see the cXML reference guide available at http://cxml.org/ .

Element Used by Description of change

CertificateInfo QualityInfo This is a new element. It represents cer­tificate information.

OrderRequestHeader-Industry

OrderRequestHeader The following element was added: QualityInfo.

QualityInfo ItemOutIndustry

OrderRequestHeader-Industry

QualityInspection-RequestHeader

The following element was added: CertificateInfo.

The following example shows three certificates that have been added to the header of an order. The first two certificates are required, and the third certificate is optional.

<OrderRequestHeaderIndustry> <QualityInfo> <CertificateInfo isRequired="yes"> <IdReference identifier="HEAD25668" domain="certificateType"> <Description xml:lang="en-US">Cert. of Analysis</Description> </IdReference> </CertificateInfo> <CertificateInfo isRequired="yes"> <IdReference identifier="HEAD3456" domain="certificateType"> <Description xml:lang="en-US">Cert. of Conformance</Description> </IdReference> </CertificateInfo> <CertificateInfo> <IdReference identifier="HEAD888" domain="certificateType"> <Description xml:lang="en-US">Cert. Additional</Description> </IdReference> </CertificateInfo> </QualityInfo> </OrderRequestHeaderIndustry>

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 13

CSC-11556: Quality Review update using email response

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Automatically on

This feature provides a simple way for buyers and suppliers to respond to a quality review through email. Buyers and suppliers can open a quality review notification in their email application and then respond to the email within 30 days of receiving it. Their responses automatically update the quality review History tab. Users can also attach files to the email response, and Ariba Network automatically attaches the files to the quality review.

Prerequisites

● Buyers must be entitled for the quality collaboration component.● Suppliers must have a trading relationship with a buyer entitled for the quality collaboration component.● To receive quality collaboration email notifications, buyers and suppliers must enable quality collaboration

notifications on the Quality tab. See How to configure quality collaboration notifications [page 15].

Limitations

Although the History tab of a quality review lists all comments that users posted, it doesn’t indicate whether comments were posted through email or the user interface.

Buyer and suppler user interface changes

The History tab of a quality review maintains an audit log of all comments posted, including comments posted through email responses.

Buyer and supplier user tasks

● How to configure quality collaboration notifications [page 15]● How to respond to a quality review notification by email [page 15]

14 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

How to configure quality collaboration notifications

You can configure the notifications you want to receive for quality collaboration. Choose to enable notifications for different types of documents and different events.

Prerequisites

● Buyers: Your account has been entitled for the quality collaboration component.● Suppliers: You have a trading relationship with a buyer entitled for the quality collaboration component.

Procedure

1. Click the Quality tab.

2. Click the settings icon .The Quality Settings page appears.

3. Click Edit.4. If you are a supplier, choose one of the following options:

○ Same rule for all customers—Applies these quality settings to all of your customers.○ Separate rules for each customer—Applies separate quality settings to each customer. If you choose this

option, click Add customer to specify a customer to define settings for.5. If you are a buyer, choose one of the following options:

○ Same rule for all suppliers—Applies these quality settings to all of your suppliers.○ Separate rules for each supplier—Applies separate quality settings to each supplier. If you choose this

option, click Add supplier to specify a supplier to define settings for.6. Check the email notification options you prefer for Quality inspections, Quality notifications, and Quality

reviews.7. Click Submit.

How to respond to a quality review notification by email

You can respond to quality review notifications through email to post a comment or attach files to the associated quality review.

Prerequisites

● Buyers: Your account has been entitled for the quality collaboration component.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 15

● Suppliers: You have a trading relationship with a buyer entitled for the quality collaboration component.● Buyers and suppliers: Before you can respond to quality review notifications, your Ariba Network account must

be configured to receive them. See How to configure quality collaboration notifications [page 15].

Limitations● You can’t reformat or delete parts of the original quality review notification message. Otherwise, Ariba

Network can’t process the message.● You can’t change the To address in the reply email. However, you can add recipients.● In your reply email, don’t enter line breaks or exceed 1024 characters. Ariba Network removes line breaks

and excess characters before posting your comment to the quality review.● You can attach files to the reply email, but they can’t exceed 1 GB in total size.● When the quality review status changes to Closed, no more notification responses can be received.● You can send a reply to a quality review notification within 30 days of receiving it. After 30 days, replies to

the quality review notification won’t be posted, but you can still edit the quality review in the Ariba Network portal.

Procedure

1. Open the email notification in your email client.2. Create a reply to the email, observing the above limitations.3. Send the email.

The text from your email reply is encrypted for transport and is posted as a comment to the quality review. Any files you attached to the email are automatically attached to the quality review.

CSC-11924: Quality notification enhancementsDescription

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Customer configured

This feature makes the following enhancements to quality notifications:

● For the task section of quality notifications, the optional Processor type, Processor ID and Processor name fields are now list fields. Only valid list values can be selected. Previously, these fields were text fields that allowed any value.

NoteValidations for these fields apply to quality notifications that are created online in Ariba Network or received as cXML.

16 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

● Several new Quality collaboration rules have been added for buyers:○ Based on a new business rule Allow suppliers to create non-PO quality notifications in a multi-ERP

environment, suppliers can select the buyer’s system ID for non-PO quality notifications to route the document to the proper system.

○ Based on a new business rule Allow suppliers to send quality notifications for indirect orders without part numbers, suppliers can now create quality notifications for line items without a material part number or location.

○ Based on a new business rule Do not allow suppliers to send non-PO quality notifications, suppliers can be prevented from creating quality notifications that don’t reference orders.

Prerequisites

● Buyers must be entitled for the quality collaboration component.● Suppliers must have a trading relationship with a buyer entitled for the quality collaboration component.

Buyer administration user interface changes

See Buyer administration user interface changes [page 17].

Supplier user interface changes

See Supplier user interface changes [page 18].

Buyer administration user interface changes

Default transaction rules > Quality collaboration rules

A new Quality collaboration rules section was added to the Default transaction rules page. It has the following rules:

● Allow suppliers to create non-PO quality notifications in a multi-ERP environment—If this rule is checked, suppliers can create non-PO quality notifications and select which system they apply to when there are multiple routing end points. Otherwise, quality notifications are always sent to the default routing end point.Default setting: No

● Allow suppliers to send quality notifications for indirect orders without part numbers—If this rule is checked, suppliers can send quality notifications for line items without specifying a customer part number or customer location. This rule makes those two quality notification fields optional.Default setting: No

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 17

● Do not allow suppliers to send non-PO quality notifications—If this rule is checked, suppliers can only create quality notifications that reference an order. Otherwise, suppliers can create non-PO quality notifications from the Quality tab.Default setting: No

NoteYou can also apply these default transaction rules to supplier groups.

Supplier user interface changes

Quality > Notification

The Quality notifications page has several changes related to new quality collaboration business rules.

Quality collaboration rule If the customer checked the rule... If the customer unchecked the rule...

Allow suppliers to create non-PO quality notifications in a multi-ERP environment

A new Customer routing identifier field lets you select a system ID from a list to route the quality notification to one of the customer’s end points.

The Customer routing identifier field is hidden. The customer’s default system ID is used to route the quality notifica­tion.

Allow suppliers to send quality notifications for indirect orders without part numbers

The Customer part no. and Customer location fields are optional.

The Customer part no. and Customer location fields are required.

Do not allow suppliers to send non-PO quality notifications

The Create quality notification button is unavailable.

A Create quality notification button ap­pears on the Quality notifications page, letting you create a quality notification that doesn’t reference an order.

When you add a task to a quality notification, the optional Processor type, Processor ID, and Processor name fields are now list fields. Previously, they were text fields.

CSC-11928: Component consumption and component inventory enhancements

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Customer configured

18 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

The following enhancements have been made to component consumption and component inventory:

● A new component inventory business rule allows buyers to choose whether to display an error message whenever consumption exceeds the available quantity.

● The Batches popup window, which displays when suppliers click the Look Up link next to the Customer Batch # field on the Create Consumption Document page, has two new columns showing the Consumed Quantity and the Balance Quantity.

● The Balance Quantity amount is now calculated whenever the supplier submits a new component consumption report or a ship notice.

● Buyers can now view component consumption in the Ariba Network buyer portal.

Buyer user interface changes

See Buyer user interface changes [page 19].

Supplier user interface changes

See Supplier user interface changes [page 20].

Buyer user interface changes

Default transaction rules > Component consumption rules

The following new rule was added:

● Do not allow consumption to exceed balance quantity in component inventory—If this rule is checked, an error message appears whenever consumption exceeds the available batch quantity. This error message can appear when the supplier tries to submit a ship notice or component consumption report. If you want to allow suppliers to send a ship notice or a component consumption report with a negative stock quantity, leave this rule unchecked.

NoteThis rule applies only to component inventory managed in batches.

Default setting: No

NoteYou can also apply this default transaction rule to supplier groups.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 19

Supplier user interface changes

Component Consumption Document page > Batches window

The Batches popup window appears when you click the Look Up link next to the Customer Batch # field. It has two new columns:

● Consumed Quantity—quantity of component inventory already consumed for the batch.● Balance Quantity—remaining quantity of component inventory for the batch.

Balance quantity calculation

The Balance Quantity amount is now calculated whenever you submit a component consumption report or a ship notice.

Validation for negative stock

The customer can enable a rule to not allow consumption to exceed the balance quantity in component inventory. If so, you can’t send a component consumption report or a ship notice with a negative stock quantity.

CSC-12187: Quality Notification mass update using Excel download/uploadDescription

Products: SAP Ariba Supply Chain Collaboration

Audience: Suppliers

Enablement: Automatically on

This feature allows suppliers to perform a mass download of quality notification documents in Excel format, edit the quality notification fields, and then upload the modified Excel files to Ariba Network.

Prerequisites

● Suppliers must have a trading relationship with a buyer entitled for the quality collaboration component.● To open and modify XLSX files, you need Microsoft Excel 2007 or later, or an application that supports

Microsoft Excel Open XML format, such as LibreOffice.

20 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

User interface changes

There are several changes to the Uploads/Downloads page:

● On the Jobs tab, a new job type is supported: Quality Notifications. You can create a job to download quality notifications from a customer. See How to create and run a job to download quality notifications [page 21].

● On the Downloads tab, you can view any quality notification jobs that have been run, and you can download the files.

● On the Uploads tab, you can click Upload to upload a quality notification Excel document that you have downloaded and edited. See How to upload changes to quality notifications [page 23].

User tasks

● How to create and run a job to download quality notifications [page 21]● How to edit quality notifications in an Excel file that you downloaded [page 22]● How to upload changes to quality notifications [page 23]

How to create and run a job to download quality notifications

You can create a job to download quality notifications for a customer in Excel format.

Prerequisites

● You must have a trading relationship with a customer entitled for the quality collaboration component.● To open and modify XLSX files, you need Microsoft Excel 2007 or later, or a spreadsheet that supports

Microsoft Excel Open XML format, such as LibreOffice.

Procedure

1. Click Upload/Download.2. On the Jobs tab, click Create to create a new job.

The Create/Edit Job window appears.3. Enter the following information:

○ Name: Enter the name of the job.○ Type: Select Quality Notification.○ Customer: Start typing a customer, and then select one from the list.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 21

○ Start Date: Select the start date for quality notifications in the job.○ End Date: Select the end datee for quality notifications in the job.

4. Choose the quality notification data to include in the download:

○ Header task○ Header activity○ Defect○ Defect task○ Defect activity○ Defect cause○ Defect additional batches

5. Click Save.6. Select the new job, and click Run.

The pages switches to the Downloads tab.7. Click Refresh Status to refresh the job's status. When it's finished, the status changes to "Completed".

8. In the File column, click the icon to download the Excel file for the job.

Next Steps

How to edit quality notifications in an Excel file that you downloaded [page 22]

How to edit quality notifications in an Excel file that you downloaded

After you download an Excel file containing quality notifications, you can edit the file for upload.

Prerequisites

● You must have a trading relationship with a customer entitled for the quality collaboration component.● Download the quality notifications file first. See How to create and run a job to download quality notifications

[page 21].● To open and modify XLSX files, you need Microsoft Excel 2007 or later, or a spreadsheet that supports

Microsoft Excel Open XML format, such as LibreOffice.

Procedure

1. Open the Excel file containing quality notifications.

22 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

2. Click any of the following tabs:

○ Header○ Header Tasks○ Header Activities○ Defects○ Defect Tasks○ Defect Activities○ Defect Causes○ Defect Additional Batches

3. For existing rows, edit any columns that are shaded blue.

NoteDon't edit any columns shaded white. Those values can't be updated.

4. For Action columns, specify one of the following values:

○ A = Add○ U = Update○ D = Delete

5. When you are finished editing, save the file.

Next Steps

How to upload changes to quality notifications [page 23]

How to upload changes to quality notifications

After you finish editing an Excel file containing quality notifications for a customer, you can upload the file to Ariba Network.

Prerequisites

● You must have a trading relationship with a customer entitled for the quality collaboration component.

Procedure

1. Click Upload/Download.2. Click Upload.

The Upload File window appears.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 23

3. Enter the following information:

○ Name: Enter the name of the job.○ Type: Select Quality Notification.○ Customer: Start typing a customer name, and then select one from the list.○ File: Click Choose File to choose the quality notifications file.

4. Click Upload.5. When the upload is complete, the Status changes to "Completed".

NoteIf the upload failed, go to the Log column and click the icon to download the error log. Fix the errors and try uploading again.

CSC-12649: Notification messages for ship notices that are declined or accepted with changesDescription

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Customer configured

Currently, suppliers can only choose to receive automatic email notification when there is a ship notice failure. The notification messages for ship notices that are declined or accepted with changes feature adds the following capabilities:

● Suppliers can also choose whether to receive email notification of these events:○ The buyer declines a ship notice.○ The buyer accepts a ship notice but proposes changes.

● When buyers accept a ship notice, they can now include in the status update request a comment with proposed changes for the supplier to consider.

Changes to existing functionality

See CSC-12649: Changes to existing functionality [page 25].

24 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

CSC-12649: Changes to existing functionality

Supplier user interface changes

This feature makes the following changes to the Company Settings Notifications Network page:

● Adds a Ship Notice Notifications section● Moves the Ship Notice Failure notification from the Electronic Order Routing section to the Ship Notice

Notifications section● Adds Ship Notice Declined and Ship Notice Accepted With Changes notifications to the Ship Notice

Notifications section

Ship notice status updates are also logged in the History tab of the ship notice details page.

cXML changes

This feature adds the AcceptedWithChanges value for the type attribute of the DocumentStatus element in a StatusUpdateRequest document. Buyers enter in a Comments element the proposed change for a line item. The comments are informational only and do not affect the ship notice.

CSC-12790: Allow integrated suppliers to send order confirmations with all item details

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Support request

The allow integrated suppliers to send order confirmations with all item details feature introduces a new entitlement, Enhanced order confirmation integration capabilities for hosted and integrated suppliers. When this entitlement is enabled, integrated suppliers must include line item information in order confirmation cXML.

This entitlement also includes all capabilities provided by the Enhanced order confirmation integration capabilities entitlement, with one exception for the Ariba Network user interface. Unlike the Enhanced order confirmation integration capabilities entitlement, when an order confirmation has an empty estimated delivery date field, the Enhanced order confirmation integration capabilities for hosted and integrated suppliers entitlement does not automatically fill that field on the following pages:

● Inbox Orders and Releases Actions Confirm Entire Order

● Inbox Orders and Releases Actions Update Line Items

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 25

Prerequisites

SAP Ariba Customer Support must enable the Enhanced order confirmation integration capabilities for hosted and integrated suppliers entitlement for the buyer.

cXML changes

The entitlement Enhanced order confirmation integration capabilities for hosted and integrated suppliers requires integrated suppliers to provide the following in a cXML order confirmation:

● Specify type="allDetail" in the confirmation header (ConfirmationHeader).● Include line item information (ConfirmationItem).

CSC-4411: Resend documents

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Automatically on

Sometimes, for any of several reasons including syntax errors, documents fail to get transmitted through Ariba Network. With the resend documents feature, SAP Ariba Supply Chain Collaboration lets you know of specific syntax errors, and enables administrators to resend these documents after correcting the errors.

Prerequisites

This feature requires buyer administrator or supplier administrator privileges.

Changes to existing functionality

See CSC-4411: Changes to existing functionality [page 27].

26 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

Administrator interface changes

See CSC-4411: Administrator interface changes [page 27].

Administrator tasks

See How to resend a document that was not received [page 28]. This procedure replaces "How to resend a purchase order from purchase order details" in Supplier guide for SAP Ariba Supply Chain Collaboration. Both buyer administrators and supplier administrators can use this procedure to resend documents.

CSC-4411: Changes to existing functionality

With the resend documents feature, SAP Ariba Supply Chain Collaboration:

● Captures document contents when they fail on arrival at Ariba Network● Provides a user interface for triggering the reprocessing of these documents● Informs users of delivery failures caused by non-compliance with business rules, whether the cause lies with

the document or with the business rule● Provides detailed error messages and suggests potential solutions● Enables buyer administrators and supplier administrators to discard or resend documents that previously

failed to be delivered● Enables buyer administrators and supplier administrators to export cXML files for the affected documents, and

to mark document transmission issues as resolved

CSC-4411: Administrator interface changes

For both buyer administrators and supplier administrators who are entitled for SAP Ariba Supply Chain Collaboration, a Documents to Resend tab is added to the Outbox tab in the user interfaces. Documents to Resend contains a Search Filter and a Documents to Resend table. The Resolution Status search filter can be set to Show unresolved entries or Show resolved entries.

Fields for resend documentsThe Documents to Resend table includes the following columns:

● Recipient● Payload ID● Document Type● Document Number● Last Failed● Last Error Category● Actions

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 27

● table customization button

The Actions column provides the following options:

● Resend which is grayed out if the failed document's problem type prevents resending the document● Export cXML● Mark as Resolved

How to resend a document that was not received

Administrators can resend some documents that were not received because of errors.

Context

Occasionally, documents sent through Ariba Network are not received at their final destination because of errors in the documents or their lack of compliance with relevant business rules. Administrators can often resend these documents after correcting the errors.

Procedure

1. As an administrator, click Outbox Documents to Resend .

The documents search results are displayed, with details about the causes of the failures. The Resolution Status search filters Show unresolved entries and Show resolved entries control which of the failed documents that meet the other search results are included.

2. Review the failed document's error message, make the correction, then click Resend in the Actions column.

NoteAlternatively, you can choose these other actions in the Actions column:○ Click Export cXML to export the affected document in cXML, then mark the document transmission

issues as resolved.○ Click Mark as Resolved if you do not want to resend the failed document.

28 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

CSC-7553: Vendor upload to enable and disable SAP Ariba Supply Chain Collaboration relationships

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers

Enablement: Automatically on

At times, buyers might need to change the SAP Ariba Supply Chain Collaboration relationship status for a greater number of vendors than the Ariba Network user interface can accommodate. With the vendor upload to enable and disable SAP Ariba Supply Chain Collaboration relationships feature, buyers can now modify SAP Ariba Supply Chain Collaboration enablement values in the Proposed Enablement Mode field of a vendor CSV file. Buyers then upload the file to enable or disable the relationship for all affected vendors in one operation.

Changes to reporting

See CSC-7553: Changes to reporting [page 29].

User tasks

See How to use a vendor CSV file to enable or disable SAP Ariba Supply Chain Collaboration relationships [page 30].

CSC-7553: Changes to reporting

This feature adds support for uploading a vendor CSV file of vendor data to change one or more vendor relationships for SAP Ariba Supply Chain Collaboration. The file can be a Vendor Data Export CSV report or a vendor CSV file created with the Upload Vendor template. A buyer can set an SAP Ariba Supply Chain Collaboration relationship with one of the following enablement values in the Proposed Enablement Mode column, then upload the vendor CSV file to apply the values:

● EnableSCCWithRetail● EnableSCCWithoutRetail● DisableSCC

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 29

How to use a vendor CSV file to enable or disable SAP Ariba Supply Chain Collaboration relationships

Buyers can use a vendor CSV file to enable or disable multiple SAP Ariba Supply Chain Collaboration relationships in one operation.

Prerequisites

● Assume a role with the Supplier Enablement Program Administrator permission.● Have available one of the following vendor CSV files, populated with vendor records:

○ Vendor Data Export report—This report prepopulates all fields that have existing data, including SAP Ariba Supply Chain Collaboration enablement settings. For more information, see "How to generate and download reports" in Buyer administration guide.

○ Upload Vendor template—Add vendor data to the template before you perform this procedure. For more information, see "How to create a vendor CSV file" in Enabling suppliers on Ariba Network.

Procedure

1. Open the vendor CSV file for editing.2. Enter in the Proposed Enablement Mode column your desired enablement settings, then save the file.

Valid values are:

Enablement value Description

EnableSCCWithRetail Enables the vendor for SAP Ariba Supply Chain Collaboration, including retail industry fields

EnableSCCWithoutRetail Enables the vendor for SAP Ariba Supply Chain Collaboration, excluding retail indus­try fields

DisableSCC Disables the vendor for all SAP Ariba Supply Chain Collaboration enablement

Observe these guidelines:○ To include other text in the same field, enter that text first, followed by a pipe character (|) and the

enablement value. For example:Your comment | EnableSCC

TipTo avoid setting the wrong enablement value, enter only one enablement value in the field. Because this field accepts free text, more than one enablement value could be entered, but only the last value in the field is applied when you upload the file.

○ You can set provisional enablement values for standard account suppliers and private suppliers. The setting becomes active after the supplier is fully registered.

30 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

○ If the vendor CSV file has multiple records with the same Network ID value but different enablement values, the value of the record nearest the end of the file is applied.

○ Enablement values for a private supplier are ignored if the private supplier consolidates to an existing vendor. The private supplier inherits the enablement values of the existing supplier.

3. Go to Supplier Enablement Manage Vendors .4. Click Upload and choose Vendors from the pulldown.5. On the Upload Vendors page, choose your edited CSV file and click Upload.

Results

On the Supplier Enablement Active Relationships page, the Supply Chain Collaboration column reflects the updated SAP Ariba Supply Chain Collaboration enablement settings.

CSC-7867: Advanced packaging with handling units

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Customer configured

Feature IDs associated with this feature: CSC-7867, CSC-8410, CSC-11021, CSC-12048

With the advanced packaging with handling units feature, buyers can enable suppliers to specify a packing plan for ship notice items as they create a ship notice.

Buyers can:

● Upload packaging instructions for the supplier and configure automatic numbering of handling units.● Provide multiple packing instructions when a single packing instruction cannot cover all materials.● Use a template to create packaging instructions.

Suppliers can:

● Use a wizard to guide them through steps to create handling units, define handling unit hierarchies, and print labels. The wizard uses the packaging instructions provided by buyers to help suppliers plan how to pack items. Suppliers can also edit the packaging instructions and build handling units on the fly.

● Set their own auto-numbering settings, which override buyer auto-numbering settings if any were made. And support of multiple same-level packaging materials enables suppliers to define those instructions.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 31

Prerequisites

To use this feature, buyers must first do the following:

● Enable the Allow suppliers to use advanced packaging on ship notices rule. When this rule is enabled, transaction rule Require suppliers to provide a unique Global Individual Asset ID for line items on ship notices is ignored.

● To allow GS1 numbering, enable the Require suppliers to provide a Global Individual Asset ID for line items on ship notices that conforms to the Serial Shipping Container Code (SSCC) format rule.

● Upload packaging instructions for each handling unit.● Configure automatic numbering for handling units.

Limitations

Auto-numbering for handling units can be configured and used only when using the Ariba Network user interface.

Changes to existing functionality

See CSC-7867: Changes to existing functionality [page 33].

User interface changes

See CSC-7867: User interface changes [page 33].

Changes to reporting

This feature adds a Packaging Instructions template in Excel format.

Buyer user tasks

● How to configure auto-numbering of handling units [page 34]● How to create packaging instructions [page 35]● Packaging Instructions fields [page 36]

32 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

Supplier user tasks

● How to create a ship notice with advanced packaging [page 37]

CSC-7867: Changes to existing functionality

The advanced packaging with handling units feature provides the following functionalities:

● Configurable automatic numbering for handling units● Packaging instructions upload● A packaging wizard added to the ship notice creation process● Packaging rules validation● Label printing

CSC-7867: User interface changes

Buyer user interface changes

● Adds a Handling Units section to the Administration Configuration Configure Document Numbering Preferences page.

● Adds a Packaging Instructions type to the Upload/Download Uploads page.

● Adds a Packaging Instructions template in Excel format to the Upload/Download Uploads Upload File page. When Packaging Instructions is chosen from the Type pulldown, a Download template link appears.

Supplier user interface changes

● Adds a Pack Items button to the Create Ship Notice page. This button launches a packaging wizard that steps through the following pages:○ Define packaging instructions○ Confirm packing plan○ Print shipping labels

● Adds a Numbering Preferences tab to the Company Settings Customer Relationships page. Supplier numbering preferences for handling units override any numbering preferences configured by the buyer. The Numbering Preferences page contains:○ A Create button that opens the Configure Numbering page.○ A Handling Units section with the following fields:

○ Buyer○ Configuration type

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 33

○ Prefix○ Suffix○ Rolling○ Max. characters○ From○ To○ Current number○ Actions (Edit, Refresh, Delete)

○ Adds a warning message when the specified buyer has already configured numbering.● Adds a Choose packaging instructions dropdown to the end of the first line item in the Items to be packed

section of the Create Ship Notice Define packaging instructions page. This dropdown provides a pick list of uploaded packaging instructions, which might include multiple packaging instructions for a material..

● Adds a Define Instructions button to the Confirm packing plan page of the packaging wizard. This button returns you to the Define packaging instructions page.

● Adds a Package document no. field to the Print shipping labels page of the ship notice packaging wizard. Suppliers can enter an optional alphanumeric ID in this field for tracking the item.

How to configure auto-numbering of handling units

You can configure how the advanced packaging wizard for ship notices will automatically number handling units. Suppliers can choose to override this configuration with their own auto-numbering settings.

Prerequisites

To allow GS1 numbering, enable the Require suppliers to provide a Global Individual Asset ID for line items on ship notices that conforms to the Serial Shipping Container Code (SSCC) format rule.

Procedure

1. Go to Administration Configuration Document Number Preferences .2. In the Handling Units section, click Create.3. On the Configure Numbering page, enter the desired numbering criteria and constraints and click OK.4. Verify the configuration and click Save.

Next Steps

● Enable transaction rule Allow suppliers to use advanced packaging on ship notices for the suppliers you want to use this feature.

34 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

● Create and upload packaging instructions [page 35].

How to create packaging instructions

Buyers can download an Excel template to create packaging specifications for different types of material, then upload the files for suppliers to use with the advanced packaging wizard.

Prerequisites

● Enable the Allow suppliers to use advanced packaging on ship notices rule for the suppliers you want to use the advanced packaging wizard.

NoteWhen this rule is enabled, transaction rule Require suppliers to provide a unique Global Individual Asset ID for line items on ship notices is ignored. To allow GS1 numbering, enable the Require suppliers to provide a Global Individual Asset ID for line items on ship notices that conforms to the Serial Shipping Container Code (SSCC) format rule.

● (Optional) Configure auto-numbering of handling units [page 34].

Procedure

1. Go to Upload/Download Uploads and click Upload.2. In the Upload File popup, choose Packaging Instructions from the Type pulldown.

The Download template link displays.3. Click Download template and choose where to save the file.

The Packaging Instructions template downloads.4. Open the template file and enter data for all desired material types.

Only the latest uploaded instructions are used.

5. Go to Upload/Download Uploads , then click Upload.6. In the Upload File popup, enter a name to call the upload and choose Packaging Instructions from the Type

pulldown. Then browse to choose the desired file and click Upload.

The Uploads page opens and shows your uploaded file.

○ If the upload status is Processing, click Refresh Status to update the status.○ If the upload status is Completed, processing is finished.○ If the upload status is Failed, click the download icon in the Log column for troubleshooting information.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 35

Packaging Instructions fields

The Packaging Instructions template contains the following fields.

NoteThe Create Handling Unit and Allow Mixed fields perform actions when set to Yes.

Field Description

Packaging Specification ID A unique ID for the packaging specification.

Capacity Not used. Capacity information is taken from the Maximum Capacity field.

Material The customer product ID of the product to be packed.

Material Description

Unit Required. The value of Unit from the ship notice.

Packaging Level

Packaging Material The packaging material to contain the product.

Packaging Material Description

Maximum Capacity The capacity value used by the system.

Minimum Capacity

Length

Unit Length

Height

Unit Height

Width

Unit Width

Volume

Unit Volume

Net Weight The total weight, excluding packaging.

Gross Weight The total weight, including packaging.

Unit Gross Weight

Total Volume

Unit Total Volume

Parent Packaging Material The next larger packaging material that can contain a number of the packaging materials.

Create Handling Unit Set to Yes to generate handling units automatically, based on these specifications. Valid values are Yes, No, and blank which is the same as No. Default is blank.

36 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

Field Description

Allow Mixed Required. Set to Yes to allow different materials in the same innermost handling unit. Valid values are Yes, No, and blank which is the same as No. Default is blank.

How to create a ship notice with advanced packaging

Suppliers creating a ship notice can use the advanced packaging wizard to pack ship notice items.

Prerequisites

● The transaction rule Allow suppliers to use advanced packaging on ship notices is enabled.● When GS1 numbering is used, the buyer has enabled the Require suppliers to provide a Global Individual

Asset ID for line items on ship notices that conforms to the Serial Shipping Container Code (SSCC) format rule.

● The buyer has uploaded packaging instructions.

Context

The ship notice advanced packaging wizard helps you develop a packing plan, use buyer packaging instructions, and print shipping labels before you submit the ship notice.

NoteTo create a ship notice without advanced packaging, see "How to create a ship notice" in Receiving and fulfilling orders.

Procedure

1. Go to Inbox Orders and Releases .2. Choose the purchase order, then on the purchase order details page click Create ship notice.3. Verify the items to ship and click Pack Items.

○ If packaging instructions exist for all items, the Confirm packing plan page opens. Skip to Step 5 [page 38].

○ If some items do not have packaging instructions, the Define packaging instructions page opens. Proceed to Step 4 [page 37].

4. To create packaging instructions, click Define instructions, add your instructions, and click Next.The Confirm packing plan page opens.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 37

5. Review packing plan details and click Next to approve them.

The Print shipping labels page opens.

NoteTo make more changes, click Define instructions to return to the Define packaging instructions page.

6. Print the desired labels, then click Next.The Review Ship Notice page opens.

7. Verify the ship notice content, then click Submit.

CSC-8401: Ship notices by third-party online suppliers

Description

Products: SAP Ariba Supply Chain Collaboration

Audience: Buyers and suppliers

Enablement: Customer configured

With the ship notices by third-party online suppliers feature, third-party logistics providers can also use Ariba Network to create ship notices against copy purchase orders. Previously, this feature was only available to integrated suppliers.

Prerequisites

This feature requires that:

● The buyer has a trading relationship with the third-party supplier.● The buyer has a logistics relationship with the third-party supplier.● The buyer has enabled the rule Allow third-party suppliers to send multi-tier ship notices to this account.

Limitations

Settlement of charges to the buyer or original supplier for transportation-related costs cannot be made through the Ariba Network.

38 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

Changes to existing functionality

See CSC-8401: Changes to existing functionality [page 39].

Workflow

See Workflow for ship notices by third-party online suppliers [page 39].

CSC-8401: Changes to existing functionality

Buyer user interface changes

This feature adds transaction rule Allow third-party suppliers to send multi-tier ship notices to this account to the Administration Configuration Default Transaction Rules page, in the Order Confirmation and Ship Notice section.

Supplier user interface changes

● This feature adds a Multi-Tier Items to Ship tab to the Inbox Extended Collaboration page. The table on this page includes a Supplier column when viewed by a third-party supplier. This page displays only if a logistics relationship is established.

● Third-party online suppliers can create and view ship notices from the following pages:

○ Inbox Extended Collaboration Multi-Tier Orders

○ Inbox Extended Collaboration Multi-Tier Items to Ship○ The details page of a purchase order, scheduling agreement, or scheduling agreement release.

Workflow for ship notices by third-party online suppliers

The following describes the workflow for ship notices by third-party online suppliers:

1. An original equipment manufacturer buyer (OEM) issues a purchase order or scheduling agreement to a supplier.

2. The buyer sends a copy of the purchase order or scheduling agreement to the third-party logistics provider (LP).

3. The supplier sends an order confirmation to the OEM.4. The supplier advises the LP, outside of the system, that the product is available for transport to the OEM.5. The LP sends the OEM a ship notice on behalf of the supplier, and the supplier automatically receives a copy

ship notice.

Ariba Network Q2 2019 release guideSAP Ariba Supply Chain Collaboration features C O N F I D E N T I A L 39

6. If needed, the OEM sends a status update request to the LP, which automatically updates the ship notice status in the supplier system.

7. The OEM issues a goods receipt notification to the supplier, which automatically updates the LP system.8. One of the following actions triggers settlement:

○ The OEM buyer performs the evaluated receipt settlement process○ The supplier generates an invoice

40 C O N F I D E N T I A LAriba Network Q2 2019 release guide

SAP Ariba Supply Chain Collaboration features

General Ariba Network features

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

Description

Products: Ariba Network

SAP Ariba Buying (integrated with SAP ERP)

SAP Ariba Buying and Invoicing (integrated with SAP ERP)

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

Buyers can now specify U (Unknown) as the value for the account assignment category for service line items on purchase orders. With this feature, Ariba Network introduces a new transaction rule named Require suppliers to provide account assignment information, which buyers can enable to ensure that suppliers submit service sheets only after they replace the value U (Unknown) with the appropriate account assignment category values. Suppliers can punch in to SAP Ariba Buying and Invoicing to retrieve the appropriate value for the account assignment category and then submit their service sheets.

For more information about this feature, see the SAP Ariba Applications Q2 2019 release guide.

CSC-9320: Enhanced storage location functionality for ship notices

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Customer configured

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 41

Based on a new buyer-side rule, Ariba Network now validates whether all items in a shipment use a single storage location.

The feature provides the following storage location functionality for ship notices:

● Adds a new ship notice rule that allows buyers to require suppliers to use only one storage location on each ship notice.

● Adds the Storage location field to the Details view for orders and releases.● Adds a sortable Storage location column on the Items to Ship table.● Allows filtering and searching by storage location on the Items to Ship tab.

Sample storage location cXML in an order

Buyer location and storage location are optional ShipTo values for items in an order. They can be specified at the item level and the schedule line level.

The storage location identifier for an item is specified in the ShipTo/IdReference element. The IdReference.domain attribute for a storage location identifier is "storageLocationID".

NoteAt the item level, if storage location is specified the buyer location must also be specified. For schedule lines, the buyer location can be omitted if it is specified at the item level.

<ShipTo> <Address addressID="" isoCountryCode="US"> <Name xml:lang="EN">BL 001</Name> <PostalAddress> <Street>123 Main Street</Street> <City>Palo Alto</City> <State>CA</State> <PostalCode>94304</PostalCode> <Country isoCountryCode="US"/> </PostalAddress> </Address> <IdReference domain="buyerLocationID" identifier="BL001"/> <IdReference domain="storageLocationID" identifier="SL001"/> </ShipTo>

Enabling this feature

This feature is enabled for all buyers and suppliers. For information about how to configure this feature, see Buyer administrator interface changes [page 43].

Prerequisites

To use this feature, buyers must include the buyer location and storage location for items in orders. Orders that don’t include buyer location and storage location are unaffected by this feature.

42 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

Limitations

● The new ship notice rule doesn’t apply to ship notices received through cXML.● When you create a ship notice from an order, the storage location is not automatically flipped from the order to

the ship notice. This is noted for your information, but it is not a problem. You don’t need to manually add the storage location to ship notices.

Buyer administrator interface changes

On the Administration Configuration Default transaction rules page, the following rule was added to the Order collaboration and ship notice rules section:

● Require all items in a ship notice to have the same storage location—If this rule is checked, all ship notice items must have the same storage location. Otherwise, ship notice items can have different storage locations. This rule applies only to orders that specify buyer location and storage location.Default setting: No

NoteYou can also apply this default transaction rule to supplier groups.

On purchase orders, the ShipTo element can now be specified for schedule lines. A new validation was added to ensure that all schedule lines have the same buyer location as the line item level. If a schedule line doesn’t have a buyer location, it defaults to the buyer location of the line item level. This validation is applied without buyer configuration.

Supplier user interface changes

On the Purchase order and Scheduling agreement release pages, the Storage location field was added to the Details view.

On the Items to Ship tab, the following changes were made:

● A Storage location column was added to the Items to Ship table.● You can now search for Storage location values in the lookup for the Customer location filter. Click Lookup to

display the Customer Location window.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 43

Figure 1: Customer Location window

NP-13576: Creating a correction service entry sheet

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Customer Configured

Previously, after a service entry sheet has been approved or invoiced, suppliers were unable to make any corrections to the service entry sheets. Buyers could reject a service entry sheet before it was approved or invoiced.

Now, buyers can configure a new service entry sheet rule to allow suppliers create a correction service entry sheet for those service entry sheets which are invoiced. While creating a correction entry sheet, suppliers cannot:

● Copy a line item.● Edit details of the Price, Part# / Description, and Subtotal fields.● Delete line items.

Suppliers must enter a negative quantity value in the correction entry sheet.

44 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

Note● You cannot copy or create an invoice for an approved correction service entry sheet.● You cannot enter a negative quantity per line item which exceeds the total quantity value of the original

service entry sheet.

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.

Supplier user interface changes

Once a service entry sheet (SES) is approved and invoiced, on the SES details page, Ariba Network displays a new Create Correction Service Sheet button.

Buyer administrator interface changes

Default Transaction Rules

In the Service Sheet Rules section, the following rule is added:

● Allow suppliers to create correction service sheets

NoteYou can also apply this default transaction rule to supplier groups.

Supplier task

● See How to create a correction service entry sheet [page 47]

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 45

Buyer administrator task

● See How to allow suppliers to submit a correction service entry sheet [page 46]

Buyer administrator task

How to allow suppliers to submit a correction service entry sheet

Context

Buyers can now allow suppliers to submit a correction service entry sheet.

Procedure

1. Click Administration Configuration2. Click Default Transaction Rules.

The Default Transaction Rules page appears.3. In the Service Sheet Rules section, check the rule Allow suppliers to create correction service sheets.4. Click Save.

Supplier task

46 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

How to create a correction service entry sheet

Context

Suppliers can create correction service entry sheets only for those service entry sheets which are either approved or invoiced.

Procedure

1. On the Dashboard, click the Outbox tab.2. Click the Service Sheets tab.3. Click the service entry sheet for which you want to create a correction service entry sheet.

Ariba Network displays the details of the service entry sheet.4. Click the Create Correction Service Sheet button.5. If required, modify the Start Date and End Date fields.6. Modify the Quantity or Unit field as required.

You can only enter a negative value in this field.7. Click Next.8. Click Submit.

NP-13966: Provision to close, reopen, and delete messaging conversations

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 47

Enhancements for supplier and buyer users

Some customers may want to close conversations which have outlived their purpose. Previously, buyer and supplier users could not close such conversations.

Now, with this enhancement, buyer and supplier users can close a conversation if it is not needed anymore. Only the initiator of a conversation or the initiator's administrator can close a conversation to avoid accidentally replying to a message. If required, the initiator of a conversation or the initiator's administrator can reopen a closedconversation.

Every conversation is associated with a unique alphanumeric string denoting the conversation ID. The administrator can refer to the conversation ID while interacting with the SAP Ariba Customer Support Representative.

NoteOnly the administrator for an account can view the conversation ID.

Any user's Ariba Network administrator can delete their user initiated conversations.

ExampleIf a supplier user has initiated a conversation, then only that supplier user's Ariba Network administrator can delete the conversation.

After a conversation is deleted, it is later purged from the system according to the system's schedule.

Buyer and supplier user interface changes

When a user opens a conversation initiated by them, in the top right corner, the Messaging feature now displays the vertical ellipsis icon (more actions) which, when clicked, displays the following dropdown options:

● Close Conversation● Delete Conversation● View Conversation Id

Buyer and seller tasks

● How to view or copy a conversation ID [page 49]● How to close or delete a conversation [page 49]● How to reopen a conversation [page 50]

Buyer and seller tasks

48 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

How to view or copy a conversation ID

Context

Every conversation is associated with a unique conversation ID. The initiator of the conversation can view and copy the conversation ID for the conversation.

Procedure

1. Open a conversation you initiated.2. Click the vertical ellipsis icon (more actions) and then choose View Conversation Id from the dropdown.

The Messaging feature displays the Conversation Id window with the details of the conversation ID.3. To copy the conversation ID, click Copy.

You can paste the conversation ID in any document.

How to close or delete a conversation

Context

Initiators of a conversation can either close or delete the conversation. You can also delete a closed conversation.

Procedure

1. Open a conversation you initiated.2. To close a conversation, click the vertical ellipsis icon (more actions) and then click Close Conversation from

the drop down.

Ariba Network displays a Confirmation window.3. Click Yes.

The Messaging feature closes the conversation. A locked icon is used to denote a closed conversation. After a conversation is closed, no participant of the conversation can respond in the conversation.

4. To delete a conversation, click the vertical ellipsis icon (more actions) and then click Delete Conversation.

The Messaging feature deletes the conversation.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 49

How to reopen a conversation

Context

Once a conversation is closed, the initiator can reopen the conversation.

Procedure

1. Open a conversation you closed.2. Click Reopen.

Ariba Network displays a Confirmation window.3. Click Yes.

The Messaging feature reopens the conversation so that any participant of the conversation can now respond.

NP-15794: Italy outbound enhancementsProducts: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

This feature is applicable to suppliers in Italy, and to buyers who trasact with suppliers in Italy.

Background

From July 01 2018, suppliers in certain industries in Italy must report all electronic invoices through the governmental electronic invoicing platform Sistema di Interscambio (SDI). This is a mandatory regulation initiated by the SDI (Italian Revenue Agency) in Italy, and is initially (from July 01, 2018) applicable only to certain industries - for example, the oil and natural gas industry. This mandate is applicable to all the industries in Italy from January 01, 2019.

Scope of current feature

The scope of the current feature is limited to these enhancements:

50 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

● CIG and CUP Codes: To prevent corrupt practices in procurement, organizations in Italy must trace payments related to public procurement using the following codes:

● Value Added Tax (VAT)● Withholding Tax● The Payment Note field on the invoice is now Payment Type.● The invoice number (ID) must not exceed 20 alpha-numeric characters.● The Street field in the 'Sold From' and 'Sold To' address element is mandatory.

Prerequisites

● Suppliers must have their legal profiles configured in Ariba Network. For more information on confiuring legal profiles, see the Ariba Network guide to invoicing features and functions.

● Buyers must upload supplier master data to Ariba Network in order to allow matching from VAT ID/Tax ID to the buyer’s vendor IDs.

● Buyers and suppliers must register their organizations at the SDI portal. The VAT ID/Tax ID are the relevant identifications for the SDI portal.

● Buying organizations must configure their SDI accounts to get their invoices routed to TrustWeaver and Ariba Network.

NP-15794 Changes to existing functionality

The following fields are introduced as a result of implementing enhancements:

Ariba Network online invoice fields

The following new line level field is introduced in the online invoice page on Ariba Network. The field is a pull down menu item with three options. This field also appears on the invoice summary and invoice PDF.

NoteThis field is made visible only when the tax category selected is VAT.

● VAT Due Time Code○ VAT due immediately: The total tax is added to the subtotal to calculate the amount due. VAT becomes

due when the invoice is issued.○ VAT payment deferred: The total tax is added to the subtotal to calculate the amount due. VAT becomes

due when the invoice is paid.○ Split payment: The total tax subject to split payment is not added to the amount due. The buyer must pay

the VAT amount that is subject to split payment directly to the tax authorities in Italy, and not to the supplier. In other words, the buyer has to 'split' the total amount due by paying the suppliers for their goods/services, and transferring the VAT due directly to the Italian tax authorities.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 51

NoteWhen the VAT Due Time Code is Split Payment, the reason for tax exemption cannot be '(N6) Reverse Charge'. This is applicable to invoices created online in Ariba Network, and also to invoices created in external systems, such as suppliers' ERPs and other in-house systems.

The following new line level field is introduced in the online invoice page on Ariba Network. The field is a pull down menu item with two options. This field also appears on the invoice summary and invoice PDF.

● Withholding Tax Type○ (RT01)Supplier administrator○ (RT02)Legal personnel

NoteIf multiple line items in an invoice contain withholding tax, the withholding tax type and tax rate must be identical in all those line iems.

Multiple tax categories cannot be added in the same line item of an invoice.

Workflow for Italy outbound enhancements

This section describes the workflow starting from the creation of the invoice in Ariba Network to the time when the buyer systems receive the invoice.

Figure 2: Workflow for tax invoicing in Italy

52 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

1. The supplier flips a purchase order to create an invoice, or creates a non-purchase order invoice in Ariba Network.

2. Ariba Network performs validation checks for mandatory fields in the invoice.3. Ariba Network invokes the TrustWeaver conversion service.4. TrustWeaver converts the cXML invoice to a FatturaPA XML document.5. Ariba Network invokes the TrustWeaver signature service.6. TrustWeaver digitally signs the FatturaPA XML document, and sends a status update to Ariba Network.7. TrustWeaver sends the signed FatturaPA XML to SDI.8. SDI receives the supplier invoice and performs its own validation of the mandatory invoice fields.9. TrustWeaver receives a status update from SDI, and in turn provides the success or rejecton status to Ariba

Network.10. Ariba Network sends the cXML with the signed FatturaPA XML and the delivery receipt as attachments to the

buyer’s system.

NP-15794 cXML changesThe table below shows the new extrinsics added to the cXML.

Table 1: Extrinsics Introduced

Extrinsic Description Sample Snippet

withholdingTaxType The type of withholding tax. This can take two possible values:

● RT01● RT02

<Extrinsic name="withholdingTaxType">RT01</Extrinsic>

taxPointDateCode The code for VAT due time. This can take three possible values:

● I - VAT due immediately● D - VAT payment deferred● S - Split payment

For more information, see NP-15794 Changes to existing functionality [page 51]

<Extrinsic name="taxPointDateCode">I</Extrinsic>

Appendix - sample invoice cXMLSample cXML invoice

Sample Code

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.036/InvoiceDetail.dtd"><cXML payloadID="[email protected]" signatureVersion="1.0" timestamp="2019-02-22T10:24:29+05:30"version="1.2.036">

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 53

<Header> <From> <Credential domain="NetworkID"> <Identity>AN02000000121</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN02000000120</Identity> </Credential> </To> <Sender> <Credential domain="NetworkID"> <Identity>AN01000000001</Identity> </Credential> <UserAgent>Supplier</UserAgent> </Sender> </Header> <Request Id="cXMLData" deploymentMode="production"> <InvoiceDetailRequest> <InvoiceDetailRequestHeader invoiceDate="2019-02-22T10:24:24+05:30" invoiceID="INV_TEST"invoiceOrigin="supplier" operation="new" purpose="standard"> <InvoiceDetailHeaderIndicator /> <InvoiceDetailLineIndicator isTaxInLine="yes" /> <InvoicePartner> <Contact role="remitTo"> <Name xml:lang="en">[email protected]</Name> <PostalAddress> <Street>jUnitDummy</Street> <Street /> <Street /> <Street /> <City>ROME</City> <State>MI</State> <PostalCode>71630</PostalCode> <Country isoCountryCode="IT">Italy</Country> </PostalAddress> </Contact> </InvoicePartner> <InvoicePartner> <Contact role="billTo"> <Name xml:lang="en">DM</Name> <PostalAddress> <Street>1</Street> <Street>1</Street> <Street /> <Street /> <City>1</City> <State isoStateCode="IT-BA">Avellino</State> <PostalCode>560037</PostalCode> <Country isoCountryCode="IT">Italy</Country> </PostalAddress> </Contact> </InvoicePartner> <InvoicePartner> <Contact role="from"> <Name xml:lang="en">ITADD</Name> <PostalAddress> <Street>jUnitDummy</Street> <Street /> <Street /> <Street /> <City>ROME</City> <State isoStateCode="AP">Ascoli Piceno</State> <PostalCode>71630</PostalCode> <Country isoCountryCode="IT">Italy</Country> </PostalAddress> </Contact>

54 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

</InvoicePartner> <InvoicePartner> <Contact role="billFrom"> <Name xml:lang="en">[email protected]</Name> <PostalAddress> <Street>jUnitDummy</Street> <Street /> <Street /> <Street /> <City>a</City> <State>CA</State> <PostalCode>99999</PostalCode> <Country isoCountryCode="US">United States</Country> </PostalAddress> </Contact> </InvoicePartner> <InvoicePartner> <Contact role="soldTo"> <Name xml:lang="en">DM</Name> <PostalAddress> <Street>2</Street> <Street>2</Street> <Street /> <Street /> <City>1</City> <State isoStateCode="AR">Arezzo</State> <PostalCode>56004</PostalCode> <Country isoCountryCode="IT">Italy</Country> </PostalAddress> </Contact> </InvoicePartner> <InvoiceDetailShipping> <Contact role="shipFrom"> <Name xml:lang="en">[email protected]</Name> <PostalAddress> <Street>jUnitDummy</Street> <Street /> <Street /> <Street /> <City>ROME</City> <State>MI</State> <PostalCode>71630</PostalCode> <Country isoCountryCode="IT">Italy</Country> </PostalAddress> </Contact> <Contact role="shipTo"> <Name xml:lang="en">[email protected]</Name> <PostalAddress> <Street>jUnitDummy</Street> <Street /> <Street /> <Street /> <City>Sunnyvale</City> <State>CA</State> <PostalCode>94089</PostalCode> <Country isoCountryCode="US">United States</Country> </PostalAddress> </Contact> </InvoiceDetailShipping> <Comments>[Ariba added comment: Created in the name and on behalf of the supplier]</Comments> <Extrinsic name="TaxInvoice">This is a tax invoice</Extrinsic> <Extrinsic name="buyerVatID">IT09665344523</Extrinsic> <Extrinsic name="supplierVatID">IT93778455678</Extrinsic> <Extrinsic name="supplierCommercialRegisterCourt">AG</Extrinsic> <Extrinsic name="invoiceSourceDocument">ExternalPurchaseOrder</Extrinsic> <Extrinsic name="invoiceSubmissionMethod">Online</Extrinsic>

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 55

<Extrinsic name="paymentMethod">MP05</Extrinsic> <Extrinsic name="paymentNote">TP02</Extrinsic> <Extrinsic name="punchinContractInvoice">no</Extrinsic> <Extrinsic name="supplierCommercialIdentifier">1234</Extrinsic> <Extrinsic name="legalCapital">1234.00</Extrinsic> <Extrinsic name="shareHolderType">SU</Extrinsic> <Extrinsic name="supplierLiquidationState">LN</Extrinsic> <Extrinsic name="supplierTaxRegime">RF01</Extrinsic> <Extrinsic name="projectCode">1234</Extrinsic> <Extrinsic name="tenderCode">1234</Extrinsic> <Extrinsic name="supplierCommercialCredentials">3222423333</Extrinsic> </InvoiceDetailRequestHeader> <InvoiceDetailOrder> <InvoiceDetailOrderInfo> <OrderIDInfo orderID="INVed" /> </InvoiceDetailOrderInfo> <InvoiceDetailItem invoiceLineNumber="1" quantity="1"> <UnitOfMeasure>1</UnitOfMeasure> <UnitPrice> <Money currency="USD">100.00</Money> </UnitPrice> <InvoiceDetailItemReference lineNumber="1"> <ItemID> <SupplierPartID>100</SupplierPartID> <BuyerPartID>1000</BuyerPartID> </ItemID> <Description xml:lang="en">100</Description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="USD">100.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">2.00</Money> <Description xml:lang="en" /> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-21T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N2"> <ExemptReason xml:lang="en">(N2) Not Subject</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">I</Extrinsic> </TaxDetail> </Tax> <GrossAmount> <Money currency="USD">102.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">102.00</Money> </NetAmount> <Extrinsic name="punchinItemFromCatalog">no</Extrinsic> </InvoiceDetailItem> <InvoiceDetailItem invoiceLineNumber="2" quantity="1"> <UnitOfMeasure>1</UnitOfMeasure> <UnitPrice> <Money currency="USD">100.00</Money> </UnitPrice> <InvoiceDetailItemReference lineNumber="2"> <ItemID> <SupplierPartID>200</SupplierPartID> <BuyerPartID>2000</BuyerPartID>

56 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

</ItemID> <Description xml:lang="en">200</Description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="USD">100.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">2.00</Money> <Description xml:lang="en" /> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-22T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N1"> <ExemptReason xml:lang="en">(N1) Excluding ex Art.15</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">D</Extrinsic> </TaxDetail> </Tax> <GrossAmount> <Money currency="USD">102.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">102.00</Money> </NetAmount> <Extrinsic name="punchinItemFromCatalog">no</Extrinsic> </InvoiceDetailItem> <InvoiceDetailItem invoiceLineNumber="3" quantity="1"> <UnitOfMeasure>1</UnitOfMeasure> <UnitPrice> <Money currency="USD">100.00</Money> </UnitPrice> <InvoiceDetailItemReference lineNumber="3"> <ItemID> <SupplierPartID>300</SupplierPartID> <BuyerPartID>3000</BuyerPartID> </ItemID> <Description xml:lang="en">300</Description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="USD">100.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">2.00</Money> <Description xml:lang="en" /> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-22T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N1"> <ExemptReason xml:lang="en">(N1) Excluding ex Art.15</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">S</Extrinsic> </TaxDetail> </Tax> <GrossAmount>

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 57

<Money currency="USD">102.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">102.00</Money> </NetAmount> <Extrinsic name="punchinItemFromCatalog">no</Extrinsic> </InvoiceDetailItem> <InvoiceDetailItem invoiceLineNumber="4" quantity="1"> <UnitOfMeasure>1</UnitOfMeasure> <UnitPrice> <Money currency="USD">100.00</Money> </UnitPrice> <InvoiceDetailItemReference lineNumber="4"> <ItemID> <SupplierPartID>400</SupplierPartID> <BuyerPartID>4000</BuyerPartID> </ItemID> <Description xml:lang="en">400</Description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="USD">100.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">-2.00</Money> <Description xml:lang="en" /> <TaxDetail category="withholdingTax" percentageRate="-2"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">-2.00</Money> </TaxAmount> <Description xml:lang="en">RT02</Description> <Extrinsic name="withholdingTaxType">RT01</Extrinsic> </TaxDetail> <Extrinsic name="withholdingTaxTotal"> <Money currency="USD">-2.00</Money> </Extrinsic> <Extrinsic name="taxTotal"> <Money currency="USD">0</Money> </Extrinsic> </Tax> <GrossAmount> <Money currency="USD">98.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">98.00</Money> </NetAmount> <Extrinsic name="punchinItemFromCatalog">no</Extrinsic> </InvoiceDetailItem> <InvoiceDetailItem invoiceLineNumber="5" quantity="1"> <UnitOfMeasure>1</UnitOfMeasure> <UnitPrice> <Money currency="USD">100.00</Money> </UnitPrice> <InvoiceDetailItemReference lineNumber="5"> <ItemID> <SupplierPartID>500</SupplierPartID> <BuyerPartID>5000</BuyerPartID> </ItemID> <Description xml:lang="en">500</Description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="USD">100.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">-2.00</Money> <Description xml:lang="en" />

58 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

<TaxDetail category="withholdingTax" percentageRate="-2"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">-2.00</Money> </TaxAmount> <Description xml:lang="en">RT02</Description> <Extrinsic name="withholdingTaxType">RT01</Extrinsic> </TaxDetail> <Extrinsic name="withholdingTaxTotal"> <Money currency="USD">-2.00</Money> </Extrinsic> <Extrinsic name="taxTotal"> <Money currency="USD">0</Money> </Extrinsic> </Tax> <GrossAmount> <Money currency="USD">98.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">98.00</Money> </NetAmount> <Extrinsic name="punchinItemFromCatalog">no</Extrinsic> </InvoiceDetailItem> </InvoiceDetailOrder> <InvoiceDetailSummary> <SubtotalAmount> <Money currency="USD">500.00</Money> </SubtotalAmount> <Tax> <Money currency="USD">2.00</Money> <Description xml:lang="en" /> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-21T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N2"> <ExemptReason xml:lang="en">(N2) Not Subject</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">I</Extrinsic> </TaxDetail> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-22T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N1"> <ExemptReason xml:lang="en">(N1) Excluding ex Art.15</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">D</Extrinsic> </TaxDetail> <TaxDetail category="vat" percentageRate="2" taxPointDate="2019-02-22T00:00:00+05:30"> <TaxableAmount> <Money currency="USD">100.00</Money> </TaxableAmount>

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 59

<TaxAmount> <Money currency="USD">2.00</Money> </TaxAmount> <Description xml:lang="en" /> <TaxExemption exemptCode="N1"> <ExemptReason xml:lang="en">(N1) Excluding ex Art.15</ExemptReason> </TaxExemption> <Extrinsic name="taxPointDateCode">S</Extrinsic> </TaxDetail> <TaxDetail category="withholdingTax" percentageRate="-2"> <TaxableAmount> <Money currency="USD">200.00</Money> </TaxableAmount> <TaxAmount> <Money currency="USD">-4.00</Money> </TaxAmount> <Description xml:lang="en">RT02</Description> <Extrinsic name="withholdingTaxType">RT01</Extrinsic> </TaxDetail> <Extrinsic name="withholdingTaxTotal"> <Money currency="USD">-4.00</Money> </Extrinsic> <Extrinsic name="taxTotal"> <Money currency="USD">6.00</Money> </Extrinsic> </Tax> <GrossAmount> <Money currency="USD">502.00</Money> </GrossAmount> <NetAmount> <Money currency="USD">502.00</Money> </NetAmount> <DueAmount> <Money currency="USD">500.00</Money> </DueAmount> </InvoiceDetailSummary> </InvoiceDetailRequest> </Request></cXML>

NP-15448: PDF based on official FatturaPA style sheetProducts: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

This Ariba Network feature is applicable to suppliers in Italy, and to buyers who transact with Italian suppliers.

60 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

Background

From July 01 2018, suppliers in certain industries in Italy must report all electronic invoices through the governmental electronic invoicing platform Sistema di Interscambio (SDI). This is a mandatory regulation initiated by the SDI (Italian Revenue Agency) in Italy, and is initially (from July 01, 2018) applicable only to certain industries - for example, the oil and natural gas industry. This mandate will become applicable to all the industries in Italy from January 01, 2019.

NoteThe scope of this feature is limited to SAP Ariba providing buyers the option to receive invoice PDFs in human readable format.

The SDI is an online system operated and maintained by the Italian tax authorities. Suppliers in Italy must send their domestic electronic invoices online to the SDI system in order to get issued.

Furthermore, suppliers must create electronic invoices in the FatturaPA format only. The FatturaPA is an electronic invoice in XML format, and is the only type of invoice that is valid and accepted by the Italian tax authorities. Suppliers must get their invoices electronically signed, and submit the signed invoices to the SDI portal.

Only invoices sent to the SDI portal and approved by the SDI are considered valid invoices. Invoices not reported to the SDI system are not accepted. In addition, penalties are levied on defaulting suppliers according to the tax laws prevalent in Italy.

Prerequisites

● Buyers must upload supplier master data to the Ariba Network in order to allow matching from VAT ID/Tax ID to the buyer’s vendor IDs.

● The buyer rule to allow PDF file extensions must be enabled.● Non-Ariba Network suppliers must get their invoices digitally signed by approved service providers, create their

electronic invoices outside the Ariba Network, and send them to the SDI portal for issuance.

Workflow for PDF based on FatturaPA style sheet

Invoices in Italy go through the following workflow to transmit a human readable PDF to a buyer's ERP system or SAP Ariba procurement solution. This workflow is applicable to the following cases:

● Where suppliers create invoices outside Ariba Network, submit the invoice to the SDI portal directly, and buyers receive invoices from Ariba Network (buyer inbound transaction).

● Where suppliers create invoices in Ariba Network, and buyers receive invoices from Ariba Network (supplier outbound transaction)

1. Ariba Network recognizes the FatturaPA XML and invokes the TrustWeaver service for FatturaPA to PDF transformation.

2. If the TrustWeaver service is unavailable or if errors occur, the request is re-tried.3. If the request still fails after the maximum number of attempts is exhausted, the PDF generation step is

skipped.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 61

4. If the service is invoked successfully, TrustWeaver performs the transformation from FatturaPA XML to PDF and sends the PDF invoice toAriba Network.

5. If Ariba Network receives the transformed PDF document without any failure, Ariba Network sends the cXML, the original FatturaPA XML, and its associated PDF (attached to the cXML invoice) to the buyer’s ERP system or SAP Ariba procurement solution..

NP-15461: Service entry sheet enhancements

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Customer Configured

Functional changes for suppliers

With this release, the following enhancements are available:

● Previously, suppliers had to manually enter the service start and end dates for every service sheet line item.Now, Ariba Network provides an option for suppliers to copy the service start and end date information specified in the service header to automatically populate the service start and end dates of service sheet line items (including ad hoc service sheet line items).

● Previously, Ariba Network displayed the allowed and accumulated quantity information in the tooltip provided for the Include field.Now, Ariba Network displays the allowed and accumulated quantity information in the tooltip provided for the Qty/Unit field.

● When an unplanned ad hoc line item is added in a service entry sheet, suppliers can specify any unit of measure (UOM) specified in the UOM file uploaded by the buyer. If a buyer did not upload a UOM master file, then suppliers must mandatorily specify the unit of measure, and it is mandatory for the suppliers to specify the UOM.

● On the Create Invoice page for suppliers, Ariba Network displays the service description field only when service and mixed purchase orders are flipped to create invoices.

● For planned line items on a service entry sheet, suppliers cannot edit item description field.● For ad hoc line items on a service entry sheet, buyers can use a new default transaction rule to require

suppliers to specify part descriptions.● For ad hoc line items on a service entry sheet, Ariba Network allows buyers to prevent suppliers from

specifying part numbers which exceed 18 characters. This also applies to integrated suppliers.● For ad hoc line items, buyers can use a new default transaction rule to prevent hosted suppliers and integrated

suppliers from specifying zero value as the quantity in the line item details of service entry sheets.

62 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

● On the Service Sheets page, Ariba Network now displays an additional pagination link at the top of the page.● On the Service Sheets page, Ariba Network now displays an attachment icon beside the service sheet number

if the service sheet contains one or more attachments.● If the supplier specifies the email address in the approver details section within the Additional Details section

on the service entry sheet page, Ariba Network sends email notifications to the approver whenever modifications are made to the service entry sheet or if the status of the service entry sheet changes.

Functional changes for buyers

Previously, buyers could not prevent suppliers from creating service sheet line items where the quantity is specified as zero.

Now, buyer administrators can enable a new default transaction rule which prevents suppliers from creating service entry sheets where the line item quantity is zero. When this rule is enabled, suppliers can enter either a positive or a negative value in the quantity field.

Buyers can use new default transaction rules to:

● Prevent suppliers from specifying part numbers which exceed 18 characters for ad hoc line items.● Require suppliers to provide part descriptions for ad hoc line items.● Require suppliers to provide line item quantities for ad hoc line items.

Supplier user interface changes

On the service sheet creation page, in the Service Sheet Header section, Ariba Network now displays the Copy the service start and end dates to the service line items check box.

Buyer administrator interface changes

See Buyer administrator interface changes [page 64]

Buyer administrator tasks

● How to prevent suppliers from creating service entry sheets with line items having zero quantities [page 64]● How to prevent suppliers from providing part numbers exceeding 18 characters in ad hoc line items [page 65]● How to ensure that suppliers provide part descriptions in ad hoc line items [page 65]● How to ensure that suppliers provide line item quanity in ad hoc line item [page 66]

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 63

Buyer administrator interface changes

Buyer administrator interface changes

On the Default Transaction Rules page, the following rule is added in the Service sheet rules section:

● Require suppliers to create service entry sheets where the line item quantity is not zero● Do not allow part number to exceed 18 characters for ad hoc line items● Require suppliers to provide description for ad hoc line items● Require suppliers to provide line item quantity for ad hoc line items

Buyer administrator tasks

How to prevent suppliers from creating service entry sheets with line items having zero quantities

Context

Buyer administrators can use this default transaction rule to restrict suppliers from creating service entry sheets where the quantity for line items is specified as zero.

Procedure

1. Click Administration Configuration Default Transaction Rules .

The Default Transaction Rules page appears.2. In the Service Sheet section, check the rule Require suppliers to create service entry sheets where the line

item quantity is not zero.3. Click Save.

64 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

How to prevent suppliers from providing part numbers exceeding 18 characters in ad hoc line items

Context

You can prevent suppliers from providing ad hoc line item part numbers which exceed 18 characters.

Procedure

1. Click Administration Configuration Default Transaction Rules .

The Default Transaction Rules page appears.2. In the Service Sheet section, check the rule Do not allow part number to exceed 18 characters for ad hoc

line items.3. Click Save.

How to ensure that suppliers provide part descriptions in ad hoc line items

Context

Buyers can ensure that suppliers provide part descriptions in ad hoc line items.

Procedure

1. Click Administration Configuration Default Transaction Rules .

The Default Transaction Rules page appears.2. In the Service Sheet section, check the rule Require suppliers to provide description for ad hoc line items.3. Click Save.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 65

How to ensure that suppliers provide line item quanity in ad hoc line item

Context

Buyers can ensure that suppliers provide line item quanities in ad hoc line items.

Procedure

1. Click Administration Configuration Default Transaction Rules .

The Default Transaction Rules page appears.2. In the Service Sheet section, check the rule Require suppliers to provide line item quantity for ad hoc line

items.3. Click Save.

NP-15612: Displaying rejection reasons in invoice, failed invoice, and SES reports

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

Reconciliation of invoices and service entry sheets (SES) is an important process especially when such documents flow through multiple systems and ERP software which may perform validation tests. Most often, reconciliation is a manual process where users make corrections to the those documents which are not compliant with the business rules. In some business scenarios, invoice and SES documents are rejected either by the users or by the system if the documents fail the validations tests. Users perform the reconciliation by understanding both the rejection reasons generated by the system and the rejection comments provided by the users.

Previously, invoice reports generated by Ariba Network displayed the Status Comments column which captured the user-provided comments. To view user-provided comments for SES reports and failed invoices, users had to view the details of each failed invoice or SES.

66 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

Now, Ariba Network captures the user-provided comments in the Status Comments column for failed invoice and SES reports.

The invoice, failed invoice, and SES reports now display a new Rejection Reasons column which show the rejection reasons generated by the ERP or procurement systems. Rejection reasons in the reports help users understand if there are any patterns in rejections. This data can help users take preventive measures to avoid unnecessary reconciliation tasks, and to make it easy to perform reconciliation tasks.

NP-15221: Ariba Network buyer capability to opt out of or disable messaging

Description

Products: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

Enhancement for buyer administrators

By default, the Messaging feature is enabled for all buyers. If buyers do not want to use the Messaging functionality to receive messages from suppliers, buyer administrators can disable the Messaging feature. When a buyer disables the messaging functionality, suppliers can no longer send messages to the buyer. However, suppliers can send messages to other buyers who have not disabled the messaging functionality.

Buyer administrator interface changes

● The Messaging Configuration displays the Opt Out tab where the buyer administrator can disable the Messaging feature.

Buyer administrator task

● How to disable the messaging functionality [page 68]

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 67

Buyer administrator tasks

How to disable the messaging functionality

Context

By default, the messaging functionality is enabled.

Procedure

1. On the upper right corner of the Ariba Network home page, click Manage Profile.

The Configuration page opens.2. Click on the Messaging Configuration link.

The Messaging Configuration page opens.3. Click the Opt Out tab.4. Uncheck the Enable Messaging checkbox.5. Click Update.6. Click Done.

NP-15657: Technical annulment of NAV invoices in HungaryProducts: Ariba Network

Audience: Suppliers

Enablement: Automatically on

This Ariba Network feature is applicable to all supplier users in Hungary.

Scope of current feature

The scope of this feature is limited to providing Hungarian suppliers the ability to annul an invoice from the Ariba Network interface. Suppliers can annul invoices that were incorrectly reported to NAV (and were subsequently

68 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

rejected or failed in Ariba Network) by using an option in Ariba Network. Annulled invoices cannot be edited, or re-submitted to NAV.

Prerequisites

● Technical annulment can be performed only on invoices that were previously reported to NAV successfully, and were later rejected or failed in Ariba Network

● Supplier organizations must register at the NAV portal and generate their Technical User ID, Password, Signature Key, and Replacement Key and provide these details in their Ariba Network user accounts.

● If supplier organizations do not have their VAT ID, they must enter the tax ID of their tax representative in the regulatory profile section.

Limitations

When suppliers use Ariba Network for invoicing in Hungary, they must ensure that the same invoice content is not reported from another invoicing system (for example, supplier ERP system). Otherwise, there is a risk of duplication of invoice data at NAV.

NP-15657 Changes to existing functionality

Supplier user interface changes

This feature adds the following changes to the supplier interface in Ariba Network:

● Annul: To annul an invoice, suppliers can click the Annul button. This option is placed on the Detail tab of an invoice.

● When suppliers click the Annul button, Ariba Network opens a new page that has the following mandatory fields:○ Annulment Code: This is a drop-down menu with two options:

○ Wrong Data○ Wrong Invoice Number

○ Annulment Reason: Suppliers must enter a reason for technical annulment.

NP-15657 Supplier user tasks

This section describes one supplier user task - How to annul an invoice.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 69

How to annul an invoice

Context

As a supplier, you can annul only those invoices that were previously reported to NAV successfully, but were later rejected or failed on Ariba Network. When you place a request for technical annulment, NAV will be informed that the invoice contains incorrect information. NAV will subsequently annul the invoice.

Note● You can annul only those invoices that are in 'Rejected' or 'Failed' status.● After an invoice is annulled by NAV, you cannot edit or resubmit the invoice.

To annul an invoice, follow these steps:

Procedure

1. In your Ariba Network supplier account, go to your Outbox.2. Open the invoice that you want to annul, and check the status of the invoice in the invoice header (Detail tab).3. Check if the status of the invoice shows 'Rejected' or 'Failed'.4. Click the Annul button.5. In the page that opens, select the Annulment Code from the drop-down options, and enter the Annulment

Reason.6. Click OK.7. After a few minutes, open the History tab to track the annulment request that was sent to NAV.

Results

The History tab displays comments in the following sequence:

1. "Technical annulment was initiated for the invoice."2. "The invoice was accepted for technical annulment at NAV. The invoice will be annulled after NAV approval.

Contact NAV for more information."

70 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

NS-5668: New Purchase Orders and Invoices tiles for standard and enterprise account usersDescription

Products Ariba Network

Audience Suppliers

Enablement Automatically on

Standard account users can now access two new tiles on the Ariba Network Home dashboard. These tiles show all of their purchase orders and invoices irrespective of the document status.

NoteThe existing Home page tile limits regarding the maximum number of documents will also apply to the new tiles.

Supplier user interface changes

See NS-5668: User interface changes [page 71]

In this section:

NS-5668: User interface changes [page 71]

NS-5668: User interface changes

Two new tiles are now available when you click on the More button on the Ariba Network Home dashboard, - Purchase Orders and Invoices. Clicking on a tile takes you to an unfiltered list of documents. All documents are displayed, regardless of their status.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 71

NS-5695: Home page tile document limit increased from last 50 to last 200

Description

Products: Ariba Network

Audience: Suppliers

Enablement Automatically on

This feature increases the number of documents that can be shown on Ariba Network Home page tiles for suppliers. Tiles can now show up to the last 200 documents. Previously, only up to the last 50 documents could be shown on a Home page tile.

This provides suppliers with greater historical visibility on documents.

Supplier user interface changes

See NS-5695: User interface changes [page 73]

72 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

NS-5695: User interface changesThe Last 50 Documents filter option on Home page tiles was changed to Last 200 Documents.

NP-15094: Status tracking of CSV invoice uploadProducts: Ariba Network

Audience: Suppliers

Enablement: Automatically on

This Ariba Network is applicable to all supplier users.

Background in brief

A CSV file is a Comma Separated Value file that represents a structured method of storing data. A CSV invoice enables suppliers with a large number of invoices to submit their invoices to customers in one consolidated file.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 73

If suppliers cannot create cXML or EDI invoices and do not want to create invoices in Ariba Network manually, CSV invoice import provides them with a convenient way of routing invoices to their customers. Another advantage of including multiple invoices in a single CSV file is that suppliers can save significant time and effort.

To import CSV invoice templates into Ariba Network, suppliers perform three steps:

1. Download their customer’s CSV invoice template.2. Fill in the field values in the CSV invoice template.3. Import the properly formatted CSV file into Ariba Network.

Correctly formatted CSV files will be imported successfully. If a CSV file is incorrectly formatted, suppliers will receive an error message. Suppliers can then correct the formatting error and repeat the import process.

Enhancements to CSV invoices

Previously, suppliers had the following limitations:

● Suppliers could not track the status of historically imported CSV files. As a result, if a CSV file failed to be imported into Ariba Network for any reason, suppliers would manually have to choose the failed CSV file and resubmit it. This became cumbersome if the supplier had a large number of CSV files.

● Suppliers could not track the status of the individual invoices in a CSV file.● Suppliers could not track the individual invoices back to the parent CSV file they were uploaded in.

The current enhancements to the CSV file functionality provide the following solutions. Suppliers now have the ability to:

● Search for and view a list of CSV files uploaded into Ariba Network.● Track the invoices created from a CSV file.● Download the original CSV file (that the supplier uploaded previously).● Download CSV file errors as a CSV file.● View errors for a given failed invoice.● Navigate to the invoice detail screen for an invoice.

Limitations

The CSV file name to be imported into Ariba Network must not have the terminology "script" anywhere in the file name.

74 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

NP-15094 Changes to existing functionality

Supplier user interface changes

This feature adds the following changes to the supplier interface in Ariba Network:

● CSV Files page: A CSV Files page is added in the supplier interface. This page lists out all the CSV invoices historically imported by the supplier.

● Search Filters: This option allows suppliers to search for a CSV file by Customer Name, CSV File Name, or by Date Range.

● CSV File Information page: Suppliers can select (click) a CSV file to open the CSV File Information section. This section shows information about the CSV file that was selected. It also shows the list of individual invoices that make up the parent CSV file.

● Download option: In the CSV File Information page, suppliers can use the Download drop-down option to:○ download the Original CSV○ download a CSV Invoice Errors file if there are any errors in the individual invoices that make up the CSV

file.

NoteIf there are no errors, the option to download the CSV Invoice Errors file is not displayed.

● Refresh button: After a CSV file is imported and submitted, and when a supplier navigates to the CSV File Information page for that particular CSV file, a few invoices may still be in 'processing' state. Clicking the Refresh button displays the current (latest) status of invoices.

● Status drop-down menu: A Status drop-down menu to view invoices by status, such as, Sent, Failed, Rejected, Approved.

NP-15094 Supplier user tasks

This section describes supplier user tasks.

NP-15094 How to download the original CSV and the CSV Invoice Errors files

Context

Suppliers can download the original CSV file and the CSV Invoice Errors files.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 75

Procedure

1. In the CSV Files page, click the CSV file that you want to download.2. In the CSV File Information page, click the Download option.3. Click Original CSV.4. Save the file to your local computer.5. If you want to download the CSV Invoice Errors file, click the Download option, and then CSV Invoice Errors.6. Save the file to your local computer.

NP-15094 How to check invoice status

Context

Suppliers can check the status of an individual invoice that is part of a CSV file.

Procedure

1. In the CSV Files page, click the CSV file you want to view the details of.2. In the CSV Invoice Details section, click the link in the Invoice Status column for the individual invoice (for

which to view the status).

The invoice history is displayed on your screen. This is the same page that is displayed in the History tab of the invoice detail page.

NP-15094 How to navigate to the invoice detail page of an invoice

Context

Suppliers can navigate to the invoice detail page in Ariba Network from the CSV File Information page.

Procedure

1. In the CSV Files page, click the CSV file you want to view the details of.2. In the CSV Invoice Details section, click the link in the Invoice # column for the individual invoice (for which to

view the invoice detail page).

The invoice detail page is displayed on your screen. This is the same page that is shown when you open an invoice in your Ariba Network Outbox. To navigate back to the CSV File Information page, click the Back button.

76 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

NP-13428: GRN report enhancementProducts: Ariba Network

Audience: Buyers and suppliers

Enablement: Automatically on

This Ariba Network feature is applicable to all buyer and supplier users.

Reports are used to collect information on the transaction activity in an SAP Ariba account. A report is a snapshot of data generated at a particular point in time.

A report template defines what information is included in reports that are generated from it.

Reports can be either manual reports or scheduled reports. You use manual reports to choose your data and generate the report. With scheduled reports, the data included in the report is based on a report template. For example, a purchase order report template defines which customers and amount ranges are to be included in the report.

A manual report can be generated any time you want to see the results.

A scheduled report is automatically generated from a template at scheduled intervals by Ariba Network.

The Goods Receipt Note (GRN) report enhancement feature allows you to view additional fields in the GRN report that you download from Ariba Network.

NoteWhen you generate a report from a template, Ariba Network creates a report file in comma-separated values (CSV) format and overwrites the last report you ran from that template. You can view and download reports to your local drive to save a record of your account activity over time.

How to generate goods receipt reports

Procedure

1. Create a report template with the Goods Receipt report type, and click next to move to the Criteria step.2. To limit the report to specific customers, click Select, and then do one of the following:

○ Enter a value in the Company Name text box and click Search. Ariba Network displays search results in the Customer list.

○ To add companies from the Customer list to the report, click the check box for the customer and click Add. Ariba Network adds these companies to the Selected Customers list.

○ To remove customers from the report, click the check boxes in the Selected Customers list and click Remove.

3. Click OK.4. To report on a goods receipt with a specific number assigned by the procurement application, enter the

numeral in the Goods Receipt Number text box.

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 77

5. To report on goods receipts that were received during a specific date range, enter the dates in the Document Received Date field.

6. Select the box Include Additional Fields if you wish the report to show the additional fields that have been added as part of this enhancement.

7. Click Submit.

You can view the report after it is processed.8. To run the report afresh, select the report and click Run.

The report gets requeued and the existing report file is rewritten. If you do not want to lose the report file, download the file to your local drive before re-running the report.

9. To refresh the status of the report, click Refresh Status.10. To download the report, click Download.11. Click Open to view the report. Click Save to save the report.

Additional fields added to GRN report

The table below shows a list of additional fields added to the GRN report as a result of the current enhancement.

Table 2: Additional fields added to GRN report

Additional field added Description Notes if applicable

Line Item Type Any service or product in an invoice, with quantities and prices added as a line item

Bill To Name Where you send invoices and other billing related information; elements of the Bill To addressBill To Street

Bill To City

Bill To State

Bill To Postal Code

Bill To Country

Sold To Name Elements of the Sold To address

Sold To Street

Sold To City

Sold To State

Sold To Postal Code

Sold To Country

78 C O N F I D E N T I A LAriba Network Q2 2019 release guide

General Ariba Network features

Additional field added Description Notes if applicable

Tax In Line Tax added at the line level of an invoice. Taxes can be added at the header level or at the line level of an invoice. This is gov­erned by the invoicing rules configured by the buyer.

NoteIf there is at least one line level tax available, then regardless of the header level taxes, the GRN report alsways shows this field (TaxInLine) as Yes ('Y').

Tax Category The tax category. For example, VAT, sales tax, GST

If there are multiple taxes in an invoice, they are named with a suffix. For exam­ple, TaxCategory_1, TaxCategory_2.

Tax Percentage Rate The tax rate expressed as a percentage, and as stipulated by country laws

Tax Description The description of the tax

Ariba Network Q2 2019 release guideGeneral Ariba Network features C O N F I D E N T I A L 79

APIs

CSC-12679: Planning Collaboration API for Supply Chain CollaborationDescription

Products: SAP Ariba APIs

SAP Ariba developer portal

SAP Ariba Supply Chain Collaboration

Audience: Buyers

Enablement: Customer configured

Feature IDs associated with this feature: CSC-12679, CSC-13514

This API enables you to retrieve certain data about your suppliers directly from Ariba Network:

● Supplier inventory data● Supplier-managed inventory data● Forecast and commitment data

Business uses

Here are some likely businesses uses for this API:

● A supplier manages certain goods for you at one of their warehouses. You can use this API to get supplier inventory data levels at that location.

● You have inventory you want to maintain at a certain level. Your supplier agrees to ship goods to maintain the stock on hand within a certain range. You can use this API to get supplier-managed inventory data with the quantity of goods the supplier is planning to ship during a certain time period.

● You might need to place a rush order of a certain material. You can use this API to learn which suppliers made commitments for the desired material in the required timeframe. You can then determine whether your suppliers can individually or collectively provide the needed quantity of the material, by the date you need it.

80 C O N F I D E N T I A LAriba Network Q2 2019 release guide

APIs

Use cases

This API supports the following usages:

Use case Description

Supplier-managed inventory data export You can use the /supplierManagedInventory endpoint to retrieve planning information from Ariba Network. This data might include supplier commitments, planned replenishment by suppliers, and projected stock at a certain location. This data is expressed as key f igure time series. You pro­vide to the API the parameters to filter the data you want.

Supplier inventory data export You can use the /supplierInventory endpoint to retrieve from Ariba Network total stock on hand data and a breakdown across the different stock types it contains. You provide to the API the parameters to filter the data you want.

Forecast data export You can use the /forecast endpoint to retrieve supplier forecast and commitment data from Ariba Network. You provide to the API the parame­ters to filter the data you want.

Prerequisites

Before you can use the Planning Collaboration API for Supply Chain Collaboration, you must:

● Complete the onboarding process on the SAP Ariba developer portal. See SAP Ariba developer portal for more information.

● Ensure that your application conforms to expected OAuth authentication. Only applications approved by the SAP Ariba APIs administration can execute OAuth authentication.

● As a buyer administrator, add your OAuth Client ID to your profile.1. In the Ariba Network buyer dashboard, click your account name in the upper right corner.

2. Click Manage Profile API Client ID Configuration .3. In the Client ID field, type your OAuth Client ID and click Save.

● Be enabled for SAP Ariba Supply Chain Collaboration and the applicable collaboration component:○ For the supplier inventory and supplier-managed inventory API endpoints, enable the inventory

collaboration component.○ For the forecast API endpoint, enable the forecast collaboration component.

● Also for the forecast API endpoint, enable the forecast collaboration transaction rules:○ Allow suppliers to view forecast data○ Allow suppliers to commit to forecast data

Limitations

This API can retrieve data only for suppliers in a relationship with you.

Ariba Network Q2 2019 release guideAPIs C O N F I D E N T I A L 81

Buyer administrator user interface changes

This feature adds an API Client ID Configuration page to the username Manage Profile page. When a buyer administrator adds an OAuth Client ID to this page, APIs that specify that client ID are authorized to retrieve from Ariba Network the data associated with that ID.

Workflow for the SAP Ariba API for planning

See Workflow for the Planning Collaboration API for Supply Chain Collaboration [page 82].

User tasks

See How to develop an application that consumes the Planning Collaboration API for Supply Chain Collaboration [page 82].

Workflow for the Planning Collaboration API for Supply Chain Collaboration1. The client application queries Ariba Network with a defined set of parameters.2. In response to the query, the API returns a JSON data set that contains all matching records in a formatted

structure.3. The receiving application processes the data.

How to develop an application that consumes the Planning Collaboration API for Supply Chain CollaborationYou can develop a client application that calls the Planning Collaboration API for Supply Chain Collaboration.

NoteIn the sample URLs in this topic, replace {{runtime_url}} with the desired runtime URL from the Environment Details table on the SAP Ariba developer portal discovery page for this API.

In the sample URLs in this topic, replace {{runtime_url}} with the desired runtime URL from the Environment Details table on the SAP Ariba developer portal operated by CDC discovery page for this API.

API requests can pass multiple parameters [page 83] in the request URL.

● Header parameters use the following syntax:

header_parameter=value

82 C O N F I D E N T I A LAriba Network Q2 2019 release guide

APIs

● The queryrsqlfilter parameter uses the following syntax, with a semicolon (;) between multiple parameters to rsqlfilter:

rsqlfilter=parameter==value;parameter==value

● Other query parameters use the following syntax, separated from rsqlfilter and other query parameters by an ampersand (&).

rsqlfilter=rsqlfilter_parameter==value&query_parameter=value&query_parameter=value

Sample CodeThe following example retrieves all supplier inventory records for vendor ID 1234 at the North10B plant, and displays 15 records per page.

GET {{runtime_url}}/supplierInventory?rsqlfilter=VendorId==1234;plantId==North10B&limit=15

Sample CodeThe following example retrieves all records for vendor ID 9876 of the projected stock demand and planned shipment of material with buyer part number ABCD345. The retrieved data is for the period between the start of business on March 4, 2019, through end of business March 15, 2019. Data is sorted by lead time and displays ten records per page.

GET {{runtime_url}}/supplierManagedInventory?rsqlfilter=buyerPartNumber==ABCD345;VendorId==9876;startDate==2019-03-04T0800;endDate==2019-03-15T1700;sortCol==LEADTIME&limit=10

Sample CodeThe following example retrieves all supplier forecast records for buyer part number XYZ.5678 dated from June 1, 2019, and June 15, 2019, and displays 20 records per page.

GET {{runtime_url}}/forecast?rsqlfilter=buyerPartNumber==XYZ.5678;startDate==2019-06-01T0800&endDate==2019-06-15T1700&limit=20

Parameters for the Planning Collaboration API for Supply Chain Collaboration

Header parameter Requirement Description

Authorization Required Your authorization credentials. Enter Bearer followed by a space and your access token.

Ariba Network Q2 2019 release guideAPIs C O N F I D E N T I A L 83

Header parameter Requirement Description

apikey Required Your application key. This key is automatically generated when you create an application on the SAP Ariba developer portal, and is visible when you select your application in the Manage Applications area.

Your application key. This key is automatically generated when you create an application on the SAP Ariba developer portal operated by CDC, and is visible when you select your application in the Manage Applications area.

X-ARIBA-NETWORK-ID Required Your Ariba Network ID (ANID).

Query parame­ters

Attributes to rsqlfilter Requirement Description

rsqlfilter Optional Specifies record search criteria and how to organize the re­turned records. If used, must specify at least one rsqlfilter attribute.

plantId Optional Plant ID.

vendorId Optional Supplier vendor ID.

buyerPartNumber Optional An item in the buyer system. The buyer specifies this identi­fier.

supplierPartNumber Optional An item in the supplier system. The supplier specifies this identifier.

startDate Optional (supplierManagedInventory and forecast end­points only)

The starting date and optional time of the buyer demand pe­riod, in the form YYYY-MM-DDThh:mm. The derived period is limited to one year from the ending date.

endDate Optional (supplierManagedInventory and forecast end­points only)

The ending date and optional time of the buyer demand pe­riod, in the form YYYY-MM-DDThh:mm. The derived period is limited to one year from the starting date.

sortCol Optional The column to sort on. Available columns are:

● BUYERLASTUPDATE● BUYERPARTNO● LEADTIME● LOCATIONID● LOCATIONNAME● PLANTID● PROCESSTYPE● STOCKONHAND● SUPPLIERLASTUPDATE● SUPPLIERPARTNO

84 C O N F I D E N T I A LAriba Network Q2 2019 release guide

APIs

Query parame­ters

Attributes to rsqlfilter Requirement Description

sortDir Optional The direction to sort data. Valid values are ASC (ascending) and DESC (descending).

limit Optional The maximum number of items to display per page. Default is 10. Maximum is 20. Any setting greater than 20 displays 20 items per page.

NoteThe pagination features of the Planning Collaboration API for Supply Chain Collaboration allow you to retrieve any number of supplier records in total.

offset Optional The report page number to return. Default is 0, which returns page 1.

Ariba Network Q2 2019 release guideAPIs C O N F I D E N T I A L 85

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.

86 C O N F I D E N T I A LAriba Network Q2 2019 release guide

Important Disclaimers and Legal Information

Ariba Network Q2 2019 release guideImportant Disclaimers and Legal Information C O N F I D E N T I A L 87

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