My Oracle Support Banner

SAP HRMS Connector Does Not Consider Character Position (Doc ID 1662504.1)

Last updated on JULY 21, 2020

Applies to:

Identity Manager Connector - Version 9.1.2.6 and later
Information in this document applies to any platform.

Goal

Using:

- SAP HRMS Employee Reconciliation Connector version 9.1.2.6
- SAP Listener running.
- OIM Incremental Recon events are created successfully.
- OIM Users are created successfully

Need to map one SAP HRMS IDOC attribute to many OIM UDFs. The expected behavior is to trim the same attribute following the mapping (Lookup.SAP.HRMS.AttributeMapping) below:

Administrative Unit Code: AUC001;NONE;SHORT_D;66;77;Text (Example.: ABCDEF)
AUC Role: AUC001;NONE;SHORT_D;66;67;Text (Expected value: AB)
AUC Role3: AUC001;NONE;SHORT_D;66;68;Text (Expected value: ABC)
AUC Role4: AUC001;NONE;SHORT_D;66;69;Text (Expected value: ABCD)
AUC Role5: AUC001;NONE;SHORT_D;66;70;Text (Expected value: ABCDE)
AUC Role6: AUC001;NONE;SHORT_D;66;71;Text (Expected value: ABCDEF)

But instead getting the same value (Example: ABCDEF) in all OIM UDF attributes:
AUC Role: ABCDEF
AUC Role 3: ABCDEF
AUC Role 4: ABCDEF
...

Notice that the source attribute is the same (Administrative Unit Code) and the AUC Roles attributes (AUC Role, AUC Role 3, 4...) are like Admin Unit Code substrings. It seems the connector is not considering the chars positions we need.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.