Oracle Project

Management
Integration with
Microsoft Project
Volume 2:
Implementation
Recommendations for
Project Process
Lifecycle
An Oracle White Paper
April, 2010
TABLE OF CONTENTS

Page ii
Table of Contents...............................................................................................................ii
Introduction.......................................................................................................................3
Terms, Definitions & Abbreviations...................................................................................3
Terms & Definitions.....................................................................................................3
Abbreviations...............................................................................................................3
Audience & Approach........................................................................................................4
Audience............................................................................................................................4
Approach............................................................................................................................4
Best Practices, Volume 1 Whitepaper.........................................................................4
Project Structures, Plans & Tasks Overview.....................................................................5
Project Structure in the Project Process...........................................................................5
Project Structure Types..............................................................................................5
Structure Types & Impact on Data Integration..........................................................5
Project Process Flows........................................................................................................6
MSP Integration Overview................................................................................................6
Best Uses for MSP Integration....................................................................................6
Use MSP Integration for the Entire Project...............................................................6
Manage Budgets & Forecasts in OP...........................................................................6
Typical Process Flow.........................................................................................................7
Project Lifecycle Overview..........................................................................................7
Typical Integration Flow.............................................................................................7
Create a New Project.........................................................................................................8
Start a new project......................................................................................................8
Consider whether to create a workplan or financial plan..........................................8
Starting your project in OP.........................................................................................8
Use templates to create projects in OP......................................................................8
When to start your project in MSP.............................................................................8
Starting your project in MSP......................................................................................8
Schedule a Project...........................................................................................................10
Schedule a Project in MSP........................................................................................10
Schedule tasks in MSP..............................................................................................12
Send a scheduled project to OP................................................................................12
Differences in MSP & OP plan schedules.................................................................12
Publish a Project Plan......................................................................................................13
Publishing the workplan in OP..................................................................................13
Select working or published version.........................................................................13
Options for financial plans........................................................................................13
Attaching the MSP File to a workplan version.........................................................14
Collect Progress...............................................................................................................14
Receive OP files in MSP before updating progress..................................................14
Viewing OP data in MSP...........................................................................................14
Collect Progress........................................................................................................14
Update a Plan..................................................................................................................16
Project Structure impacts on updates......................................................................16
Managing financial plans..........................................................................................16
Updating plan information........................................................................................16
Using time-phased data.............................................................................................17
Example.....................................................................................................................18
Appendices.......................................................................................................................19
Appendix 1: FAQs.............................................................................................................19
Appendix 2: MSP Integration Setup Options..................................................................21
Appendix 3: Viewing financial fields in MSP...................................................................24

Page iii
Page iv
INTRODUCTION
TERMS, DEFINITIONS & ABBREVIATIONS
Terms & Definitions
Term Definition
Link Projects A project is considered linked when you send project
information from MSP to OP or when receiving a project
from OP to MSP and enabling the Retain Link to Oracle
Projects option in the Receive Project page.
Receive A project file is received from OP to MSP
Project
Send Project A project file is sent from MSP to OP
Resource List Resource lists are groupings of resources to assign to tasks
for a project. You attach resource lists to projects to
effectively budget project cost and revenue, to track
resource usage, and to view cross-project reporting.
WBS Work Breakdown Structure, also called workplan
FBS Financial Breakdown Structure, also called financial
structure
Plan Type Refers to a characteristic of the financial: either a budget or
a forecast
NSTBM / Split Non-Shared Task Based Mapping Structure shared between
and Mapped WBS and FBS. The task and structure of both are completely
different. However the workplan tasks are mapped to
financial task. Many workplan tasks can be mapped to one
financial task but not vice-versa.
NSNM / Split Non-Shared No Mapping. The task and structure of WBS
and and FBS are completely different. And the workplan tasks
Unmapped are not mapped to financial tasks
FSS Fully Shared Structure. The task and structure of WBS and
FBS are identical. There cannot be a different financial
structure, as the workplan structure is shared by the
financial structure.
PSS Partially Shared Structure. Part or portion of the tasks and
structure of the WBS are identified as FBS task. There
cannot be different financial structure, as the portion of
workplan structure is shared by financial structure.
Split One of the non-shared workplan structures (e.g., Non-
Structure Shared Not Mapped or Non-Shared Task Based Mapping)
Project A template you define and use to create new projects.
Template Information on the template defaults to a new project when
you create a new project from a template.
Scheduling Scheduling is the identification of task dates, priorities,
dependencies and/or milestones and assigning and
managing resource assignments
Summary Calculated amounts for a parent task based on the amount
Values values of the related child tasks.
Actual Cost Costs associated with the workplan from actual expenditure

Page 5
 Term Definition
transactions, such as time cards, processed for the project.
Estimate to The remaining effort to complete the work for a task
Completion resource assignment
Physical The amount of effort already completed for a task resource
Percent assignment.
Complete

Abbreviations
Abbreviation Meaning
OP Oracle Project Management
MSP Microsoft Office Project
NSTBM Non-Shared Task Based Mapping
Structure
NSNM Non-Shared No Mapping Structure.
FSS Fully Shared Structure.
PSS Partially Shared Structure
WBS Work Breakdown Structure
FBS Financial Breakdown Structure
ITD Inception To Date
PTD Period To Date
UOM Unit Of Measurement
ETC Estimate to Completion
PPC Physical Percent Complete

AUDIENCE & APPROACH

AUDIENCE
This document is intended to provide helpful tips for implementation teams to
configure Oracle’s MSP Integration features successfully to integrate Microsoft
Office Projects (MSP) with Oracle Projects (OP).

APPROACH
This document is intended for implementation teams to help them integrate
Oracle Projects with Microsoft Office Projects using Oracle’s MSP Integration
features. The implementation team should read the following documents during
the planning and implementation phases of its implementation of Oracle Projects.
 Oracle Project User Guide
 Oracle Project Implementation Guide
 Integration with Microsoft Projects, Volume 1: Best Practices Whitepaper
 Integration with Microsoft Projects, Volume 2: Implementation
Recommendations for Project Process Lifecycle
 Integration with Microsoft Projects, Volume 3: Implementation Tips for
Project Structures
At a minimum, implementation teams should read the introductory Overview
sections of each whitepaper. During the implementation phase, read the listed

Page 6
 documents below as a reference companion to understand user procedures
described in the Oracle Project Implementation Guide. First, read the
Implementation Guide Overview to understand what you need to set up and why.

Best Practices, Volume 1 Whitepaper

This document focuses on the impact of the different project structures on the
business processes in a project lifecycle, from creating a project through updates
and publishing. Therefore, read Oracle Project Management Integration with
Microsoft Project, Volume 1 Best Practices whitepaper to understand the
recommendations for selecting the optimum Project Structure for your types of
projects.

Project Structure, Volume 3 Whitepaper

