CONFIDENTIAL

2019-05

Spend analytics and invoicing workflows

configuration guide
SAP Ariba Buying
© 2019 SAP SE or an SAP affiliate company. All rights reserved.

SAP Ariba Buying and Invoicing

SAP Ariba Invoice Management

THE BEST RUN

Content

Expansion of Spend Analytics and Invoicing Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Enabling expanded spend analytics and invoicing workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Incremental master data loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configuring the SAP Ariba procurement solution site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

How to configure Ariba Network Shared Secret Settings in Ariba Procurement Solution. . . . . . . . . . . . 7

How to configure Ariba Network Endpoint Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Document routing channel configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ERP integration configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Integration changes for buyers using SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Integration changes for Buyers using Oracle ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Site configuration parameter settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Site-level parameters configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Possible scenarios for parameter configuration settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Ariba Network Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuration requirements for new customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring SAP Ariba solution end point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Configuring document routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Considerations for configuring document routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Default document routing reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuration requirements for existing SAP Ariba Invoice Management customers migrating to a
merged site environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Performing cXML setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

About Transaction Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Requisition-to-Invoice Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Invoice-to-Invoice Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Requisition-to-Payment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

About Purchase Order Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

About Receipt Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Revision history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Spend analytics and invoicing workflows configuration guide

2 CONFIDENTIAL Content
Expansion of Spend Analytics and Invoicing
Workflows

SAP Ariba Buying and Invoicing can be combined with SAP Ariba Invoice Management and other Ariba
procurement solutions to provide customers with a comprehensive workflow and reporting solution. Procurement
organizations can gain visibility to additional spend categories not initiated in an Ariba procurement solution.

This architectural enhancement provides customers with the option to deploy any of the following new Ariba
solution combinations on the same site:

● SAP Ariba Buying and Invoicing and SAP Ariba Invoice Management
● SAP Ariba Buying and Invoicing, SAP Ariba Invoice Management, and SAP Ariba Catalog
● SAP Ariba Buying and Invoicing and SAP Ariba Catalog
● SAP Ariba Buying and SAP Ariba Catalog
● SAP Ariba Catalog and SAP Ariba Invoice Management

Functionality Introduced with the Expansion of Spend Analytics and Invoicing Workflow

The following areas of additional functionality are provided by this feature:

● ERP BPO—BPOs created in an external ERP system are routed as copy requests to the SAP Ariba Buying
solutions from Ariba Network.
Prior to this release, suppliers were not able to create invoices against BPOs created in an external ERP system
because the BPOs did not exist in the Ariba Procurement and Invoicing Solution. Every time suppliers
attempted to create an invoice against an externally created BPO, suppliers were required to punch in to the
Ariba Procurement and Invoicing Solution, resulting in PunchIn errors.
Because the external BPOs are now routed to the Ariba Procurement and Invoicing Solution as copy requests,
suppliers can successfully create invoices. Buyers can also create invoice reconciliations (IRs) for invoices that
correspond to these external BPOs and process the IRs for payment.
● Enhanced Requisition Import—The following requisition import enhancements are included:
○ Allows import of requisitions from external ERP systems using cXML, Web Services, or CSV channels.
○ Allows requisition creation along with change and update operations on imported requisitions.
○ Allows creation of requisitions with Buyer Part Number and Facility values that can be mapped internally to
the appropriate Supplier and Supplier Part Number values. Internal mapping ensures the best price match.
Internal mapping is configured using the Item Master file. For more information on the Item Master file, see
the Ariba Procurement Data Import and Administration Guide.
● ERP filtering of Purchase Orders and Receipts—Allows customers to restrict an external ERP system from
routing purchase orders and receipts originating in the SAP Ariba Buying solutions to Ariba Network.
Implement filtering of purchase orders and receipts through the Ariba Network Adapter you use to integrate
your external ERP with the Ariba Network.
ERP integration configurations are required to enable this feature, and provide the following capabilities:
○ Purchase orders originating from the SAP Ariba Buying solutions and processed with the ERP order
method when routed from the external ERP system to Ariba Network are not sent back to the SAP Ariba
Buying solutions, eliminating the creation of duplicate POs.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 3
 ○ Purchase orders originating from the SAP Ariba Buying solutions and processed with the ERPCC order
method are not routed to Ariba Network from the external ERP. Instead, the POs are filtered by the Ariba
Network Adapter.
○ Receipts originating from the SAP Ariba Buying solutions are exported to the external ERP systems, but
they are filtered by the Ariba Network Adapter (DB Adapter for Oracle ERP users) to restrict them from
being routed to Ariba Network.
○ Receipts originating from an external ERP system get routed to the SAP Ariba Buying solutions through
Ariba Network as copy receipts. When receipts originating from the SAP Ariba Buying solutions are
exported to the external ERP system, this feature restricts such receipts from being routed to Ariba
Network.

In this section:

Enabling expanded spend analytics and invoicing workflows [page 4]

Incremental master data loads [page 5]

Configuring the SAP Ariba procurement solution site [page 7]

Document routing channel configuration [page 8]

ERP integration configurations [page 9]

Site configuration parameter settings [page 14]

Ariba Network Configurations [page 27]

Configuration requirements for existing SAP Ariba Invoice Management customers migrating to a merged site
environment [page 39]

About Transaction Flows [page 40]

Related Information

About Purchase Order Filtering [page 45]

About Receipt Filtering [page 47]

Enabling expanded spend analytics and invoicing

workflows
Support for spend analytics and invoicing workflow enhancements are available on all SAP Ariba Procurement
solutions sites by default. To configure your site with multiple SAP Ariba Procurement solutions (called a merged
site) purchase the required licenses/subscriptions and contact your Customer Success Manager or Account
Manager for more information on Ariba Services

Spend analytics and invoicing workflows configuration guide

4 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Enablement requirements for merged sites

Configuring your site for this feature requires multiple steps and action items. Certain configuration tasks can be
performed by SAP Ariba Customer Support representatives only and those have been marked as SAP Ariba
Internal Tasks.

The following table lists the recommended tasks be performed in sequence before converting a single SAP Ariba
solution site to a merged solution site. Contact your Customer Success Manager or Account Manager to configure
your site as required.

Task Owner

Perform incremental master data load Customer

For more information, see Incremental master data loads [page 5].

Configure the SAP Ariba procurement solution Ariba Support

For more information, see Configuring the SAP Ariba procurement solution site [page 7].

Determine document routing channel Customer

For more information, see Document routing channel configuration [page 8].

Configure ERP integration settings Customer

For more information, see ERP integration configurations [page 9].

Configure parameters Ariba Support

For more information, see Site configuration parameter settings [page 14].

Configure Ariba Network Ariba Support

For more information, see Ariba Network Configurations [page 27].

Configure Ariba Network endpoints Customer

For more information, see Ariba Network Configurations [page 27].

Incremental master data loads

Before converting a single SAP Ariba solution site to a merged solution site, you must load certain master data into
your customer site. If you are an existing customer, the incremental master data you upload depends on the
current SAP Ariba procurement solution deployed on your site and the other solutions that you chose to deploy as
part of the merged environment.

 Note

If you are an existing SAP Ariba Buying and Invoicing customer, then the master data that has been loaded
becomes a superset of all master data that is required for other configurable SAP Ariba procurement solutions.

The following table lists the CSV files you must load based on your site’s ERP system:

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 5
SAP PeopleSoft Generic

AdjustmentType.csv AdjustmentType.csv AdjustmentType.csv

AllowableHierarchyChoice.csv AllowableHierarchyChoice.csv AllowableHierarchyChoice.csv

AutoType.csv AutoType.csv AutoType.csv

ExpenseCodeMapping.csv ExpenseCodeMapping.csv ExpenseCodeMapping.csv

ExpenseHeaderCategoryMap.csv ExpenseHeaderCategoryMap.csv ExpenseHeaderCategoryMap.csv

ExpenseTaxCodeLookup.csv ExpenseTaxCodeLookup.csv ExpenseTaxCodeLookup.csv

ExpenseTaxRateLookupByTax­ ExpenseTaxRateLookupByTaxCode.csv ExpenseTaxRateLookupByTaxCode.csv

Code.csv

ExpenseType.csv ExpenseType.csv ExpenseType.csv

ExpenseTypeGLMapping.csv Level2Charge.csv Level2Charge.csv

Level2Charge.csv LocationType.csv LocationType.csv

LocationType.csv POConditions.csv POConditions.csv

POConditions.csv ReceiptByCommodityCode.csv ReceiptByCommodityCode.csv

ReceiptByCommodityCode.csv ReceiptByPartNumber.csv ReceiptByPartNumber.csv

ReceiptByPartNumber.csv ● RuleCSVHelperFiles.zip ● RuleCSVHelperFiles.zip (set of 6 files)

○ CommodityCentralReceiv­ ○ CommodityCentralReceivers.csv
ers.csv ○ CommodityCentralReceiversForAp­
○ CommodityCentralReceivers­ provalProcess.csv
ForApprovalProcess.csv ○ CommodityReceivers.csv
○ CommodityReceivers.csv ○ CommodityReceiversForApproval­
○ CommodityReceiversForAp­ Process.csv
provalProcess.csv ○ ExpenseTypeApprovers.csv
○ ExpenseLimit.csv
○ ExpenseTypeApprovers.csv
○ RequisitionLimit.csv

● RuleCSVHelperFiles.zip (set of ● ScheduledTaskData.zip (set of 47 ● ScheduledTaskData.zip (set of 35 files)

10 files) files) ○ ExpenseGuidelines.table
○ CommodityApprovers.csv ○ ExpenseGuidelines.table ○ JCNForHierarchyTestForCatalog.cif
○ CommodityCentralReceiv­ ○ Supplier-RPC-01.cif ○ JohnWoodmanEGVL1.cif
ers.csv ○ Supplier-RPC-02.cif ○ Supplier-RPC-01.cif
○ CommodityCentralRecei­ ○ Supplier-RPC-03.cif ○ Supplier-RPC-02.cif
versForApprovalPro­ ○ Supplier-RPC-04.cif ○ Supplier-RPC-03.cif
cess.csv
○ Supplier-RPC-05.cif ○ Supplier-RPC-04.cif
○ CommodityReceivers.csv
○ Supplier-RPC-06.cif ○ Supplier-RPC-05.cif
○ CommodityReceiversFor­
○ Supplier-RPC-06.cif
ApprovalProcess.csv
○ ExpenseLimit.csv
○ ExpenseTypeApprovers.csv
○ RequisitionLimit.csv

Spend analytics and invoicing workflows configuration guide

6 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 SAP PeopleSoft Generic

● ScheduledTaskData.zip (set of
24 files)
○ ExpenseGuidelines.table
○ Supplier-RPC-01.cif
○ Supplier-RPC-02.cif
○ Supplier-RPC-03.cif
○ Supplier-RPC-04.cif
○ Supplier-RPC-05.cif
○ Supplier-RPC-06.cif

Configuring the SAP Ariba procurement solution site

Ariba Customer Success Managers or Account Managers must complete the configuration of Ariba Network
Shared Secret Settings and Ariba Network Endpoint Settings before selecting multiple SAP Ariba procurement
solutions as part of the merged site deployment.

Configuring the End Point and Shared Secret is mandatory for all existing SAP Ariba Invoice Management
customers. Configuring these values is also mandatory when SAP Ariba Buying and Invoicing customers are
upgrading to a merged site environment (that is, enabling SAP Ariba Invoice Management on the same site).

This configuration is optional for SAP Ariba Buying and Invoicing only customers or SAP Ariba Buying only
customers that use the ERP order method as their primary purchase order processing configuration.

How to configure Ariba Network Shared Secret Settings in

Ariba Procurement Solution

Ariba Customer Success Managers or Account Managers must configure Ariba Network Shared Secret settings.

Procedure

1. Log on to the Ariba Service Manager.

2. Under Site Manager, click Customer Sites.
3. Select the relevant customer site and select Edit Site Profile from the available options.
4. In the Ariba Network Settings section, do the following:
a. Enter the customer’s AN ID in the SN Network ID field.
b. Enter the customer’s Ariba Network Business Application System ID.
c. Enter the Ariba Shared Secret in the SN Shared Secret field and re-enter to confirm this value.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 7
How to configure Ariba Network Endpoint Settings
Ariba Customer Success Managers or Account Managers must configure Ariba Network Endpoint settings.

Procedure

1. Log on to the Ariba Service Manager.

2. Under Site Manager, click Customer Sites.
3. Select the relevant customer site and select Edit Site Profile from the available options.
4. In the Ariba Network Endpoint Settings section, enter the Ariba On Demand Solution End Point (End Point
ID) value that was configured for the customer’s Ariba Network Buyer Account.

 Note

You must verify the End Point ID value on Ariba Network prior to this step to ensure you are using the same
end point ID.

5. Click OK

Document routing channel configuration

During the configuration process, you can select the routing channel for invoice reconciliation (IR) documents.

If you are an SAP Ariba Invoice Management solution user, you must decide whether to continue with the existing
transaction flow using the cXML channel or move to a CSV file format for all IR transactions.

If you are an existing SAP Ariba Buying and Invoicing solution user and are moving to a merged site environment by
switching from File Channel-based document routing to cXML-based document routing, you must ensure that all
existing IR documents are fully processed.

To ensure all existing IR documents are fully processed, decide on the channel of communication and contact your
Customer Success Manager or Account Manager to have an Ariba Customer Support representative follow up by
configuring the associated parameter as necessary.

Spend analytics and invoicing workflows configuration guide

8 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
ERP integration configurations
You must configure certain ERP integration settings to ensure that purchase orders are routed correctly after the
merged site is enabled. The ERP integration settings that you configure depend on your site’s ERP system.

The ERP integration configurations ensure that:

● Purchase orders originating from the SAP Ariba solution and processed using the ERP order method when
routed from the external ERP system to Ariba Network are not sent back to the SAP Ariba solution, eliminating
the creation of duplicate POs.
When a purchase order processed using the ERP order method reaches the Ariba Network Adapter from the
ERP system, the cXML document generated and sent to Ariba Network is populated with the new
AribaOrderID field, which determines the PO originated from the SAP Ariba solution.
● Purchase orders originating from the SAP Ariba solution and processed using the ERPCC order method are not
routed to Ariba Network from the external ERP. These POs are filtered by the Ariba Network Adapter.

Related Information

Integration changes for buyers using SAP ERP [page 9]

Integration changes for Buyers using Oracle ERP [page 11]

Integration changes for buyers using SAP ERP

You must make the following integration changes for SAP ERP to ensure that purchase orders are routed correctly
after the merged site is enabled.

Updating the Ariba network Adapter for SAP Netweaver

You must update the Ariba Network Adapter for SAP Netweaver.

To update, download the following adapter, transports, and mappings before starting with the configurations:

● Appropriate adapter from Connect—To download the adapter, go to http://connect.ariba.com and click
Download Software tab. Search for Ariba Adapter for SAP Netweaver and download the ZIP file (for example,
AribaAdapterSAPNetweaver_v2013 <Month> <Release>.zip).
● Latest SAP transports—To download the latest transports log into Connect and go to the required product
area (for example, SAP Ariba Buying and Invoicing). In the Resources page, click the SAP Transports (SAP
Only) link and download the ZIP file.
These transports contain sample SAP development objects (development classes, function groups, and
function modules) for the SAP Ariba solution and SAP application integration. You can install the samples into
your SAP system, and customize them as necessary for the transfer of data between theSAP Ariba solution
and your SAP ERP system.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 9
● SAP Netweaver Mapping (if you are using the Web Services integration)—Log into Connect and go to the
required product area (for example, SAP Ariba Buying and Invoicing). In the Resources page, click the SAP
NetWeaver Mapping (SAP Web Service Only) link and download the ZIP file.

