Populating the org chart
So, however you display the org chart in your portal, you will need to get things right in the back end or suffer the constant “massaging” of your data.
A common approach is to have a field in every employees record with the value of the employees managers name, and/or a field with the managers employee id (or some unique value). Problem is, when someone leaves the company, changes their name, or changes jobs, the chart can “break”.
A solid way to implement the unbreakable chart is to create a Position Code schema for each position in the company (big job, I know). These are different from Job Codes where a manager can have 5 employees with the same Job Code, the position code is unique to each desk in the organization.
Then, the hierarchical relationship between the Position Codes can be established completely seperate from names, by using a table that matches the codes, to the code of their manager. Then each employees record has a field for their Position Code.
Basically, you have an org chart of only position codes, until you join it with employee names. Anytime a position code exists without a name attached to it, you have a vacancy, which you can then tie into your Internal Job Postings application.