ARIBA INTEGRATION

AR820
1. Products / Solutions
Strategic Sourcing Procure to Pay or Procurement Network
Ariba Sourcing Catalogs Order and Invoice
Transmission
Ariba Contracts Requisitioning Catalogs
Ariba Supplier Information and Ordering RFX Responses
Performance Management
Receiving
Invoicing
2. Ariba Commerce Cloud
A web-based platform for efficient and effective global commerce between
companies.
On-demand technology to optimize the commerce lifecycle
Useful in
o Controlling costs
o Minimize Risks
o Improve profits
o Optimize Cash Flow
o Increase Sales
3. Ariba Procure-to-Pay mainly used in Cost Reduction and Fiscal Control &
Complaisance.
4. Ariba Discount Professional mainly used in Cash Management.
5. Aribal Sourcing and Contracting Solutions:
o Ariba Sourcing -> Creates Events to get the information and Pricing
from suppliers.
o Ariba Discovery -> Identify additional suppliers for sourcing events.
o Ariba Contract -> Author, negotiate and execute the contract
documents with suppliers.
o Ariba Supplier Information Management -> Manage supplier data
and On-Boarding.
o Ariba Supplier Performance Management -> Creates reports, surveys
for performance evolution against KPIs.
6. The Ariba Commerce Cloud spans the entire commerce lifecycle from sourcing to
settlement and from market to receipt.
7. Ariba Procure-to-Pay(P2P) spans the entire lifecycle of a purchasing transaction from
requisitioning to ordering to receiving to invoicing and reconciliation
Contract -> Request -> Approve -> Order -> Receive -> Invoice -> Payment
8. Ariba Procure-to-Order(P2O) covers procurement lifecycle processes, except for
invoice reconciliation and payment.
 Contract -> Request -> Approve -> Order -> Receive
9. Ariba Procurement Content covers part of P2P process
Contract -> Request
10. Ariba Invoice Pro used for accounts payable automation
Invoice -> Payment
11. Standard Text is nothing but name of document which is created.
12. Italicized text represents an action that is performed.
13. With Ariba Network, it is possible to have comprehensive and up-to-date spend and
supplier management information and which in turn allows to work with the right
suppliers to lower the cost and minimize risks.
14. Ariba Network Portal for Buyers contains:
o Inbox -> Received from suppliers e.g. Invoices
o Outbox -> Sent to Suppliers e.g. POs
o Catalogs -> Catalogs from suppliers to download.
o Supplier Enablement -> Form a relationship with suppliers
o Administration -> Settings, Rules and Preferences
o Reports -> CSV reports about discounts, sales, quotes and suppliers.
15. Ariba Network Portal for Supplier contains:
o Home -> Contains informational widgets that needs attention e.g.
POs
o Inbox -> Received from Buyers
o Outbox -> Sent to Buyers
o Catalogs -> Public and Private catalogs for buyers
o Reports -> CSV reports for data including PO’s and Invoices.

16. In 3 ways we can integrate an ERP System and Ariba Procurement

