This chapter provides an overview of the integration of Project Costing and Program Management (if installed) with Microsoft Project 2002 and discusses how to:
Set up integration options.
Create Microsoft projects from PeopleSoft projects.
Create PeopleSoft projects from Microsoft projects.
This section lists prerequisites and discusses:
Project Costing and Microsoft Project integration.
Copying data from Project Costing to Microsoft Project 2002.
Copying data from Microsoft Project 2002 to Project Costing.
The Project Costing 8.9 integration is intended for use with Microsoft Project 2002, desktop edition only. Projects residing in Microsoft Project Server must be saved locally by using Microsoft Project 2002 Professional prior to integration. Before running the Microsoft Project 2002 Integration for the first time, you must:
Install the PeopleSoft - Microsoft Project Integrator on the network.
See PeopleSoft Enterprise Financials, ESA and Supply Chain Management 8.9 Product-Specific Installation Instructionslocated on the PeopleSoft Customer Connection website.
Specify the Third-Party Data Exchange default options on the Installation Options - Project Costing Integration page.
See Defining Project Costing Integration Installation Options.
The PeopleSoft - Microsoft Project Integrator is an application that must reside on at least one computer that is available on the network in order for integration to take place. The computer on which it resides requires these two components:
FTP service or access to an FTP share directory.
Microsoft Project 2002 application.
See PeopleSoft Enterprise Financials, ESA and Supply Chain Management 8.9 Product-Specific Installation Instructionslocated on the PeopleSoft Customer Connection website.
Integrating Project Costing and Microsoft Project 2002 combines the Project Costing project accounting capabilities with the Microsoft Project 2002 planning and scheduling features. The integration allows the Project Costing and Program Management applications to incorporate scheduling information for use across the enterprise and enables project managers to update their individual Microsoft Project 2002 files with actual costs, resources, schedules, and so forth from the PeopleSoft Enterprise applications.
The Microsoft Project 2002 integration allows for the transmission of data from PeopleSoft to Microsoft and vice versa. When you integrate, you have the choice of exporting data from Project Costing to a Microsoft Project 2002 file or importing data from a Microsoft Project 2002 file into the PeopleSoft system. You can run the integration either direction at any time, depending on the needs of the business and the project management methodology.
By using the integration of Project Costing and Microsoft Project you can synchronize:
Projects.
Project teams.
Activities.
Duration and date calculations.
Percent-complete calculations.
Budgets.
Actual costs.
Dependencies and constraints.
In addition, if Program Management is installed, the integration provides the ability to create and maintain assignments for labor, material, and assets at both the project and activity levels by utilizing the Program Management functionality of the Resources, Resource Detail, and Resources by Activity pages.
The Project Costing and Microsoft Project 2002 integration allows for the creation of projects in either application. The integration also allows for the transfer of tasks (in Microsoft Project) or activities (in Project Costing) and their associated resource assignments. Microsoft Project's user-definable field objects store specific Project Costing fields such as business unit and project ID. Microsoft Project also stores the Project Costing project and activity definition, description, status, manager, percent complete for the activity, budgets, dates, and duration.
Data Flow
There are four ways to integrate project data between PeopleSoft and Microsoft:
Integration Procedure |
Flow of Data |
Creating a project in Microsoft from an existing PeopleSoft project. |
Export from PeopleSoft to Microsoft |
Updating a Microsoft Project with data from PeopleSoft. |
Export from PeopleSoft to Microsoft |
Updating a PeopleSoft project with data from Microsoft. |
Import from Microsoft to PeopleSoft |
Create a project in PeopleSoft from an existing Microsoft project. |
Import from Microsoft to PeopleSoft |
This diagram is a high-level view of the integration data flow:
Flow of data between Project Costing or Program Management and Microsoft Project 2002
This table lists the types of data that are exchanged and the direction of the data flow:
Data Type |
Direction |
Project data. |
Bidirectional. |
Project team (resources). |
Bidirectional if Program Management is not installed. |
Activity or task. |
Bidirectional. |
Team or task assignments. |
Bidirectional if Program Management is installed. |
Job codes. |
PeopleSoft to Microsoft from project team if Program Management is not installed. |
Cost and bill rates. |
Bidirectional if you use custom rates. |
Budget items. |
Bidirectional. |
Actual costs. |
PeopleSoft to Microsoft. |
Budgeted costs. |
Microsoft to PeopleSoft. |
Work. |
PeopleSoft to Microsoft. |
Dates. |
Bidirectional. |
Percent complete (activity level). |
Bidirectional. |
Percent complete (project level if calculation method is manual). |
Microsoft to PeopleSoft. |
Duration. |
Bidirectional. |
Milestones. |
Bidirectional. |
Terminology
This table describes terms that are relevant to the integration between Project Costing and Microsoft Project:
Term |
Description |
Activity |
A project component that the system uses to capture charges that relate to that aspect of the project, and a representation of the work that is required to complete part of a project. In Microsoft Project 2002, activities are called tasks. |
Actual Work |
Tracks the amount of time that a resource has currently expended working on an activity. Actual work can be updated by time entry in Expenses, Time and Labor, and manually adding a transaction in Project Costing. The system calculates actual work at the activity level by rolling up the detailed actual rows. Actual work is not updated from Microsoft Project to Project Costing. |
Resources |
People, equipment, and material that are required for completing the project and the activities that are on the project. Resources can have rates associated with them for the purposes of deriving their estimated and actual costs to an activity and a project. |
Start Date |
A required field that represents the current start date of the project and activity. The start date can be entered in PeopleSoft or Microsoft. Given the duration and end date of a project or activity, the start date can be calculated. |
End Date |
A required field that represents the current end date of the project and activity. The end date can be can be entered in PeopleSoft or Microsoft. The end date can be calculated if there are values for the duration and start date. |
Baseline Start Date |
The planned beginning date of a project or activity. This field can be entered in PeopleSoft or Microsoft. |
Baseline Finish Date |
The planned completion date of a project or activity. This field can be entered in PeopleSoft or Microsoft. |
Actual Start Date |
The date on which the project or activity actually begins. It can be entered in PeopleSoft or Microsoft based on progress information that you enter. |
Actual Finish Date |
The date on which the project or activity actually finishes. |
Late Start Date |
Represents the latest date that an activity or task can start without delaying the finish of the project. This date is based on the task's start date, the late start and late finish dates of predecessor and successor tasks, and other constraints. |
Late Finish Date |
Represents the latest date that an activity or task can finish without delaying the finish of the project. This date is based on the task's late start date, the late start and late finish dates of predecessor and successor tasks, and other constraints. This field can be entered in PeopleSoft or Microsoft. |
Early Start Date |
Represents the earliest date that an activity or task can possibly begin, based on the early start dates of predecessor and successor tasks, and other constraints. This field can be entered in PeopleSoft or Microsoft. |
Early Finish Date |
Represents the earliest date that an activity or task can possibly finish, based on early finish dates of predecessor and successor tasks, other constraints, and any leveling delay. This field can be entered in PeopleSoft or Microsoft. |
Duration |
The total number of days that are needed to complete an activity from start date to end date. Duration is stored as hours and appears as days. Duration exists at both the project and activity level. Duration can be calculated if there are values for the project or activity start and end dates. |
Work |
The total number of hours spent or to be spent by a resource on an activity. Work does not equal duration. For example, the expected duration of an activity may be five days, but the work that is assigned to the activity may be 80 hours with two resources working on the activity. You define work in hours at the activity level. |
Remaining Work |
Remaining work, also known as estimate to complete (ETC), can be either automatically calculated or manually entered. When calculated, (ETC) = (work) −(actual work). |
Note. The PeopleSoft Enterprise 8.9 Integration Architecture for Microsoft Project 2002 Integrations document that is available on the PeopleSoft Customer Connection website discusses how the PeopleSoft and Microsoft systems exchange data fields and the business logic behind the exchange.
PeopleSoft - Microsoft Project Integrator
When the integration process runs, the Microsoft Project file that is associated with the PeopleSoft project is transferred, through FTP, to a share directory that is accessible by the Integrator server. The Integrator performs all reading and writing to the Microsoft Project file. When a user requests an integration, data is staged for the Integrator to start. The Integrator checks every 15 seconds for the staged data. If a user attempts an integration while the Integrator is engaged with a previous request, the new request is placed in a queue until an Integrator is available. You can set up more than one Integrator to enable multiple integrations to occur simultaneously.
An Integrator has several states:
Hold: Indicates that a previously available integrator has been taken offline.
Waiting: Indicates an idle state.
The Integrator is ready and waiting for staged data to appear to perform an integration.
Busy: Indicates that the Integrator is working on a previous integration request.
Error: Indicates that the last integration has a nonrecoverable error.
In this case, the Microsoft Project file or the PeopleSoft project is not updated. The messages that are generated by the error are stored with the project. The next time that the Integrator checks for data, the error information that appears at the bottom of the Maintain Project with Microsoft page is cleared and the Integrator continues on to the next integration request.
The state of the Integrator, warnings, and error messages appear in the Integration Session Log that you can view on the Create Project from Microsoft page.
This section covers issues that are related to creating or updating a project in Microsoft Project 2002 with data existing in Project Costing.
Project Data
When you're creating a project from PeopleSoft to Microsoft, 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, start and end dates, project manager, project type, integration template, and the project tree name, tree description, and tree parent.
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 PeopleSoft are stored in the Microsoft Project Task.Text20, Task.Text21, and Task.Text22 (and alsoText30) fields, respectively, when synchronizing activities and tasks. If the value of Text30 is altered or deleted, future updates are inaccurate.
If you use Program Management, the activity date cascade calculation method that you define in PeopleSoft 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 Establishing Program Management Business Unit Options.
Note. If the autocalculation option is selected when you export data to Microsoft, the dates and duration data that are sent to Microsoft may not remain intact. This is due to the many internal calculations that Microsoft Project makes to new or altered data.
Work Breakdown Structure (WBS)
The WBS ID is specified on the PeopleSoft activity definition and is copied to Microsoft when you export activity definitions. The WBS ID in PeopleSoft and Microsoft 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 Microsoft during the next integration process.
The PeopleSoft - Microsoft Project Integrator moves tasks by cutting and pasting. Activities that you delete in PeopleSoft are not automatically deleted in Microsoft.
Dependencies and Constraints
If you use Program Management and export activity definitions from PeopleSoft to Microsoft, 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 PeopleSoft.
During the export process PeopleSoft also sends activity constraint information such as the deadline date, constraint type, and constraint date.
See Understanding Integration of Dependencies and Constraints with Microsoft Project.
Team Members and Resource Assignments
The contents of the project team list can be copied into Microsoft Project's resource sheet. Resources that are on the project activity team can be assigned in Microsoft Project's 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 Project Costing if you use Program Management. If you use Project Costing without 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 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 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 populate 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 Microsoft.
Transaction Data
Transactions and resource data are sent to Microsoft as follows:
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 Microsoft.
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 Microsoft.
This section covers issues that are related to creating or updating a project in Project Costing with data existing in Microsoft Project 2002.
Project Data
When copying a project from Microsoft Project to Project Costing, the user enters the business unit, project ID, project description, project type, and integration template. These values are used to create the project in PeopleSoft and are also stored in Microsoft's custom properties to validate future updates.
Task and WBS Data
Microsoft Project's tasks are synchronized with PeopleSoft activity-level data. The integration process imports summary and nonsummary tasks to PeopleSoft from Microsoft. Updated activity data includes activity ID, activity type and description, start and finish dates, percent complete, duration, summary flag, and milestones. New activities are formatted on the Activities Interface staging table (INTFC_ACT_GEN) with an activity ID of NEXT, while existing activities are formatted with the Project Costing activity ID.
Regardless of the method that you use in Microsoft to calculate start and end dates for summary activities, the system assigns a calculation method of Manual in PeopleSoft for tasks that you import from Microsoft.
The WBS ID field on the task specifies the placement of activities within the WBS. The WBS ID field in Microsoft Project maps to the WBS ID in Project Costing. The system verifies that the WBS structure for a project in Microsoft Project contains no more than nine levels, which is the maximum number of levels in PeopleSoft. If a WBS contains more than nine levels, a message appears indicating that you cannot import the WBS into PeopleSoft. If WBS ID in Microsoft contains a prefix, such as PC1.1, PC1.2, and so on, the system removes the prefix prior to populating the WBS ID field in PeopleSoft.
The Load Projects and Activities Application Engine process (PC_INTF_GEN) creates any new activities imported from Microsoft Project and renumbers the WBS ID on existing activities as needed to match the Microsoft Project WBS.
If you use Program Management, you can select an option on the Microsoft Integration Options page for new projects created from Microsoft to copy the Microsoft WBS only up to the project charging level that is specified on the Create Project from Microsoft page in PeopleSoft.
Tasks that you delete in Microsoft Project are not automatically deleted in Project Costing during the integration process. For deleted tasks, the next time that you import Microsoft data to PeopleSoft, the system:
Assigns a WBS level 1 to the deleted tasks.
Moves the deleted tasks to the end of the project WBS structure.
Changes the activity processing status to Inactive.
See Understanding Project Charging Levels.
Dependencies and Constraints
If you use Program Management and import tasks from Microsoft to PeopleSoft, the integration process copies task dependencies and constraints. During the import process the system deletes the existing dependencies in PeopleSoft and creates new dependencies based on the dependency data received from Microsoft.
You must enter dependency lag time in days in Microsoft Project to integrate with PeopleSoft. The integration process does not support percentage lag durations or elapsed time.
You cannot import dependencies for summary activities from Microsoft to PeopleSoft.
See Understanding Integration of Dependencies and Constraints with Microsoft Project.
Team Members and Resource Assignments
When you create a project all resources and assignments that are on Microsoft Project's resource sheet can populate the Project Team Member table, and resources that are assigned to tasks in Microsoft Project can populate the Project Activity Team table. Entries in the Resource Name field should be either <First Name Last Name> such as Tom Jones or a resource requirement entry such as Java Developer. The Resource Name field value is validated against the employee names that are in the PeopleSoft system, and if a valid name match is located, the appropriate employee is added to the project or activity. If you use Program Management and no match is found, the resource from Microsoft is added as a generic resource in Program Management. If you use Project Costing without Program Management and no match is found, the resource is not imported.
The Resource Unique ID from the Microsoft resource (RES_UID) is stored in the Project Team Member table to facilitate future updates to Microsoft Project. The Resource Unique ID and the Task Unique ID (ACT_UID) are stored in the Project Activity Team table to facilitate future updates into Microsoft Project.
The integration process imports the project role values from the resource sheet in Microsoft Project to the project team, activity team, and schedule level in Program Management. If you use Project Costing without Program Management, the system imports the project role from the resource sheet in Microsoft Project to the project team in Project Costing. If the import process updates an existing project, the project role values from Microsoft Project override the existing values in PeopleSoft. If there is no project role for the resource in Microsoft Project, or if the project role on the resource sheet is not valid in Project Costing, the system assigns the default project role that you specify on the Microsoft Integration Options page. The system validates imported project roles against the Project Role table (PROJ_ROLE).
If you use Program Management and Resource Management, you can select integration options to:
Automatically add a named resource with a status of Requested if manager approval is required, or Committed if manager approval is not required, and generate a Resource Management assignment if you import a resource from Microsoft Project that exists as a resource in Resource Management.
If you import a named resource from Microsoft Project that is not an existing resource in Resource Management, the system adds the resource to the Resources page in Program Management as a generic resource. If you import a named resource from Microsoft Project that is an existing resource in Resource Management, the Resource Management values for resource pool, region, personnel status, and primary project role populate the Resources page for the resource.
Automatically add a generic resource with a status of Requested and generate a Resource Management allocation if you import a resource from Microsoft Project that does not exist as a resource in Resource Management.
If you import a generic resource from Microsoft Project that belongs to a resource group (known as a resource pool in PeopleSoft) that does not match a resource pool in Resource Management, the system adds the generic resource with a resource pool value of Unassigned. The system imports the Microsoft Project values for resource name and region. The integration process does not overwrite Resource Management assignments or allocations that are already requested if you subsequently import the same project from Microsoft Project.
If a pending or approved assignment request already exists for the resource, the system updates the assignment schedules only for resources with a status of Considered.
Disregard Resource Management schedule conflicts and create assignments even if it results in overbooking resources.
Select a default region from which to request generic resources.
When task dates change, all resources and resource assignments are copied to PeopleSoft, and a routine is called to adjust the dates, if needed, and to create new entries into the team tables during updates.
If you use Program Management, values from the Units field in the resource sheet in Microsoft Project copy to the assignment schedule in the Resource Details page.
Resources or assignments that you delete from Microsoft are not automatically deleted in PeopleSoft during the next import process. Assignments must be manually deleted from PeopleSoft.
Transaction Data
The system identifies budget rows in Microsoft Project if there is a value the BaselineCost field at the task level. Each task is examined. If the task is not a summary and its BaselineCost value is not zero, the system copies the row to the budgeting tables if Projects Budgeting is enabled. If Projects Budgeting is disabled, the system copies the row to the Project Transaction table. The PeopleSoft - Microsoft Project Integrator selects the analysis types based on the budget analysis group. Changes to task BaselineCost can be reflected in future updates.
If Projects Budgeting is enabled, the Microsoft Project budget periods for an activity cannot exceed 36 periods from the project start date. Budget rows for activities with start dates that are outside of this date range are not imported to budgeting tables or the Project Transaction table. Budget rows with more than 36 periods are not imported and create process errors that you can view in the Integration Session Log on the Create Project from Microsoft page. The system copies the total amount from the budget periods in Microsoft to the start date period in Project Costing.
If Projects Budgeting is not enabled, there are no period restrictions.
The integration process imports the budget items from the resource sheet in Microsoft Project to the project team, activity team, and schedule level in Program Management. If you use Project Costing without Program Management, the system imports the budget item from the resource sheet in Microsoft Project to the project team in Project Costing. If the import process updates an existing project, the budget item values from Microsoft Project override the existing values in PeopleSoft. The system validates imported budget items against the Budget Category Control table (GM_BUD_CATEGORY).
If there is no budget item for the row in Microsoft Project, or if the budget item on the resource sheet is not valid in Project Costing, the system assigns the default budget item that you specify on the Microsoft Integration Options page. The system assigns a budget item to budget rows for activities based on the default Material Budget Item if either of these conditions exist:
The task contains at least one material resource row from Microsoft Project.
The task does not contain any resource rows.
If a task contains only labor resource rows in Microsoft Project, the system assigns a budget item to budget rows for those activities based on the default Labor Budget Item that you specify on the Microsoft Integration Options page.
Initially, integration between Project Costing and Microsoft Project 2002 is a matter of establishing integration options at the business unit to eliminate setting them on a project-by-project basis. Integration options that are set at the business unit level, however, can be overridden at the project level.
This section discusses how to define integration criteria.
Page Name |
Object Name |
Navigation |
Usage |
PC_MSP2_BUDEFS |
Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options, Microsoft Project |
Establish the default settings for integrating projects for this project business unit with Microsoft Project 2002. |
|
PC_MSP2_RUNDEFS |
Project Costing, Third Party Integration, Microsoft, Create Project, Create Project from Microsoft Click the Options link on the Create Project from Microsoft page. |
Modify the default integration options that are originally defined at the business unit level on the Microsoft Project page. The Microsoft Integration Options page is similar to the Microsoft Project page; therefore, both pages are discussed in this section. |
Access the Microsoft Project page to define integration criteria default values at the business unit level, or access the Microsoft Integration Options page to define integration criteria for a specific project.
Note. Many of the fields on both the Microsoft Project page and the Microsoft Integration Options pages are similar; therefore, the discussion in this section applies to both pages. The Business Unit and Project fields at the top of the page designate the level (business unit or project) at which you are defining the integration criteria.
The settings that you enter on the Microsoft Project page for the business unit appear by default on the Microsoft Project Integration page for all projects that belong to the business unit.
Export |
Select the check box that corresponds to each data element that you want to send to Microsoft Project when the integration process runs to export data from Project Costing to Microsoft. |
Import |
Select the check box corresponds to each data element that you want to receive in Project Costing when the integration process runs to import data from Microsoft to Project Costing. |
Project/Activity Detail
Project Definitions |
Select to copy information such as project name, project ID, description, type, business unit, manager ID, project tree name, tree effective date, and parent node if applicable. |
Dates and Duration |
Select to copy the project start and end dates. This option also copies project duration if you use Program Management. |
Percent Complete (project) |
Select to import the percent complete value from Microsoft Project to PeopleSoft if the calculation method is manual. |
Activity Definitions |
Select to copy information such as activity ID or task name, activity type, description, summary flag, and work breakdown structure ID (WBS ID). If you use Program Management, the integration process copies activity dependencies and constraints when you export data from PeopleSoft to Microsoft. |
Dates and Duration |
Select to copy the activity start and end dates. This option also copies activity duration if you use Program Management. |
Percent Complete (activity) |
Select to copy the percent complete value that appears on the Activity Definitions - General Information page for each activity or task. If the transmission is from Project Costing to Microsoft, the value sent is the percent complete based on the calculation method that is defined for the project business unit. When the percent complete arrives in Microsoft, it triggers a recalculation of actual work in Microsoft, which automatically updates actual work based on percent complete as part of its standard functionality. When Project Costing receives the percent complete from Microsoft Project, only the percent complete value that is in PeopleSoft changes. Actual work does not change. |
Milestones |
Select to synchronize milestones. In PeopleSoft, you designate an activity as a milestone on the Activity Definitions - Definition page. |
Include only costing level WBS |
Select Import to copy the Microsoft WBS only down to the project charging level that is specified on the Create Project from Microsoft page in PeopleSoft. Clear the Import check box to import the entire WBS to PeopleSoft. This option is available for new projects that you create from Microsoft. Important! If you select the Include only costing level WBS option and import the WBS only down to the specified activity costing level, we recommend that you do not export the WBS back into Microsoft Project from PeopleSoft because the WBS structures now differ. This field appears if you select an activity costing level as the project charging option on the Create Project from Microsoft page. The Include only costing level WBS option is available on the Microsoft Integration Options page for the project if you use Program Management. The option is not available on the Microsoft Project page for the business unit. |
Project Team |
This field appears only if you use Project Costing without Program Management. If Program Management is installed, this field is replaced with the Project Resource List / Resource Sheet fields. Export: Select to copy members of the project team to the Microsoft Project resource sheet. Import: Select to copy labor resources from the Microsoft Project resource sheet to the Project Team Member Team table. |
Job Codes |
Select Export to copy all of the resources that belong to the job codes that are specified on the Project Definitions - Team page in Project Costing to Microsoft. This field appears only if you use Project Costing without Program Management. |
Project Resource List / Resource Sheet |
Select to copy project-level data such as description, project type, start and end dates, and so on. This field appears only if you use Program Management. Export: Select to copy data from the project resource list on the Resources page in Program Management to the Microsoft Project resource sheet. Import: Select to copy resource data from the Microsoft Project resource sheet to the project resource list on the Resources page in Program Management. |
Include Labor |
Select to copy labor resources for the project. This field appears only if you use Program Management. |
Include Material |
Select to copy material and asset resources, such as consumable supplies and machinery, for the project. Material and asset resources do not have time or work components associated with them. This field appears only if you use Program Management. |
Assign Named Resource |
Select to add the resource with a status of Requested, which triggers the process to create a Resource Management assignment. Clear the check box to add the resource with a status of Considered. This field appears only if you use Program Management and Resource Management. |
Allocate Generic Resource |
Select to add the resource with a status of Requested, which triggers the process to create a Resource Management allocation. Clear the check box to add the resource with a status of Considered. This field appears only if you use Program Management and Resource Management. |
Allow Overbooking |
Select to assign a resource status of Requested when you import named resources from Microsoft Project, and create Resource Management assignments regardless of schedule conflicts. Clear the check box to assign a resource status of Considered on the Program Management Resources page if there are resource schedule conflicts. This option applies only if you select the Auto Assign Named Resource option. This field appears only if you use Program Management and Resource Management. |
Default Region |
Select a default region from which to request generic resources. The default region populates the Region Code field on the Program Management Resources page for new resources. This value does not update the region for existing resources. This option applies only to generic resources that you import from Microsoft Project. This field appears only if you use Program Management and Resource Management. |
Activity Resource List / Task Assignments |
Select to copy activity-level data such as task name or activity ID, activity type, description, start and end dates, and resources. This field appears only if you use Program Management. Export: Select to copy resource data from the Program Management Resources by Activity page to the Microsoft task assignments. Import: Select to copy resource data from the Microsoft Project tasks to the PeopleSoft Resources by Activity page. |
Include Labor |
Select to copy labor resources and their related work information for activities. This field is available for selection only if you select the Include Labor option for the Project Resource List / Resource Sheet. |
Include Material |
Select to copy the material and asset resources for activities. This field is available for selection only if you select the Include Material option for the Project Resource List / Resource Sheet. |
Transactional Detail
Options
Project Role |
Enter the value to use as the default project role that appears in Project Costing for labor rows that you import from Microsoft Project if a project role value does not exist for the rows in Microsoft Project. The system also assigns the default value to imported rows that contain project roles that do not exist in the Project Role table. During the import process, project roles in Microsoft Project override the default project role on this page. |
Named Resources
This group box appears only if you use Program Management.
Cost Rate Type |
Select an option to appear as the cost rate type for named labor resources on the Resources page or Resources by Activity page in Program Management when you import new resources from Microsoft Project. This field is required if you select the Include Labor option for the Project Resource List / Resource Sheet or Activity Resource List / Task Assignments. Available options are: Employee Rate: The system uses the cost rates that are defined on the Rates by Employee page for new resources that you import from Microsoft Project. Subsequent modifications that you make to resource cost rates in Microsoft Project are not imported into PeopleSoft. Jobcode Rate: The system uses the cost rates that are defined on the Rates by Job Code page for new resources that you import from Microsoft Project. Subsequent modifications that you make to resource cost rates in Microsoft Project are not imported into PeopleSoft. Project Role Rate: The system uses the cost rates that are defined on the Rates by Role page for new resources that you import from Microsoft Project. Subsequent modifications that you make to resource cost rates in Microsoft Project are not imported into PeopleSoft. User Defined Rate (custom): If you import a new resource from Microsoft Project, the system populates the Resources page and Resources by Activity page with the Resources.StandardRate field value from the Microsoft Project resource sheet. If the resource exists on the Resources page and has a custom rate type, the system updates the rate with the Resources.StandardRate field value from the resource sheet. When you export resources from PeopleSoft to Microsoft Project, the system sends the activity resource cost rates that appear on the Resources by Activity page. If there is no cost rate defined for a named labor resource on the Resources by Activity page, the system uses the resource's cost rate from the Resources page for the project. Rates that you modify in Microsoft Project do not update PeopleSoft data if the existing resource on the Resources page does not have a custom rate type. You can control the available options by restricting rate types on the Program Management Options page for the business unit. See Establishing Program Management Business Unit Options. Note. New material resources are brought into the Program Management Resources page and Resources by Activity page from Microsoft with a rate type of User Defined Rate (custom). |
Bill Rate Type |
Select an option to appear as the bill rate type for named labor resources on the Resources page or Resources by Activity page in Program Management when you import new resources from Microsoft Project. This field is required if you select the Include Labor option for the Project Resource List / Resource Sheet or Activity Resource List / Task Assignments. These options behave in a similar manner as the Cost Rate Type options for named resources, except that the system uses the bill rate types—not the cost rate types—that are defined for the selected option. Bill rate types are stored in the Resources.Cost1 field in Microsoft. |
Generic Resources
This group box appears only if you use Program Management. These options behave in a similar manner as the Cost Rate Type and Bill Rate Type options for named resources.
The section discusses how to create and update Microsoft projects from PeopleSoft data.
Page Name |
Object Name |
Navigation |
Usage |
PC_MSP2_UPDATEPROJ |
|
Create or update a project in Microsoft Project 2002 from data existing in a Project Costing or Program Management project. |
|
PC_MSP2_VIEWINTG |
|
View the status of integration requests. |
Access the Integrate with Microsoft Project page.
Refresh |
Click to update information on the progress of the current integration. |
Administer Integrators |
Click to access the Administer Integrators page to view the integrators that are updating the integration requests and the status of integrations. This button appears only if you have security access to the Administer Integrators page. |
Options |
Click to access the Microsoft Integration Options page to enter integration criteria for this project. |
Attached File |
Click a file name link to download a Microsoft Project 2002 *.mpp file that is associated with the PeopleSoft project. To modify the attachment version that is stored in the PeopleSoft system:
Note. To indicate to other users that you are working on the current version of an mpp file, click the Check Out MSProject File button. |
Check In MSProject File and Check Out MSProject File |
Click the appropriate button to check in or check out the Microsoft Project *.mpp file that is associated with the project. If a file is checked out, you can edit it and check it back in when you are done, or cancel the checkout. If you edit and check in the file, the changes you have made are saved to the version of the file that is posted. The data changes, however, are not uploaded to the PeopleSoft application tables until you perform the integration process on the file. Any user with access to this page can check out a file. When a file is checked out, only the user who checked out that version of the file can edit it. The Check Out process is primarily intended to facilitate coordination of efforts and ensure that two people do not accidentally overwrite each other's work. |
Export to MSProject File |
Click to create a new Microsoft Project *.mpp file that contains the changes that are made in PeopleSoft. The affected project attributes are those for which the Export option is selected on the Microsoft Project page for the business unit. Click Options to access the Microsoft Integration Options page and override the business unit options. |
Import from MSProject File |
Click to update PeopleSoft project file with data from Microsoft. Click to update the project in PeopleSoft with changes that are made in a Microsoft Project *.mpp file. The affected project attributes are those for which the Import option is selected on the Microsoft Project page for the business unit. Click Options to access the Microsoft Integration Options page and override the business unit options. |
Project General |
Click to access the Project Definitions - General Information page for the project. |
Integration Session Log
Progress and Results |
Displays the progress and results of the current or last data integration between PeopleSoft and Microsoft. |
Warnings and Errors |
Displays errors, if any, that occur during the integration process. Note. If the integration completes and adds a new file to the grid, but warnings and error messages appear, you should review the messages and review the project for accuracy. In these circumstances, the majority of the integration is most likely successful, but a value in a particular field may be truncated or not integrated due to unusual data or characters in the Microsoft Project file. |
This section discusses how to create and update PeopleSoft projects from Microsoft Project data.
Page Name |
Object Name |
Navigation |
Usage |
PC_MSP2_CREATEPROJ |
|
Create a new project in PeopleSoft from an existing Microsoft Project 2002 project (*.mpp file). |
|
PC_MSP2_UPDATEPROJ |
|
Update an existing PeopleSoft project with data from Microsoft. |
Access the Create Project from Microsoft page.
A message appears at the top of the page if errors or warnings occurred in the previous integration process.
Business Unit and Project Name
Enter the PeopleSoft project business unit, project, and project description for the project that you are creating in PeopleSoft. The business unit appears by default from the User Preferences - Project Costing page for the person who is logged into the system. The integration options appear by default from the Project Costing Options - Microsoft Project page for the business unit.
Last Project Created |
Displays the project ID of the last imported project. |
Integration Template |
Select the integration template to use for integrating data for this project with General Ledger, Asset Management, and Purchasing, if applicable. |
Project Type |
Enter the project type for the system to assign to this project. |
Processing Status |
Displays the processing status that the system uses to control incoming transactions. The system assigns the Processing Status field value based on the Project Status field value that you select. Processing status types are mapped to the delivered and user-defined project status types during implementation. These processing statuses may appear:
|
Project Status |
Select the project status to assign to this project in PeopleSoft. |
Project Charging Level
This group box defines the charging level for new projects that are created from Microsoft. The default values are based on the project charging level settings for the business unit. The group box appears if you use Program Management.
All Detail Activities |
Select to import the entire WBS that includes all tasks. |
Activity Costing Level |
Select to import a partial WBS that includes only tasks up to the activity costing level. If you select this option, you must select an activity costing level of 1, 2, or 3 from the drop-down list box. To use this option you must also select the Import option for the Activity Definitions field and the Include only costing level WBS field on the Microsoft Integration Options page. |
Charging Level for Time Report |
Select the charging level for time reports that appears as the selected option for new projects that are created from Microsoft. If you select All Detail Activities as the project charging level, the system automatically selects All Detail Activities as the time report charging level. This option is available if you use Expenses and Program Management. |
See Understanding Project Charging Levels.
Project Tree Integration
Tree Name |
Select the project tree to which the project belongs. |
Effective Date of Tree |
Enter the date that the project is considered added to the tree. |
Parent Tree Node |
Select the parent tree node to which to assign the new project as its child. |
Additional Fields
MSP File Name |
Displays the name of an existing Microsoft Project *.mpp file to be used to create the project in PeopleSoft. |
Add Attachment |
Click to add an existing Microsoft Project *.mpp file to be used to create the project in PeopleSoft. |
Options |
Click to access the Microsoft Integration Options page to modify the integration default settings. |
Import from MSProject File |
Click to create the project in Project Costing with the Microsoft Project *.mpp file. The affected project attributes are those for which the Import check box is selected on the Microsoft Project page for the business unit. Click Options to access the Microsoft Integration Options page and override the business unit options. |
Integration Session Log |
Click to view warnings, errors, progress, and results of the integration session. |
Project General |
Click to access the Project Definitions - General Information page for the project just created. |