This document describes integrating Coupa, an online e-procurement system, with Oracle E-Business Suite 11i using Oracle's web services tools. It will create a bidirectional integration bridge between the two systems. The scope includes integrating key information like accounts, suppliers, addresses, invoices, payments, catalog items, requisitions, purchase orders, and inventory transactions. Oracle web services are recommended due to benefits like lower costs, extensibility, and customizability. The Coupa API uses a RESTful design with resources that can be created, read, and updated through HTTP requests.

1. Oracle e-Business Suite-Coupa
(Web Service Integration)
Presented By:
Ravindra Tripathi
(Oracle e-Business Suite Techno-Functional, Integration expert)
1
OptioSys Technologies, Inc.
OptioSys Technologies, Inc.

2. Presentation Contents
 Introduction
 Scope
 Requirements
 Integration Tools
 Web Service Integration
 Why Oracle Web Service
 Web service Integration Approach
 Coupa API
OptioSys Technologies, Inc.
2

3. Introduction
OptioSys Technologies, Inc.
3
The purpose of this document is to describe at a high level the approach of integrating
Coupa (an online e-Procurement package in the cloud) to Oracle E-Business Suite 11.5.10.

4. Scope
OptioSys Technologies, Inc.
4
The scope of this document will cover the integration points between Oracle e-Business
Suite 11i and Coupa.
 Create a Bi-directional integration bridge between Oracle e-Business suite 11i and
Coupa using Oracle’s Web Services tools.

5. Sr. Summary of Requirement from PRD
Source
System
Target
System
Phase
1. GL Account Information Oracle Coupa I
2. Supplier Information Oracle Coupa I
3. Address Information Coupa Oracle I
4. AP Invoice Information Coupa Oracle I
5. AP Invoice Payment Information Oracle Coupa I
6. Catalog Items Information Oracle Coupa I
7. Requisition Information Coupa Oracle II
8. Inventory Transactions Coupa Oracle II
9. Purchase Order Coupa Oracle II
Requirements
OptioSys Technologies, Inc.
5

6. Integration Tools
OptioSys Technologies, Inc.
6
 Boomi Middleware
 Cast Iron Middleware
 Oracle BPM (BPEL)
 3rd Party Middleware
 Oracle’s Web Service

7. Why Oracle’s Web Service API
OptioSys Technologies, Inc.
7
 Lower TCO (Total Cost of ownership).
 No Third party tool, Middleware OR Licensing.
 SOA architecture.
 Future extendibility.
 Easy development and Maintenance.
 Core Oracle Native language.
 No upgrade cost.
 Customizable.
 Adaptable to business needs.

8. Web service Integration Approach
OptioSys Technologies, Inc.
8
To address the requirements we will utilize Oracle’s Web Services tools and Coupa’s
APIs.

9. Web service Integration Approach Cont..
OptioSys Technologies, Inc.
9
Optio Coupa Connector
GL Code
Combination
Supplier
Address
Items
Requisition
Purchase
Order
AP Invoice
Payment
Inventory
Transaction

10. Coupa API
OptioSys Technologies, Inc.
10
The Coupa API is resource based, also known as a REST API. The resources
available are data objects like users, accounts, suppliers, purchase orders, invoices,
etc.
Resource URLs
Each resource has its own url, of the form /api/[resource]. We recommend using
https:// instead of http:// to prevent redirects.
Each Coupa customer has their own url, of the form *.coupahost.com.
Example:
https://example.coupahost.com/api/invoices

11. Coupa API Cont…..
OptioSys Technologies, Inc.
11
A REST request is very similar to a request by a browser, except each request has an
action, a resource and a payload. The allowed verbs are create, read and update.
 Create
o A HTTP POST to the resource root with an XML payload will attempt to
create a new resource. If successful, the resource is returned with the new
id. You can not set the ID of any resource when creating it, Coupa will create
the ID.
o You can also create/update multiple objects of the same type. You should
pass an extra parameter, bulk=1 in the URL.
o For certain resources we have listed field limitations for critical elements. For
other columns use the information from the GET as a guide

12. Coupa API Cont…..
OptioSys Technologies, Inc.
12
 Read
A HTTP GET at the resource root will list the first 50 resources in XML starting from
ID .
 Update
A HTTP PUT to /api/[resource]/[id] will attempt update a resource. The payload
should be XML with the elements you want to update. Only a few fields are
available, where possible we have listed them with the resource type. Please
contact support with specific questions.

13. QA
13
QA
Q/A
Ravindra Tripathi
rtripathi@optiosys.com
www.optiosys.com
OptioSys Technologies, Inc.