HRBAIRS Data Dictionary -

Date of birth.

Employee ID. The key field used to uniquely identifying employees and non-employees in HRMS. Values auto-generated by HRMS upon hire.

The Ethnic Category Code described by a row of data. Ethnic Categories are those with which employees are invited to self-identify (e.g., Chinese, Japanese, Mexican, Latin-American, etc.). Ethnic Categories are aggregated into Ethnic Groups defined by the federal government for regulatory reporting purposes. Data in this field can be accessed only by central-office employees who prepare the reports in which it is used.

A code identifying the Ethnic Group in which the Ethnic Category described by this row of lookup table data is aggregated for federal reporting purposes. Data in this field can be accessed only by central-office employees who prepare the reports in which it is used.

A person's full name. Last name is given first in this field (e.g.: Smith, Lee X.).

A person's sex (M or F)

Identifies the broad category of transaction represented by a row on the HRMS job record (e.g., Data Change, Hire, Promotion, Return from Leave, Termination). Values for this field may be viewed on the HCM: Action/Reason Chart

ACTION_REASON, with which ACTION_CD is paired, identifies the specific kind of transaction within the broader category.

Date this row of Job data was created; this date is not modified when the row is corrected using PeopleSoft HRMS "Correction Mode."

ACTION_REASON identifies the specific kind of transaction represented by a row on the HRMS job record, within the broader category defined by ACTION_CD. For example, ACTION_REASON codes subsidiary to the ACTION_CD signifying "Hire" include: Hire with Recruitment, Hire with Waiver, Hire from other UC Campus, etc. Values for this field may be viewed on the HCM: Action/Reason Chart

In the ACTION_REASON_LKUP view, this field is the Action Reason described by the row of lookup data, and is a key field in the view.

Rate of pay for the job represented by this row of data, in dollars per year, normalized to 1.00 FTE.

This field does not contain meaningful data.

This field does not contain meaningful data.

Begin date of the most recently created appointment in PPS that corresponds to the row of HRMS job data in which this field occurs.

Transactions in HRMS create appointments in PPS or not depending on the Action Code and Action Reason used. Only those Action Codes/Reasons that create new appointments in PPS cause this field to be changed from its value in the previous row of job data to the effective date of this row. In most cases, but not all, an Appointment Begin date signifies a new or a change in the JobCode for the Employment Record (EMPL_RCD_NO) described by this row of data.

The category of duration-of-employment. Examples include: Indefinite, Tenure, End Date, Visa, etc.

The last date on which the job represented by the row in which this field occurs is effective. Not required in all cases; may be populated with a high value (12/31/9999).

APPT_END_DT is populated with a "real" date only when APPT_DURATION (Employment Duration) is set to certain values. For example, when Employment Duration is set to "I - Indefinite," HRMS shows a blank field for End Date, and APPT_END_DT in the data warehouse is set to 12/31/9999.

The Appointment Type code described by a row of data. The single-character codes (e.g. 2, X, 3, 1) translate to Appointment Types such as Regular/Career, Faculty, Limited, and Contract. A full list of values for this field can be found on the the HCM: Appointment Types page.

Phone number associated with the job described by this row of data.

The business title associated with the Employment Record row represented in this row in the Data Warehouse.

This is not a centrally-assigned title, but one associated with an individual campus position. A departmental user of HRMS may populate it with whatever descriptive title is appropriate.

Amount of change in salary from its most recent previous value. This amount is calculated only for "add to base" type components of pay.

Percentage change of salary compared to its most recent previous value. This percentage is calculated only for "add to base" type components of pay.

Status regarding citizenship in the United States (e.g., U.S. Citizen, Non-Resident, Resident Alien).

The organization to which the entity described by this row of data belongs (e.g., "UCB").

In the DEPT_TBL_LKUP view, the organization in which the Org_Node described by a row of data exists, e.g., "UCB".

Amount of periodic payment, expressed at a rate described by a related Compensation Rate code and disbursed at the frequency specified by a related Compensation Frequency field.

In the COMPENSATION view, the amount associated with this component of pay.

In the JOB_EARNS_DIST view, the rate or amount from which pay is to be calculated for a row of Job Earnings Distribution data.

For example, if the DIST_PERCENT is 10.0000%, and the COMP_RATE is $3,000.00, this row describes an earnings distribution of $300.00. Where Earnings Codes are not based on a percentage of time (e.g., stipends or housing allowances), the earnings distribution described by the row is based on the COMPRATE only.

The frequency at which the job-level pay described in the COMPRATE field is paid.

In the COMPENSATION view, the frequency at which a component of pay, described by the row of data in question, is disbursed to the employee.

The Control Unit associated with the Org_Node (loosely, "Department") to which the job described by this row of data is assigned.

Currency in which compensation rates are recorded, e.g., "USD" (United States dollars).

The most current record for each employee and job, not future-dated, as of the most recent refresh of the Data Warehouse table contains the value "Y" in this field. Records other than the current one contains the value "N".

Date of death.

