SAP Concur supported features

Users created in Okta are also created in SAP Concur.

Here are some important things to note:

• When you add a username in Okta, it appears as the employee number in SAP Concur. This is a required field. You can edit it in your SAP Concur org if needed.
• You must assign a user country, user locale, and user reimbursement currency when you create a user. These values depend on the country packs that are enabled in your SAP Concur org. See Country Codes and Locale Codes for supported codes. For more information, contact your SAP Concur representative.
• To view the supported reimbursement currency for your org, contact an expense admin. See Expense Pay Country Availability for more information.
• If the user country, user locale, or user reimbursement currency is invalid, the user's spend profile fails in SAP Concur and their Okta profile is deactivated.
• If a user shows a pending status in SAP Concur, try recreating the user later.

Here are some important things to note:

• If the user's spend profile is missing, you can't update their role. See Spend Role Codes.
• If a user shows a pending status in SAP Concur, try pushing profile updates later.
• If the user country, user locale, or user reimbursement currency is invalid, the user's spend profile fails in SAP Concur and their Okta profile is deactivated.
• You can't update a user's role if Okta detects conflicting role permissions.

Updates made to a user's profile in SAP Concur are downloaded and applied to the profile fields in Okta.

Imports more user attributes from SAP Concur. This is also known as schema discovery.