Last updated on JANUARY 17, 2017
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.
Attempting to save multiple seniority dates using SmartHR and it fails at the last step in the component interface save. If only one seniority date is defined at the SmartHR template section level, it will save.
It appears to not be assigning the SENIORITY_DATE_ID correctly in the CI and causing a duplicate key error upon save.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms