SAP Concur Account Aggregation via OOTB connector

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

IIQ Version - 8.3
Hello Experts,

We want to import the below attributes from the SAP Concur via the SAP Concur OOTB connector.

image
image1531×478 21.9 KB

we have made the below jsonPathConfig configurations for this and also added the attributes in schema

image
image1476×238 140 KB

But still the values are not getting imported.

Can you please guide if any configuration is missed?

Thanks,

Shamal

2

Hi @shamal_khokle Have you enabled custom account attribute support? See Enable Custom Account Attribute Support

3

Hi @j_place

Yes, we have enabled that.

image

Thanks,

Shamal

4

Hi @shamal_khokle

Small Observation(miss match) on your configuration as highlighted below.

image
image1601×759 321 KB

please check incorrect config as highlighted above and rectify it.

5

Thanks @shamal_khokle Have you included the spend.user.general.read scope on the concur oauth 2.0 application? Also, can you see these attributes returned using Postman?

6

Yes, its included.

image
image556×484 83 KB

Thanks,

Shamal

7

HI @shamal_khokle Can you confirm where that screengrab is from? Also can you confirm that the Account ID is getting mapped correctly?

8

Hi @shamal_khokle

Looks like you have skipped my comment?

9

Hi @pattabhi

We fixed that config and tried but still values are not imported.

Thanks,

Shamal

10

Hi @j_place

Account ID is properly mapped.

For other attributes values are getting imported but not for the one mentioned above.

Thanks,

Shamal

11

Thanks @shamal_khokle When you say other attributes are getting imported, have you retrieved any spend type attributes? AFAIK IIQ has to make a supplementary call (using the UUID) to the Spend API to retrieve those attributes.

Have you been able to connect to the Spend API using Postman? See SAP Business Accelerator Hub

12

@j_place Yes, we are able to connect to Spend API using postman.

In Sailpoint we are importing customData.custom17, customData.custom21, customData.orgUnit1, customData.orgUnit2 and report.approver from Spend API.

Thanks,

Shamal

13

Notwithstanding @pattabhi comment on incorrect xpath for promptForCardTransactionsOnReport could you include your attribute mapping schema.

Are you for instance processing the Preference type attributes as Booleans?

Also, the wildcard in request approver may not be returning what you’re after, maybe specify the Approver Type and Primary flags to return one element.

Also, stateProvince - are you sure it’s getting populated in Concur?