o CSV File Transfer using Ariba Integration Tool Kit
o SAP Direct Connectivity
o Web Services
17. Examples of Master Data Types in Ariba Procurement Integration
o Organization
o Material Groups
o Exchange Rates
o Vendor Master
o Users and Groups
o Accounting
o Taxes
18. Ariba Integration Tool Kit can be used as Standalone tool or as part of Process
Orchestration (SAP PI). It Contains 2 Components
o Data Transfer Tool -> Used to transfer master data (in CSV format)
from file server to Ariba solutions
o DB Connector
19. Additional types of master data for Ariba Procurement includes
o Unit of Measure
o Supplier Bank Information
o Purchasing Units
20. Transactional Data represents electronic business documents that are modeled in
the Ariba systems.
o Requisitions
o Invoices
o Receipts
o Purchase Orders
21. The transactional data documents can be exported from Ariba or can be created
in Ariba with integration to an external system.
22. Transactional Data in Ariba can be exported using
o File Channel ->
i. Uses Data Transfer Tool to export the data in CSV format to the
ERP system from Ariba Procurement Solution for each
integration event.
ii. The integration event extracts the data, converts the data to
a .CSV file and sends the file embedded in a MIME message to
the Data Transfer tool, which in-turn downloads the .CSV files
to the ERP System.
o Web Services -> Data is directly exchanged in real-time between the
Ariba Procurement Solutions and ERP or Middleware.
23. Integration Tool Kit
o Used to transfer .csv flat files.
o Uses HTTPS with encrypted shared secret or certificate-based
authentication
o Deployed at customer’s server with minimal system requirements.
o Can be deployed directly in SAP PI or Oracle Fusion
o ITK is not required to exchange csv tiles with Ariba. but most Ariba
Procurement customers use ITK because of ease of deployment
o It must be scheduled as there is no in-built functionality to schedule.
24. Web Services
o Via SOAP XML messages over HTTPS.
o Uses shared secret or certificate-based authentication.
o Allows for real-time integration of Ariba Procurement with SAP ERP
systems using SAP PI.
o Allows integration of Master and Transaction Data. But for master
data it is rarely used as it supports only some master data.
o WSDL is an XML format and is often used in combination with SOAP
and XML Schema to provide web services over the Internet.
o The SOAP URL is the endpoint on the Web Service.
25. SAP Direct Connectivity
 o ARBA/MASTER_DATA_EXPORT program can be used to transfer the
master data directly either in full load or incremental load to ARIBA
from SAP
o Posts a CSV/ZIP as an attachment to Ariba as an HTTP POST method
based on SOA.
o Uses shared secret authentication in SOAP Header.
o This program supports error handling and SLG1 logging.
26. SAP Transports
o These are ARIBA provided SAP Programs for master data export
extractions.
o These are scheduled programs which will generate a .csv files when
master data is exported from ERP system.
o With these programs not all integration points are covered
i. Some master data files (Payment Methods, Purchasing Units, etc.)
ii. Budget check files
iii. Requisition import

27. Mediated Connectivity Integration Method

o Used to integrate master and transactional data from SAP ERP to
Ariba Procurement Solution seamlessly using SAP PI.
o Can securely download the master data from SAP ERP to ARIBA
Procurement solution or Fieldglass using SOAP Messages through SAP
PI.
28. Master Data integration should be done via batch loads.
29. Transactional data integration should be with real time loads.
30. When custom tabular data is required within the Ariba solutions, need to create
custom Flex Master Data.

31. Suite Integration

o Is the integration between Ariba Procurement and Ariba Sourcing
and Contracts.
o Enables seamless integration of Contract Workspaces and Contract
Compliance documents.
o Provides a single logon location for Ariba users who access both
applications. This is handled by Ariba Procurement.
32. Changes when suite integration:
 o Contract requests(procurement) must be created in Contract
Workspaces. They cannot be created directly.
o Users should be managed in Ariba Procurement only.
o User Passwords must be regenerated when suite integrating an Ariba
Sourcing realm that is already live.
o Contract Request in stand alone Ariba Procurement system will be
known as Contract Terms in Suite Integration.
o The approval process can be in both contracts or procurement
systems.
o It is recommended to create a very simple Contract Workspace
template to support the creation of a Contract Terms file without any
required tasks or documents.

33. Using Suite Integration, we can only transfer

o Users, system and custom groups, dashboards, and log-in ability (user
ID is synchronized)
o Suppliers (only the Common Supplier level)
o Commodity Codes, Units of Measure, Currencies
o Reporting
o Common data (top level hierarchy) is only synchronized for users and
suppliers.
34. We can only integrate two realms (Ariba Sourcing and Ariba procurement) only
when the Ariba Network ID and Default Currency are matched.
35. While doing the suite integration, should include resources from BOTH the Sourcing
and Procurement teams.
36. For suite integration, Partitioned User data must exist tor all the users tor successful
user logons in both the systems.
37. For suite integration, Branding (e.g. company logo) must be performed separately
for Sourcing and Procurement.
38. Various Integration Methods in ARIBA:
o Manual file (CSV) transfer
o Automated file transfer using the Integration Toolkit or SAP Direct
Connectivity
o Real-time data transfer with Web Services
o cXML Channel
o HTTP Requests (for Sourcing projects only)
39. The Integration Toolkit is used to synchronize below master data with Ariba Sourcing:
o Users
o Commodities
o Departments
o Exchange Rates
o Regions
o Suppliers and Supplier Extended Profiles
o Sourcing Event (import)
o Contract Workplace Header
40. The Webservices are used to synchronize below transactional data with Ariba
Sourcing:
o Users
o Suppliers and Supplier Extended Profile
o Sourcing Headers and Full Projects (import/update)
o Sourcing Events (import) and Awards (export)
o Attachments
o Contract Workspace Header (export)
o Project Documents (import)
41. For better performance, while loading the master data always set filters to specify
the criteria for exporting the data.
42. REST Architecture model to exchange data with a master data governance system
or ERP.
43. A sourcing request is created derived from the RFQ generated in ERP. This request is
based on the cXML document.
44. Process - Sourcing Event Export to SAP ECC
o Create a Sourcing Event directly or from a Sourcing Request.
o Add line items from the Material Master if they have not been added
automatically.
o Publish the event to suppliers and receive bids.
o Award the event to suppliers
o The Award is pushed to the Ariba Network and is added to the Buyer
Pending Queue.
o SAP ECC retrieves the data from the queue and creates an Outline
Agreement or Purchase Order.

45. Supplier Master Data Integration with SAP MDG

o Ariba Supplier Information Management (SIM) can integrate supplier
data with SAP MDG using Direct Connectivity or Mediated
Connectivity.
 o The integration is bidirectional and can be full or incremental.
o Suppliers in Ariba can be marked as “Integrated” or not; only
Integrated suppliers are synchronized with SAP MDG.
o Supplier Organizations within Ariba SIM must have a Supplier User in
order to be exported to SAP MDG.
o Supplier registration is handled through the Ariba Network and
replicated to SIM.
Note: Read 49 and 50 Pages in PDF.

46. ARIBA Procurement can be integrated natively with

o SAP CRP
o SAP S/4 HANA
o SAP NetWeaver PI
o Oracle Financials
o Oracle Fusion
o PeopleSoft
o SAP Fieldglass
47. For integrating the Data Dictionary Master data, the .CSV integration files must
contain
o What files define the integration event?
o Column (Field Names) Names for each file
o Sample values
o Referential Integrity
48. The Data Dictionary Master Data integration
o Automatically includes the custom fields and flex master data types
o Considers Import Batch Data option by default (i.e. batch loads)
49. Ariba recommends you use Import Batch Data to import your data because it always
runs data import tasks in the proper order. The sequence of execution for each task
is very important in data integration.
50. Some data import tasks depend on the data imported by other data import tasks.
So When running individual data import tasks, any object referenced in the CSV file
must already exist in the Ariba system.
51. User data is typically imported using the Import User Data (Consolidated File) task,
UserConsolidated.csv. This file contains both enterprise and ERP-specific user
information.
52. Below ERP User data is loaded
o Name and email address
o Supervisor
o Default accounting
o Default language and currency
o ShipTo Address
o P-Cards
53. The Import User Data (Consolidated File) imports data from a single CSV file and
contains data consolidated from multiple CSV files used by multiple data import
 tasks. It allows importing all user-group mapping related data using a single CSV file
