Copying Data from PeopleSoft Project Costing to Microsoft Project
This topic discusses issues that are related to creating or updating a project in Microsoft Project with data that exists in PeopleSoft Project Costing.
Project Data
When you're creating a project from PeopleSoft software to Microsoft software, project-level data is stored in the Microsoft custom properties to validate future updates. This data includes project origin—PeopleSoft or Microsoft—business unit, project ID, project type, project status, duration, project manager name and employee ID, project manager start and end dates, and project manager effective date.
Activity Data
PeopleSoft activity-level data is synchronized with the Microsoft Project tasks. Activity data copied or updated includes activity ID or task name, activity type, description, start and finish dates, percent complete, duration, summary flag, and milestones. User text type fields are used to store key information for use in future updates. For example, the unique ID that is used for each activity business unit, project ID, and activity ID in the PeopleSoft system is stored in the Microsoft Project Task.Text20, Task.Text21, and Task.Text22 (and alsoText30) fields, respectively, when you are synchronizing activities and tasks. If the value of Text30 is altered or deleted, future updates are inaccurate.
If you use PeopleSoft Program Management, the activity date cascade calculation method that you define in the PeopleSoft system is exported to Microsoft Project based on the mappings in this table:
| PeopleSoft Activity Date Cascade Calculation Method Exported to Microsoft | Calculation Method Converted in Microsoft |
|---|---|
|
Manual |
Manual |
|
Delay Calculations Until Save |
Manual |
|
Realtime Calculations |
Automatic |
See PeopleSoft Program Management: Establishing PeopleSoft Program Management Business Unit Options.
Note:
If the autocalculation option is selected when you export data to the Microsoft system, the dates and duration data that are sent to the Microsoft system may not remain intact. This is due to the many internal calculations that Microsoft Project makes to new or altered data.
Work Breakdown Structure
The WBS ID (work breakdown structure ID) is specified on the PeopleSoft activity definition and is copied to the Microsoft system when you export activity definitions. The WBS ID in the PeopleSoft system and the Microsoft system is a concatenation of the parent outline number and activity outline number, and cannot be modified manually. Changes that you make to a project WBS structure are reflected in the Microsoft system during the next integration process.
The PeopleSoft - Microsoft Project Integrator moves tasks by cutting and pasting. Activities that you delete in the PeopleSoft system are not automatically deleted in the Microsoft system.
Dependencies and Constraints
If you use PeopleSoft Program Management and export activity definitions from the PeopleSoft system to the Microsoft system, the integration process copies activity dependencies and constraints. During the export process, the system deletes the existing dependencies in Microsoft Project and creates new dependencies based on the dependency data sent from the PeopleSoft system.
During the export process, the PeopleSoft system also sends activity constraint information such as the deadline date, constraint type, and constraint date.
Team Members and Resource Assignments
The contents of the project team list can be copied into the Microsoft Project resource sheet. Resources that are on the project activity team can be assigned in the Microsoft Project resource assignments. If activities and resources are copied to Microsoft Project, the integration process creates Microsoft resource assignments if the assignments in the PeopleSoft project activity team match a task and resource in Microsoft Project.
The resource's cost rate and bill rate are from the Cost Rate field (COST_RATE) and Bill Rate field (BILL_RATE) in the Project Team Member table (PROJECT_TEAM) in PeopleSoft Project Costing if you use PeopleSoft Program Management. If you use PeopleSoft Project Costing without PeopleSoft Program Management, the resource's cost and bill rates are from the Rates by Role table (PC_RATE_ROLE). The resource's cost rate is stored in the Resources.StandardRate field in Microsoft Project. The resource's bill rate is stored in the Resources.Cost1 field. Job codes do not exist in the resource sheet.
You can export the Budget Item field (PC_BUDGET_ITEM) and Project Role field (PLAN_PROJROLE) values from the project level in PeopleSoft Project Costing to the resource sheet in Microsoft Project. The Microsoft Project system stores these values in custom text field Resources.Text10 and Resources.Text9. The project role is exported to Microsoft Project only for labor resources.
If you use PeopleSoft Program Management, values from the Units field in the assignment schedule in the Resource Details page copy to the resource sheet in Microsoft Project.
As resources are copied to the resource sheet, the system creates a unique ID and stamps it in the Resource ID field (RES_UID) in the Project Team Member table for future updates. If you remove a team member or delete an assignment, it is not reflected in the Microsoft system.
Transaction Data
Transactions and resource data are sent to the Microsoft system in the following way:
-
Actual Cost Rows: Rows in the Project Transaction table that have actual cost analysis types are summarized by activity and copied to Microsoft Project as actual cost values at the task level.
Resource amount is the summarized field. The Actual Cost (Task.ActualCost) field is updated on the matching task in the Microsoft system.
-
Actual Work Rows: Rows in the Project Transaction table that have actual cost analysis types and an employee ID are summarized by activity and copied to Microsoft Project as actual work values at the task level.
Resource Quantity is the summarized field. The Work field (Task.Work) is updated on the matching task in the Microsoft system.