Read Oracle Project Management Integration with Microsoft Project, Volume 3:
Implementation Tips for Project Structure whitepaper to understand the process
considerations for the Project Structures you are interested in implementing. This
includes specific MSP Integration issues that you may need to address or plan for
during implementation. This volume provides implementation tips to set up and
use the specific Project Structure you selected without having to read tips for
other project structures.

PROJECT STRUCTURES, PLANS & TASKS OVERVIEW

PROJECT STRUCTURE IN THE PROJECT PROCESS
Project Structure Types
Before you setup a project, determine the relationship you want to maintain
between your workplan and financial plans. While the overall project management
process remains the same regardless of which project structure you use, the
structure you select will impact how some MSP Integration features function.
To understand MSP Integration fully, review the available documents that
describe how Project Structures work. Read Oracle Project Management
Integration with Microsoft Project, Volume 1 Best Practices Whitepaper to select
the optimum project Structure, and read Oracle Project Management Integration
with Microsoft Project, Volume 3: Implementation Tips for Project Structure
Whitepaper to learn implementation tips for your selected Project Structure. In
summary, Project Structures are defined in the following table.
Shared Structures
Name Alternate TermsDescription
Fully Shared FSS Tasks in WBS are the same as the FBS
Partially Task structure of the FBS is identified from
PSS
Shared the WBS

Non-Shared & Split Structures

Name Alternate TermsDescription
Non-Shared NSTBM or Task structures in WBS and FBS are
Task Based Split & Mapped completely different, but tasks are mapped
Mapping between the two structures

Page 7
 Structure

Task structures in WBS and FBS are

Non-Shared NSNM or
completely different, and no tasks are
No Mapping Split & Unmapped
mapped between the two structures

Structure Types & Impact on Data Integration

The structure you select determines how some MSP Integration features function.
Understand the implications of your choice of structure on how you want to share
data between MSP & OP. This table summarizes general considerations for each
Project Structure.
Structure Considerations
Fully When you use FSS, the project workplan structure and the financial
Shared plan structure are identical. Use FSS to manage the financial
(FSS) impacts of project costs and revenues by task or task assignment.
Partially Like FSS, the high-level project work structure and financial
Shared structure are identical; yet you can use PSS to manage the project
(PSS) at a task level, while managing the financial plan at a higher level.
Non Like PSS, you can track a project at the task level, while managing
Shared the financial plan at a higher level. Although you can map any tasks
Task Based between the structures, you typically use NSTBM to manage
Mapped separate plans and rollup workplan values to the financial plan by
(NSTBM) mapping lower level tasks in the workplan to higher-level tasks in
the financial plan.
Non When you use NSNM, you can manage your workplan and financial
Shared plans, and their resource assignments, independently. The project’s
Non financial and work structures are not related regardless of the level
Mapped of tracking.
(NSNM)

To decide how to configure MSP Integration features for your unique project
management needs, you need to understand how MSP Integration features
transfer information between MSP and OP for the project workplans and financial
plans and evaluate the required project structures to manage your business
process through the project lifecycle.
Plan structures are organized as a hierarchy of tasks. MSP plans are work
breakdown structures (WBS) that may carry some financial information; an OP
plan can be a WBS or a financial breakdown structures (FBS). When you transfer
a file between MSP and OP, you are sharing information for a specific version of a
plan. Once you associate a plan file from MSP with a plan in OP, you cannot
change the association. Not all information for a task in MSP is shared with OP
when you send a file. And, depending on the whether the plan is a workplan or
financial plan in OP and the project structure, not all task information in OP is
received in MSP.

Page 8
PROJECT PROCESS FLOWS
MSP INTEGRATION OVERVIEW
To help you use the MSP and OP applications together to manage your projects
through the project lifecycle, we will review how MSP Integration features are
used in the typical process flow before addressing alternative structures and
flows you might configure.

Best Uses for MSP Integration

The primary benefits in using MSP to help manage your projects are in the
flexible and simple user interfaces and file management capabilities. MSP can
reduce your costs and time to implement since it is generally easier to setup and
train users. MSP files can be easily shared amongst users and data in multiple
files can be easily manipulated and consolidated.
In general, the best approach is to use MSP for scheduling and use OP for all
other aspects of enterprise project management. This approach leverages the
best functionality from each application. OP has limited features for scheduling
complex projects, but has very strong capabilities to manage project financial
information. By using this approach, the two applications share project
information while maintaining the security setup for projects, functions and roles
in OP.
Although OP has a secure and integrated workplan feature for collecting progress
from team members, MSP can also be very useful in collecting task progress.
Depending upon your project types and structures, collecting progress in MSP
files and consolidating them before sending a file to OP can be a simple process.

Use MSP Integration for the Entire Project

If you use MSP Integration, you should use the MSP for the entire project. When
you manage a project using both MSP and OP without applying MSP Integration
features, you may incur significant cost to reconcile and report results generated
for different plan versions.

Manage Budgets & Forecasts in OP

As you share financial information between MSP and OP, you should always use
OP to manage budgets and forecasts. OP has robust features for managing
enterprise operations that affect your project. Although you can assign resources
to financial plans in MSP, you cannot send those assignments to a financial plan in
OP. However, you may consider using MSP to help setup your financial structures
when you maintain detailed financial plans (as long as you are not using a FSS)
and to view planned costs for task resource assignments in MSP. The simple user
interfaces in MSP may it suitable for handling plans with large amounts of details.

TYPICAL PROCESS FLOW

Project Lifecycle Overview
This volume provides general information to set up and use MSP Integration and
how to make it work managing projects through the project lifecycle. Understand
the various ways project information is shared between OP and MSP through the
life of your projects and to identify the impacts of MSP Integration on each
process step:
1. Create the Project

Page 9
 2. Schedule the Project
3. Publish the Project Workplan
4. Collect Progress
5. Update the Project Workplan

Typical Integration Flow

A typical flow to share project information between OP and MSP can serve as a
foundation to learn tips and avoid common problems. Then you can build on this
understanding to configure unique variations to meet your project requirements.
Typical Process Flow of Information between MSP & OP

Oracle Projects MS Office

Projects

CREATE A NEW PROJECT

Start a new project
Start by creating a project in either MSP or OP. These two applications are
designed to process project information differently and will impact how that
information is transferred. Consider whether you want to create your workplan in
MSP and schedule it before you sending the project to OP, or whether you want to
create your project in OP first, then receive it in MSP for scheduling.

Consider whether to create a workplan or financial plan

When you create a project, consider the types of plans you intend to manage and
the tools you want to use to manage your plans. In OP a project can have both a
workplan and a financial plan. When you want to manage both types of plans,

Page 10
select a project structure that defines the desired relationship between the two
plans. Remember, each plan you create in OP must be associated with a different
MSP file when you want to share plan information.

Starting your project in OP

