IIQ Upgadre issue from 8.3 to 8.4p2

[nasiralam]

After IIQ upgrade from 8.3p2 to 8.4p2 SAP SAP HR/HCM connector is not reading the custom attribute from the SAP. While running account aggregation custom attribute name with Login id getting set as bull. Is any things we need to check for custom attribute configuration to read from SAP side. Custom attribute already added in applciation sceham in IIQ with same name as defined in SAP side.

[enistri_devo (Emanuele Nistri)]

It could possible with the new version of IIQ, the SAP connector has been changed the reading method. Check if IIQ 8.4p2 is compatible with your SAP version and read into the connector documentation how read the custom attributes.

[vinnysail (vinod kumar maram)]

Hi @nasiralam

I also faced similar issues but for different SAP connector (SAP GRC)

Please raise a case with sailpoint to understand if there is any issue with sap connector which is present under web-inf/lib folder (explain more details about your use case in the case)

[narayanag (NarayanaG G)]

@nasiralam I have reviewed the release notes for this connector—SailPoint has introduced new features and resolved some existing issues.

Go through the release notes.
The SAP HR/HCM connector now correctly populates the values for communication data.
CONETN-4673
The SAP HR/HCM connector no longer fails during account aggregation
when a build map rule is configured.

CONETN-4355
The SAP HR/HCM Connector no longer creates dump in SAP target system when
an aggregation is performed.

SAP HR/HCM connector is now enhanced to configure with load balancer
parameters when SAP system is configured with load balancer at customer
end.
SAP HR/HCM connector is now certified with SAP S4Hana 2022 version.
CONNAMDANG-4337

@ Emanuele Nistri said how to read the custom attributes.

[nasiralam]

@vinnysail - thanks for your response. I have already raised case with SailPoint however as of now no solution received. may i know what was the root cause and fix in your case.

[vinnysail (vinod kumar maram)]

Hi @nasiralam
In our case the connector was sap Grc and we connected to the connectors team and they shared a new sap grc connector jar after placing in lib folder. We tested couple of scenarios which were failing and they worked after the replacement of new jar file.