Enable the Ariba Network adapter to filter purchase orders

You can restrict your SAP ERP system from routing purchase orders originating in theSAP Ariba solution to Ariba
Network. Filtering of purchase orders is performed at the Ariba Network Adapter.

Typically, all purchase orders processed using the ERP order method in the SAP Ariba solution are routed to Ariba
Network from the SAP ERP system. These orders are then routed back to the SAP Ariba solution from Ariba
Network with updates from the ERP system.

When purchase orders are processed using the ERPCC order method, the SAP Ariba solution routes the POs to the
SAP ERP system and also sends a copy of these POs directly to Ariba Network. When the SAP ERP system
attempts to route POs processed as ERPCC to Ariba Network, the Adapter must identify them as POs that already
exist in Ariba Network and filter them out.

To enable the Ariba Network Adapter to filter purchase orders, change purchase orders, and cancel purchase
orders that are processed in the SAP Ariba solution using the ERPCC order method from reaching Ariba Network,
perform the following tasks on your SAP ERP system:

● Create separate document types for each such documents

● Ensure that the condition record is not configured for these document types

The purchase order document types that are not configured for IDoc are automatically filtered and do not get
routed to Ariba Network.

 Note

For more information on how to create document types and configure condition records, see the Ariba Network
Adapter for SAP NetWeaver Guide.

Enable the Ariba Network adapter to filter receipts and invoices

To filter receipts and invoices originating from the SAP Ariba solution, the Ariba Network Adapter populates the
unique receipt and invoice ID to determine the originating source of these documents.

● Receipts—On the General tab of the material document display page in the SAP system, the receipt document
that originated from the SAP Ariba solution is populated with a unique identifier in the Header Text field. For
example, “Ariba-RC 10”.
● Invoices—On the Details tab of the invoice document display page in the SAP ERP system, the Header Text
field is populated with a unique identifier if the invoice document is originating from the SAP Ariba solution. For
example, “ARIBA_P2P”.

The Adapter filters out all receipts and invoice documents for which the Header Text value populated. These
documents are not routed to Ariba Network.

Spend analytics and invoicing workflows configuration guide

10 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Integration changes for Buyers using Oracle ERP
You must make the following integration changes for Oracle ERP to ensure that purchase orders are routed
correctly after the merged site is enabled.

Update the Ariba Network adapter for Oracle Fusion Middleware

You must update the Ariba Network adapter for Oracle Fusion Middleware.

The Ariba Network adapter for Oracle Fusion Middleware has changed.

To update, download the following adapter and SQL sample queries before starting with the configurations:

● Appropriate adapter from Connect—To download the adapter, go to http://connect.ariba.com and click
Download Software tab.
● Latest SQL sample queries for Oracle ERP—To do this, log into Connect and go to the required product area
(for example, SAP Ariba Buying and Invoicing). In the Resources page, click the Sample SQL Queries Only
(Oracle) link and download the following files:
○ AribaNetworkAdapterOracleFusion_v12s2_11g.zip
○ AribaNetworkAdapterOracleFusion_v12s2_10g.zip
These queries contain sample Oracle development objects (queries for different versions of Oracle
application and custom packages) for the SAP Ariba solution's integration with Oracle application system.
You can download these queries and packages, install them into your Oracle application system, and
customize them as necessary for the transfer of data between the SAP Ariba solution and your Oracle ERP
system.

For more information about downloading the adapter and the sample queries, see the Ariba Network adapter for
Oracle Fusion Middleware Setup Guide.

SQL configuration changes for purchase orders

Download the enhanced version of the PurchOrdHeaderDetails.sql file. With this release, a new attribute,
attribute2, has been introduced, and is mapped to the OrderMethodCategory. This value determines whether
a purchase order is of order method type ERP or ERPCC.

PurchOrdHeaderDetails.sql SQL file is available on Connect (http://connect.ariba.com ) as part of a ZIP file.

Extract the zip file contents and open the Ariba_P2P_ORA_SQL_12s2 folder. Navigate to the Oracle11i > SQL
Queries> PurchaseOrder location and download the PurchOrdHeaderDetails.sql SQL file.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 11
cXML Changes

A new extrinsic field, AribaOrderID, has been introduced in the purchase order and receipt cXML documents to
identify the originating source. AribaOrderID enables the Ariba Network adapter for Oracle Fusion Middleware to
identify the originating source of these documents.

Filtering of ERP orders by the Ariba Network adapter for Oracle

Fusion Middleware

When a purchase order originating from the SAP Ariba solution reaches an Oracle ERP system, it is routed to Ariba
Network using the Ariba Network adapter for Oracle Fusion Middleware.

Before routing the purchase orders to Ariba Network, the Adapter filters PO documents based on the
“attribute2 = xx” value (that is, attribute2="ERP" or attribute2="ERPCC").

Depending on the value of attribute attribute2 the Adapter filters out all purchase orders that are processed
using the ERPCC order method. Only purchase orders processed using the ERP order method are routed to Ariba
Network.

Filtering of ERPCC orders by the Ariba Network adapter for Oracle

Fusion Middleware

If the order method is ERPCC the Ariba Network adapter for Oracle Fusion Middleware does not download purchase
orders from the external ERP system, preventing these purchase orders from being routed Ariba Network.

 Note

ERPCC type purchase orders are not routed to Ariba Network from the external ERP system.

 Example

Example of Purchase Order cXML

The purchase order cXML example illustrates how attribute2 is used.

</ns5:Extrinsic>
<xsl:choose>
<xsl:when test='/ns0:CompositeElementLangTerritory/
DetailInputLangTerritory/ns1:PoHeadersAllCollection/ns1:PoHeadersAll/
ns1:attribute2="ERP"'>
<ns5:Extrinsic>
<xsl:attribute name="name">
<xsl:text disable-output-escaping="no">AribaOrderID</xsl:text>
</xsl:attribute>
<xsl:value-of select='/ns0:CompositeElementLangTerritory/
DetailInputLangTerritory/ns1:PoHeadersAllCollection/ns1:PoHeadersAll/
ns1:segment1'/>
</ns5:Extrinsic>

Spend analytics and invoicing workflows configuration guide

12 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Filtering receipts

A new extrinsic field, AribaOrderID, is populated for all receipts that are associated with purchase orders
originating from SAP Ariba solutions.

Irrespective of whether a receipt is created in the SAP Ariba solution or in an external ERP system, if the receipt is
associated with a purchase order that was created in the SAP Ariba solution, the AribaOrderID is automatically
populated.

Filtering of receipts is performed by the DB Adapter based on the interfaceSourceCode field value. This field is
populated with the value “Ariba” (interfaceSourceCode="Ariba") only when receipts have been created in
the SAP Ariba solution. Receipts with this value are not routed to Ariba Network. Only receipts that have been
created in the external ERP system get routed to Ariba Network.

 Example

Example of the Receipt cXML

The receipt cXML code snippet illustrates the use of AribaOrderID and interfaceSourceCode=”Ariba”.

<ns5:OrderIDInfo>
<xsl:attribute name="orderID">
<xsl:value-of select='concat(ns2:poLineLocationsAll/ns2:poLinesAll/
ns2:poHeadersAll/ns2:orgId,".",ns2:poLineLocationsAll/ns2:poLinesAll/
ns2:poHeadersAll/ns2:segment1)'/>
</xsl:attribute>
<xsl:attribute name="orderDate">
<xsl:value-of select="ns2:poLineLocationsAll/ns2:poLinesAll/
ns2:poHeadersAll/ns2:creationDate"/>
</xsl:attribute>
<xsl:choose>
<xsl:when test='ns2:poLineLocationsAll/ns2:poLinesAll/
ns2:poHeadersAll/ns2:interfaceSourceCode="Ariba" '>
<ns5:IdReference>
<xsl:attribute name="domain">
<xsl:text disable-output-escaping="no">AribaOrderID</
xsl:text>
</xsl:attribute>
<xsl:attribute name="identifier">
<xsl:value-of select="ns2:poLineLocationsAll/ns2:poLinesAll/
ns2:poHeadersAll/ns2:segment1"/>
</xsl:attribute>
</ns5:IdReference>
</xsl:when>
</xsl:choose>
</ns5:OrderIDInfo>

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 13
Site configuration parameter settings
Ariba Customer Success Managers or Account Managers must complete the configuration of service level and
application level parameters to enable expanded Spend Analytics and Invoicing Workflows architecture on a
customer site.