A typical practice is to start your project in OP using pre-defined project template
then add resource lists and workplan tasks. Then transfer the project to MSP to
specify task dates, priorities, dependencies and/or milestones and assign and
manage resource assignments.
You should never use a process that makes update to a plan from both MSP and
OP. This will probably result in the loss of information. For example, once you
decide to use MSP or OP for making progress updates, you should only use that
application to make updates for the life of the project.
If you are using a FSS relationship between financial and workplan information,
the structure in both plans is identical. Since OP will typically be used to manage
financial plans, it is recommended that you create any FSS type project in OP and
use MSP for assigning resources and scheduling.

Use templates to create projects in OP

You use project templates to create new projects in OP. It is best to define project
categories used by your business and develop a project template in OP for each
category. Then use the template to create new projects using the appropriate
category.
If your projects are typically of the same type and use the same settings, you can
start a new project in OP by copying an existing project. Then you can update the
required setups and plan values. When you create a new project from a copy of a
project or template the project structure defaults to the project.
When you create your project in OP, you can create both project workplans and
financial plans. Create different types of financial plans based on the copied
project structure. Then download the unscheduled OP resource and workplan
data into MSP.

When to start your project in MSP

Creating and scheduling your project in MSP before sending it to OP for ongoing
project management more effectively handles some business scenarios. You might
consider starting your project in MSP:
 To utilize project creation or scheduling features in MSP that are not
available in OP.
 When you schedule the project as you create it.
 When you manage your workplans exclusively in MSP and use OP only to
manage your financial plan. You send progress information from MSP to OP
to produce financial forecasts.

Starting your project in MSP

One reason project managers typically create projects in OP is that MSP does not
have a template management feature. Templates in OP carry many of the project-
level attributes needed to manage your project that are not available in MSP. You
cannot copy a template to create a project in MSP. You can only start a project by
copying another project in MSP or entering a new project.

Page 11
Since many of the template attributes are required for an OP project, you must
associate an OP project template with your MSP file when you create a project in
MSP and send it to OP. The structure type specified on the project template
defaults to the project when you send it to OP. When you send your file to OP, you
also determine whether to create a workplan or financial plan.
In some cases, you need to complete the process of creating a financial plan in OP
by selecting mapped tasks depending upon the structure. (For more detailed
descriptions of project structures, see Oracle Project Management Integration
with Microsoft Project, Volume 1: Best Practices and Volume 3: Implementation
Tips for Project Structure white papers.)
Complete MSP and Integration Setups
When you create your project in MSP insure that the MSP and integration setup
steps are completed before you start. Then open the new project in MSP and
make your updates before sending your file to OP. See Appendix 2: MSP
Integration Setup Options for a discussion on recommended setup options.
Select a valid OP template
After you enter your project in MSP, you must select and associate an OP project
template before you send the file to OP. To select a project template and send
your new projects to OP follow these steps:
 From the MSP tool bar, select Oracle Projects, then Send to Oracle
Projects > Send as Project Data
 In the Send Project: Select Project Template field select the template
with which you wish to send the project and create the project in OP.
You can select from any available template in OP. Only the template-
level setups are used to create the new project. Tasks and plans are
not copied from the template, but only from your MSP project file.
Send the MSP project file to OP
After selecting the project template, complete the following steps to send your
file to OP and create a new OP project:
 Enter the project name /number field with which you wish to identify
the project in OP
 In the Send Project: Enter Options window, select the plan, workplan
(WBS) or financial plan (FBS) that you want to create in OP. The
structure of the selected template determines the type of data to send
to OP. Not all options are available for all structures. For example,
when you select a project template with an FSS both plan structures
are fully shared in OP and MSP. This means that both the workplan and
the financial plans are created when you send the file to OP since. The
process is different when you use partial or not shared structures. For
more detailed descriptions of project structures, see Oracle Project
Management Integration with Microsoft Project, Volume 1: Best
Practices and Volume 3: Implementation Tips for Project Structure
white papers.
 Determine whether to send the project as a working version or a
published version. If you do not expect to make any further updates in
OP, you should send the project as a published version so it is ready
and available for collecting progress and actuals.

Page 12
 When you send a plan file to OP and specify the type of plan it is, only the
related plan information is updated in OP. When you create or receive a
financial plan in MSP and update the financial information on tasks, changes
are made only to the financial plan. Once the MSP file is linked to an OP plan,
you cannot change the type of OP plan that it is linked to (e.g., you cannot link a
file to a plan as a workplan and then change it to a financial plan later).
When you send the MSP file to OP the first time, the MSP project file and the
OP project plan are linked to transfer data between the two projects during the
project lifecycle. Once this link is established, you cannot update it. You can
have more than one linked MSP project file for each OP project.
Complete the project setup
If you are using any project structure with mapped tasks between the workplan
and financial plan, you must complete your plan mappings after sending the
plan file to OP.
For projects with separate workplans and financial plans, you must send the
plans in separate MSP transfers with separately linked files.

SCHEDULE A PROJECT
Schedule a Project in MSP
Project scheduling generally involves the identification of task dates, priorities,
dependencies and/or milestones and assigning and managing resource
assignments. You can assign task start dates, end dates and resources in OP. In
MSP you can use out-of-the-box MSP Integration functionality to apply additional
scheduling capabilities including managing task dependencies, priorities and
milestones. MSP Integration also supports the ability to manage updates to
workplan task information as well as the collection of task progress updates.
When you schedule a project in MSP, you must use a valid resource list from OP to
select resources to assign to tasks if you want to view and use resource
assignments in OP. Only resources from a valid resource list associated to your
MSP plan file can be sent to OP.
Select MSP receiving options
Before you receive a plan from OP, select the Oracle Projects menu in the MSP
toolbar to open the Receive Options page. You can determine whether to receive
the workplan or the financial plan. You receive Project Data when you want to
update the WBS, create new resource assignments or update existing resource
assignments in the OP workplan. You can also receive the OP financial plan and
modify the FBS, create new budget amounts or modify budget amounts
assignments. While you can make resource assignments in MSP for a financial
plan, you cannot send them to OP. You can only send budget amounts to OP for a
financial plan.
If you want to modify resource assignments, you must specify which resources
you want to receive when you receive a project or receive resources separately.
Select the version to receive
When you receive the plan, you have options to determine the version:

Page 13
  Receive an Existing Version – select this option when you want to start
with a working version of an OP plan and update the structure,
assignments or workplan schedule. You have the option to send this file to
OP as a working version or published version once you complete your
updates.
 Receive the Latest Published Version – select this option when you
want to make updates to the last version published in OP. You can send this
to OP as a working version or published version after you complete your
updates.
 Receive only the Resource List – select this option if you plan to create a
project in MSP and schedule it before sending it back to OP with a
template as a new project. You receive the resource list so you can assign
resources to tasks in MSP using pre-define resources in OP.
Reschedule an existing project
When you reschedule an existing project, you may want to view information
about the plan when you perform scheduling activities. Use the Receive Options
page to indicate other information you want to receive from OP. The type of
information you can receive is based on the type of plan you selected. For
example, if you selected workplan, then progress information can be selected.
Use a valid OP resource list
When you use MSP to assign resources to the workplan schedule you must use
a valid resource list from OP if you intend to send any project information back
to OP during the life of the project. If you are receiving a project you created in
OP, you can also receive the OP resource list by selecting it as part of the
receiving process. If you are creating and scheduling your project in MSP
before the first time you send it to OP, you must receive the resource list from
OP and use it to assign valid resources.
In summary, you have two options to obtain a resource list. The option you
choose depends on how you create the project.
Option Resource List Options User Procedures
Create When you create the project in When you receive the file in
Project in OP and transfer the project to MSP, check the box,
OP and MSP for scheduling, receive the “Resources” in the “Receive
Schedule project and resource list Project: Enter Options”
in MSP together. Use the OP resource list window. When not checked,
to perform resource assignments resources will not be received
in your schedule. in MSP and you will not be
able to assign resources.
Be sure to select the right
resource list for the plan you are Select resources in the
creating to avoid errors when “Receive Resources” window
sending your project to OP. to assign to tasks in MSP.
You cannot send resource
assignments for a financial plan
to OP, only for a workplan.
Create Receive only a valid resource list Select “Oracle Projects” from
and from OP to use in scheduling. the MSP tool bar, then select
Schedule “Receive From Oracle

Page 14
 Project in If you create and schedule the
MSP project in MSP without using a
valid resource list, resource
assignments are not sent to OP.
Be sure to select the right
resource list for the plan you are
creating to avoid errors when
sending your project to OP.
You cannot send resource
assignments for a financial plan
to OP, only for a workplan.
Projects” > “Resource List”. In
the “Select Project
Information” window select a
project template and select
whether you want to receive
the resource list attached to
the ‘workplan’ or the ‘financial
plan’ in the "Receive
Resources: Select Project
Information" field. Or you can
select the option in this field
not to receive a resource list in
future transfers.
When you want to select a
resource list associated to a
‘financial plan’ select the plan
or select any other value from
the ‘Resource List’ LOV.
When you select to receive a
resource list associated to a
‘workplan’ you can select any
Resource List from ‘Resource
List’ LOV.
When you do not select a
resource list, the value of
‘None’ is used by default.
NOTE: When you send the
project to OP you must also
select a template, but you can
select a different project
template than the template
you select when you receive a
resource list.

Schedule tasks in MSP

In MSP, you can either create tasks or use tasks received in the project file from
OP to assign resources. You schedule tasks in MSP by creating task dependencies,
dates and resource assignments.

Send a scheduled project to OP

Once scheduling is completed, you send your plan file to OP. Depending on
whether you send the plan file as a workplan or financial plan and the type of data
you send (Project Data or Budget Data), the project workplan or financial plan is
created in OP. If you created your project in MSP, the new project is created first
in OP using the project template you specified in the Send Project Data options.
When you send your plan file to OP, you must decide whether to send it as a new
version and whether to send summary information.

Page 15
 Not all sending options for plans and data types are available for all project
structure types. Review the Whitepaper Volume 3: Implementation Tips for
Project Structure for more information.
Enable plan versioning
If you want to send your MSP plan file as a new version in OP, you must enable
versioning on the project template that was used to create the project in order
to create new plan versions. Otherwise, the plan file you send will update the
latest version of the plan in OP.
Specify the project task level
To send only summary task information to OP from your MSP plan file, you
specify the MSP project task level (e.g., level 1, 2, 3…n) the first time you send
the plan. Each time you transfer the file with a plan version between MSP and
OP the level selected for the original file transferred to OP specifies the level
project tasks can be created or updated in OP. To avoid data corruption, the
level selected for the original file is maintained and cannot be updated. If you
want to work at a different level in future transfers, you must send the file from
MSP to OP as a new version. This new version can be maintained at a different
task level.

Differences in MSP & OP plan schedules

When you send your plan to OP, the treatment of dates and task weightings may
appear different depending on your calendar setups and whether you defined
milestone tasks in your MSP plan file.
Scheduling calendars
As part of the Oracle eBusiness Suite (EBS), OP has a very flexible calendar
definition. Not all OP calendar settings are available in MSP. Therefore, there
is no mapping between the calendar definitions in MSP and OP. This means
that when you receive a file in MSP, the default calendar is always the standard
calendar definition. You need to update the calendar setting in MSP for your
project before performing any scheduling.
Also, while there are other possible definitions available in OP, MSP only
recognizes a 5-day work week unless you use elapsed days (e-days or calendar
days). You cannot use e-days to define duration in OP. Only business days are
counted in the duration when you send your project to OP. To achieve the same
effect, you can change the standard MSP calendar to use 24/7 (similar to the
concept of elapsed days).
Milestone tasks
MSP assigns all milestone tasks the duration of 0. When tasks are received in
OP with duration of zero, they are updated with a default value of 1 in order to
calculate summary values. To account for this difference when summarizing
values, milestone tasks received from MSP are assigned a task weighting of 0.

PUBLISH A PROJECT PLAN

Publishing the workplan in OP
When you publish a workplan, you can choose to create a new version or update
an existing version. Whether you created the project in OP and scheduled it in

Page 16
MSP or simply started a new project in MSP, you must send the project back to
OP with the updates. If you enabled workplan versioning on your project, or the
project was created from a template with versioning enabled, MSP Integration
allows you to specify whether you want to create a new version or update an
existing version. Each new version in OP has a unique file link to the MSP project
plan file.

Select working or published version

When you send your plan file, you choose to send the plan to OP as a working
version or a published version. Consider the following conditions to determine the
version type to send:
 You can only have one published version in OP. Therefore, when you send a
published version from MSP existing OP published versions are updated.
Any updates to the OP published version performed since the file was
received in MSP are overridden when you send the updated file to OP from
MSP. Therefore, prevent progress updates in OP if you perform updates in
MSP.
 You cannot send progress status or task status from MSP to OP for a
working version. You can only create or update statuses in OP for
published versions.
 Updates to your MSP plan structure are updated in the OP workplan. If
there is a published workplan in OP, when you delete tasks in MSP and
send the file back as a working version, they will not appear as deleted in
OP until you publish the workplan. When there is no existing published
workplan in OP or you send the version as a published version, the changes
are made immediately in OP.
Specify what type of file version you want to send using one of the 3 following
Send options:
 Send as Publish the Plan
 Send as Update Received Plan
 Send as a new working version

Options for financial plans

If the financial structure is received and new financial tasks are added in MSP,
select the Budget Data option to send the file back to OP. You can send as many
versions as required for the same plan with combinations of the following options:
 Send task level cost only
 Send Resource Assignment Work and Cost: Both task level and
resource level cost are sent
 Send Resource Assignment Work: Only resource level cost is sent and
not task level cost.
 Send versions as ‘working’, ‘current’ or ‘baselined’.
 Store costs as raw cost or burdened cost.

Page 17
 Even though you can send cost data between OP and MSP for financial plan
resource assignments, you cannot update or send resource assignments to OP
from MSP, only budget amounts.
Not all options are available for all project structures. For example, you cannot
make changes to the FBS for a project using a FSS. If you wish to use these
options, review the white paper “Oracle Project Management Integration with
Microsoft Project, Volume 3: Implementation Tips for Project Structures”.

Attaching the MSP File to a workplan version

When you send a plan file from MSP to OP, you can add the actual MSP file as an
attachment. This allows you to track the MSP files for each version you create in
OP.
To attach the MSP file, go to the Oracle Projects menu in the MSP toolbar, select
Send to Oracle Projects and select MSP File. When you send a project from MSP
that is linked to an OP project the corresponding *.mpp file is attached to the
working version or published version based on the version which was downloaded
to MSP. To view the MSP *.mpp file in OP, open the project and from the Maintain
Versions page for the correct version and click the details icon. The file is
available as an attachment in the Attachments section of workplan details page.
The attachments are only visible by default when you enable versioning on your
project. When versioning is not enabled, you may add the details icon through
personalization. From the Task page, select the Personalize link to enable the
Details column for display. Then when you return to the page and click on this
icon for the structure, you can find the file attached in Workplan Details page.

COLLECT PROGRESS
Collect progress for a plan to track your project and re-calculate estimates to
completion (ETC) in a forecast. While OP is most often used to collect progress,
you can collect progress in MSP and send updates to OP. However, you should
only use one method for the life of a project. When you update progress in both
MSP and OP, you risk loss of updates unless you tightly control the timing of the
transfers.
When you update published plan progress in OP after receiving the plan in MSP
and before sending the updated file back to OP, your updates may be lost.

Receive OP files in MSP before updating progress

While you are not required to receive an updated workplan file in MSP from OP
before you maintain WBS and collect progress in MSP, in order to preserve any
changes you make in OP you should receive a plan file in MSP before making any
updates.

Viewing OP data in MSP

Use the following views to view OP data after receiving a plan file in MSP.
View Navigation Description Actions
Calend From MSP View tasks on each Right click on the calendar and
ar toolbar, select day of a project select a formatting option:
“View” > period. - Task List: View list of all tasks
“Calendar” - Time Scale: Set calendar setup
options
- Gridlines: Change to a grid

Page 18
View Navigation Description Actions
view.
- Others: Text style, bar style,
layout, etc.
Tasks From MSP View a list of task You can add or delete tasks and
toolbar, select with perform resource assignments.
“View” > personalizable
“Gantt Chart” columns, Right click on task sheet and
predecessor select “Insert Column” to insert
information and columns from the available list of
resource field names.
assignments
On the “Task” pane, click on links
to perform MSP specific tasks:
- ‘Set a date to schedule from’ to
enter the estimated date your
project will begin
- ‘Define general working time’
to set weekly/daily working
hours
- ‘Organize tasks into phases’ to
organize your project by
creating a hierarchy. Where
tasks are similar or will be
completed in the same
timeframe, indent them under a
summary.
- ‘Schedule task’ to schedule
dependent tasks by linking
them. Often a task's start or
finish depends on the start or
finish of another task.
Task From MSP View a list of tasks Right click on task sheet and
Usage toolbar, select with select “Insert Column” to insert
“View” > “Task personalizable columns from the available list of
Usage” columns, field names.
predecessor
information,
resource
assignments and
time-phased data
by day for each
day of project.
Resour From MSP View a graphical Select “More Views” to view data
ce toolbar, select representation of for task sheet, Gantt chart or
Usage “View” > resource utilization baseline Gantt,etc.
“Resource with information
Graph”, about resource
“Resource rates and time-
Sheet” or phased data about
“Resource resource
Usage” assignments

Page 19
 View Navigation Description Actions
spread over
project life.

For a mapping of financial fields between OP and MSP, see Appendix 3: Viewing
financial fields in MSP.

Collect Progress
The following table describes important considerations when deciding whether to
use MSP or OP for collecting progress.
Method Process Considerations
Collect  Progress is specified as the Physical Percent Complete
Progress (PPC). MSP displays progress updates calculated by both MSP
using MSP and OP. The MSP value is stored in the “%-Complete” column
and the OP value is stored in the “Text 19” field.
 Choose to send either MSP progress value to OP by setting
the value for ‘Send Oracle Percent Complete’ option in the
preferences setup. To set this value in the MSP tool bar, select
“Oracle Projects” > “Preferences” and select the “Send Oracle
Percent Complete”. When you want to send the MSP value do
not set this value to “Yes”.
 You can copy the values from the MSP ‘% Complete’ fields to
the Oracle ‘Text 19’ fields within your MSP file depending on
which value you want to use. Select the rows for which you want
to copy values and use the “Copy Oracle Progress Fields to MSP
Progress” option by selecting from the MSP tool bar, “Oracle
Projects” > “Tools”.
 Percent complete can be sent for all structure types and for
all the tasks for both financial and workplans. However, for
version-enabled projects, it is mandatory to have at least one
published version to send percent complete to OP.
 MSP calculates ‘% Complete’ based on Duration of the task.
 Planned Effort is sent from MSP to OP; Actual Costs are not
sent.
 When you send progress for split workplan structures to OP,
Actual Work and Remaining Work are sent. Actual Work is
mapped as Actual Effort in OP and Remaining Work is mapped
as ETC Effort in OP. Therefore Actual and ETC values can only
be sent from MSP to OP for split workplan structures.

Page 20
 Method Process Considerations
Collect  When you collect progress in OP, you can send the values to
Progress MSP and view them in the ‘Text 19’ field.
using OP  When you choose to update the values in MSP and send it
back to OP, you must set the correct preference in the MSP
preferences setup (see description above).
 Percent complete can be received for all structure types and
for all Financial and Workplan tasks.
 OP calculates PPC based on Duration, Cost, Effort and or
Manual. When you select Manual, you enter the PPC values.
 Actual Costs, Actual Effort and ETC Effort can be received in
MSP from OP for all structure types.

UPDATE A PLAN
You can use MSP to maintain a plan by adding tasks, removing tasks and updating
task information, including resource assignments. You maintain resource
assignments and scheduling information in the same manner, using the same
procedures and techniques as you use to schedule the original plan.

Project Structure impacts on updates

The project structure you select may have a significant impact on the process you
use to remove tasks or manage workplan details. See the Oracle Project
Management Integration with Microsoft Project, Volume 1: Best Practices and
Volume 3: Implementation Tips for Project Structure whitepaper for details.

Managing financial plans

While you can share financial information between MSP and OP, you should
always use OP to manage budgets and forecasts. OP has robust features for
managing enterprise operations that affect your project.
However, you can manage financial structures and create multiple plan versions
with the flexibility to define a plan using different task and amount combinations.
Use multiple plan versions to perform ‘what-if’ analysis for different task
structures and combinations that you plan in MSP and send to OP. You can assign
resources to financial type plans in MSP, but you cannot manage financial plan
resources in MSP and send them to OP. Only budget amounts can be shared.

