E1:08: HCM Foundations Employee Supplemental Data FAQs
(Doc ID 1070530.1)
Last updated on OCTOBER 28, 2019
Applies to:JD Edwards EnterpriseOne HCM Foundation - Version XE and later
Information in this document applies to any platform.
***Checked for currency on 29-Apr-2011***
This document clarifies the allowable grid changes to Employee Supplemental Data Type.
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
|Questions and Answers|
|Question 1: Is it possible to design the order of data items on the grid when defining Employee Supplemental Data Type?|
|Question 2: Why is T3EFTE defaulting to 12/31/2012 when a new record is created in Supplemental Data. How can this be turned off?|
|Question 4: How can applicant supplemental data be transferred t an employee during the hire process?|
|Question 5: In Supplemental Data inquiry, why is the data not aligned with the column headings?|
|Question 7: How does EnterpriseOne assign the unique key identifier (UKID) in the Supplemental Data table F00092?|
|Question 8: Is it possible to make one field in supplemental data mandatory of another field that has a certain value? For example, if the UDC value is populated, then the user date must also be populated ?|
|Question 1: When running R0500104 (HRM Supplemental Data Narrative Text Conversion) why is a duplicate key error received?|