Concur - PSA MappingsThe mappings used by the connector are defined as records of the following custom metadata types:
Concur Expense Type Mapping
IHC Mapping Concur to PSA
The Integration Hub Connector: Concur - PSA provides default mappings that can be used out-of-the-box. Depending on your requirements, you can modify existing or create new mappings. For a full list of default mappings, see the following in the PSA Help :
Notes:
When creating or changing mappings, make sure to map PSA fields to Concur fields of the same type. For example, you must map a Boolean PSA field (checkbox or formula field) to a Boolean field in Concur.
Once you activate the Integration Hub Connector: Concur - PSA via the Feature Console , the customized mappings become active. If you already activated the connector before editing the mappings, you need to revert the Push the keys and mappings step in the Feature Console and perform it again. If you create or change a Concur expense type mapping, you must also revert the step for enabling the Sync Expense Reports from Concur to PSA workflow and perform it again.
Warning 1: If FinancialForce Services Resource Planning (SRP) is installed in your org, you must ensure that each Concur expense type mapping has an equivalent expense type GLA mapping. This allows SRP to automatically populate the Expense GLA Code field for expense records. If an expense type GLA mapping is not configured for an expense type, the expense report cannot be approved. For more information, see Creating Expense Type GLA Mappings
Warning 2: The following mappings are required for the connector to work properly. You must not change or delete them.
ConcurItemId Level1Code Level2Code ListId
PSAAssignment
PSAExpenseAssignmentId Id ProjectId ReportId ResourceId
PSAExpenseReportAssignmentId Id ProjectId ResourceId
PSAProject
PSAResource
For steps on how to create, edit, or delete mappings, see the following: