Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: SAP concur limitations

Answered
Akshay Salunke User
  • Edited

Hi Fivetran Team,

This feature request is related to the SAP Concur connector.

1. Missing Objects Due to Scope Limitations

Currently, we are unable to load the following objects using the available SAP Concur scopes in Fivetran, and as per our requirement we request to be available on priority:

Scope: cards.transaction.read

  • Credit Card
  • Unassigned Credit Card

Scope: expense.report.read

  • Audit Comments
  • Header Comments

2. API Version Upgrade Request

The SAP Concur team has recommended using the latest API version to access the complete data set.
We would like to request upgrading all SAP Concur API versions to the latest version available in SAP Concur so that we receive all information from SAP concur side.

For example:

  • The Attendee table is missing the external_id column due to this API version limitation. This is available in version 4.0

3. Missing Columns

The following columns are currently missing from the respective objects and we request for adding these:

  • external_id in the Attendee table
  • employee_id in the Expense Entry table

 

4. additionally, we got following response from Fivetran support team(ticket: #357757)
      The EMPLOYEE table, along with the EmployeeID and Employeeuuid columns, is also not currently supported.
can you please make it available in same connector?

Please let us know if you need any additional details from our side to evaluate this request.

 

Thanks,
Akshay

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Official comment
    Tom Jose Fivetranner

    Hi Akshay,

    Thank you again for the detailed request. I'm Tom, the Product Manager for the SAP Concur connector at Fivetran.

    We have reviewed the items internally and understand the gaps you’ve outlined:

    • Additional objects (Credit Card, Unassigned Credit Card, Audit Comments, Header Comments)

    • Missing columns (external_id in Attendee, employee_id in Expense Entry)

    • EMPLOYEE table support (including EmployeeID and Employeeuuid)

    • API version upgrades to unlock additional fields such as external_id in Attendee

    Given your planned rollout by end of April, it would help us to align on prioritization:

    • For go live, which of these items are must-have versus nice-to-have?

    • If we need to phase delivery, which should we prioritize first?

    • Is the API version upgrade required before rollout, or could that follow shortly after?

    This will help us assess sequencing and provide clearer expectations as we evaluate engineering bandwidth.

    We want to make sure we deliver what matters most for your rollout and are actively reviewing next steps. Looking forward to your guidance on priority so we can move forward effectively.

    Thanks,
    Tom

  • Akshay Salunke User

    Hi Tom,

    Thanks for reaching back.

    Just to provide some additional context, we are currently extracting SAP Concur data through Cognos, where several business rules and transformations have been implemented before the data is passed to the Qlik dashboard. This solution is already live. And we need to switch urgently to Fivetran based SAP Concur ingestion due to some limitations in the current ingestion process using Cognos.

    Given your planned rollout by end of April, it would help us to align on prioritization: 
    [Astellas]: We need to begin our Development from 1st of April and would need the entire data to be available before that for us to consume. We have shared the complete list of objects and columns with Milan(Customer Support Engineer | Fivetran) that are required.
    I have asked Milan to share file with you.

    For go live, which of these items are must-have versus nice-to-have? : 
    [Astellas]: Everything is a must-have as we are already LIVE with this solution.

    If we need to phase delivery, which should we prioritize first? : 
    [Astellas] We can de-prioritize Header Comments and Audit Comments as they are part of a different pipeline, however everything else needs to be delivered earliest and together.

    Is the API version upgrade required before rollout, or could that follow shortly after? 
    [Astellas]
    1) SAP Concur support team recommends consuming data from the latest version or V4 API.
    2) Now for example:  Attendee is available however we do not see ‘external_id’ flowing in through Attendee as it is only available in V4 and we currently have V3 setup in Fivetran. Hence it would be advisable to upgrade to the latest versions of the API, so that such issues do not occur.

    Based on this information, could you please share an ETA from your team on how long it may take to make these features available in the Fivetran SAP Concur connector?

     

     

    Thanks,
    Akshay

  • Hardy Titz User

    Hello Tom,

    is there an update of introducing the 

    • Additional objects (Credit Card, Unassigned Credit Card, Audit Comments, Header Comments)

    To the concur Fivetran connector?

     

    Best regards,

    Hardy

  • Tom Jose Fivetranner

    Hi Hardy,

    Thank you for reaching out and for your interest in these enhancements.

    This particular ticket has been scoped to address a specific set of requirements, so to make sure your use case gets the right attention and tracking, could you please submit a separate feature request through the Fivetran support portal?

    That way, we can properly capture your requirements, prioritize them independently, and keep you updated on progress directly.

    Thanks,
    Tom