The date since which ORG_NODE has remained constant at the value in this Data Warehouse row (for the EMPL_ID plus EMPL_RCD_NO in this Data Warehouse row only). That is, the most recent effective-date on which the value of ORG_NODE in job rows with the EMPL_ID + EMPL_RCD_NO in this Data Warehouse row changed to the value of ORG_NODE in this row.

The grade associated with the job represented in this row in the Data Warehouse, as displayed on the Compensation page (as opposed to the Salary Plan page) in the Job Data component of the HRMS application.

This value is blank (null) for certain values of Grade displayed on the Salary Plan page of the HRMS application (SAL_GRADE in the Data Warehouse). As of October 2002, job rows with grades displayed on the Salary Plan page as "NA", "OPN", or "STP" will have DISPLAY_GRADE fields populated as blanks (a single space character).

The step associated with the job represented in this row in the Data Warehouse, as displayed on the Compensation page (as opposed to the Salary Plan page) in the Job Data component of the HRMS application.

This value is blank (null) for certain values of Step displayed on the Salary Plan page of the HRMS application (SAL_STEP in the Data Warehouse). Determination of whether the DISPLAY_STEP is blank is based on the Salary Administration Plan associated with the Job_Code for this row; and/or the values of the OFF_ABOVE_SCALE_CD in Compensation table child-records to the row of Job data reprented by this Data Warehouse row

A system-generated key field that distinguishes one concurrent job from another for those employees who hold multiple jobs simultaneously.

When multiple jobs are held simultaneously, concurrently-effective rows with different EMPL_RCD_NO (Employment Record Number) values will exist. Different jobs held sequentially will generally re-use the same EMPL_RCD_NO value; a new EMPL_RCD_NO is generated for an employee when an ADD ADDITIONAL JOB action occurs. More information is available on the HR web site about HCM: Concurrent Jobs.

The Employee Relations code indicates whether a job is that of a manager or supervisor; and whether or not the position is considered "confidential."

In summary views, indicates the Employee Relations code for which data is summarized in a row.

Employee Status. Examples: Active, Leave with Pay, Leave without Pay, Suspended, Terminated, etc.

The position title, for Employee Relations purposes, associated with the Employment Record row represented by a row in the Data Warehouse. This title is a derived value, based on the value of the Employee Relations Code (EMPL_RELATIONS_CD).

Status of this job as Fixed or Variable time.

Status with respect to the Fair Labor Standards Act (e.g., Exempt or Non-Exempt).

The FTE associated with the job described by a row of job-level data.

Note that the sum of Distribution Percent values in certain of the Job Earnings Distribution rows associated with the Job must equal the value of this field. Job Earnings Distribution rows with selected Earnings Code values are *not* counted toward the FTE value on the Job level.

Status as a full-time or part-time employee.