Service Level Parameter Configuration

The System.Base.EnableComboRealm parameter is set to Yes by default. This parameter allows you to select
multiple Ariba Procurement Solutions on a single customer site.

Site-level parameters configuration

Configure site-level parameters based on customer requirements.

Application.Base.UseServiceProviderIDForCommonCredential

Application.Base.UseServiceProviderIDForCommonCredential is an application-level parameter used

for internal purposes only. Do not change this default configuration without consulting the Ariba Engineering team.

The default value of this parameter is No.

In this configuration, all cXML documents such as copy orders, copy receipts, invoice and invoice-related
documents (including invoice reconciliation and payment requests), must use the Buyer AN ID as the common
credential, instead of the service provider ID.

If the parameter value is set to Yes, then all cXML documents such as copy orders, copy receipts, invoice and
invoice-related documents (including invoice reconciliation and payment requests), will use the service provider ID
as the common credential, instead of the Buyer AN ID.

Changing the default configuration impacts ALL transactions reaching Ariba Network.

Application.Invoicing.SendIRtoAN

In a merged Ariba solutions environment the Application.Invoicing.SendIRtoAN parameter value

determines whether to send invoice reconciliation documents to Ariba Network using cXML configurations.
Enabling this will send invoice reconciliation documents for all types of invoices to Ariba Network.

 Note

When configuring this parameter, you must also ensure that the
SendInvoiceAndPaymentsForPrivateSupplierToAN parameter value is set to Yes. If the

Spend analytics and invoicing workflows configuration guide

14 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 SendInvoiceAndPaymentsForPrivateSupplierToAN parameter is set to No, then the invoice and invoice
reconciliation documents will not be routed to Ariba Network, irrespective of the SendIRToAN parameter value

If Application.Invoicing.SendIRtoAN is disabled, all invoice reconciliation documents are exported to an

external ERP in OK2Pay file format using the SAP Ariba integration toolkit.

The default value of this parameter is No.

The following tables describe the behavior of Application.Invoicing.SendIRtoAN for SAP Ariba Buying and
Invoicing and SAP Ariba Invoice Management customers.

For SAP Ariba Buying

and Invoicing Custom­
ers Behavior Behavior When Parameter Value is Changed

No All invoice reconciliation documents are exported to All invoice reconciliation documents are sent
external ERP systems using the SAP Ariba integra­ to Ariba Network in cXML format.
tion toolkit. These IRs are then processed and sent
to the suppliers using other third-party systems.

For SAP Ariba Invoice

Management Custom­
ers Behavior Behavior When Parameter Value is Changed

Yes All invoice reconciliation documents are sent to All invoice reconciliation documents are ex­
Ariba Network in cXML format. ported to external ERP systems using the SAP
Ariba integration toolkit. These IRs are then
processed and sent to the suppliers using
other third-party systems.

About parameter configuration impact on SAP Ariba Buying and Invoicing only customers

If a SAP Ariba Buying and Invoicing only customer requests Application.Invoicing.SendIRtoAN parameter
be enabled, then ensure that two additional parameters and End Point and Shared Secret are also configured.

Configure the following:

● Configure ExternalReconciliationEnabled parameter value to be set to Yes

● Configure AllowLegalEntityCodeAtSplitLevel parameter value to be set to Yes
● Configure the End Point and Shared Secret on your site profile

About invoice reconciliation behavior when a PO is associated with a manual supplier

Irrespective of the Application.Invoicing.SendIRtoAN parameter configuration, if the purchase order is

associated with a manual supplier (a supplier whose preferred ordering method is either Print or No Choice), then
the corresponding invoice is not sent to Ariba Network.

The resulting IRs created for such invoices are also not sent to Ariba Network.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 15
  Note

If the supplier Preferred Ordering Method is configured as Print or No Choice (or if the associated parameters
are configured NOT to send invoice and payment documents to Ariba Network, or the supplier has neither an
ANID nor a Private ID), then the following message is displayed at the time of invoice creation:

The supplier associated with this invoice has configured their preferred ordering method as Print or No
Choice. You will not be able to export payment-related data to an external ERP system.

Application.Invoicing.ExternalReconciliationEnabled

Application.Invoicing.ExternalReconciliationEnabled determines whether an external ERP

reconciliation step is required for an IR to move to the Reconciled state in the SAP Ariba Buying solutions.

Application.Invoicing.ExternalReconciliationEnabled is dependent on the

Application.Invoicing.SendIRtoAN parameter value. Configure the
Application.Invoiceing.ExternalReconciliationEnabled parameter value to Yes only if the
Application.Invoicing.SendIRtoAN is set to Yes.

Application.Invoicing.AllowLegalEntityCodeAtSplitLevel

Application.Invoicing.AllowLegalEntityCodeAtSplitLevel determines whether each split of each line

item for a non-PO invoice can have its own Company Code. Currently this parameter is supported only for Ariba
Procurement Solutions deployed on SAP ERPs.

The default value for this parameter is No.

 Note

Prior to this feature release, the option of specifying different Company Codes at the invoice split line level for
non-PO based invoices, previously only available to SAP Ariba Invoice Management customers is now also
available to SAP Ariba Buying and Invoicing customers.

Possible scenarios for parameter configuration settings

Ariba Customer Success Managers or Account Managers must be aware of the combinations of parameter
configuration that can exist on a customer site and how those configurations can affect invoice and invoice-related
document processing for various suppliers.

 Note

The following table lists eight configuration scenarios and is followed by a discussion of each scenario. In this
discussion, it is assumed that all private suppliers are configured for Quick Enablement:

Spend analytics and invoicing workflows configuration guide

16 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 Send Invoice And Pay­
Configuration ments For Private Sup­ External Reconciliation
Option plier To AN Send IR to AN Enabled Result

1 Yes Yes Yes Valid Configuration

2 Yes Yes No Valid Configuration

3 Yes No Yes Invalid Configuration

4 Yes No No Valid Configuration

5 No Yes Yes Valid Configuration

6 No Yes No Valid Configuration

7 No No Yes Invalid Configuration

8 No No No Valid Configuration (Custom­

ers to use OK2Pay file)

 Note

Regardless of configuration settings, users are not be able to submit invoices for suppliers whose preferred
ordering method is set to Print).

Configuration option 1

In configuration option 1, the customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = Yes

● Send IR to AN = Yes
● External Reconciliation Enabled = Yes

The following table and illustration explain the transaction flow in configuration option 1:

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoices are sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are sent to Ariba Network IRs sent to Ariba Network

IR status is set to Awaiting Reconciliation from External IR status is set to Awaiting Reconciliation from External ERP.
ERP.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 17
Configuration option 2

In configuration option 2, the customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = Yes

● Send IR to AN = Yes
● External Reconciliation Enabled = No

The following table and illustration explain the transaction flow in configuration option 2:

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoices are sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are sent to Ariba Network IRs sent to Ariba Network

