The tables below list the workplan and financial attributes transferred between Oracle Projects and Microsoft Project, the direction of data transfer, the Oracle Projects fields, and the corresponding fields in Microsoft Project. For successful integration, columns must not contain other information that Microsoft Project Integration uses.
Workplan Attributes
The following table lists the task planning attributes for Oracle Projects and Microsoft Project.
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Task Name | Task Name | Both ways |
| Task Number | Unique ID or Text5 or Outline Number | - Unique ID and Outline Number:
Microsoft Project to Oracle Projects - Text5: Both ways |
| Task Manager | Text16 | Oracle Projects to Microsoft Project |
| Task Manager ID | Text6 | Both ways |
| Task Description | Notes | Both ways |
| Task Priority | Text10 | Both ways |
| Task Outline Number and Level | Outline Number and Level | Both ways |
| Task Type | Text18 | Oracle Projects to Microsoft Project |
| Task Type ID | Text7 | Both ways |
| Scheduling Tool Task Type | Task Type | Both ways |
| Work Type | Text17 | Oracle Projects to Microsoft Project |
| Work Type ID | Text8 | Both ways |
| Service Type Code | Text4 | Both ways |
| Chargeable Flag | Text2 | Both ways |
| Billable Flag | Text3 | Both ways |
| Scheduled Start Date | Start | Microsoft Project to Oracle Projects |
| Scheduled Finish Date | Finish | Microsoft Project to Oracle Projects |
| Scheduled Duration: For task with no assignments | Duration | Both ways |
| Scheduled Duration: For task with assignments | Duration | - Both ways for fixed duration
tasks - Microsoft Project to Oracle Projects for fixed units and fixed work tasks |
| Actual Duration | Actual Duration | Microsoft Project to Oracle Projects |
| Transaction Start Date | - Start1 for shared structures - Start for split structures | Both ways |
| Transaction Finish Date | - Start1 for shared structures - Start for split structures | Both ways |
| Milestone Flag | Milestone | Both ways |
| Critical Flag | Critical | Microsoft Project to Oracle Projects |
| Constraint Date | Constraint Date | Both ways |
| Constraint Type | Constraint Type | Both ways |
| Early Start | Early Start | Microsoft Project to Oracle Projects |
| Early Finish | Early Finish | Microsoft Project to Oracle Projects |
| Late Start | Late Start | Microsoft Project to Oracle Projects |
| Late Finish | Late Finish | Microsoft Project to Oracle Projects |
| Free Slack (Free Float) | Free Slack | Microsoft Project to Oracle Projects |
| Total Slack (Total Float) | Total Slack | Microsoft Project to Oracle Projects |
| Task Effort Driven Flag | Effort Driven | Both ways |
| Level Assignments | Level Assignments | Both ways |
| Item Code | Text14 | Both ways |
| UOM Code | Text15 | Both ways |
| Dependencies: Predecessors | Predecessors | Both ways |
| Planned Efforts | Works | Both ways |
| Planned Cost | Cost | Microsoft Project to Oracle Projects when Calculate Cost Using Microsoft Project option is selected. |
The following table lists the Oracle Projects fields and Microsoft Project fields for task progress attributes:
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Progress Status Code | Text11 | Both ways |
| Progress Overview | Text12 | Both ways |
| Progress Comments | Text13 | Both ways
Note: Microsoft Project receives only the first 255 characters from Oracle Projects. |
| Planned Work Quantity | Number2 | Both ways |
| Cumulative Work Quantity | Number1 | Both ways |
| Actual Effort to Date | Actual Work | Both ways |
| Estimated to Complete Effort | Remaining Work | Microsoft Project to Oracle Projects |
| Estimate to Complete Cost | Cost6 | Oracle Projects to Microsoft Project |
| Actual Start | Actual Start | Both ways if task has no assignments |
| Actual Finish | Actual Finish | Both ways if task has no assignments |
| Estimated Start | Start3 | Both ways |
| Estimated Finish | Finish3 | Both ways |
| Physical % Complete | Text19 | Both ways |
| Task Status Code | Text9 | Both ways |
The following table lists the Oracle Projects fields and Microsoft Project fields for resource assignment planning attributes:
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Planning Resource Name | Resource Name | Both ways |
| Role Name | Text2 | Both ways |
| Unit of Measure | Text3 | Oracle Projects to Microsoft Project |
| Assignment Delay | Assignment Delay | Microsoft Project to Oracle Projects |
| Scheduled Start | Start | Microsoft Project to Oracle Projects |
| Scheduled Finish | Finish | Microsoft Project to Oracle Projects |
| Planned Quantity | Work | Both ways |
| Planned Cost | Cost1 | Both ways |
The following table lists the Oracle Projects fields and Microsoft Project fields for resource assignment progress attributes:
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Actual Start | Actual Start | Both ways |
| Actual Finish | Actual Finish | Both ways |
| Actual Effort | Actual Work | Both ways |
| Estimate to Complete Effort | Remaining Work | Microsoft Project to Oracle Projects |
| Actual Cost | Actual Cost | Oracle Projects to Microsoft Project |
| Estimate to Complete Cost | Cost2 | Both ways |
The following table lists the Oracle Projects fields and Microsoft Project fields for the resource attributes:
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Planning Resource Alias | Name | Oracle Projects to Microsoft Project |
| Resource Class | Resource Type | Oracle Projects to Microsoft Project |
| Resource Unit of Measure | Text2 | Oracle Projects to Microsoft Project |
| Burden Rate | Standard Rate | Oracle Projects to Microsoft Project |
Financial Attributes
The following table lists the Oracle Projects fields and Microsoft Project fields for financial attributes:
| Oracle Projects Field | Microsoft Project Field | Direction of Data Transfer |
|---|---|---|
| Baseline Cost | Cost 10 | Oracle Projects to Microsoft Projects |
| Billable/Capitalizable | Text3 | Both ways |
| Burdened Cost | Cost | Microsoft Project to Oracle |
| Chargeable | Text2 | Both ways |
| ITD Burden Cost | Cost 2 | Oracle Projects to Microsoft Projects |
| ITD Raw Cost | Cost 1 | Oracle Projects to Microsoft Projects |
| Latest Published Cost | Cost 9 | Oracle Projects to Microsoft Projects |
| Microsoft Project to Oracle | Projects | Quantity |
| Projects | Revenue | Cost |
| PTD Burden Cost | Cost 6 | Oracle Projects to Microsoft Projects |
| PTD Raw Cost | Cost 4 | Oracle Projects to Microsoft Projects |
| Raw Cost | Cost | Microsoft Project to Oracle Projects |
| Revenue | Cost3 | Oracle Projects to Microsoft Projects |
| Service Type Code | Text4 | Both ways |
| Work | Microsoft Project to Oracle | Projects |
| YTD Burden Cost | Cost 7 | Oracle Projects to Microsoft Projects |
| YTD Raw Cost | Cost 5 | Oracle Projects to Microsoft Projects |
The integration process also uses several project-level columns in Microsoft Project. However, you should not access these columns to view or change information for the Project Summary Task using Microsoft Project Integration or any of the related features in Microsoft Project.
The following business rules apply to sending attribute values from Microsoft Project to Oracle Projects:
Depending on the option you select during the Send Budget Data process, Microsoft Project Integration transfers the Cost field in Microsoft Project to either the Raw Cost, Burdened Cost, or Revenue field in Oracle Projects.
To send billable and chargeable statuses to Oracle Projects, you must enter either Yes or No in Microsoft Project for the billable and the chargeable flags. These values are not case sensitive. If you enter only Y or N, then Microsoft Project Integration ignores the values and does not send them to Oracle Projects.
Task manager, task type, and work type have two columns in Microsoft Project, a descriptive text column and an ID column. If you enter the description, but leave the ID column blank, then Microsoft Project Integration does not send the value to Oracle Projects. For example, if you enter the task manager name in the Task Manager column and leave the Task Manager ID column blank, then Microsoft Project Integration does not sent the value you entered in the Task Manager column to Oracle Projects.
Although Oracle Projects strongly recommends that you use a list of values to enter values in Microsoft Project whenever a list of values is available, you can choose to directly enter the values. If the value that you enter in Microsoft Project does not exactly match the value in Oracle Projects, then one of the following two outcomes can occur, depending on the attribute:
Microsoft Project Integration ignores the value and does not send it to Oracle Projects. However, the send process sends the remainder of the information to Oracle Projects. This outcome occurs for the following attributes: Service Type, Priority, Progress Status, Item, UOM, Task Status, and Work Type.
The entire send process is unsuccessful. This outcome occurs for the following attributes: Task Manager (if you enter the Task Manager ID incorrectly) and Task Type (if you enter the Task Type ID incorrectly).