Updating plan information

When you update a plan in MSP, you can add or delete tasks, update task
information and create or modify resource assignments. Some project values and
options you select when sending or receiving the plan file the first time affect the
type of data you can share between MSP and OP.
 The structure of the project as defined in the project or the project
template can affect whether you can send Budget or Project type data and
whether you can add or delete tasks. This applies to new projects or
updates to the workplan in MSP.
 The task summary level selected. You do not have to send all task levels of
the full workplan when you send the file back to OP. However, if you
previously sent the same version to OP, the level you previously sent will
automatically be sent each time to transfer the file back to OP. If you send

Page 21
 summary information, the detailed task attributes will not be updated in
OP.
Carefully consider the impact of the structure you select and the information you
need in OP to manage your project to avoid overriding values in OP when you
send the MSP file with updates. To avoid problems with data consistency and
potential errors when updating task attributes in MSP, receive and work with the
OP List of Values (LOV).
See Oracle Project Management Integration with Microsoft Project, Volume 1:
Best Practices Volume 3: Implementation Tips for Project Structure whitepapers
for more details.
Plan and data type options
Based on the type of plan you received and the type of data you are sending
back to OP, only some updates are made in OP.
Plan & Data Type
Updates Allowed
Options
Send a Financial Plan Since the financial plan is sent with budget data,
with Budget Data only financial data is sent to OP financial plan.

The following updates are sent for all structure

types:
 Financial plan task attributes (enter,
update, remove)
 Updates to financial plan amounts (cost)
 Cost information (by cost type)
 Except for PSS, new or deleted financial
plan tasks are updated.
The following updates are never sent for any
structure type:
 Workplan task attributes
 Task dependencies
Send the Financial Plan Since the financial plan is sent with project data,
with Project Data only workplan attribute updates on the financial
tasks are sent.

To send workplan task attributes for workplan

tasks, send project data for the workplan
separately.

Updates to the following are not sent:

 Financial plan task attributes
 Financial plan task resource assignments
 Task dependencies
 Added or deleted financial plan tasks
 Cost information
Send the Workplan with This combination is disabled and never allowed for
Budget Data any structure type.
Send Workplan with Since the workplan is sent with project data, only
Project Data workplan information updates are sent for all
structure types.

Page 22
 Plan & Data Type
Updates Allowed
Options
The following updates are sent:
 Workplan task attributes (enter, update,
remove)
 Resource assignments
 Task dependencies
 Added or deleted workplan tasks

The following updates are never sent for any

project structure workplan since they are either
related to the financial plan or are considered
budget data:
 Financial task attributes
 Cost information

Using time-phased data

Time-phased data are the values assigned to a resource for the individual periods
of the assignment duration.
Receiving Time Phased Data in MSP
Time-phased data cannot be received in MSP from OP. Assignment data is
received from OP as lump sum amount and by default is spread by MSP for the
task assignment duration based on the MSP flat contour. You can check the setup
for work contour when resources are assigned to tasks by viewing the Task-
Resource assignment in MSP. From the MSP tool bar, select View > Resource
Sheet and double-click the task-resource assignment.
To modify the spread in MSP, you can select a different spread method or update
the periodic values manually.
Send Time Phased Data to OP
After you send the time-phased data back to OP, the spread curve recorded for the
resource assignment is Null signifying that MSP used its own spread logic for this
resource assignment. You can send time-phased data for all 4 types of workplan
structures.
When you want to send your periodic data for a resource assignment from MSP to
OP, select the Oracle Projects menu from the MSP tool bar, and select
Preferences. Check the box for Send Time-phased Cost and Work Data for
Resources.
The logic to spread data differs in MSP and OP. MSP receives data as a lump sum
and spreads data in a flat contour by default. Therefore when actuals for tasks are
already collected, be careful when transferring data. When periodic data exists
before the ETC Start Date and you apply actuals to the current working version of
a workplan, you cannot send time-phased data from MSP to OP. A message warns
that the data can be modified for periods on or after ETC date. The message
provides the Project, Task, Resource and ETC date so you can easily identify
resource assignment details and correct the data for periods before the ETC date.

Page 23
 Correct the time-phased data for resource assignments to send the information to
OP successfully.

Example
Consider the following example:
120 hours of Resource R1 is assigned to Task T1 of a
project. Task T1 has start and end dates as 01-Jan-09 to
31-Dec-09. Workplan has GL periods as the basis for time-
phasing. The resource assignment has even spread curve.
The periodic distribution for the assignment shows 10
hours from Jan-09 to Dec-09.
Now apply 10 hours of R1 is actual effort. After
distributing the effort and summarizing the actuals, the
progress is applied to the current working version. The
periodic distribution for the assignment shows period Jan-
09 to June-09 as closed and the remaining effort (ETC) is
distributed from Aug-09 to Dec-09. Jul-09 would show
planned as 10 hours and actual as 10 hours.
Once the data is received from OP in MSP for the current
working version, MSP re-spreads the planned effort of
120 from Jan-09 to Dec-09 based on the flat contour
algorithm. Therefore if the ETC date is 20-Jul (the
progress as of date in OP), MSP spreads the effort before
20-Jul. In this situation, when the time-phased data is
sent from MSP to OP, an error message is triggered
because the periods from Jan-09 to June-09 are closed in
OP.
To correct this, you should delete any periodic data before the “ETC Start Date”
and spread the planned data on or after that date.

APPENDICES
APPENDIX 1: FAQS
Frequently Asked Questions

Q: What MSP Versions are certified for Oracle Project Management releases?
A: The table below shows the status (Refer to Metalink note- 550450.1)
Oracle Compatible with
Projects
12.1 MSP – 2000,2003
12.1.1 MSP –
2000,2003,2007

12.0 MSP – 2000,2003

12.0.1 MSP – 2000,2003

Page 24
 12.0.2 MSP – 2000,2003
12.0.3 MSP – 2000,2003
12.0.4 MSP – 2000,2003
12.0.6 MSP – 2000,2003

11.5.10 CU #1 MSP – 2000,2003

11.5.10 CU #2 MSP – 2000,2003
11.5.10 CU #3 MSP – 2000,2003

11i.FP.M Rup.3 MSP – 2000,2003,

11i.FP.M Rup.4 MSP – 2000,2003,
2007

Q: Are the MSP Integration pages personalizable?

A: The Microsoft Project integration pages are designed using the UIX
components directly and hence cannot be personalized. (Refer to ER 8813476)

Q: Are all structures of Workplan/Financial Plan supported through MSP

Integration?
A: Metalink Note332563.1 stands withdrawn. All structures of Workplan/Financial
Plan are supported through MSP Integration.

Q: Is Portuguese language supported for MSP Integration?

A: For the MSP Integration to work in Portuguese language, all the following
settings should be in same language.
 Self service application user session language at the time of installing MSP
integration
 Windows regional settings
 Language in which Microsoft Project application is installed
 Language setting used while logging in to self service application from MSP in