IR status is set to Paying. IR status is set to Paying.

Spend analytics and invoicing workflows configuration guide

18 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Configuration option 3

This configuration is invalid and not recommended.

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = Yes

● Send IR to AN = No
● External Reconciliation Enabled = Yes

The following table explains the transaction flow if configuration option 3 is deployed.

 Note

This is an invalid configuration and Ariba does not recommend this parameter combination.

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoices are sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are NOT sent to Ariba Net­ IRs NOT sent to Ariba Network
work

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 19
Supplier Type

IR status moves to the Paying state. IR status remains stuck in the Awaiting Reconciliation from
External ERP state.

Configuration option 4

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = Yes

● Send IR to AN = No
● External Reconciliation Enabled = No

The following table and illustration explain the transaction flow for configuration option 4:

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoices are sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are NOT sent to Ariba Net­ IRs NOT sent to Ariba Network
work

IR status is set to Paying. IR status is set to Paying.

Spend analytics and invoicing workflows configuration guide

20 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Configuration option 5

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = No

● Send IR to AN = Yes
● External Reconciliation Enabled = Yes

The following table and two subsequent illustrations explain the transaction flow for configuration option 5. The
first illustration is a diagram of invoice and IR transaction flow for POs against Ariba Network. The second
illustration is a diagram of invoice and IR transaction flow for POs against a private supplier configured for email or
fax.

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoice is NOT sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are sent to Ariba Network IRs NOT sent to Ariba Network

IR status is set to Awaiting Reconciliation from External IR status is set to Paying.

ERP.

Invoice and IR transaction flow for POs against Ariba Network supplier

The illustration is a diagram of invoice and IR transaction flow for POs against Ariba Network.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 21
Invoice and IR transaction flow for POos against private supplier (Configured with Email or Fax)

The illustration is a diagram of invoice and IR transaction flow for POs against a private supplier configured for
email or fax.

Spend analytics and invoicing workflows configuration guide

22 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Configuration option 6

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = No

● Send IR to AN = Yes
● External Reconciliation Enabled = No

The following table and illustrations explain the transaction flow for configuration option 6.The first illustration is a
diagram of invoice and IR transaction flow for POs against Ariba Network. The second illustration is a diagram of
invoice and IR transaction flow for POs against a private supplier configured for email or fax.

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoice is NOT sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are sent to Ariba Network IRs NOT sent to Ariba Network

IR status is set to Paying. IR status is set to Paying.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 23
Invoice and IR transaction flow for POs against Ariba Network supplier

The illustration is a diagram of invoice and IR transaction flow for POs against Ariba Network.

Invoice and IR transaction flow for POs against private supplier (Configured with Email or Fax)

The illustration is a diagram of invoice and IR transaction flow for POs against a private supplier configured for
email or fax.

Spend analytics and invoicing workflows configuration guide

24 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Configuration option 7

This configuration is invalid and not recommended.

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = No

● Send IR to AN = No
● External Reconciliation Enabled = Yes

The following table explains the transaction flow if configuration option 7 is deployed.

This is an invalid configuration and Ariba does not recommend this parameter combination.

The following table explains the transaction flow:

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are sent to Ariba Network Invoice is NOT sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are NOT sent to Ariba Net­ IRs NOT sent to Ariba Network
work

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 25
Supplier Type

IR status is set to Awaiting Reconciliation from External IR status is set to Awaiting Reconciliation from External ERP
ERP

Configuration option 8

In configuration setting option 8, customers use the OK2Pay file and the Ariba Integration Toolkit for all
communications between the Ariba Procurement Solution and the external ERP system.

If a customer site is configured as follows:

● Send Invoice And Payments For Private Supplier To AN = No

● Send IR to AN = No
● External Reconciliation Enabled = No

The following table explains the transaction flow:

Supplier Type

Ariba Network Supplier (having AN ID) Private Supplier (Configured with Email or Fax)

Invoices are NOT sent to Ariba Network Invoices are NOT sent to Ariba Network (after Quick Enablement)

Invoice reconciliations (IRs) are NOT sent to Ariba Net­ IRs NOT sent to Ariba Network
work

IR status is set to Paying. IR status is set to Paying.

Spend analytics and invoicing workflows configuration guide

26 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Ariba Network Configurations
Ariba Customer Success Managers or Account Managers must ensure that Ariba Network is properly configured.

In this section:

Configuration requirements for new customers [page 28]

Configuring SAP Ariba solution end point [page 29]

Configuring document routing [page 35]

Considerations for configuring document routing [page 38]

Default document routing reference [page 38]

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 27
Configuration requirements for new customers
For new customers sites you must ensure that Ariba Network is properly configured.

Specifically, for a merged Ariba Procurement Solutions environment ensure that the customer:

● Has an Ariba Network Buyer account enabled for Open Network

● Is a designated SAP Ariba Invoice Management Buyer
● Is enabled as an SSP Buyer
● Is configured with Ariba On Demand Solution End Point
● Has the site reviewed for correct document routing.

Optionally the customer site may also be:

● Enabled for multi-ERP support (optional)

● Enabled for multi-end point support (optional)

 Note

This configuration is not mandatory if a site is deployed with a combination of SAP Ariba Buying and Invoicing
and SAP Ariba Catalog solutions.

How to enable a Buyer Account for Ariba Open Network

When a Buyer account is enabled for Ariba Open Network, data flow can be established between Ariba Network and
an external ERP system.

Prerequisites

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

 Note

A Buyer account must be on the Ariba Open Network for any data to flow between Ariba Network and an
external ERP system.

Procedure

1. Log into the Ariba Network Administration module as an Ariba Administrator, and search for the required Buyer
account.
2. Select the required user from the search results and click User Detail.
3. In the User Detail - Buyer Information page that is displayed, go to the Ariba Open Network and do the
following:

Spend analytics and invoicing workflows configuration guide

28 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 ○ Select Convert to Ariba Open Network and click Update.
○ Select Designate buyer as Ariba Invoice Pro Buyer. This initiates all invoice and invoice-related (IRs and
payments) document flows.

How to enable the Account as an SSP Buyer

When a Buyer account is enabled as an SSP Buyer, Ariba Network can initialize the flow of all procurement-related
documents such as receipts, ERP receipts, orders, invoice and invoice-related documents, and payment
documents.

Prerequisites

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log into the Ariba Network Administration module as an Ariba Administrator, and search for the required Buyer
account.
2. Select the required user from the search results, and click User Detail.
3. In the User Detail - Buyer Information page that is displayed, go to the SSP Buyer section and select the
Designate this buyer as an SSP Buyer? check box, and click Update SSP Info.

Configuring SAP Ariba solution end point

All document routing is based on end points. As an Ariba Administrator, you configure end points for each Buyer
account on Ariba Network to manage and control the flow of data from an Ariba account to each of the various
external ERP systems connected to it.

An end point in Ariba Network acts as a document routing placeholder that ensures documents from Ariba
Network are sent to the required destination.

 Note

Prior to release 12s2, all documentation flows between an SAP Ariba Buying solutions and an external ERP via
Ariba Network were transacted using the Ariba service provider account. The service provider account for
document transactions is deprecated.

If a Buyer account is not enabled for end point support, the value that a customer specified in the Profile URL field
under cXML Setup is used as the default end point.

The default end point is the destination for all documents routed from Ariba Network for which a specific end point
cannot otherwise be determined or is specified.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 29
A buyer account on Ariba Network may have any of the following administration configuration options:

Convert to Ariba Open Network Enable End Point Support Multiple ERP Support

Yes No No

Yes No Yes

Yes Yes No

Yes Yes Yes

Related Information