instead of several different files.
54. Users and Suppliers are required master data for Ariba implementations.
55. Supplier organization stores general information about the supplier, such as preferred
language and supplier profile information. There is a 1:1 mapping between suppliers
and supplier organizations in ERP. These suppliers are known as partitioned or ERP
supplier
56. Supplier locations represent a physical location for a company and contains all the
address details properly.
57. Supplier Data can be loaded using single or multiple tasks using Import Supplier Data
(Consolidated file, SupplierConsolidated.csv). These tasks load both Common and
Partitioned Suppliers.
58. SupplierConsolidated.csv which is used to load the supplier data, will run by default
as part of SAP Direct Connectivity. But this file can also be run manually.
59. In ARIBA Sourcing, the suppliers are connected using a Supplier ID. If any supplier is
not available, a new common supplier will be created.
60. Ariba contains a base set of Unit of Measures based on UN/CEFACT standard.
UnitsOfMeasureMap.csv can be used to map and link the external UOM with Ariba
UOM.
INTEGRATION POINTS
Transaction Type P2O P2P
Purchase Order Export Required Optional
Receipt Export Required Optional
Receipt Import Optional Optional
Payment Request Export Not Applicable Required
Remittance Advance Export Not Applicable Optional

61. Purchase Order Integration in Procurement:

o ERP Order Method with Acknowledgement
i. PO is created in ordering status (PR) and retrieved from ERP
ii. PO is sent with ERP PO No as an ID
iii. If error occurs, requisition will be returning as composing state
o ERP Order Method without Acknowledgement
i. PO is created with an ARIBA PO ID
ii. PO is sent via ARIBA Network before ERP Response
iii. PO is copied back to ERP
o Direct Order Method
i. Create PO and sent to ARIBA Network
62. Receipt Integration:
o It can be imported from external system or can be exported from
ARIBA. 3 Options
o ERP Receipt Export with Acknowledgement
i. Errors must be handled in ARIBA Procurement
o ERP Receipt Export without Acknowledgement
i. Errors can be handled in ARIBA or ERP
 o Standard Receipt Export
63. Payment Request (OK2Pay) Integration: 3 Options
o Default
i. No response is expected from ERP
ii. Error are handled in External System
o Direct
i. Status is expected from ERP via webservices
o Asynchronous
i. Status is expected from ERP via file channels
64. Remittance Advance (Payment Details) Integration:
o Imported to P2P regardless of payment request send method used.
o Can be in paid or cleared status. This status is dependent on the
clearing period defined in payment method. The status will only
change after the nightly scheduled batch job runs. It won’t change
immediately.
65. Other Inbound Transactional Integrations:
o Requisitions
i. Can be imported from external system. Even the changes or
cancellations to requisitions
ii. Approvals can be turned off if the approvals are in external
system
iii. Imported using .csv, webservices or cXML.
o Receipts
i. Can imported the external receipts against the PO’s which are
created in Ariba
ii. Imported using .csv only
o P-Card Charges
i. Can import the charges to reconcile against the P-Card Orders
created in Ariba
ii. Imported using .csv only
66. Other Outbound Transactional Integrations:
o Charge Payment Requests
i. Can export the fully reconciled P-Card charges in .csv format
only
o Advanced Ship Notices
i. Can export the ship notices sent from suppliers via Ariba
Network as part of PO export in .csv format only
67. Custom Fields Export to Ariba Network
o Custom fields in Ariba are known as “Extrinsic Fields”.
o These fields within procurement can be added to the cXML message
being sent to the Ariba Network.
o To add a custom field to cXML, Ariba customer support needs to add
the “ExternalField” template to custom field that needs to be
exported.
o In this “ExternalField” xml tag, “Label” tag contains the extrinsic field’s
name which needs to be changed in Ariba Procurement.
68. Integrating with Ariba Procurement Content (APC)
o Nothing but catalogs-only version of Ariba procurement.
o The shopping process begins in ERP and items will be added to cart
by punching out the APC.
o The completed shopping cart will return to ERP for approvals and
Ordering.
o Integration with APC happens via
i. OCI Punchin
ii. Oracle Native XML
iii. cXML
o User are created in APC automatically using “Organic Growth”
during punch in process without needing to be upload the master
data.
69. Multiple Ariba realms can be integrated with multiple ERP systems using “Federated
Process Control (FPC)”. FPC contains a parent realm and one or more child realms.
The Enterprise Wise Data is loaded to Parent and ERP Specific data is loaded to child
realm. While integration, the suite realm is integrated with the parent procurement
realm.
70. Fieldglass Integration
o Ariba Procurement and Fieldglass can be integrated.
o In Fieldglass, a work order or SOW is created and go throughs the
approval process once submitted. This SOW will be sent to Ariba
procurement solution and a service requisition is created and submits
for approval.
o The requisition in Ariba procurement solution goes through an
approval process and if approved a PO is created is created and
send it to Supplier’s Ariba Network Account. At this point the
requisition and PO will be in Ordered status.
o If the requisition approval in Ariba Procurement is denied, no PO is
created.
o Ariba Procurement send the requisition ID back to Fieldglass in the
from of URL. In Fieldglass they can view the requisition created in
Ariba Procurement as External Approval.
o Ariba Procurement sends a status update about the requisition is
ordered or denied PO to Fieldglass. If the status is ordered (requisitions
is approved) the PO ID will be sent.
o When Fieldglass receives a requisition status of Ordered, the work
order or SOW continues through the Fieldglass approval flow. When
fully approved, the status of the work order or SOW changes to
Created, and Fieldglass sends it to the supplier.
o When Fieldglass receives a requisition status of Denied, the work
order or SOW status changes to Rejected. User can edit and resubmit
it. Then the supplier accepts the SOW or work order.
o In Fieldglass, the contractor or worked submits time sheets, expense
receipts, fees, schedules, and any other documents. They will follow
 an approval process and once approved an Invoice is created in
