This document gives you a brief overview on what is CONCUR, its market share and interface repository for any enterprise to integrate with Concur

1. CONCUR & IT’S INTEGRATION WITH SAP-PI
Author : Satya Suman L
Certified SAP PI Consultant

2. WHAT DO YOU KNOW FROM THIS?
Corporate Travel and Expense world
Leading Travel and Expense solutions
SAP’s – SAAS Solution
CONCUR – Know more about it
CONCUR – Integration Need & Standard connectors
CONCUR – Interface Repository
CONCUR Implementation - Case Study
Pros and Cons of CONCUR

3. CORPORATE TRAVEL AND EXPENSE WORLD
Corporate owning hundreds and thousands of employees working in a global
model often request their employees to travel different locations to fulfil business
needs.
To meet employee satisfaction, organising travel and their official expenses with a
hassle free process is a major challenge for corporates.
Here is where Corporate heads towards their IT department or IT partners to make
the process simple and better which can save employee time and also corporate
have a clean ledger on their employee business trips.

4. KEY DRIVERS TO AUTOMATE EXPENSE PROCESS
Cost Efficiency
Ensure Internal and Regulatory Compliance
Increase Visibility into Spending
Minimize Fraud
Integrate Travel into your Expense
Stay Flexible and Scalable with Cloud-based Solutions
Managing Risk Effectively
Expense on the Move

5. LEADING SOLUTIONS FOR A HASSEL FREE EXPERIENCE

6. SAP’S SAAS SOLUTION : CONCUR
 With more than 1.6 million connected companies in 190 countries transacting over half
a trillion dollars in commerce on an annual basis, the SAP business network is the
largest in the world.
 SAP added CONCUR into its nest enabling partners with a better travel and expense
capabilities in 2014.
 CONCUR is a leading T&E management software run on cloud providing a flexible and
scalable solution to its partners.

7. CONCUR : METRICS FOR A BUSY DAY
Over 1.2 Million users log into Concur
Clients book over 160,000 trips
Archive 222,000,000 records
Clients submit 600,000 expense reports
Concur send about $70,000,000 to banks daily
Over 400,000 logins to Concur Mobile

8. INTEGRATION AND DATA EXCHANGE
Firewall
DESIGN
BUILD
RUN
MONITOR
IDOC/SFTP/Proxy
SFTP wt PGP / REST
Service
Firewall
HR Database
Employee Data : General Details, Manager ID, Cost Centre etc.
List Data : Project Codes, Events, Meetings, Internal Orders
Attendee List (Optional)
Expense Form Lists(Optional)
Validation Tables(Optional)
Exchange Rates(Optional)
Payment Confirmation(Optional)
Standard Accounting Extract(SAE)/Expense Report Details
Reporting Data(Optional)
Receipt Images(Optional)

9. INTERFACE DETAILS : DEEP DRIVE
S # Category Interface Interface Details
Direction
wrt
CONCUR
Mode/Frequency
Mandat
ory
Flow File Naming Standard(sent/Received by Concur)
1 Master Data Employee Import
Complete employee data with details like Role, ID,
Location Cost Center etc. will be sent to Concur. This
includes only employee details of the customer
Inbound Asynchronous/Daily YES
HR Data Cache(JDBC) --> SAP PI -->
CONCUR(SFTP-PGP)
employee_<event ID>_<description>_<Timestamp>.txt.pgp
2 Master Data Employee Login Data
Employee email ID, user details etc details to be sent to
concur for single sign-on
Inbound Asynchornous/Daily YES
HR Data Cache(JDBC) --> SAP PI -->
CONCUR(SFTP-PGP)
employee_<event ID>_<description>_<Timestamp>.txt.pgp
3 Master Data Employee DoA Data
DoA(Delegation of Authority) data to be sent to Concur,
this holds the managers approving limit information for
approving its employee expense
Inbound Asynchronous/Daily YES
HR Data Cache(JDBC) --> SAP PI -->
CONCUR(SFTP-PGP)
employee_<event ID>_<description>_<Timestamp>.txt.pgp
4 Master Data Attendee Import
Complete details of attendees will be sent to Concur,
this file will include data of customer's employee and its
partners as well.
Inbound Asynchornous/Daily YES
HR Data Cache(JDBC) --> SAP PI -->
CONCUR(SFTP-PGP)
attendee_<event ID>_<description>_<Timestamp>.txt.pgp
5 Master Data List Import: Project Codes
Project Code master along with all relevant project
details to be sent to Cocnur
Inbound Asynchornous/Daily YES SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
6 Master Data List Import: Events
Event master with all relevant event related information
like venue, event ID, dates etc to be sent to Concur
Inbound Asynchornous/Daily NO SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
7 Master Data List Import: InternalOrders
Any Internal orders raised in source ERP(SAP) active and
relevant to travel and expense to be sent to Concur
Inbound Asynchornous/Daily YES SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
8 Master Data List Import: WBS Elements
WBS Element master with all relevant related information
like company code, country code, cost center, vendor
codes to be sent to Cocnur
Inbound Asynchornous/Daily NO SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
9 Master Data List Import: Meetings
Meeting master with related information like company
code, country code, cost center, meeting ID to be sent
to Cocnur
Inbound Asynchornous/Daily NO SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
10 Master Data List Import: Cost Center Cost center master with active dates to be sent Concur Inbound Asynchornous/Daily YES SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) list_<eventID>_<description>_<TimeStamp>.txt.pgp
11
Transaction
al Data
Expense Data: Payment
Confirmation
Once the claimed expenses are settled by Customer in
ERP, status agains the expenses to be sent to Concur
Inbound Asynchornous/Daily NO SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP)
exp_pay_confirm_<event
ID>_<description>_<Timestamp>.txt.pgp
12
Transaction
al Data
Expense Data: Exchange Rates
Exchange Rates considered by the customer to be sent
to Concur for expense calculations
Outbound Asynchornous/Daily NO SAP(IDOC) --> SAP PI --> CONCUR(SFTP-PGP) exp_<eventID>_<description>_<TimeStamp>.txt.pgp
13
Transaction
al Data
Extracts: Attendee Extract Concur sends this file with all attendee details for which
the claims have been made on a day
Outbound Asynchornous/Daily NO CONCUR(SFTP-PGP) --> SAP PI --> SAP(IDOC)
extract_attendee_detail_<event
ID>_<description>_<Timestamp>.txt.pgp
14
Transaction
al Data
Extracts: SAE Extract
Standard Accounting Extract, Concur generates this file
with itemised expense details claimed by an employee
Outbound Asynchornous/Daily NO CONCUR(SFTP-PGP) --> SAP PI --> SAP(IDOC)
extract_CES_SAE_v3_<eventID>_<description>_<TimeStam
p>.txt.pgp
15 Real Time External Guest Search
If any employee want to claim expense for his
guests/partners who are external partners.These guest
data can be searched using a real time call
Real Time
Synchronous/Real
Time
NO
CONCUR(REST Service) <--> SAP PI <-->
Financial/ERP System(SOAP/JDBC)
NA

10. CONCUR : PROS & CONS
It is an SAP’s SaaS product i.e., provided as ‘Software as a Service’ which gives flexibility to its customers on product
enhancements and upgrades.
Reporting and automation made simple and hassle free.
Besides PGP encryption on data exchange, it is a high secured cloud platform with 96000+ firewalls in front of its
infrastructure.
Interactive and simple GUI, which makes customer’s employee more productive and fast to finish their Travel & Expense
process
No standard content yet available, but as per SAP’s roadmap it is planned in FY2016-17
Web Service calls restricted to REST protocol only, to do REST calls using PI the minimum version supported is PI 7.4 SP09
or equivalent.
Concur being a SaaS product, customizations were restricted to certain extent.

11. CONCUR : STANDARD CONNECTOR
 Concur provides standard connectors called, Financial Connectors.
 The Concur Financial Connector with support for SAP is a bi-directional integration solution that ensures
expense-related information captured in Concur is properly posted into SAP.
 This offering simplifies integration with SAP thru the use of pre-built connector templates designed around SAP
file structures, making the exchange of data easy, quick to deploy and without significant configuration required
in either Concur or SAP.
 All the data exchange using this connector process through ‘The Bhoomi Atom’
Connected
List Item
Firewall