How to configure the Ariba End Point when a Buyer Account is enabled for Ariba Open Network [page 30]
How to configure the Ariba End Point for a multi-ERP Environment [page 31]
How to configure Ariba End Points for a Buyer Account configured for Multiple ERP Support [page 33]
How to configure Ariba End Points when a Buyer Account is configured for SAP Ariba Invoice Management [page
34]

How to configure the Ariba End Point when a Buyer Account is

enabled for Ariba Open Network

When the Ariba Network Buyer account is enabled for Ariba Open Network, this topic describes how to configure
the Ariba end point to manage and control the flow of data from an Ariba account to each of the various external
ERP systems connected to it.

Prerequisites

This task applies to a Buyer account with the following configuration settings:

● Convert to Ariba Open Network = Yes

○ Designate buyer as Ariba Invoice Pro buyer = Yes
○ Is SSP Buyer? = Yes/No
● Enable End Point Support = No
● Enable Multiple ERP Support = No

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log in to the customer’s Ariba Network Buyer account and click Manage Profile to display the Configuration
page.

Spend analytics and invoicing workflows configuration guide

30 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 2. Click cXML Setup.

If you have configured this buyer account as an SAP Ariba Invoice Management customer, the cXML Setup
page displays the Configure Ariba On Demand Solution End Point button. Click this.
3. The Configure End Point page is displayed. Enter an appropriate End Point ID value.
4. In the Authentication Method section, enter the Shared Secret and confirm the same again.

 Note

Ensure that the shared secret you enter here is the same as what has been specified at the customer site
during the SAP Ariba Buying solutions deployment.

5. The Profile and Post URL fields are populated by default. Retain these values. Click Save.
6. Click Configure Document Routing to review and edit the document routing settings.

Related Information

Configuring document routing [page 35]

How to configure the Ariba End Point for a multi-ERP Environment

When the Ariba Network Buyer account is configured for a multi-ERP environment, this topic describes how to
configure the Ariba end point to manage and control the flow of data from an Ariba account to each of the various
external ERP systems connected to it.

Prerequisites

This task applies to a Buyer account with the following configuration settings:

● Convert to Ariba Open Network = Yes

○ Designate buyer as Ariba Invoice Pro buyer = Yes
○ Is SSP Buyer? = Yes/No
● Enable End Point Support = No
● Enable Multiple ERP Support = Yes

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log in to the customer’s Ariba Network Buyer account and click Manage Profile to display the Configuration
page.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 31
2. Click Business Application IDs. This page displays the “Default” application ID that is automatically created
by Ariba Network.

You can click Edit to change the system-generated name and save the changes.
3. Click Create to add more System IDs to the multi-ERP environment.
4. Click the corresponding System ID link for which you want to configure the Ariba end point.
5. In the Manage Business Application ID page that displays, click Configure Ariba On Demand Solution End
Point.

 Note

The Configure Ariba On Demand Solution End Point button is available only if you have performed the
following in the Ariba Network Administration module:

a. Search for this Buyer account, and go to the User Detail - Buyer Information page.
b. Under the Ariba Open Network and SSP Buyer sections, select the required System IDs and click Update
Invoice Pro Info and Update SSP Info respectively. This action automatically configures the Ariba end
points for the selected System IDs (ERPs).
6. The Configure End Point page is displayed. Enter an appropriate End Point ID value.
7. In the Authentication Method section, enter the Shared Secret and confirm the same again.

 Note

Ensure that the shared secret you enter here is the same as what has been specified at the customer site
during the SAP Ariba Buying solutions deployment.

8. The Profile and Post URL fields are populated by default. Retain these values. Click Save.
9. Click Configure Document Routing to review and edit the document routing settings.

 Note

The Configure Document Routing action is available only when you login to the Buyer account as the Ariba
Administrator.

Related Information

Configuring document routing [page 35]

Spend analytics and invoicing workflows configuration guide

32 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
How to configure Ariba End Points for a Buyer Account configured
for Multiple ERP Support

When the Ariba Network Buyer account is configured for multiple ERP support, this topic describes how to
configure Ariba end points to manage and control the flow of data from an Ariba account to each of the various
external ERP systems connected to it.

Prerequisites

This task applies to a Buyer account with the following configuration settings:

● Convert to Ariba Open Network = Yes

● Enable End Point Support = Yes
● Enable Multiple ERP Support = No

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log into your Ariba Network Buyer account and click on Manage Profile.
2. In the Configuration page that is displayed, click Business End Points (cXML Setup).
3. The Configure Business End Points page is displayed.

When enabling the account for Open Network, if you have selected the following options and update the
information:

○ Designate buyer as Ariba Invoice Pro buyer = Yes

○ Is SSP Buyer? = Yes
Then, Ariba Network automatically configures the Ariba On Demand Solution End Point.
4. If the above-mentioned options have not been selected, this page will not list any end point. Click Create to add
more end points to the configuration.
5. A confirmation dialog box is displayed asking you to confirm copying of the existing cXML setup details. Click
Yes.
6. The Configure End Point page is displayed. On this page, specify the following:

○ End Point ID: Enter a unique end point name

○ Profile URL: The profile URL that was specified during the creation of your account is populated by default.
If you want to change this, click Reset Profile and specify a new URL.
○ Post URL: Similar to the Profile URL, this value is also populated by default. You can change this as
required.
7. Click Save.
8. Click Configure Document Routing to review and edit the document routing settings.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 33
  Note

The check boxes that provide copy routing options for each document type in the Document Routing page
are available only when you login to the Buyer account as the Ariba Administrator.

Related Information

Configuring document routing [page 35]

How to configure Ariba End Points when a Buyer Account is

configured for SAP Ariba Invoice Management

When the Ariba Network Buyer account is configured for SAP Ariba Invoice Management, this topic describes how
to configure Ariba end points to manage and control the flow of data from an Ariba account to each of the various
external ERP systems connected to it.

Prerequisites

This task applies to a Buyer account with the following configuration settings:

● Convert to Ariba Open Network = Yes

○ Designate buyer as Ariba Invoice Pro buyer = Yes
○ Is SSP Buyer? = Yes/No

 Note

When you make these selections and click Update Info in the Ariba Network Administrator module,
Ariba Network instantly configures the Ariba end point, and creates the Default System ID.

● Enable End Point Support = Yes

● Enable Multiple ERP Support = Yes

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log into your Ariba Network Buyer account and click on Manage Profile.
2. In the Configuration page that is displayed, click Business Application IDs and End Points (cXML Setup).
3. The Configure Business Application IDs page is displayed. This page lists the default System ID and any other
system ID that you may have created.

Spend analytics and invoicing workflows configuration guide

34 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 4. Click Create to add a new System ID to the configuration.
5. After creating the System ID, you can do one of the following:

○ Go to this Buyer account in the Ariba Network Administrator Module; under the Ariba Open Network and
SSP Buyer sections, select the new System ID that you have created and click Update Invoice Pro Info
and Update SSP Info respectively. This action automatically configures the Ariba end points for the
selected System IDs (ERPs).
○ Manually create end points for each System ID.
6. To manually create an end point, click the System ID link for which you want to configure an end point.
7. The Manage Business Application ID page is displayed. Click the End Point tab.
8. A confirmation dialog box is displayed asking you to confirm copying of the existing cXML setup details. Click
Yes.
9. The Configure End Point page is displayed. On this page, specify the following:

○ End Point ID: Enter a unique end point name

○ Profile URL: The profile URL that was specified during the creation of your account is populated by default.
If you want to change this, click Reset Profile and enter a new URL.
○ Post URL: Similar to the Profile URL, this value is also populated by default. You can change this as
required.
10. Click Configure Document Routing to review and edit the document routing settings.

 Note

The check boxes that provide copy routing options for each document type in the Document Routing page
are available only when you login to the Buyer account as the Ariba Administrator.

Related Information

Configuring document routing [page 35]

Configuring document routing