Fieldglass.
o Fieldglass sends the invoice to Ariba Network as an ERP copy Invoice
using cXML copy request. This document in Ariba Network is not
editable. The Ariba Network matches the invoice to the PO using the
PO ID and sends the invoice to the Ariba Procurement Solution.
o In Ariba Procurement solution the invoice document is automatically
approved, and status of invoice is reconciled. For this invoice, Ariba
Procurement creates a payment request and exported to ERP
system. The status of invoice is changed to Paying.
o Once the ERP system notifies system notifies the Ariba Procurement
Solution that the invoice is paid, the status of the invoice becomes
Paid.
71. Ariba Invoice Conversion Services (ICS)
o The paper invoices can be converted to electronic format with
validation, approval process, using ICS for posting to Ariba Network.
o The scanned invoice will be created in cXML format. These invoices
will follow the same process as cXML invoices sent by suppliers.
o ICS can capture all the data including line item details, extract
additional details based on supplier id and follows all the approval
process and send it to Ariba Network in cXML format using secure FTP.
o During ICS Process, if a service provider posts an invoice to the Ariba
Network from a supplier that is not registered on Ariba Network, a
private supplier account is created by Ariba Network.
o A private supplier is a supplier that has not yet registered on Ariba
Network and taken ownership of the account. Ariba Procurement
supports transactions with private suppliers.
o in cXML document, the tag “PrivateID” indicates known supplier and
“ProviderID” indicates unknow supplier. Ariba Network checks
whether this ProviderID is already exists or not. If not, then it creates
the private supplier account.

72. Ariba Network(AN)

o Provides connectivity and online services to organizations engaged
in business-to-business commerce.
o Buyers and Suppliers do the business over the internet and access
multiple network- delivered services to enhance interaction and
collaboration.
o Provides buyers, single point of integration to many suppliers. Buyers
see value through features like Ariba Network match (for invoices),
Light Enablement, and Invoice against Contract.
o Provides each supplier with a single point of point of integration to
multiple large buying organizations. Suppliers see value through
accelerated payment cycles and document status visibility.
o Ariba Network Adapter
 i. Tools for trading business documents with sellers, e.g. POs and
