Chapter 6: How to Create, Edit, or Close a Project
Learn about Chapter 6: How to Create, Edit, or Close a Project
Departments must use PADUA to create a new Oracle project with tasks, add new tasks to existing projects, or update to project or task including project team members and/or task manager. Each project must have at least one task. If a task is not requested by the department, it will be created by default. A task under a project is needed when you need the ability to track expense established at the project or task level.
6.1.1: Step by Step – Manual
6.1.1.2: General Projects - Move Fund Balances from Tasks to Projects
Submit Services & Support request to Internal Controls and Accounting – Support.
6.1.1.3: General Projects - Move YTD payroll transactions from old Tasks to Projects
Process Direct Retros in UC Path to ensure DOPES matches financial accounting. Or if that is not required, process manually in PPM.
6.1.1.4: General Projects - Move YTD non-payroll transactions from old Tasks to Projects
Review 3.3.2 Cost Transfer Matrix.
6.1.2: Step by Step – Automated Mass conversion of tasks to projects for General Projects
As of Spring 2021, the Projects team is working with ITS on a way to support departments that want to change their projects/task with a mass request. The below steps are still in pilot phase as of this publication and are subject to change.
- Access spreadsheet of Department/FinU projects
- Review projects and identify which tasks to move to new project.
- Indicate project manager (PM) email and Department category (Faculty/Dept Controlled) if desired. PM will carryover from current project if left blank.
- New Project name will be the current task name, but appended with the prefix from the project.
- New task name will be the same as the original task.
- Project Classification will stay the same.
- Submit S&S back when above is completed.
- Identify project/tasks that are on active contracts—will ask ITS if they can pull this.
- Update contracts appropriately (oracle doesn’t allow for Contract updates that we know of)
- ITS will create new projects.
- **If Dept already created new projects, annotate separately in step 2 so that this step is skipped
- ITS will move all project costs from old task to new project.
- Costs not in PPM but in GL
- Resources at project level
- Expenses with 0 project or missing POET
- Costs not in PPM but in GL
- Dept to do journal to move revenue appropriately.
- Dept verify that transactions transferred as desired in PPM and GL—using GL reports and Projects Panorama or other reports.
- Carryforward transactions and miscellaneous revenue will be reversed from PPM project costs.
- Dept verify balances in GL remained the same.
- Dept to communicate to upstream systems to stop using the old project/task combination (Concur, PO, ISIS, UCPath, recharges)
- Review any inflight transactions:
- If any open AR, those will have to be reverse on existing project task and redone on new project/task.
- If any open POs: initiate change order
- If any AP
- If any open Concur
- ITS to inactivate (end date) old task.
- Any transactions that post to old task after this conversion are the responsibility of the dept to initiate cost transfers.
In addition, at OFC Go live, Gift Revenue, IFIS converted carryforward balances and miscellaneous revenue was posted in PPM as negative costs. As of the release of this guide, that practice will not continue, and the existing transactions will be reversed by end of FY21.
Find answers, request services, or get help from our team at the UC San Diego Services & Support portal.