An end point in Ariba Network acts as a document routing placeholder that ensures documents from Ariba
Network are sent to the required destinations. When the Ariba end point is configured, Ariba Network automatically
configures a default routing of all documents.

End point destinations can be external ERP systems and/or the SAP Ariba solution. As an SAP Ariba Administrator
you can review default document routing and make changes to the target destinations, if required.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 35
How to configuring document routing

You can configure document routing to ensure that documents from Ariba Network are sent to specific locations.

Prerequisites

You must be an Ariba Customer Success Manager or Account Manager to perform this task.

Procedure

1. Log into the Ariba Network Buyer account as an Ariba Administrator.

2. Depending on how the Buyer account has been configured, click the cXML Setup link or the Business
Application IDs link and navigate to the End Point page. Click Configure Document Routing.

Spend analytics and invoicing workflows configuration guide

36 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 Ariba Network configures a default routing for all documents at the time of the end point creation. You can
review this routing and change it based on the customer requirement.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 37
Considerations for configuring document routing

If you choose to modify default document routing there are a number of considerations to keep in mind.

Considerations include:

● Ariba Network creates the “Default” end point when the Buyer account is configured for Ariba Open Network
and is enabled as an Invoice Pro or SSP Buyer. This default end point refers to the external ERP system with
which Ariba Network communicates.
● If the Buyer account is not configured for multi-ERP, then the Default end point is automatically considered to
be the ERP end point.
● Ariba Network creates the Ariba On Demand Solution End Point (default name “Ariba”) as soon as the Buyer
account has been configured as an “Invoice Pro User” and/or an “SSP Buyer”. This means that the Ariba end
point becomes the gateway for all documents to flow between Ariba Network and the SAP Ariba solution.
● Typically, in a multi-ERP environment, multiple end points are created (for each ERP system). These end points
are available for selection in the dropdown list.
● Select the check box corresponding the documents that require copies to be delivered to certain end points
based on customer requirements.

Default document routing reference

A table lists the default routing of the following document types:

Document Type Destination Copy Routing Result

Order Confirmation Purchase Order Send a copy to the destination of the pur­ Routes all order confirmations (OCs) to
Origin chase order copy the destination (SAP Ariba Buying solu­
tions or external ERP) where the PO was
created.

Routes a copy of the OC to the destina­

tion where the PO copy was sent.

Ship Notice Purchase Order Send a copy to the destination of the pur­ Routes all ship notices to the destination
Origin chase order copy (SAP Ariba Buying solutions or external
ERP) where the PO was created.

Routes a copy of the Ship Notice to the

destination where the PO copy was sent.

PO-flip Invoice Purchase Order Send a copy to the destination of the pur­ Routes all PO-flip invoices to the destina­
Origin chase order copy tion (SAP Ariba Buying solutions or exter­
nal ERP) where the PO was created.

Routes a copy of this invoice to the desti­

nation where the PO copy was sent.

Non-PO Invoice Ariba NA Routes all non-PO based invoices to the

SAP Ariba Buying solutions.

Summary Invoice of Ariba NA Routes all summary invoices to the SAP

POs Ariba Buying solutions.

Spend analytics and invoicing workflows configuration guide

38 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 Document Type Destination Copy Routing Result

Invoice Reconcilia­ Default NA Routes all invoice reconciliation docu­

tion ments to the default external ERP sys­
tem.

Payment Proposal Default ● Send a copy of a payment proposal If the PP is originating in the SAP Ariba
(PP) originating in the Ariba on de­ Buying solutions, a copy of this document
mand solution to the selected end is sent to the destination end point that is
point selected.
● Send a copy of a payment proposal If the PP is originating in the external ERP
originating in the external system to
system, then a copy is sent to the SAP
the Ariba on demand solution
Ariba Buying solutions.

Payment Proposal Payment Proposal Send a copy to the destination of the pay­ Routes all PP updates to the destination
Update Origin ment proposal copy where the PP was created.

Routes a copy of the PP update to the

destination where the PP copy was sent.

Payment Remit­ Default ● Send a copy of a payment remit­ If the payment remittance is originating in
tance tance originating in the Ariba on de­ the SAP Ariba Buying solutions, a copy of
mand solution to the selected end this document is sent to the destination
point end point that is selected.
● Send a copy of a payment proposal If the payment remittance is originating in
originating in the external system to
the external ERP system, then a copy is
the Ariba on demand solution
sent to the SAP Ariba Buying solutions

Receipt Default Send a copy of a receipt originating in the If the receipt is created in an external ERP
external system to the Ariba on demand system, then Ariba Network routes a copy
solution of this receipt to the SAP Ariba Buying
solutions.

ERP Requisition Ariba NA If a requisition is created in an external

ERP system, then Ariba Network routes a
copy of this document to the SAP Ariba
Buying solutions.

Configuration requirements for existing SAP Ariba

Invoice Management customers migrating to a
merged site environment
Existing SAP Ariba Invoice Management customers migrating to a merged site environment must ensure that the
Ariba Network account is properly configured.

Ariba Network must be:

● Enabled as an SSP Buyer

● Configured with the Ariba On Demand Solution End Point
● Configured with the correct document routing settings

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 39
Optionally the customer site may also be enabled for:

● Enabled for Multi-ERP Support

● Enabled for Multi-End Point Support

To configure your site for a merged SAP Ariba procurement solutions site, contact your Designated Support
Contact log a service request to have an Ariba Customer Support representative follow up.

Performing cXML setup

If you have already configured your Business Application IDs there are three more steps to take.

These include

● Configuring end point integration.

 Note

Contact your Ariba Customer Support Representative for assistance in configuring your end point
integration.

● Configuring the new Ariba On Demand Solution end point.

● Configuring Document Routing

Buyer administrators can configure end points in Ariba Network to manage and control the flow of data from an
Ariba account to each of the various systems connected to it. An end point in Ariba Network acts as a document
routing placeholder that ensures documents from Ariba Network are sent to the required destination.

About Transaction Flows

Depending on your SAP Ariba Buying solutions there are a number of possible transaction flows to be aware of.

The following table lists transaction flows and the Ariba Solution(s) they apply to:

Transaction FLow Ariba Solution

Requisition-to-Invoice Reconciliation [page 41] SAP Ariba Buying and Invoicing only

Invoice-to-Invoice Reconciliation [page 42] SAP Ariba Invoice Management only

Requisition-to-Payment [page 44] SAP Ariba Buying and Invoicing and SAP Ariba Invoice Manage­
ment

About Purchase Order Filtering [page 45] SAP Ariba Buying and Invoicing and SAP Ariba Invoice Manage­
ment

About Receipt Filtering [page 47] SAP Ariba Buying and Invoicing and SAP Ariba Invoice Manage­
ment

Spend analytics and invoicing workflows configuration guide

40 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Requisition-to-Invoice Reconciliation

In SAP Ariba Buying and Invoicing you can have requisition-to-invoice reconciliation transaction flows.

The following diagram illustrates this flow:

The following table explains the illustration’s numbered steps in the transaction flow:

Step Process

1 Users create requisitions in SAP Ariba Buying and Invoicing and approve them for purchase orders to be cre­
ated.

1a Alternatively, users also perform a requisition import to load requisitions created in an external ERP system.
These are again processed as purchase orders.

2 All purchase orders (including ERPCC orders, direct orders, and PCard orders) are processed and sent to Ariba
Network in cXML format.

2a Ariba Network then routes these orders (using cXML) to the appropriate suppliers.

2b Simultaneously, users can export all orders to the external ERP using the Export Purchase Orders and Export
Purchase Orders to ERP data export tasks.

3 and 4 Suppliers send Order Confirmations (OCs) and Advance Ship Notices (ASNs) to Ariba Network (using cXML).

3a and 4a Ariba Network then routes these OCs and ASNs to SAP Ariba Buying and Invoicing (using cXML)