Invoices
ii. The trading of business document’s transmission between
brokers and sellers happens in 2 parts.
1. To get from the buyer's systems to Ariba Network, and
then
2. To get from the Ariba Network to the supplier
iii. it gets messages that originate in the buyer's ERP to the Ariba
Network and it gets seller messages on the Ariba Network into
the buyer's ERP.
iv. Network Integration and Adapter installation is primarily an On-
Premise solution.
o The transactions from the Ariba Network are sent with one business
document per message transaction, not in batches. HTTP POST
method is used.
o If the Ariba Network (AN) can’t post to the customer or supplier for
some reason, e.g. server is down, the document will go into retry
mode. It will try to send it once an hour for 10 hours. If the transmission
is still unsuccessful, it will be updated to a Failed status on the AN.
o The allowed message delivery methods between Ariba Network and
Supplier are cXML, EDI, Fax, Email, Ul.
o AN support both outbound and inbound attachments. Outbound
attachments are always MIME. For Inbound attachments, customers
can receive a URL link to the AN to view the file, or the file itself can
be sent via MIME.
o The AN native language is cXML. all documents must be translated
between cXML and ERP format. One of the Adapter's principal
functions is to turn business documents into this intermediate format.
o AN has standards that must be adhered to - UNUOM codes, ISO
Country Codes, etc. Data must be translated to match this format.
o Ariba Network(AN) can send data to ERP in 2 ways
i. HTTP Push -> Each Message is pushed to Middleware.
ii. HTTP Pull -> Middleware/Adapter requests AN for pending
messages via a HTTP Request. The no of messages to be pulled
and polling (Time interval) frequency can be set in the
adapter.
o No need of inbound port in the firewall to connect to middleware.
o Shared Secret or Digital Certificate authentication is used in AN.

73. Connecting ERP Systems to the Ariba Network

o Multiple ERP instances can be linked to sing AN Account. Each
system is identified unique identifier, SystemID corresponds to the
logical system ID of the connected ERP instance.
o pre-packaged integration options for connecting other systems to
the Ariba Network:
i. SAP Business Suite Add-on tor Ariba Network
 ii. Ariba SAP Net Weaver Adapter
