HRBAIRS Data Dictionary - ORG_NODE

The Berkeley campus organizational unit with which a job is associated. This code is not the same as any component piece of chartstrings that are part of the campus General Ledger.

Codes that identify nodes on the UC Berkeley Organization Tree - the same tree used in BFS - are valid values of ORG_NODE. Codes corresponding to Level 2 (Control Unit) through Level 7 (Org Code) are allowed. Spreadsheets that list these codes and their hierarchical relationship are available on the Organization Tree Reports page.

FAKE PARAGRAPH ONE - Some Experimental text with an insertion of inline-code in the middle of it. How does it look??? Here's another insertion of inline-code ... did we get both?

FAKE PARAGRAPH TWO - And now here's a FAKE code block:

1: select *
2: from table
3: where field="value"
4: ;

UCB Home Page is a link that leads off FAKE PARAGRAPH THREE.

Some inline code leads off FAKE PARAGRAPH FOUR.

Though labeled "Department" on PeopleSoft screens where an HRMS user most often comes across this code, ORG_NODE can in fact refer to levels of the Org Tree ranging from Level 2 (Control Unit) to Level 7 (Org Code) -- including but not limited to Level 4 (Department). It is because this code can refer to levels of the Org Tree other than Department that the field is re-named to ORG_NODE in the Data Warehouse.

This code should not be confused with Org Code, which is a component of the General Ledger chart string.

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 lookup view provides information about parent-nodes of the ORG_NODEs it describes. 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, this view includes one row for every node above it, and one for itself. It is a relational variant of the Data Warehouse view DEPT_HIERARCHY_LKUP. It allows, for example, the ability to select a parent node (without specification of a level) and all subsidiary nodes to the parent.

Lookup view DEPT_TBL_LKUP provides descriptions for code values.