Highest level of education attained by employee (e.g., HS Graduate or Equivalent, Bachelor's Level Degree). This field must be populated for employees who hold Academic jobs. It is otherwise optional.

Date of most recent hire.

Hourly rate of pay for the job described by this row of data.

The code identifying the job (classification) described by this row of data.

The single non-null value, if it exists, from the Components of Pay (rows on the COMPENSATION view) associated with the job represented in this row in the Data Warehouse. Note that among multiple Pay Components (PS_Compensation table rows) associated with a job, a maximum of one may hold a non-null value in the O/A Scale field. That value, if it exists, populates this row of job-level data in the warehouse. Otherwise, the value of this field is Null.

A code that allows differentiation between Principal, Budgetary-Hold, Secondary, and Conversion categories of Job Rows (codes are P, B, S, and C, respectively). Human Resources analytical reporting is generally concerned with Principal rows only (and sometimes with Budgetary-Hold rows). The meanings of these categories and programmatic rules by which they are determined can be viewed in the full definition.

The date and time the row of Employment data represented in this row in the Data Warehouse was last modified in HRMS.

Date and time the job data in this row was updated in HRMS.

The user id of the HRMS operator who last modified the row of Employment data represented in this row in the Data Warehouse.

The Operator ID of the person whose login was used the last time job data in this row was updated in HRMS.

Last day person performed work in the job described by a row of data.

A system derived value indicating the date the last pay rate change was made on the Compensation page of the HRMS application (does not indicate pay changes entered through Earnings Distributions only).

Last date this person was "in pay status" in the job represented by a row of data.

The Leave Code for the job row represented in this row in the Data Warehouse. Values for this field may be viewed on the HCM: Leave Codes page

Location where the job described by this row of data is performed.

The mail code from the employee's campus mailing address.

MAX_PAY_RT_ANNUAL, taken from an HRMS lookup table not accessed directly by most HRMS users, is the highest dollar amount in the salary range for the job described by this row of data.

MIN_PAY_RT_ANNUAL, taken from an HRMS lookup table not accessed directly by most HRMS users, is the lowest dollar amount in the salary range for the job described by this row of data.

In a row of data that represents a hire where initial data entry was "cloned" from a "model" member of a group of similar hires, this field contains the Employee ID (EMPL_ID) of the employee from which the row's default values were cloned.

Rate of pay for the job represented by this row of data, in dollars per month, normalized to 1.00 FTE.

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.

Date of original hire at the University of California.

Pay Group associated with the job represented by this row of data. Examples include: ACA (Academic), MSP (SMG/MSP), PSE (PSS - Exempt), PSN (PSS Non-exempt).

The Pay Schedule for the job row represented in this row in the Data Warehouse. Examples include MA (Monthly Arrears), MO (Monthly), and SM (Semi-Monthly)

The Personnel Program associated with the job described in a row of data.

A person in HRMS can be an Employee ("E") or a Non-employee ("N"). This status is stored in the field PERSONNEL_STATUS_CD.

In summary views, indicates whether a row summarizes data on Employees or Non-Employees.

An indexable value to be used in choosing a single primary job (appointment) from among a single employee's multiple jobs (appointments) active at any given date (as-of date, or "snapshot" date).

This field is not used; it was superceded by PRIMARY_APPT_INDEX before any HR-BAIRS queries or reports utilized it.

The date on which a row of job (appointment) data took effect, often called "effective date." Job data pertains to a job held by an employee, rather than to the employee her/himself or to earnings-distribution or component-of-pay (compensation) data. Examples of "job-level" data include: job code, action code, Org_Node, and personnel program code.

In HRMS, the effective date and the date of data-entry often differ.

In the COMPENSATION view, this field contains the effective date of the Job row of which the Compensation row is a child.

In the JOB_EARNS_DIST view, this field contains the effective date of the Job row of which the Job Earnings Distribution row is a child.

When multiple job rows exist that are effective on a single date, this field indicates the sequence in which they were entered. The lowest, default value, zero, indicates first row entered on the effective date in question. Rows with higher sequence numbers supercede rows with lower sequence numbers on a given date. Effective sequence numbers are meaningful only in conjunction with the effective date of the row in which they occur.

In the COMPENSATION view, this indicates the effective sequence number of the Job row of which the Compensation row is a child.

In the JOB_EARNS_DIST table, this indicates the Effective Sequence number of the Job row of which the Job Earnings Distribution row is a child.

The date on which a row of employee data took effect, often called "effective date." Employee data pertains to an employee, rather than to an employee's job or a job's earnings-distribution. Examples of "employee-level" data include: name, home address, student status, birthdate.

Status as a regular or temporary employee. The value of this field is auto-populated based on the value of JOB_CODE in the job row in which it occurs.

Date of most recent rehire action (REH) in the Employment Record represented by this row in the Data Warehouse.

The date of the next scheduled performance/salary review for the job represented in this row in the data warehouse. As of September 2002, Review Type and Review Date apply to Career appointments only, and the Revew Type is always "2" (Merit) or Null. In general, these fields are populated for new hires only.

The type of review associated with the REVIEW_DT (review date) in the job represented by a row in the data warehouse. As of September 2002, Review Type and Review Date apply to Career appointments only, and the Revew Type is always "2" (Merit) or Null. In general, these fields are populated for new hires only.

Salary Administration Plan associated with the job described by this row of data.

Salary Grade associated with the job described by this row of data.

The grade associated with the job described in this row of lookup table data. A key field in this table (i.e., multiple rows for a single job can occur in this table when the job can be associated with multiple salary grades).

Salary Step associated with the job described by this row of data.

A key field internal to PeopleSoft HRMS, useful if the PeopleSoft installation tracks data for multiple organizations. At UC Berkeley, as of January 2004, all values of SETID are the same.

A key field internal to PeopleSoft HRMS, useful if the PeopleSoft installation tracks data for multiple organizations. At UC Berkeley, as of January 2004, all values of SETID are the same.

The usual shift (Day, Evening, Night, etc.) worked by the employee in the job described by this row of data. ("N/A" - for Not Applicable - is the default value for Exempt employees.)

Student status (e.g., Undergraduate, Graduate, Not Registered).

The Employee ID (EMPL_ID) identifying the supervisor of the person whose job is described by this row of data.

Date on which the job described by this row of data was terminated. Note that termination of a job may differ from termination of an employee (an employee may hold multiple jobs).

The Time Code for the job row represented in this row in the Data Warehouse. Values include: A (Positive Pre-list), E (Exception Time), N (None), W (Without Salary), Z = (Positive Roster - electronic)

Code representing a campus bargaining unit. Examples include: 99 (Non-represented), CX (Clerical Unit), RX (Staff Research Profession Unit), SX (Service Unit).

In summary views, this field indicates the bargaining unit summarized in a row of data.

A key field internal to PeopleSoft HRMS, useful if the PeopleSoft installation tracks data for multiple organizations. At UC Berkeley, as of January 2004, all values of SETID are the same.

A key field internal to PeopleSoft HRMS, useful if the PeopleSoft installation tracks data for multiple organizations. At UC Berkeley, as of January 2004, all values of SETID are the same.

The postal Zip Code in an address.