iii. Oracle Fusion Adapter
iv. Open Adapter
74. SAP Business Suite Add-on for Ariba Network
The business suite add-on now allows 3 options to connect to AN.
o Direct Connectivity (SAP recommended one)
o Mediated with SAP HANA Cloud Integration (HCI)ae middleware
o Mediated with SAP NetWeaver PI as middleware
75. The Ariba Network Adapter for SAP NetWeaver
o It is a module for SAP business applications that enables integration
between Ariba Network and your SAP ERP system.
o It allows your SAP ERP system to send and receive cXML documents
to and from Ariba Network by mapping data elements between
IDOC and cXML documents.
o Runs on the SAP NetWeaver Process Integration (PI) component
o It consists of
i. The Design Package for SAP PI i.e. Interface objects,
Integration processes, mappings for IDOC to cXML and Vice
versa
ii. The cXML adapter installed on SAP PI with cXML transport
protocol
iii. SAP Transport Files installed on SAP ERP System
76. The Ariba Network Adapter for Oracle Fusion Middleware
o Used to facilitate exchange of business documents between Ariba
Network and your Oracle ERP systems
o It consists of
i. The cXML with cXML transport protocol
ii. Mapping services that contain Oracle Business Process
execution Language (OPEL) processes to transform business
data from Oracle ERP (DB Schema) to the cXML formal
required by Ariba Network and from the cXML format to Oracle
ERP (DB Schema)
iii. ANT Build and Deploy Tool
77. SAP Ariba’s Buyer Integration team supports the process of connecting buyer ERP
systems to the Ariba Network for certain document types, e.g.:
o Request tor quotation
o Sending Purchase Orders
o Receiving Invoices
78. Sellers on the Ariba Network
o Ariba Network sellers can receive documents (PO’s, Contracts,
Payments) from buyers and send documents to buyers (Order
Confirmations, Ship Notices, Invoices).
79. Seller Integration in Ariba is defined as the direct connection between a seller’s ERP
or accounting system and the Ariba Network to exchange documents electronically.
It is a completely automated and touchless connections and removes manual
transaction processing.
80. Various Integration Methods supported in Seller Integration are
o cXML
o EDI
o CSV
o Dell Boomi
These methods help in achieving the elimination of manual transaction
processing.
cXML and EDI are most widely used methods.
81. An Integration Method is a standard formatting language or “computer language”
used to structure business data in business documents like POs and Invoices.
82. A Transmission Protocol is the mechanism used to communicate the transactions-
the WAY transactions are sent from one system to another.
83. Seller Integration Methods - cXML
o It is SAP Ariba’s Native Language and the Ariba Network and other
Ariba applications are built on cXML.
o Recommended for high volume of transactions i.e. >500
invoices/year and as a first choice if not already integrated.
o Only supports HTTPS as a transmission method.
o New Technology.
o Main advantages over EDI are
i. cXML does not require language translation since the AN is
built on cXML
ii. cXML is very flexible and has the ability to easily add extrinsics
iii. All new features and functionality are supported.
84. Seller Integration Methods - EDI
o EDI is recommended for sellers who already have an existing EDI
infrastructure in place, either an in-house solution or an outsourced
solution.
o Ariba supports two transmission protocols for suppliers to exchange
EDI documents: AS2 and VAN
o Recommended for high volume of transactions i.e. >500
invoices/year and existing EDI system infrastructure.
o Support of both ANSI and FDIFACT standards.
o Old Technology and is more rigid and restricted formatting language
that doesn’t allow for much customization and flexibility.
85. Seller Integration Methods -CSV
o A partial integration option as it requires manual action.
86. Seller Integration Methods -Dell Boomi
o Option for high volume sellers without EDI or cXML capabilities.
o Dell Boomi is a sell-side adapter that will translate a seller’s system
output into the cXML format for the Ariba Network to consume.
o There are pre-built templates for sellers using three accounting
systems - QuickBooks, Sage 50, and Microsoft Dynamics GP - that
allow for an easy integration.
87. Important facts to remember for Integration
 o cXML is the native language of the AN and the preferred integration
method
o Suppliers can use any integration method or combination of
methods to send/receive transactions
o The AN is flexible with regards to seller ERP and accounting systems.
o It should not matter to the Buyer if the supplier is transacting via
Integration or PO Flip.
88. Benefits for Sellers with Ariba Integration:
o Improves the customer retention. (Integration is Sticker)
o integration reduces the procure-to-pay cycle time as there is no
manual intervention.
o Increases the accuracy of orders and invoices with integration.
o Efficient Management of Business Transactions.
89. Benefits for Buyers with Ariba Integration:
o Mostly same benefits as sellers.
o Reduction in disputes for both orders and invoices.
90. Minimum required criteria for a Seller to be good fit for integration:
o High Annual Document Volume (more than 500 docs/annum)
o A supplier must have cXML (https) or EDI (VAN/AS2) capabilities
o Their ERP/accounting system and middleware support testing as this
is a critical step in the integration project.
o Available resources from an eCommerce or IT team to devote to the
integration project
o Ability to support an 8-week project timeline.

91. Ariba Catalog

o It is an organized, descriptive list of goods and services available to
potential Buyers.
o Catalogs are aggregated content.
i. Has items from all the suppliers for biller in a single database.
ii. Tied into Ariba contracts module to find items specific to a
contract.
o Catalogs are organized in a hierarchical structure.
o Provides a unified interface to access both goods and services within
the Ariba environment.
92. Ariba Catalog Types:
o Two Basic Types:
i. Static or CIF (Catalog Interchange Format) Catalogs
ii. Punchout Catalogs
o CIF format is like CSV with header section with metadata. These are
flat files with static information about each catalog item.
o CIF files give tight control of catalog management, approvals and
maintenance as they are stored within the Ariba application and
can be controlled by the buying organization.
 o With PunchOut, the Ariba Network supports the suppliers’ technical
