Failed Submissions to SAP Concur
If there is a failure when submitting an expense to SAP Concur, the Expense Entry is deleted in SAP Concur. All associated Itemizations, Entry Attendee Associations, and receipt attachments are also deleted.
Attendees and Reports created before the Expense Entry are not deleted in SAP Concur.
If the delete fails in SAP Concur or if the response of a successful delete is not returned to Veeva, the SAP Concur System ID value is retained in Veeva on the Expense Header record. When the expense is resubmitted to SAP Concur, the integration checks if a record with the saved SAP Concur System ID exists in SAP Concur. If the record exists in SAP Concur, the integration deletes it before resubmitting. If this secondary deletion attempt fails, the SAP Concur Status of the Expense Header is updated to Failed_Duplicate_vod.
If the submission fails, the Resubmit to SAP Concur button displays on the page layout. The reason for failure is saved and accessible in the SAP Concur Real-Time Sync History section of the SAP Concur Real-Time Administration tab.
Failures display to users in the following locations:
|iPad Event Grid View|
|Event Detail Page|
|Expense Headers Related List|
|Expense Header Detail Page|
Administrators can view the submission transaction log from the SAP Concur Real-Time Sync History section of the SAP Concur Real-Time Administration tab. Other actions include:
- Filtering to only display errors
- Searching expenses by time, Expense Header name, status, user, or failure reason
- Downloading individual or bulk transaction logs
Veeva stores logs for up to two years. To obtain logs between 90 days and two years, contact Veeva support.
- Resubmit expense records. Expenses resubmitted by the administrator are submitted on behalf of the record owner in SAP Concur.