2267497 - HRIS sync fails - Remote exception: SQLException thrown ORA-00001

HRIS Daily Sync fails repeatedly. The daily sync detail log information in the provisioning displays an error:

"Remote Exception: SQLException thrownORA-00001: unique constraint (SFV4_[customer's instance ID].UC_USER_ACCOUNT_USER_NAME)"

Where "[customer's instance ID]" is the company ID of the customer instance.

In this case a custom string, custom-string18, is mapped to the username field in the HRIS sync mapping section of the Succession Data Model (SDM). The custom string field value being sync'd with the username field is not a unique username. Since the custom string field is mapped to username and username must be unique, the value being passed via sync mapping must also be unique otherwise the system will throw the "ORA-00001" error when the sync job is executed.

 Sync Mapping XML excerpt from the Succession Data Model:

  <hris-sync-mappings>
    <hris-element-ref refid="jobInfo">
      <hris-mapping >
        <hris-field-ref refid="custom-string18"/>
        <standard-element-ref refid="username"/>
      </hris-mapping>
    </hris-element-ref>
  </hris-sync-mappings>

There exists two choices to resolve:

1. Ensure the custom-string field value being passed to the username field via sync mapping is unique.

2. Or remove the HRIS sync mapping of the custom-string field to the username field from the Succession Data Model sync mapping section.

PLEASE NOTE: Synchronizing data to the "username" field is not supported. Though technically the sync-mapping does work, as per the note in this article, you can encounter a non-descript Application Error when you try to enter a username value that is already assigned to another user account. This is expected behaviour and currently there are no plans to support this in the future. Please refer to the following article for further information

• 2328225 - HRIS Sync: Unable to synchronize EC field to username (EP) from specific elements

KBA , LOD-SF-EC-HRS , HRIS Sync , Problem