The database table OrgUnit contains organizational units.

This table has changed structure as of version 4.17 of the data model:

• Data model 4.16 and earlier

• Data model 4.17 and later

Typically, database tables containing data related to organizational units will only store the key (Type,Code) of the organizational unit (this is called "database normalization"). Therefore, when accessing data in the data model using SQL, you will very often need to join with the OrgUnit table, e.g. to get the name of the organizational unit.

However, you should NEVER join with the OrgUnit table directly. Always use view OrgUnitCurrent! This will hide the complexities of handling current/historic data and differences in data models.