5 Receipts are created in SAP Ariba Buying and Invoicing and/or imported from an external ERP system.

6 and 6a Suppliers send invoices to Ariba Network, which are then routed to SAP Ariba Buying and Invoicing.

6b Alternatively, users create invoices in SAP Ariba Buying and Invoicing.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 41
Step Process

7 Users then send the Invoice Reconciliation (IR) documents to an external ERP system using the OK2Pay file
(Export Payment Requests export task). The IRs are moved to the Paying status.

8 The remittance files are generated in the external ERP and imported into SAP Ariba Buying and Invoicing using
the Import Remittance import task. The IRs then are processed to the Paid or Rejected status depending on the
payment remittance files.

Invoice-to-Invoice Reconciliation

In SAP Ariba Invoice Management you can have invoice-to-invoice reconciliation transaction flows.

The following diagram illustrates this flow:

The following table explains the illustration’s numbered steps in the transaction flow:

Step Process

1 The external ERP system sends purchase orders to Ariba Network in cXML format.

1a Ariba Network routes these purchase orders to the appropriate suppliers

1b Ariba Network simultaneously routes a copy of the purchase orders to SAP Ariba Invoice Management.

Spend analytics and invoicing workflows configuration guide

42 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 Step Process

2 and 3 Supplier sends the order confirmations (OCs) and advance ship notices (ASNs) to Ariba Network.

2a and 3a These OCs and ASNs are routed to the external ERP from Ariba Network.

2b and 3b The copies of the OCs and ASNs are routed to SAP Ariba Invoice Management from Ariba Network.

4 and 4a External ERP sends the receipt to Ariba Network (4). Ariba Network routes a copy of the receipt to SAP Ariba
Invoice Management (4a).

5 and 5a Supplier sends electronic invoices to Ariba Network (5). Alternatively, users also create invoices in SAP Ariba
Invoice Management.

5b Ariba Network sends invoices received from suppliers to SAP Ariba Invoice Management.

6 and 6a Users create the invoice reconciliation (IR) documents in SAP Ariba Invoice Management and send them to
Ariba Network(6). The IRs are then sent from Ariba Network to the external ERP system (6a).

The external ERP then sends a status update request (SUR) to SAP Ariba Invoice Management via Ariba Net­
work.

7 The external ERP generates the Payment Proposal Request (PPR) and sends it to Ariba Network.

7a Ariba Network routes this PPR to SAP Ariba Invoice Management

With every PPR update that is sent from Ariba Network, SAP Ariba Invoice Management sends back an acknowl­
edgment to the external ERP via Ariba Network.

8 and 8a The external ERP then generates the Payment Remittance Request (PRR) and routes it to SAP Ariba Invoice
Management via Ariba Network.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 43
Requisition-to-Payment
In SAP Ariba Buying and Invoicing and SAP Ariba Invoice Management you can have requisition to payment
transaction flows.

The following diagram illustrates this flow:

The following table explains the illustration’s numbered steps in the transaction flow

Step Process

1 Requisitions are downloaded from an external ERP system electronically into Ariba Network using the Enhanced
Requisition Import feature (cXML format).

You can also create requisitions on your SAP Ariba Buying solutions (existing behavior).

1a Ariba Network routes these imported requisitions to the SAP Ariba Buying solutions (cXML format).

2 All purchase orders processed in the SAP Ariba Buying solutions using the ERP order method (including direct
orders, and PCard orders) are sent to the external ERP system using the File or Web Services channel.

2a All purchase orders processed using the ERPCC order method are routed to Ariba Network from the SAP Ariba
Buying solutions.

3 Purchase orders created in the external ERP system are routed to Ariba Network.

3a These ERP originating POs are routed to the SAP Ariba Buying solutions as Copy Orders.

Spend analytics and invoicing workflows configuration guide

44 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
 Step Process

Supplier sends the order confirmations (OCs) and ship notices to Ariba Network.

These OCs and ship notices are routed to the external ERP from Ariba Network.

The copies of the OCs and ship notices are routed to the SAP Ariba Buying solutions from Ariba Network.

4 Receipts are created in SAP Ariba Buying solutions are exported to the external ERP system using the File or
Web Services channel.

5 Receipts that are created in the external ERP system are routed to Ariba Network in cXML format.

5a Only the receipts that are created in the external ERP system are downloaded into Ariba Network and routed to
the SAP Ariba Buying solutions as Copy Receipts (in cXML format).

6 Supplier creates invoices on Ariba Network. Alternatively, users also create invoices in the SAP Ariba Buying sol­
utions.

6a Ariba Network sends invoices created by suppliers to the SAP Ariba Buying solutions.

7 Invoices that are created in the external ERP system are routed to Ariba Network.

8 Invoices that are created in the SAP Ariba Buying solutions are routed to Ariba Network.

9 Blanket Purchase Orders (BPO) created in an external ERP system are routed to Ariba Network.

9a Such BPOs are routed to the SAP Ariba Buying solutions.

10 Invoice Reconciliation (IR) documents created in the SAP Ariba Buying solutions are routed to Ariba Network.

10a The IRs are then sent from Ariba Network to the external ERP system.

The external ERP system then sends status update requests (SUR) to the SAP Ariba Buying solutions via Ariba Network.

11 The external ERP system generates the Payment Proposal Request (PPR) and routes it to Ariba Network.

11a Ariba Network routes this PPR to the SAP Ariba Buying solutions.

With every PPR update that is sent from Ariba Network, the SAP Ariba Buying solutions sends back an acknowl­
edgment to the external ERP system via Ariba Network.

12 The external ERP system then generates the Payment Remittance Request (PRR.)

12a This PRR is then routed from Ariba Network to the SAP Ariba Buying solutions.

About Purchase Order Filtering

Purchase Order filtering is handled either through the ERP order method or the ERPCC order method.

PO Processing Using the ERP Order Method

A graphic illustrates the purchase orders transaction flow when the SAP Ariba Buying solutions uses the ERP order
method to process the requisition.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 45
PO Processing Using the ERPCC Order Method

A graphic illustrates the purchase orders transaction flow when the SAP Ariba Buying solutions uses the ERPCC
order method to process the requisition.

Spend analytics and invoicing workflows configuration guide

46 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
About Receipt Filtering
Receipt filtering occurs for receipts created in the SAP Ariba Buying solutions or in an external ERP system.

Receipts Created in the Ariba Procurement Solution

A graphic illustrates the receipt transaction flow when receipts are created in the SAP Ariba Buying solutions.

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 47
 Spend analytics and invoicing workflows configuration guide
48 CONFIDENTIAL Expansion of Spend Analytics and Invoicing Workflows
Receipts Created in an External ERP System

A graphic illustrates the receipt transaction flow when receipts are created in an external ERP system:

Spend analytics and invoicing workflows configuration guide

Expansion of Spend Analytics and Invoicing Workflows CONFIDENTIAL 49
Revision history

The following table provides a brief history of the updates to this guide. Ariba updates the technical documentation
for its On Demand solutions if:

● software changes delivered in service packs or hot fixes require a documentation update to correctly reflect the
new or changed functionality
● the existing content is incorrect or user feedback indicated that important content is missing

Ariba reserves the right to update its technical documentation without prior notification. Most documentation
updates will be made available in the same week as the software service packs are released, but critical
documentation updates may be released at any time.

Month/Year of Update Updated Chapter/Section Short Description of Change

May 2019 Service Level Parameter Configuration Merged into Parameter Configurations: Ariba Internal Task
topic

n/a Updated topic naming convention

Spend analytics and invoicing workflows configuration guide

50 CONFIDENTIAL Revision history
Important Disclaimers and Legal Information

Hyperlinks
Some 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 Features

Experimental 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 Code
Any 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 Language
We 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.

Spend analytics and invoicing workflows configuration guide

Important Disclaimers and Legal Information CONFIDENTIAL 51
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