The first step in setting up the Veeva-SAP Concur Integration is to enable the Veeva Partner Application in SAP Concur.
Note: Prior to enabling the connector, SAP Concur requires all customers to sign the Letter of Authorization that authorizes Veeva to link services and access customer data.
SAP Concur Administrators can follow these steps to enable the Veeva Partner Application in SAP Concur:
- Log in to SAP Concur as the System Administrator.
- Navigate to App Center.
- Search for Veeva CRM Connector.
- Select Connect.
- Follow the steps in the pop-up window to select the Sandbox or Production environment.
- Enter Veeva CRM system admin credentials to finish connecting.
Any SAP Concur Data Center region is available to connect to Veeva CRM.
This App Center connection only needs to be enabled once per SAP Concur environment. For details on migrating an SAP Concur connection to multiple CRM environments, see Deploying SAP Connection to Multiple CRM Environments.
Initial Setup for SAP Concur Integration
The initial setup of the Veeva - SAP Concur Integration must be performed to link your Veeva Org to your SAP Concur system. A system administrator typically performs the one-time setup and configuration to enable the integration. Navigate to the Concur Admin tab to complete these steps.
If the Concur Admin tab is hidden, follow these steps to display it:
- Select Setup.
- Select Manage Users.
- Select Profiles.
- Select System Administrator.
- Select Edit.
- Select Custom Tab Settings.
- Select Concur Admin.
- Select Default On from the drop-down menu.
If the VADMIN user's profile contains an allowlist for IP addresses, include the 52.14.227.54 IP address.
Initial setup of the integration involves establishing connectivity between Veeva and SAP Concur by activating the Veeva CRM Connector through SAP Concur App Center.
- Log into SAP Concur as Administrator and navigate to App Center.
- Search for Veeva CRM Connector.
- Select Connect and follow the on-screen instructions to select the CRM sandbox or production environment.
Deploying SAP Concur Connection to Multiple CRM Environments
The Veeva CRM Connector only needs to be activated once in SAP Concur App Center. After a connection is established for a CRM environment, system administrators can migrate and deploy the connection as they would standard metadata.
The integration connection information is stored in Concur_Settings_vod__c custom settings. To migrate the connection, deploy the custom setting to the target environment.
- Ensure Company_Id_vod__c, Concur_Data_Center_Region_vod__c, and OAuth_Refresh_Token_vod__c are deployed properly. These custom settings are used for connection purposes.
- The individual SAP Concur User Ids are stored in the Veeva User Profiles.
- Veeva uses the SAP Concur credentials to log into SAP Concur and post expenses to the appropriate users.
- During the sync, the OwnerId field is used to determine which user recorded the call that identifies the corresponding SAP Concur user Id.
- The Expense posts to the SAP Concur user, but using the admin credentials.
Field mappings are stored in Veeva Messages. To migrate field mappings, migrate the applicable Veeva Messages for configured sections based on the following table.
|
Feature |
Mapping |
Veeva Message |
|---|---|---|
|
Call |
User to Report Header |
Report_Header_Mapping_vod__c |
|
Call |
Call to Expense Entry Mapping |
Call_Mapping_vod__c |
|
Call |
Expense Line to Expense Entry Mapping |
Call_Expense_Line_Mapping_vod__c |
|
Call |
Call Primary Attendee to Expense Attendee Mapping |
Call_Primary_Attendee_Mapping_vod__c |
|
Call |
Call Attendee to Expense Attendee Mapping |
Call_Attendee_Mapping_vod__c |
|
Medical Event |
Medical Event to Expense Entry |
Medical_Event_Mapping_vod__c |
|
Medical Event |
Medical Event to Expense Entry Attendee |
Medical_Event_Attendee_Mapping_vod__c |
|
Events Management |
Expense Header to Expense Entry |
Expense_Header_Mapping |
|
Events Management |
Expense Line to Itemization |
Expense_Line_Mapping |
|
Events Management |
Expense Attribution to Attendee - User |
Expense_Attribution_User |
|
Events Management |
Expense Attribution to Attendee - Account |
Expense_Attribution_Account |
|
Events Management |
Expense Attribution to Attendee - Contact |
Expense_Attribution_Contact |
|
Events Management |
Expense Attribution to Attendee - Write-In Event Team Member |
Expense_Attribution_Event_Team_Member |
|
Events Management |
Expense Attribution to Attendee - Write-In Event Attendee |
Expense_Attribution_Event_Attendee |
|
Events Management |
Expense Attribution to Attendee - Write-In Event Speaker |
Expense_Attribution_Event_Speaker |
|
Events Management |
Expense Attribution to Entry Attendee Associations |
Expense_Attribution_Mapping |
Configuration Parameters for SAP Concur Integration
Veeva uses the following SAP Concur Web Services. For more information about SAP Concur API, refer to the Expense section of the SAP Concur API documentation.
|
Category |
Sub-Category |
Usage |
|---|---|---|
|
Attendee |
Get Attendee Type v1.0 |
Retrieves the picklist values for the Other Attendees Type picklist on the SAP Concur Admin page. |
|
Expense |
Get Expense Group Configuration |
Retries the picklist values for the Payment Type picklist on the SAP Concur Admin page. |
|
Expense |
Get Reports List v2.0 |
Retrieves the list of reports. |
|
Expense |
Post Expense Entry Attendee v1 |
Creates or updates attendee records for the specified expense entry. |
|
Expense |
Post Expense Entry v1.1 |
Posts an expense report entry for the specified report. |
|
Expense |
Post Expense Report Header Batch |
Posts a batch of expense report headers, which contain classification information for the expense report. |
For information about how to schedule the SAP Concur Sync, refer to the Salesforce.com documentation.
Configuring Parameters
Expense Type/Expense Key – the default type is Business Meal. This picklist uses SAP Concur API to retrieve all available expense types and displays them as available configuration options.
Payment Type – the default type is Cash. This picklist uses the SAP Concur API to retrieve all available payment types and displays them as available configuration options.
Expense Attendee Type Field – the default type is BUSGUEST for Call Reports and Medical Events
This is an optional field that can be added to Call Reports or Medical Events
Custom/multiple attendee types can be added as picklist values for the Expense Attendee Type field in Veeva (must correspond to attendee types setup in SAP Concur)
Can select a default type to display on the Call/Medical Event page
Can custom-map additional attendee specific fields, for example, Specialty
Email Notification for SAP Concur Integration
Customers need to receive emails, at a configurable email address, if a SAP Concur sync fails. We do not send notifications about successful syncs.
To configure the email address, add the Email_Notification_Recipients_vod__c field to the SAP Concur Settings object. You also need to expose this field on the SAP Concur Admin tab under Configuration Parameters.
If an email is not specified, no fail notifications are sent.
The email address field has a max of 255 characters. To avoid maximizing the field length, create a distribution list email address to allow notifications to be sent to multiple email addresses.
