When you send tasks to Oracle Projects, the task numbers can be populated with any one of the following Microsoft Project fields:

• Outline Number

• Unique ID

• Text 5

To set task numbering preferences in Microsoft Project

1. In Microsoft Project, open the project for which you want to set preferences.

2. Choose > Preferences.

   The Preferences window opens.

3. Assign Oracle Task Number field to: Outline Number, Unique ID, or Column Text5.

   Warning: After you send a project to Oracle Projects, you cannot change the preferences. For more information, see: Clearing the Project Link.

About the Task Numbering Options

There are advantages and disadvantages for each of the options available for specifying task numbers in Microsoft Project. A complete description of each option and an example follows the procedure.

Outline Number

Use the Outline Number option if you want to use the task numbers generated in the Outline Number field in Microsoft Project to generate task number in Oracle Projects.

Advantages: The outline style of this field (for example, 1.1, 1.1.1, 1.1.2) is an intuitive way to organize a WBS.

Disadvantages: Microsoft Project generates the numbers as you create tasks, and then regenerates (and changes) the numbers as you add, move, and delete tasks. Microsoft Project may even reuse some numbers. You cannot modify the outline numbers yourself. Oracle Projects attempts to reconcile the changed outline numbers when you send a project to Oracle Projects, but it is possible for the outline numbers for linked projects to become unsynchronized.

Unique ID

Use the Unique ID option if you want Oracle Projects to use the task numbers generated in the Unique ID field in Microsoft Project.

Advantages: Microsoft Project generates the numbers as you create tasks, but values are always unique because Microsoft Project does not reuse the numbers as you add, move, and delete tasks. You cannot modify the outline numbers yourself. Because the numbers are always unique, the task numbers for linked projects are unlikely to become unsynchronized.

Disadvantages: Some people may find that the simple integer format of the task number makes it difficult to discern tasks and subtasks.

Column Text5

Use the Column Text5 option if you want to enter your own task numbers. When you select this option, Oracle Projects uses the values in this field as task numbers.

You can also control which tasks are sent to Oracle Projects, because only tasks that have entries in the Text5 column are sent to Oracle Projects. However, Oracle Projects does not send numbered subtasks that belong to an unnumbered direct or higher-level parent.

Advantages: You have complete control over both the task numbering format and which tasks are sent to Oracle Projects. After you send a project to Oracle Projects, the font of the task number in Text5 changes to bold italic. If you add a new task, you can see immediately if it has been sent to Oracle Projects or not.

Disadvantages: You are completely responsible for coordinating the task numbers in linked projects. If you overwrite or delete values in the Text5 field, linked projects may become unsynchronized. You must be very careful not to reuse task numbers in Microsoft Project that have already been sent to Oracle Projects. Use of the Column Text5 also affects templates and projects that you receive into (download to) Microsoft Project. For more information, see: Receiving Project Information from Oracle Projects.

Example: In the following example, tasks without an entry in the Text5 column are not sent to Oracle Projects or included in the Oracle Projects WBS. Subtask 3.1 is not sent because its parent task is unnumbered.