Impact of making 'Overlap Allowed' field at position level to Yes/No in ORC.

Summary:

Hi All,

Can anyone help in understanding the relevance of 'Overlap Allowed' field at Position structure in ORC. We went live with Oracle Fusion last year and during data migration for positions, we migrated the position data with 'Overlap allowed' field marked as Yes.

Now business want to have a control on all those positions created, so we have a request to make this field 'No' and set the HC and FTE as per the no. of employees currently tagged to these positions.

We want to understand the impact and implications of making this field as 'No' from ORC point. And understand what challenges we might face if we make this field as No. Since there are more than 1K positions so we want to be sure before doing this activity.