Integrate SAP Concur

Integrate with SAP Concur to submit requests and receive notifications about the status of requests.

As a System Admin, you use the following process to enable the Concur Integration. Ensure you meet the prerequisites then set up the Concur integration. After you set up the integration, you must provide employees with the employee name, email address, employee id, or log-in id of the dedicated account and ask them to adjust their SAP Concur profile settings. After you complete this process, your existing level of audit logging persists, including any actions carried out by the use of Citrix Microapps.

For a comprehensive list of out-of-the-box SAP Concur microapps, see Use SAP Concur microapps.

Review prerequisites

These prerequisites assume you administer the SAP Concur instance of your organization to set up the integration. You must have these details to add the integration in Citrix Workspace Microapps:

  • Instance URL
  • Username
  • Password

For OAuth 2.0:

  • OAuth Client ID
  • OAuth Client Secret
  • Authorization URL

Note: It is recommended that you always use OAuth 2.0 as your service authentication method where available. OAuth 2.0 ensures that your integration meets the maximum security compliance with your configured microapp.

  • Obtain a new oauth2 client_id and client_secret and define the scope of client’s application.

Important: Create a support ticket with Concur to configure the integration using OAuth 2.0 and register correct authentication callback URLs. We recommend using the following text for your support ticket:

We request OAuth 2.0 credentials to enable an integration with Citrix Workspace. This tool downloads recent expense reports and line item details using a service account to present pending approvals to managers. It allows employees to submit, approve, and reject quick expenses. Actions taken by end users are directed to the 3LO authorization page where they enter their Concur credentials and approve access by the Workspace app.

Add your Concur Client ID.

Add the following authorized redirect URLs to Concur for this integration with authorization grant access granted to allow access to private data and enable OAuth authenticated user actions:

  • <https://microapps_server_URL/admin/api/external-services/com.sapho.services.concur.ConcurService/auth/serverContext>

  • <https://microapps_server_URL/app/api/auth/serviceAction/callback>

  • You must have the Web Services component purchased from SAP Concur. If your company hasn’t purchased the Web Services component, ask the SAP Concur administrator in your organization to contact your Account Manager at SAP Concur.
  • Configure Citrix Gateway to support single sign-on for SAP Concur so that once users log in they are automatically logged in again without having to enter their credentials a second time. Follow the instructions in Concur Single Sign-on Configuration. For more information about configuring SSO, see Citrix Gateway Service.

Add the integration to Citrix Workspace Microapps

Add the SAP Concur integration to Citrix Workspace Microapps to connect to your application. This delivers out-of-the-box microapps with pre-configured notifications and actions which are ready to use within your Workspace.

Follow these steps:

  1. From the overview page, select Get Started.

    The Manage Integrations page opens.

  2. Select Add New Integration, and Add a new integration from Citrix-provided templates.
  3. Choose the SAP Concur tile.
  4. Enter a name for the integration.

    Concur connector parameters, Instance, URL, Authentication Method, Username, Password, Consumer Key

  5. Enter the Connector parameters that you collected as prerequisites.
    • Enter your Instance URL.
    • Enter the Username and Password.
    • Select an Authentication Method. Use the OAuth 2.0 security protocol to generate request/authorization tokens for delegated access.
    • Enter an Authorization URL to define the authorization server url provided when setting up the target application integration.
    • Select an OAuth 2.0 Authentication Method.
      • Credentials The client’s credentials are used instead of the resource owner’s. The access token is associated either with the client itself, or delegated authorization from a resource owner.
      • Authorization grant (3LO) The resource owner allows access.
    • Enter the OAuth Client ID and OAuth Client Secret that you collected in the prerequisites procedure.
  6. Select the following radio buttons as required:

    • Expense module Provides access to employee expense tracking.
    • Expense Group Configuration Retrieves the list of Expense Polices, Expense Types, and Payment Types for the Expense Group that the OAuth access token is assigned to.
    • Expense Report Details (allocations and Itemizations) Allows for the retrieval of allocation information as it relates to a Report ID, Entry ID, or Itemization ID.
    • Travel module Provides access to travel data such as itineraries, travel profiles, and travel requests.
    • Expense delegators Retrieves a list of users that have granted delegate permissions to the user specified in the OAuth access token.
  7. Enter a quantity for Number of Connections. This value determines the number of strings the data sync initiates.

    Note: The default number of connections is one. Opening more connections reduces the time for data synchronization, but increases the load on the Microapps server and can influence its performance. If you require, we recommend no more than 10.

  8. Select Add.

The Microapp Integrations page opens with your added integration and its microapps. From here you can add another integration, continue setting up your out-of-the-box microapps, or create a new microapp for this integration.

You are now ready to set and run your first data synchronization. As a large quantity of data can be pulled from your integrated application to the Microapps platform, we recommend you use the Table page to filter entities for your first data synchronization to speed up synchronization.

For more information, see Verify needed entities and Set data synchronization in the Configure the integration article.

For more details of API endpoints and table entities, see Concur connector specifications.

Use SAP Concur microapps

Existing application integrations come with out-of-the-box microapps. Start with these microapps and customize them for your needs.

Important!

These SAP Concur microapps are now deprecated: Submit Quick Expense, Create User, and User. Users need to delete these microapps as they will become misconfigured. To delete the microapp, from the Microapps Integrations page select the menu next to the microapp that you want to delete. Select Delete microapp and confirm.

How to delete a microapp

Our SAP Concur integration comes with the following preconfigured out-of-the-box microapps:

Approvals: Approve pending expense reports or send them back.

Notification or Page Use-case workflows
Approval Reminder notification When an expense report is pending approval and passes a defined threshold before deadline (for example, 3 days by default), the approver receives a notification reminder.
New Request notification When a new request for approval is assigned to an approver, the approver receives a notification.
New Request (changed) notification When there is a change to a request for approval, the approver receives a notification.
Expense Detail page Provides a read only view of an expense with details.
My Pending Approvals page Provides a personalized list of pending approvals.
Review Report page Provides an actionable form with a detailed view of an expense report pending approval.

Expenses: Search and view expenses.

Notification or Page Use-case workflows
Expense Detail page Provides a read only view of an expense with details.
My Expenses page Provides a personalized list of expenses.
Report Detail page Provides a detailed view of an expense report with a field for commenting.

Itineraries: Search, view, and share itineraries.

Notification or Page Use-case workflows
New Itinerary successfully booked notification When a user’s new itinerary is booked and ticketed, the user receives a notification.
New Shared Itinerary notification When an itinerary is shared with a user, they receive a notification.
Itinerary Detail page Provides a view of a user’s itinerary and an actionable share button.
My Itineraries page Provides a personalized list of itineraries.
Share Itinerary page Provides a form for sharing a user’s itinerary.

Quick Expenses: Search and view quick expenses.

Notification or Page Use-case workflows
My Quick Expenses page Provides a personalized list of quick expenses.
Quick Expense Detail page Provides a read only view of a quick expense with details.

Reports: Search and view your submitted expense reports.

Notification or Page Use-case workflows
Request Approved notification When a user’s expense report is approved, they receive a notification.
Request SendBack notification When a user’s expense report is sent back, they receive a notification.
Expense Detail page Provides a read only view of an expense with details.
Expense Report page Provides a detailed view of an expense report with a field for commenting.
My Pending Expense Reports page Provides a personalized list of expense reports.