Job code restructure ideas and best practices

Summary:

We are undertaking a project to convert our existing job code structure to a more rational scheme.

Content (please ensure you mask any confidential information):

As mentioned earlier, I’m looking for any insights, best practices, or lessons learned from others who have gone through a similar exercise.

I have a few foundational questions:

1. Is there a recommended approach for structuring job codes effectively?
2. What specific changes are typically required from an HCM perspective? We've done a preliminary impact analysis but would appreciate validation.
3. Are there any known limitations in Oracle HCM related to nomenclature, field lengths, or other constraints?