Impact of Disabling Standard FTE Field

Summary

Hello,

We're evaluating the possibility of disabling the standard FTE field in Oracle HCM and replacing its usage with a custom field.

Before proceeding, we'd like to understand the potential impacts of this change.

In particular:

• Which standard HCM processes rely on the standard FTE field?
• Could disabling it affect transactions such as Hire, Change Assignment, Local Transfer, Global Transfer, or Position Synchronization?
• Are there any impacts on approvals, reports, extracts, integrations, OTBI, HDL, REST APIs, or delivered calculations?
• Has anyone already implemented a similar approach and identified any limitations or side effects?

Any feedback or lessons learned would be greatly appreciated.