infrastructure and existing B2B website. Users “punch out from the
Ariba application to shop on the Supplier’s site.
o Catalog items are not stored in the Ariba application and are
located on the Supplier's website
o Auditing and oversight is performed outside of the Ariba tools
o PunchOut Catalogs use the cXML protocol to communicate
o There is more complexity in configuration: Suppliers must have the
infrastructure and
o tools necessary for PunchOut transactions
o There are two types of PunchOut Catalogs: Level I and II.
93. Static (CIF) Catalogs
o Comma separated, static file, either:
i. Maintained and uploaded by Suppliers to the Ariba Network,
or
ii. Created and managed by the Buying organization.
o Each file contains complete & comprehensive information for each
item know as SKU
i. Part Number
ii. Price
iii. Description
iv. Image link
v. Commodity Code (Stock Keeping Unit) including
o CIF extensions allow for these configurations:
i. Custom fields
ii. Partial Items
iii. Catalog Kits (Multiple Items from single or various suppliers)
iv. Item Rankings (Prior
o Advantages:
i. Very easy to get up and running (static file upload)
ii. Maximum control and audit for contract compliance
iii. Catalog approval workflow
iv. User searches in Ariba interface return results and can
compute items side-by-side
v. Users can create favorites
vi. Item ranking
o Disadvantages:
i. No real-time update regarding inventory or pricing changes.
ii. Often requires supplier management to keep catalogs current
iii. Large files must be split for Ariba Network loading as there is a
file size limitation.
94. Level I PunchOut
o User clicks “Buy from Supplier” button against each item, which will
take them to supplier’s external website. Then they will add the items
to the cart and bring the cart back to Ariba application.
 o To provide buyer the cart, supplier the supplier uploads a single line
static file (CIF File) to the Ariba Network. Which is known as index file.
o Catalogs are maintained by suppliers.
o Advantages
i. Dynamic Quotes
ii. Real time information like pricing and availability
iii. Custom Configurations
o Disadvantages
i. User must know from which supplier to purchase and cannot
do an Ariba search and get specific results
ii. User cannot create favorite items (on Ariba interface)
iii. Each site has a different look-and-feel user to learn
iv. Supplier controls the content and pricing
v. Audit for contract compliance is manual, outside the system
vi. Somewhat more complicated for suppliers to set up
95. Level II PunchOut
o the catalog interface allows users to search and see results in Ariba
similar to static catalog items.
o Supplier uploads CIF-like index file (one line per SKU) to the Ariba
Network
o Catalogs and Index Files are maintained by suppliers.
o Advantages
i. facilitate searching within the Ariba application
ii. real-time pricing, availability, and accuracy of content.
o Disadvantages
i. Index Files needs to be maintained by supplier
ii. more complicated to set up and suppliers must modify an
existing Level I site
96. Determining Catalog Types
o Choose a Static Catalog, when
i. An easy solution for low tech supplier with Excel skills
ii. Catalogs for commonly ordered items
iii. To search across multiple suppliers for items
iv. Items with static pricing
v. Catalogs with low/medium number of SKUs
o Choose a Punchout Catalog, when
i. Have an supplier with an existing B2B site you wish to leverage
ii. Have a catalog with a large number of SKUs offered
iii. Need to buy configurable/custom Items
iv. Have items with volatile pricing
97. Major catalog value for buyers is a greater efficiency in the ordering process.
98. Major catalog value for suppliers is better product visibility and reduction in errors in
orders.
99. Catalog Enablement
o The catalog build process will be managed by the supplier with
support from the Ariba Catalog Knowledge Expert. Testing is required
 for PunchOut catalogs. While testing is not required for static
catalogs, it is recommended.
100. Ariba Catalog Team’s Roles
o Buyer-facing catalog tasks – Works with buyer/customer and guides
him with best practices, approach, scope, strategy etc.
o Supplier-facing tasks – Works directly with suppliers and assist the
supplier in troubleshooting issues and provide support throughout the
maintenance and refresh processes.