Position Management

Is there an option for mass inactivate position?

Course: Position Control

No, there is no way to inactivate multiple positions at once at the Location level.

Should I ever use the Worksite ID of: "N - I-9 integration not required"?

In most cases, you must select the department’s Region as the HR Worksite ID to ensure proper integration with the Tracker I-9 system.

In the rare situation that a position number is needed for a contingent worker (CWR) (only for CWRs that will be supervising Employees). In this case, an I-9 is not required and the HR Worksite field in Position needs to be “N – I-9 integration not required”. The “N” Worksite must be in place prior to hire; otherwise, an I-9 email notification will be sent erroneously to the person.

If you have a contingent worker “A” who supervises another contingent worker “B”, but contingent worker “B” does not need to submit a timesheet in CalTime, does contingent worker “A” need to have a position number?

Position numbers are only assigned to contingent workers who need to sign off on the time of an employee they supervise. If a contingent worker "A" supervises another contingent worker "B," there is no CalTime involved, so there is no need for a position number. If a contingent worker "A" supervises an employee "B", who enters time into CalTime that then needs to be approved, the contingent worker "A" will need a position number.

What is the difference between the department code and the Dept ID?

The department code in Position and Job data identifies the department an employee works in, and is a series of letters (ex: KNBAM). The Position Management and Job Data pages display this value as ‘Department’, but the Person Organizational Summary page abbreviates “Department” to “Dept ID”, and it is showing the Department (ex. PMATH).

There is also another value present on GL pages (Funding Entry, Salary Cost Transfer, Benefit Cost Transfer) called DeptID, which is a series of numbers. This value is a component of a chartstring (FAU).

Employee Relations Codes (ERC)

What are Employee Relations Codes?

Employee Relations Codes (ERC) are designations in UCPath that identify an employee’s labor relations status as "confidential, supervisory, or managerial." The ERC determines whether an employee is included in or excluded from a bargaining unit under the Higher Education Employer-Employee Relations Act (HEERA). Using the correct code is important because it directly impacts collective bargaining...

Position Management Community of Practice

What is the Position Management Community of Practice?

A quarterly meeting series hosted by the Berkeley UCPath Operations Team to bring together subject matter experts and decentralized UCPath Position Management Transactors.

Job Aids & Resources | Vacant Position Management

Access step-by-step guides, checklists, resources, and reference materials related to Vacant Position Management.

Training Options & Requirements | Vacant Position Management

Find available training courses, eligibility requirements, and details on what’s required for UCPath access.

SARA Roles to Request | Vacant Position Management

Learn which roles to request (Inquiry, Initiator, Approver) and how to get the right access for your job.

(Vacant) Position Management

What is Vacant Position Management about?

The Position Control module in UCPath is essential for creating, maintaining, and updating vacant position data.

Position data forms the backbone of UCPath operations, influencing job creation, employee assignments, and organizational structure. Positions are essential to the function of many other parts of UCPath.