order to receive the project (Refer to bug 8793415)

Q: If a project template has “quick entry” fields for Start Date and End Date of
the project, why they are not displayed when creating and sending project
from MSP to OP?
A: When sending project from MSP to OP, the start and end date of the projects
are taken from the project in MSP so when sending a file from MSP to OP you
cannot enter them.

Q: Are tasks of a project attached to a program downloaded to MSP when the

program is received in MSP?
A: Program functionality is not supported in MSP Integration (Refer to ER
8635490)

Page 25
Q: Where is the progress% that is entered in OP shown in MSP?
A: Progress% entered in OP is shown in MSP under 'Oracle % Complete' column.

Q: Are PTD/YTD Revenue columns available for download to MSP?

A: Only PTD/YTD Raw Cost and Burdened Cost are currently receivable from OP
(Refer to ER 8558782)

Q: How is time-phased data send and received to and from MSP to OP?
A: Time-phased data cannot be received from OP to MSP but can only be sent
from MSP to OP(Refer to ER 8549455)

Q: How does “Copy Oracle Progress fields to MSP fields” functionality work?
A: To copy progress for a row, or task, highlight that row and perform the “Copy
Oracle Progress fields to MSP fields” action. In order to copy all rows, you have to
highlight all rows. Do not highlight or copy to Level 0 row or the link to Oracle
Projects may be broken.

Q: Can duration be interfaced from MSP to OP in ‘elapsed days’?

A: Currently you cannot send duration in calendar days (elapsed days) between
MSP and OP. Only business days, based upon the calendar setup, are supported.
Even though it is allowed, the transfer of the correct duration to OP, while
retrieving it back, the unit measure will not be retained. The duration will come in
as business days. A similar issue for the lag days field is described in Metalink
note 564391.1

Q: Why is the UOM for a resource of ‘currency’ is shown in MSP as ‘Dollars’?

A: The displayed UOM is the lookup meaning corresponding to the lookup code of
'DOLLARS'. The UOM that is displayed in MSP is the UOM code and not the
corresponding UOM meaning. This is why it shows the UOM as 'DOLLARS' and
not ‘Currency’.

Q: How do I delete a task in MSP and send to OP?

A: If there are one or more Published versions, you need to update the current
working version to see that tasks are deleted. After deleting a task from MSP, the
tasks will be selected for deletion. When sending data back to OP, the working
version must first be published to have tasks deleted. If there is No Published
version, in this case, you can simply DELETE a task and it will be deleted
IMMEDIATELY. You need to upload the Project after deletion to complete the
process.

Q: The cost field is not being sent from MSP to Oracle Projects.
A: Costs are sent only for non-shared workplan structure. Financial structure
costs are sent with the budget data. When you set the preference "Calculate Cost
Using Microsoft Project", Cost is calculated based on the Standard Rate and Per
Use Cost for the resource and the amount of work assigned to the resources for
the task. It is computed using the formula = (Standard Rate x Quantity)+ (Cost
per use).

Page 26
 For the workplan task without any resource assignment, planned cost will be
calculated based on the [planned effort x unit rate] for people effort. In this case it
cannot be sent to OP from MSP because MSP can only send assignment level cost
and that is only if the preference was set to “Use MSP to Calculate Cost.”

Q: What are scheduling capabilities available in OP?

A: Oracle Projects does not have true scheduling capabilities. As such, the
scheduling of tasks and assignments are done via integration with MSP or
Primavera. In MSP integration, the scheduled dates from Oracle are not passed to
MSP when the project is downloaded. Information that is passed includes the
scheduling attributes like constraint types, constraint dates, scheduled duration,
etc., based on which the MSP scheduling engine does the actual scheduling. Once
the workplan has been scheduled, it is then sent back to OP. Only at this point the
workplan is considered scheduled. If any re-planning happens, then the workplan
has to again be downloaded to MSP, rescheduled and then uploaded back to OP.

Q: What are the task types supported in MSP Integration?

A: The following Task Types are supported:
1) Fixed Units (default): the number of assignment units remains constant,
regardless of the amount of work or duration on the task. In this case, when an
assignment is created, then the assignment work is sent to MSP. The assignment
units will remain constant and the assignment duration will be computed by
MSP based on the scheduling formula. The user entered scheduled duration in
OP will not be honored.
2) Fixed Duration: the duration for the task remains constant, regardless of the
number of resources (assignment units) assigned or the amount of work. In this
case, the task duration and the assignment work are sent to MSP. MSP will keep
the scheduled duration fixed and for the assignment work, compute the
assignment units, i.e., both the user entered scheduled duration and the
assignment work is honored.
3) Fixed Work: the amount of work remains constant, regardless of any change in
duration or the number of resources (assignment units) assigned to the task.

Q: What steps should be performed if I want to create one MSP file from
existing MSP file which has resource assignments and send to OP, to save
effort of creating another MSP file with large data?
A: Do not copy and paste from one MSP file to another because copy-paste may
bring along attributes from the older project. Following steps are suggested:
1) Create a large WBS structure in MSP with all the required resource
assignments and attributes (by referring to the already existing large WBS).
Save this WBS in MSP.
2) Send this file from MSP and create a new project in OP using the same template
that has the centralized PRL.
3) To reuse, open the saved WBS (which we saved in step 1), make any required
changes and then again send it to OP by creating another new project, again by
using the same template as above.

Page 27
Q: What is the functionality to assign new tasks added in MSP in the
Workplan?
A: When a project is received in MSP, if the checkbox for ‘Task Numbers’ is
checked then after the task numbers are added in MSP, it is necessary to populate
data in column for ‘text5’. Otherwise the new tasks are not sent to OP. When
project is received in MSP, if checkbox for ‘Task Numbers’ is NOT checked then
after the task numbers are added in MSP, it is NOT necessary to populate data in
column for ‘text5’, AND the new task are correctly sent to OP

Q: If mapped task are received from OP to MSP, is the mapping link between
the workplan task and financial task lost?
A: The link is maintained, vide fix done in Bug 8612963-bug is under fix.

APPENDIX 2: MSP INTEGRATION SETUP OPTIONS

Configure setups to enable or control features. The following list provides

recommendations for typical implementations or important information about
setups.
Step Navigation Recommendation Impacts
Initialize OP - After logging in Enable this option if You cannot work with an
MSP with Projects Super you want to work with OP project in MSP
Integration User responsibility, a project in both MSP without enabling the
go to Setup and and OP integration option
select the
Microsoft
Project Integration
Installation
hyperlink
Select In Microsoft You must select the Currently supported
installed MSP Project Integration correct version which MSP versions are MSP
version Installation window is installed before you 2000, MSP 2002, MSP
select the MSP initialize MSP 2003, MSP 2007.
Version Integration Browser requirements:
 Internet Explorer 5.5
or greater.
 Insure your browser
option settings are
enabled for ActiveX
controls. Refer to the
FAQ section for
further details.
Setup MSP From MSP toolbar, Set the following MSP sets default values
preferences Select “Tools” > options based on your for each of these
and controls “Options” user or business preferences. You should
for integration preferences: insure the default values
 View: Use this are consistent with your
option to setup business practices to
your default view, avoid mismatches in
toolbar setup, etc., data for resource
for viewing a assignments.

Page 28
Step Navigation Recommendation Impacts
project in MSP. OP has an extremely
 General: Use this flexible calendar
option to setup the definition and not all OP
default for calendar settings are
standard rate available in MSP.
/overtime rate  When you receive a
 Edit: Use this file in MSP, the
option to set default calendar is
preferences for always the standard
time units such as calendar definition
days, hours, etc . since there is no
 Calendar: Use this mapping between the
option to setup calendar definitions
calendar defaults, in MSP and OP. You
such as hours per need to update the
day, per week, calendar setting
default start and before performing
end times, etc. any scheduling.
This setup allows  You cannot use e-
you to schedule days (elapsed or
resources based calendar days) for a
on your standard schedule in OP. Only
business calendar business days are
including holidays counted in the
each of the duration when you
resource would send your project to
have during OP.
project duration.
Setup OP From MSP toolbar, Set the following  When you select an
preferences select the Oracle preferences to “Up to Task Level” to
and controls Projects menu, determine how your send the WBS,
for integration then select data is controlled summary task values
“Preferences” when sending files are sent to OP for the
between OP and MSP: tasks at the specified
 Send Work level. For values that
Breakdown are simply added,
Structure: there is generally no
Determine the difference in the
level to which you amounts except
want to send your occasionally small
tasks to OP. You amounts in rounding.
can select all However, when you
levels if you want update Physical
to send the full Percent Complete
WBS from MSP to (PPC), the averaging
OP or Up to Task calculation may have
Level to send a more than a rounding
portion of the difference. Therefore,
WBS to OP. if exact matching is
 Assign Oracle required, you can copy
Projects "Task the value calculated by

Page 29
Step Navigation Recommendation Impacts
Number": You can MSP to the Oracle field
determine the and that value will be
basis on which sent to OP for the
task numbers are summary tasks.
assigned when  Resource rates (along
creating tasks in with UOM) are used to
OP. Your options calculate costs for
are: resource task
- Outline assignments in MSP.
number: Use When you receive a file
the Outline in MSP, the existing
Number option rates in OP are sent to
if you want to MSP where you can
use the task view them. After
numbers updating the Quantity
generated in and sending the file to
the Outline OP, these rates are
Number field used to calculate
in MSP to resource costs in the
generate task workplan. When you
number in OP. are using one of the
- Unique ID: The split structures, you
same applies to can work separately
Unique ID. with the workplan, so
- Column text 5: you have the option to
Use the enter override rates in
Column Text5 MSP and use those
option if you rates to calculate cost.
want to enter To enter and use these
your own task rates, you select
numbers. “MSP” as the Cost
When you Calculation Method.
select this This option is available
option, OP uses only when you are
the values in working with the
this MSP field workplan costs and not
as task available for FSS or
numbers. PSS structures.
 Calculate Cost
Method: You can
choose whether
your costs will be
calculated using
OP or MSP.
 Send Time-phased
Data: Use this
option if you want
to send periodic
values to OP for
resource
assignments when

Page 30
 Step Navigation Recommendation Impacts
you send your
MSP project data.
Time-phased data
cannot be received
in MSP from OP
(see the Time-
phased Data
section below for
more details).
 Send Oracle
Percent Complete:
Use this option if
you want to send
the values in the
Oracle Percent
Complete column
when you send
your MSP project
data.
After you send a
project to Oracle
Projects, you cannot
change the
preferences.

APPENDIX 3: VIEWING FINANCIAL FIELDS IN MSP

When you send OP data for actuals, the performance data is stored in specific
locations in MSP depending on the information received. The table below list
where the OP data is stored in MSP. The table also lists the location of project
information in MSP and OP. For MSP Locations, unless otherwise specified,
navigate to the Oracle Projects menu in the MSP tool bar.
Measure or MSP Location in MSP Name in OP Location in
Field Name OP
ITD/PTD Raw Cost  MSP Tool Bar > View> ITD Raw Cost Reporting Tab
Gantt chart
 MSP Tool Bar > View >
Tracking Gantt
ITD/PTD Burdened  MSP Tool Bar > View> ITD Burdened Reporting Tab
Cost Gantt chart Cost
 MSP Tool Bar > View >
Tracking Gantt
ITD Revenue  MSP Tool Bar > View> ITD Revenue Reporting Tab
Gantt chart
 MSP Tool Bar > View >
Tracking Gantt
Progress Status  View > Oracle Review Progress status Workplan Tab >
Gantt / Oracle Progress Task
Gantt

Page 31
Measure or MSP Location in MSP Name in OP Location in
Field Name OP
Oracle % Complete  View > Oracle Review
Gantt/ Oracle Progress
Gantt/ Oracle Financial
Gantt
Planned Effort  View > Oracle Review Planned Effort Workplan Tab >
Gantt/ Oracle Progress Task
Gantt
Cost  View > Oracle Review Planned Cost Workplan Tab >
Gantt/ Oracle Progress Task
Gantt/ Oracle Financial
Gantt
Actual Effort  View > Oracle Review Actual Effort Workplan Tab >
Gantt/ Oracle Progress Task
Gantt
Estimated  View > Oracle Review ETC Effort Workplan Tab >
Remaining Effort Gantt/ Oracle Progress Task
Gantt/ Oracle Financial
Gantt
Baseline Cost (for  View > Oracle Review Baselined
workplan version Gantt/ Oracle Progress Version of Cost
set to ‘baseline’) Gantt/ Oracle Financial
Gantt
Latest Published  View > Oracle Review Published
Cost Gantt/ Oracle Progress Version of Cost
Gantt/ Oracle Financial
Gantt
Remaining Cost  View > Oracle Review
Gantt/ Oracle Progress
Gantt/ Oracle Financial
Gantt
Actual Cost  View > Oracle Review Actual Cost Workplan tab >
Gantt/ Oracle Progress Task
Gantt/ Oracle Financial
Gantt
Work  View > Oracle Review Planned Effort Workplan tab >
Resource Usage Task
Actual work  View > Oracle Review Actual Effort Workplan tab >
Resource Usage Task
Remaining work  View > Oracle Review ETC Effort Workplan tab >
Resource Usage Task
Standard rate Burdened cost Workplan tab >
rate Task> task
details>resourc
es tab

Page 32
Oracle Project Management
April 2010

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
www.oracle.com

Oracle Corporation provides the software

that powers the Internet.

Oracle is a registered trademark of Oracle Corporation. Various

product and service names referenced herein may be trademarks
of Oracle Corporation. All other product and service names
mentioned may be trademarks of their respective owners.

Copyright © 2010 Oracle Corporation

All rights reserved.

Page 33