Skip to main content

Community

Connector Improvement: SAP Concur: Support for the additional columns for the rejected expenses in Concur connector

Answered

Please sign in to leave a comment.

Comments

5 comments

  • Official comment

    Hi Mark, 

    We use this endpoint to sync information about reports. This should help clarify that if there are certain fields that are missing we don't receive it from the Concur API. Let me know if you find documentation on the specific fields that you would like to include. 

    Frank

    Field Concur Location Comment
    Employee ID  [Expense].[Report Header Information]  
    Employee Org Unit 1 - Code     [Expense].[Report Header Information]  
    Report Name  [Expense].[Report Header Information]  
    Approval Status    [Expense].[Report Header Information]  
    Sent for Payment Date    [Expense].[Report Dates and Statuses]  
    First Submitted Date     [Expense].[Report Dates and Statuses]  
    Sent Back Date/Time      [Expense].[Expense Report Workflow Trail] "Step Action Date/Time" is actual field
    Report ID    [Expense].[Report Header Information]  
    Commenter's Name   [Expense].[Report Header Comments]  
    Comment      [Expense].[Report Header Comments]  
    Comment Date/Time  [Expense].[Report Header Comments]  
    Sent Back Reason Code    [Expense].[Report Header Information]  
    Sent Back Reason Text [Expense].[Report Header Information]  

    The ERD does not show the requested fields which are a part of the Expense object.

    Hi Frank,

    Does Fivetran plan on supporting the Exceptions endpoint for SAP Concur?

    Thanks for submitting this information. At this time exception information is blocked by our support for the v4 endpoints for expense. Fivetran cannot implement this endpoint at this time as SAP does not provide a way to sync this data incrementally which is important to the performance of this connector. We will add this functionality if the capabilities change in the future. 

    Thanks, 

    Frank