Troubleshooting SAP Concur Errors

When troubleshooting Concur Sync for SAP Concur API Version 3, the sync log CSV file contains error messages for the specific process and Veeva CRM record that failed. The table below provides additional information on description of the error and possible resolutions for troubleshooting.

Error	Description	Resolution
Internal Server Error	A general error response from SAP Concur that may be due to an outage or a configuration preventing an expense or attendee creation.	Log a product support ticket. Veeva will investigate with SAP Concur to identify the root cause.
Failed to Retrieve Open Reports	Occurs when the integration is unable to find any SAP Concur reports for the submitting user.	In Veeva CRM, verify that the Concur User ID field is populated with a correct value on the user record.
Invalid List item ID	Occurs when a mapped SAP Concur field is configured as a List and an incorrect Veeva CRM field value is mapped. SAP Concur requires using ListItemId when creating the attendee or expense.	In Veeva CRM, evaluate which mapped SAP Concur field is configured with a List. For Call, ensure the SAP Concur List is selected for the mapped Veeva CRM field. For Events, ensure the ListItemId is passed for mapped Veeva CRM field.
Missing required field: <Field Name>	Occurs when an attendee or expense is submitted and is missing required fields.	Check the attendee or expense and ensure the mapped Veeva CRM field is populated.
Field description exceeds the maximum length of <char limit>	A Veeva CRM field is mapped to an SAP Concur field with a character limit and that the Veeva CRM value exceeds that limit.	Ensure the Veeva CRM field does not exceed the character limit designated in the SAP Concur sync message.
Missing attendee last name / first name	The integration is creating an Attendee in SAP Concur with the specified mappings of the related Veeva CRM object, however, the attendee is missing requiring first or last name information.	Check the attendee record and ensure the mapped Veeva CRM field has values populated.
Failed to Retrieve Existing Attendees	The integration is unable to query the SAP Concur attendee database to determine which attendees must be created.	In Veeva CRM, review the configured Attendee Types. In SAP Concur, ensure they are valid and active in the SAP Concur policy by working with your Concur Administrator. Ensure that Attendee Types are configured with an External Id field on the Expense Attendee Form and that the field is available in the Duplicate Search setting.
An attendee with the specified External ID already exists	The integration is attempting to create an Attendee in SAP Concur with the External Id mapping when there is already an existing Attendee with the same Attendee Id. This indicates an attendee visibility issue in Concur.	In SAP Concur, update the configuration to remove the Created By (Private List) field from the Expense Attendee form for that Attendee Type.
You do not have permission to access the requested resource(s)	The integration is unable to associate an attendee to the submitted expense. This is because the integration is unable to access that attendee based on External Id.	In SAP Concur, ensure that the Attendee with the specified External Id is Active. Update Concur configuration to remove the Created By (Private List) field from the Expense Attendee form for that Attendee Type.
Missing attendee ID	An attendee is missing an External Id value.	Review the attendee mapping for ExternalId field. Ensure that all attendees under the expense have the mapped Veeva CRM field populated.
PaymentTypeID was not specified	Payment Type was included in the expense mapping.	In Veeva CRM, ensure Payment Type is mapped correctly with a value.
The payment type isn’t available for this user	A payment type was specified, however, it is not configured in the end user’s policy in SAP Concur.	In SAP Concur, ensure that the end user is tied to the Policy the Payment Type belongs to.
The expense type isn’t active in the Policy associated with this expense report.	The expense has a mapped expense type that the user does not have access to.	In SAP Concur, ensure the mapped Expense Type is valid for the end users’ policy.
The specified Expense Type Code doesn’t match an Expense Type for this user’s Expense Group	The expense has a mapped expense type that the user does not have access to.	In SAP Concur, ensure the mapped Expense Type is valid for the end users’ policy.
ExpenseTypeCode was not specified	The expense was not created because it did not have an expense type mapped correctly.	In Veeva CRM, review the expense mapping for ExpenseTypeCode and ensure a value is populated.
Input string was not in a correct format	One of the mapped fields is sending a value that does not match the expected format in SAP Concur. For example, the number field in SAP Concur cannot include a decimal point.	In Veeva CRM, Review the mapped fields and ensure they are sending the expected field values. Log a Veeva Support ticket if further investigation is needed.