For each extant value of ORG_NODE, this table provides the "parent node" (the node above a given ORG_NODE in the campus hierarchy) and Level Number (as detailed in description of the DEPT_HIERARCHY_LKUP view).
Contains fields:| DEPTH_FROM_PARENT |
The number of levels between the Parent_Node and Org_Node described by this row of lookup table data. For example, the number of levels between an Org_Node and itself is zero; the number of levels between Department and Division is one; the number of levels between Department and Control Unit is two; etc. |
| LEVEL_NUM |
The level of the Org_Node described by this row of lookup table data. |
| PARENT_NODE |
One of the parent-nodes in the UCB Organizational Tree that occurs above the ORG_NODE described by this row of lookup table data. A parent-node is a node "above" the ORG_NODE in question. For example, an ORG_NODE that corresponds to a Department will have parent-nodes that corresponded to a Campus, a Control Unit, and a Division. For each ORG_NODE, the DEPT_HIERARCHY_MAP view includes one row for every node above it, and one for itself. |
| ORG_NODE |
The Berkeley campus organizational unit with which a job is associated. Codes are taken from the campus Organizational Tree. This code is not the same as any component piece of chartstrings that are part of the campus General Ledger. In the lookup view DEPT_HIERARCHY_LKUP, a single record exists for each ORG_NODE. All levels of the UCB Organizational Tree associated with that ORG_NODE - which may occur at any level between 2 (Control Unit) and 7 (Org Code) - are given on the same row. This allows database joins that can always yield, for example, the Control Unit and Division in which an ORG_NODE occurs on the UCB Organizational Tree. Levels below that which a row in this table describes are populated with null or a placeholder (e.g., double-hyphen). The DEPT_HIERARCHY_MAP view provides information about parent-nodes of the ORG_NODEs it describes. Lookup view DEPT_TBL_LKUP provides descriptions for code values. |