Instructions Index

Overview
Projects
Tasks
Transaction Controls
Project Team Members
Project Classifications
Project Expense Resources
Task Resources
Task Dependencies
Team Member Progress
Project Codes
Task Codes
Preparing the Table Data
Loading the Data
Generate CSV
Excel Template Format
Recommendations for Loading Project Data
Importing the Loaded Data

Overview
Use this workbook to import projects (both for planning only as well as the ones enabled for financial management) and ass
resources, task resource assignments, task dependencies, team member progress, project codes, and task codes from any e
template to prepare the comma separated values (.CSV) files that you can use to upload projects, tasks, resources and relat
open interface tables and all exceptions are printed in the process output report.

Use the Options sheet to first select the features you want to implement for your project before you enter data in this sprea
implement are then available on the spreadsheet.

Important Note:
The comma separated values (.CSV) files generated from this template will have different column order than the column or
source system, follow the order specified in the control file. You must enter the project name on every sheet. Any row with

Projects
Consider the following when you prepare the project data:
• The following fields are required:
- Project Name
• If you do not specify the project template, the project will only be available in the Project Management work area. If you n
financial management from the Project Financial Management work area.
- For execution only projects, you need to specify the Project Manager in the Projects sheet.
• To create a project for financial management, you must set up a project template first. This template allows you to copy v
project. You can specify the values you want to copy from the template in the columns on the Projects sheet. The following
customers, suppliers, and partners.
• Enter the lookup meanings instead of the lookup codes wherever it's not explicitly mentioned to enter code.
• If descriptive flexfields use a table value set, enter the value for the value set instead of the value set ID.

Tasks
Consider the following when you prepare the task data:
• You must include the imported tasks and the projects to which the tasks belong in the same spreadsheet.
• The following fields are required:
- Project Name
- Task Number
• You must associate a project that is enabled for financial management with a Project Plan Type before you can add tasks t
• Enter top-level tasks before subtasks to ensure the task structure is correct.
• The task outline is determined by the sequence of the tasks in the spreadsheet. Ensure the tasks sequence reflects the tas
• Tasks created in Project Financial Management inherit the setup options from the Project Plan Type associated with the p
project.
• Use this template to prepare the comma separated values (.CSV) file that uploads tasks to the tasks open interface table.
• A financial task cannot have a parent task that is not enabled for financial transactions.
• The application ignores the tasks available in the Tasks sheet if the Copy Tasks from Template column has the value Y.
• For a project, Project Plan Baseline is created only if there is at least one task with baseline information. In the baseline p
baseline information is provided for the task or for one of its subtasks in the hierarchy below it.

Transaction Controls
Consider the following when you prepare the transaction controls data:
• You must include the projects and the transaction controls assigned to those projects in the same spreadsheet.
• The following fields are required:
- Transaction Control Reference
- Project Name
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us

Project Team Members

Consider the following when you prepare the team members data:
• You must include the projects and the team members assigned to those projects in the same spreadsheet.
• The following fields are required:
- Project Name
- Team Member Number or Team Member Name or Team Member Email
- Project Role
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us
• You can only import internal team members. You cannot import customer, partner, or supplier contacts.
• The person you are adding as a team member must already be defined either as a project enterprise resource or as a valid
• All the resources are added in the Planned status in Manage Project Resources.

Project Classifications
Consider the following when you prepare the project classifications data:
• You must include the classifications and the projects to which the classifications are assigned in the same spreadsheet.
• The following fields are required:
- Project Name
- Class Category
- Class Code
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us

Project Expense Resources

Consider the following when you prepare the Project Expense Resources data:
• You must include the nonlabor resources and the projects the resources are assigned to in the same spreadsheet.
• The following fields are required:
- Project Name
- Resource Name
- Expense Resource Amount
• This sheet will not be available if you do not select Yes for Project Execution Management in Options sheet.

Task Resources
Consider the following when you prepare the Task Resource assignment data for the Project Plan:
• You must include the task resources and the projects to which the tasks belong in the same spreadsheet.
• The following fields are required:
- Project Name
- Task Number
- Resource Type
- Resource Name for Expense resources and Resource Name or Resource Email for Labor resources
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us
• This sheet will not be available if you do not select Yes for Project Execution Management in Options sheet.

Task Dependencies
Consider the following when you prepare the Task Dependencies data for the project plan:
• Projects and tasks to which the dependencies are assigned must be included in the same spreadsheet.
• The following fields are required:
- Project Name
- Task Number
- Predecessor Task Number
• Only subtasks can have dependencies on other subtasks. There cannot be more than one dependency between any two t
• The schedule mode of a task is set to Auto if you add at least one predecessor for that task. This ignores the value specifie
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us
• This sheet will not be available if you do not select Yes for Project Execution Management in Options sheet.

Team Member Progress

Consider the following when you prepare the Team Member Progress data for the Tasks in the Project Plan:
• You must include the tasks and the task resource assignments to which the Team Member Progress is reported in the sam
• The following fields are required:
- Project Name
- Task Number
• All other fields are optional. If you don't provide a value, the default value specified in the column header comments is us
• Task Progress Status is calculated based on the Task Percent Complete. If the Percent Complete is zero or unspecified, pro
otherwise In Progress.
• If there are multiple resource assigned to a task, provide cumulative progress for all the team members for the task.
• This sheet will not be available if you do not select Yes for Project Execution Management in Options sheet.

Project Codes
Consider the following when you prepare the Project Codes data:
• Projects to which the codes are assigned must be included in the same spreadsheet.
• If the project code value is not set in the Manage Enterprise Project Codes setup page, then the user entered values will b
• The following fields are required:
- Project Name
• All other fields are optional.
• This sheet will not be available if you do not select Yes for Project Execution Management and for Project Codes in Option

Task Codes
Consider the following when you prepare the Task Codes data:
• You must include the tasks to which you are assigning the task codes in the same spreadsheet.
• If the task code value is not set in the Manage Enterprise Task Codes setup page, then the user entered values will be igno
• The following fields are required:
- Project Name
- Task Number
• All other fields are optional.
• This sheet will not be visible if you do not select Yes for Project Execution Management and Task Codes in Options sheet.

Preparing the Table Data

1. Prepare the data for the interface tables using the corresponding worksheets in this template. See the section Excel Tem
2. Refer to the comment on each column header either for detailed instructions on preparing the data in that column, or fo
Loading the Data
1. After you finish preparing the data in the worksheet, click the Generate CSV File button to generate a ZIP file containing o
2. Load the data using the Load Interface File for Import process.
a. Navigate to the Scheduled Processes page.
b. Click the Schedule New Process button.
c. Select the Load Interface File for Import process.
d. Select Import Projects as the import process. Select the data file to upload. You can upload either the CSV file or the z
e. Verify that the process completes successfully.
f. If required, correct the data in this template, regenerate the CSV file and the zip file that contains the CSV file, and resu
3. Correct load errors:
a. If the load of the CSV file fails for a row, the Load Interface File for Import process completes in error and the Load File
b. All rows that are loaded from the CSV file into the interface table are deleted, even the rows that loaded successfully.
the process without having to separate the successful rows from the rows that need correction.
c. Review the log and output files of the Load File to Interface child process for information about the data that caused t
d. Correct the data in this template.
e. Repeat steps 1 and 2 of this section, generate the CSV file, and load the data using the Load Interface File for Import p
f. Repeat the above steps until all data is loaded successfully.

For information on loading the data in the CSV files into the interface tables, see the File-Based Data Import for Oracle PPM
To view the interface tables, see the topic Import Projects in the File-Based Data Import for Oracle PPM Cloud guide.

Generate CSV File

Excel Template Format

• Each interface table is represented as a separate Excel sheet.
• The first row in each sheet contains column headers that represent the interface table columns.
• You can hide columns that you do not intend to use, but you cannot delete columns. Deleting columns will cause the load
• Each column header contains comment about the expected data type and, in some cases, instruction text.
• You must enter data that conforms to what the control file can accept and process for the associated database column.
- Date fields must be entered in YYYY/MM/DD format.
- Amount columns must not contain a thousands separator and must use a period (.) as the decimal separator.
- You can enter only whole numbers in columns that allow whole numbers only.
• Columns have been formatted, where applicable, to match the expected data type to eliminate data entry errors.
• For columns that require internal ID values, refer to the comment for additional guidance about finding these values.

Recommendations for Loading Project Data

Because the details of any data conversion will vary, the scope of this document is limited to a best practices approach. If yo
strategies for populating them.

In general, we recommend the following to generate the export files:

1. Extract the data from the source application in the same format as the open interface described in this template. You can
template; or use SQL, ODI, or a similar tool to extract data directly into .CSV files with the same structures as the .CSV files
2. If you extract the data into a spreadsheet, the spreadsheet must have the same columns as this template and the column
the relevant worksheets provided in this template.

Additional recommendations:
• Set up project templates carefully by analyzing the projects that are being loaded. For example, if many projects use the s
template in the upload data file.
• For performance reasons, keep the source template as simple as possible with minimal setup data or use copy controls to
any other child objects, consider loading such projects separately in multiple iterations.

Importing the Loaded Data

After you successfully load your data, you must submit the Import Projects process to import the data into the application t
transaction controls associated with that project are also imported. After the import process is complete, all processed reco

To submit the Import Projects process:

1. Navigate to the Scheduled Processes page.
2. Click Schedule New Process.
3. Search for the Import Projects process.
4. Submit the process.
5. Monitor the process in the Scheduled Process section of the work area.
6. If the Import Projects process ends in error or warning, review the output report for details about the rows that caused t

To correct import errors:

1. The Output section of the Import Projects process contains the output reports. There are two output reports that the use
report (in EXCEL format).
2. Review the projects and associated child objects that resulted in errors in the Import Projects Rejections report. This repo
message for each failed row. The rejections report does not contain the Options sheet. It is not recommended to use the re
data.
Note:
a. As the Import Projects Rejections report is in XLS format, it has a limitation of containing only 65535 rows in a single work
Projects Rejections report won't be generated. In such a case, review the projects and associated child objects that resulted
b. Due to the row limitation of 65530 and performance reasons mentioned in the Recommendations for Loading Project Da
more than 65530 records each.

3. Correct the errors in the Import Projects Rejections report and generate the CSV files again. If the Import Projects Rejecti
template and generate the CSV files. Make sure you enter only the records you want to re-upload in the original Import Pro
4. Submit the Load Interface File for Import process to upload the CSV files into the open interface tables.
5. Submit the Import Projects process again to process the revised data.
6. Repeat the submit and error correction steps in this section until all rows are imported successfully.
 Oracle Project Portfolio Management Cloud
Project Interface Version 2

ex

Data

mat
for Loading Project Data
ed Data

to import projects (both for planning only as well as the ones enabled for financial management) and associated child entities such as task
ource assignments, task dependencies, team member progress, project codes, and task codes from any external source to Oracle Fusion P
e the comma separated values (.CSV) files that you can use to upload projects, tasks, resources and related information to the open interf
es and all exceptions are printed in the process output report.

eet to first select the features you want to implement for your project before you enter data in this spreadsheet and generate the CSV file
n available on the spreadsheet.

ted values (.CSV) files generated from this template will have different column order than the column order in this template. Do not chang
ow the order specified in the control file. You must enter the project name on every sheet. Any row without a value in the project name co
wing when you prepare the project data:
ds are required:

cify the project template, the project will only be available in the Project Management work area. If you need to perform financial manage
ent from the Project Financial Management work area.
only projects, you need to specify the Project Manager in the Projects sheet.
ct for financial management, you must set up a project template first. This template allows you to copy values such as team members, atta
ecify the values you want to copy from the template in the columns on the Projects sheet. The following values are always copied from th
rs, and partners.
meanings instead of the lookup codes wherever it's not explicitly mentioned to enter code.
fields use a table value set, enter the value for the value set instead of the value set ID.

wing when you prepare the task data:

the imported tasks and the projects to which the tasks belong in the same spreadsheet.
ds are required:

te a project that is enabled for financial management with a Project Plan Type before you can add tasks to the project. Note that this is no
sks before subtasks to ensure the task structure is correct.
s determined by the sequence of the tasks in the spreadsheet. Ensure the tasks sequence reflects the task structure.
Project Financial Management inherit the setup options from the Project Plan Type associated with the project. The tasks also inherit the P

to prepare the comma separated values (.CSV) file that uploads tasks to the tasks open interface table.
annot have a parent task that is not enabled for financial transactions.
nores the tasks available in the Tasks sheet if the Copy Tasks from Template column has the value Y.
oject Plan Baseline is created only if there is at least one task with baseline information. In the baseline plan, create only those subtasks for
n is provided for the task or for one of its subtasks in the hierarchy below it.

ls
wing when you prepare the transaction controls data:
the projects and the transaction controls assigned to those projects in the same spreadsheet.
ds are required:
ntrol Reference

e optional. If you don't provide a value, the default value specified in the column header comments is used.

bers
wing when you prepare the team members data:
the projects and the team members assigned to those projects in the same spreadsheet.
ds are required:

Number or Team Member Name or Team Member Email

e optional. If you don't provide a value, the default value specified in the column header comments is used.
ort internal team members. You cannot import customer, partner, or supplier contacts.
re adding as a team member must already be defined either as a project enterprise resource or as a valid person in Oracle Fusion HCM wit
are added in the Planned status in Manage Project Resources.

ns
wing when you prepare the project classifications data:
the classifications and the projects to which the classifications are assigned in the same spreadsheet.
ds are required:

e optional. If you don't provide a value, the default value specified in the column header comments is used.

sources
wing when you prepare the Project Expense Resources data:
the nonlabor resources and the projects the resources are assigned to in the same spreadsheet.
ds are required:

e
rce Amount
t be available if you do not select Yes for Project Execution Management in Options sheet.

wing when you prepare the Task Resource assignment data for the Project Plan:
the task resources and the projects to which the tasks belong in the same spreadsheet.
ds are required:

e for Expense resources and Resource Name or Resource Email for Labor resources
e optional. If you don't provide a value, the default value specified in the column header comments is used.
t be available if you do not select Yes for Project Execution Management in Options sheet.
wing when you prepare the Task Dependencies data for the project plan:
s to which the dependencies are assigned must be included in the same spreadsheet.
ds are required:

sk Number
n have dependencies on other subtasks. There cannot be more than one dependency between any two tasks.
de of a task is set to Auto if you add at least one predecessor for that task. This ignores the value specified for the task in the Tasks sheet.
e optional. If you don't provide a value, the default value specified in the column header comments is used.
t be available if you do not select Yes for Project Execution Management in Options sheet.

gress
wing when you prepare the Team Member Progress data for the Tasks in the Project Plan:
the tasks and the task resource assignments to which the Team Member Progress is reported in the same spreadsheet.
ds are required:

e optional. If you don't provide a value, the default value specified in the column header comments is used.
tus is calculated based on the Task Percent Complete. If the Percent Complete is zero or unspecified, progress status is marked as Not Star
ess.
ple resource assigned to a task, provide cumulative progress for all the team members for the task.
t be available if you do not select Yes for Project Execution Management in Options sheet.

wing when you prepare the Project Codes data:

the codes are assigned must be included in the same spreadsheet.
e value is not set in the Manage Enterprise Project Codes setup page, then the user entered values will be ignored by the import process.
ds are required:

e optional.
t be available if you do not select Yes for Project Execution Management and for Project Codes in Options sheet .

wing when you prepare the Task Codes data:

the tasks to which you are assigning the task codes in the same spreadsheet.
alue is not set in the Manage Enterprise Task Codes setup page, then the user entered values will be ignored by the import process.
ds are required:

e optional.
t be visible if you do not select Yes for Project Execution Management and Task Codes in Options sheet.

ble Data
for the interface tables using the corresponding worksheets in this template. See the section Excel Template Format for details about this
ment on each column header either for detailed instructions on preparing the data in that column, or for a description of the data and dat
preparing the data in the worksheet, click the Generate CSV File button to generate a ZIP file containing one or more CSV files.
sing the Load Interface File for Import process.
e Scheduled Processes page.
dule New Process button.
d Interface File for Import process.
Projects as the import process. Select the data file to upload. You can upload either the CSV file or the zip file. Click Submit.
e process completes successfully.
rrect the data in this template, regenerate the CSV file and the zip file that contains the CSV file, and resubmit the Load Interface File for Im
ors:
the CSV file fails for a row, the Load Interface File for Import process completes in error and the Load File to Interface child process compl
are loaded from the CSV file into the interface table are deleted, even the rows that loaded successfully. This lets you edit the problematic
without having to separate the successful rows from the rows that need correction.
g and output files of the Load File to Interface child process for information about the data that caused the failure.
ata in this template.
1 and 2 of this section, generate the CSV file, and load the data using the Load Interface File for Import process.
ove steps until all data is loaded successfully.

loading the data in the CSV files into the interface tables, see the File-Based Data Import for Oracle PPM Cloud guide.
ce tables, see the topic Import Projects in the File-Based Data Import for Oracle PPM Cloud guide.

ate CSV File

ormat
ble is represented as a separate Excel sheet.
ach sheet contains column headers that represent the interface table columns.
umns that you do not intend to use, but you cannot delete columns. Deleting columns will cause the load process to fail.
der contains comment about the expected data type and, in some cases, instruction text.
data that conforms to what the control file can accept and process for the associated database column.
be entered in YYYY/MM/DD format.
s must not contain a thousands separator and must use a period (.) as the decimal separator.
nly whole numbers in columns that allow whole numbers only.
een formatted, where applicable, to match the expected data type to eliminate data entry errors.
require internal ID values, refer to the comment for additional guidance about finding these values.

ns for Loading Project Data

 of any data conversion will vary, the scope of this document is limited to a best practices approach. If you are new to data conversion, we
lating them.

mmend the following to generate the export files:

from the source application in the same format as the open interface described in this template. You can build the export files in one of tw
QL, ODI, or a similar tool to extract data directly into .CSV files with the same structures as the .CSV files generated by this template (as de
e data into a spreadsheet, the spreadsheet must have the same columns as this template and the columns must be in the same order. Afte
heets provided in this template.

endations:
mplates carefully by analyzing the projects that are being loaded. For example, if many projects use the same project manager then you ca
oad data file.
reasons, keep the source template as simple as possible with minimal setup data or use copy controls to avoid copying unnecessary data f
ects, consider loading such projects separately in multiple iterations.

aded Data
lly load your data, you must submit the Import Projects process to import the data into the application tables and to create projects along
s associated with that project are also imported. After the import process is complete, all processed records are purged from the open int

ort Projects process:

Scheduled Processes page.
ew Process.
mport Projects process.
ess.
cess in the Scheduled Process section of the work area.
jects process ends in error or warning, review the output report for details about the rows that caused the failure.

rrors:
on of the Import Projects process contains the output reports. There are two output reports that the user may see in the Output section -
rmat).
cts and associated child objects that resulted in errors in the Import Projects Rejections report. This report contains only the worksheets f
ailed row. The rejections report does not contain the Options sheet. It is not recommended to use the rejections sheet for loading any new

ojects Rejections report is in XLS format, it has a limitation of containing only 65535 rows in a single worksheet. So, if there are more than
report won't be generated. In such a case, review the projects and associated child objects that resulted in errors in the Import Projects R
mitation of 65530 and performance reasons mentioned in the Recommendations for Loading Project Data section, it is recommended to b
ecords each.

s in the Import Projects Rejections report and generate the CSV files again. If the Import Projects Rejections report is not generated due to
rate the CSV files. Make sure you enter only the records you want to re-upload in the original Import Projects template .
Interface File for Import process to upload the CSV files into the open interface tables.
rt Projects process again to process the revised data.
mit and error correction steps in this section until all rows are imported successfully.
 Summary

Projects Accepted 0
Tasks Accepted 0
Transaction Controls Accepted 0
Project Team Members Accepted 0
Project Classifications Accepted 0
Tasks Dependencies Accepted 0
Task Resources Accepted 0
Project Non-labor Resources Accepted 0
Team Member Progress Accepted 0
Project Codes Accepted 0
Task Codes Accepted 0
Summary

Projects Rejected 1
Tasks Rejected 0
Transaction Controls Rejected 0
Project Team Members Rejected 0
Project Classifications Rejected 1
Task Dependencies Rejected 0
Task Resources Rejected 0
Project Non-labor Resources Rejected 0
Team Member Progress Rejected 0
Project Codes Rejected 0
Task Codes Rejected 0
Projects
* Required

Error Message
JBO-FND:::FND_VS_VAL_REQUIRED: Total *Project Name Project Number
Project Budget is a required field. 4th Annual Nat Neuro Review
 Source Application Source Project
Source Template Number Code Reference Project Calendar
T, Inova Non-Capital LAWSON 420014
EPS View-Only Project Plan Access Schedule Type
Element Code Code Organization
Legal Entity Project Description Project Manager Number
Inova Health Care Service4th Annual National Neuroscience Review , ,
Project Manager Name Project Manager Email Project Start Date
[email protected] 2020/03/09
 Project Plan Baseline Project Plan Baseline
Project Finish Date Closed Date Name Description
Project Plan
Baseline Date Project Status Priority Code Outline Display Level
Active
 Limit to Transaction
Planning Project Service Type Code Work Type Controls
Enable Budgetary Project Project Currency
Controls Currency Conversion Rate Type
N USD
Project Currency Conversion Project Currency Allow Capitalized
Date Type Code Conversion Date Interest
Capitalized Interest Capitalized Interest Asset Cost Allocation Capital Event Processing
Rate Schedule Stop Date Method Code Method Code
Allow Charges from All Process Cross-Charge Labor Transfer Price
Provider Business Units Transactions for Labor Schedule
Labor Transfer Price Process Cross-Charge Nonlabor Transfer Nonlabor Transfer
Fixed Date Transactions for Nonlabor Price Schedule Price Fixed Date
 Burden Schedule KPI Notifications KPI Notifications Enabled
Burden Schedule Fixed Date Enabled for Project Manager
Include Notes in KPI Copy Team Members Copy Classifications Copy Attachments
Notifications from Template from Template from Template
Copy Descriptive Flexfields Copy Project Space Copy Tasks from
from Template from Template Template
Y
Copy Task Attachments Copy Task Descriptive Copy Task Assignments
from Template Flexfields from Template from Template
Copy Transaction Controls Copy Assets from Copy Asset Assignments
from Template Template from Template
Copy Costing Overrides Opportunity Customer
from Template Opportunity ID Opportunity Number Number
Opportunity Customer Opportunity Win
ID Opportunity Amount Opportunity Currency Code Confidence Percent
 Opportunity Opportunity Customer Opportunity
Opportunity Name Description Name Status Attribute Category
Attribute1 Attribute2 Attribute3 Attribute4
Attribute5 Attribute6 Attribute7 Attribute8
Attribute9 Attribute10 Attribute11 Attribute12
Attribute13 Attribute14 Attribute15 Attribute16
Attribute17 Attribute18 Attribute19 Attribute20
Attribute21 Attribute22 Attribute23 Attribute24
Attribute25 Attribute26 Attribute27 Attribute28
Attribute29 Attribute30 Attribute31 Attribute32
Attribute33 Attribute34 Attribute35 Attribute36
Attribute37 Attribute38 Attribute39 Attribute40
Attribute41 Attribute42 Attribute43 Attribute44
Attribute45 Attribute46 Attribute47 Attribute48
Attribute49 Attribute50 Attribute1_Number Attribute2_Number
Attribute3_Number Attribute4_Number Attribute5_Number Attribute6_Number
Attribute7_Number Attribute8_Number Attribute9_Number Attribute10_Number
Attribute11_Number Attribute12_Number Attribute13_Number Attribute14_Number
Attribute15_Number Attribute1_Date Attribute2_Date Attribute3_Date
Attribute4_Date Attribute5_Date Attribute6_Date Attribute7_Date
Attribute8_Date Attribute9_Date Attribute10_Date Attribute11_Date
Attribute12_Date Attribute13_Date Attribute14_Date Attribute15_Date
Project Tasks
* Required

Error Message *Project Name *Task Name

 Source Task Financial
*Task Number Reference Task Task Description
Parent Task Planned Start Planned End Planned Effort in Duration in
Number Date Date Hours Days
Milestone Critical Chargeable Billable Capitalizable
Limit to Transaction Service Type Allow Cross Charge
Controls Code Work Type Task Manager Flag
Cross Charge Process Cross Charge Process Receive Project
Labor Flag Non Labor Flag Invoice Flag Organization
Requirement Project Plan
Code Sprint Priority Schedule Mode Baseline Start Date
Project Plan Baseline Project Plan Baseline Project Plan Baseline Project Plan Baseline
Finish Date Effort in Hours Duration Allocation
Project Plan Baseline Project Plan Baseline Project Plan Baseline
Labor Cost Amount Labor Bill Amount Expense Cost Amount
Constraint Type Code Constraint Date Attribute Category Attribute1
Attribute2 Attribute3 Attribute4 Attribute5
Attribute6 Attribute7 Attribute8 Attribute9
Attribute10 Attribute11 Attribute12 Attribute13
Attribute14 Attribute15 Attribute16 Attribute17
Attribute18 Attribute19 Attribute20 Attribute21
Attribute22 Attribute23 Attribute24 Attribute25
Attribute26 Attribute27 Attribute28 Attribute29
Attribute30 Attribute31 Attribute32 Attribute33
Attribute34 Attribute35 Attribute36 Attribute37
Attribute38 Attribute39 Attribute40 Attribute41
Attribute42 Attribute43 Attribute44 Attribute45
Attribute46 Attribute47 Attribute48 Attribute49
Attribute50 Attribute1_Number Attribute2_Number Attribute3_Number
Attribute4_Number Attribute5_Number Attribute6_Number Attribute7_Number
Attribute8_Number Attribute9_Number Attribute10_Number Attribute11_Number
Attribute12_Number Attribute13_Number Attribute14_Number Attribute15_Number
Attribute1_Date Attribute2_Date Attribute3_Date Attribute4_Date
Attribute5_Date Attribute6_Date Attribute7_Date Attribute8_Date
Attribute9_Date Attribute10_Date Attribute11_Date Attribute12_Date
Attribute13_Date Attribute14_Date Attribute15_Date
Project and Task Transaction Controls
* Required

*Transaction Control
Error Message Reference *Project Name
 *Expenditure
Task Number Task Name Category *Expenditure Type
Nonlabor Resource Person Number Person Name Person Email
Person Type Job *Organization Chargeable
Billable Capitalizable Start Date End Date
Project Team Members
* Required

Team Member
Error Message *Project Name Number
Team Member Name Team Member Email *Project Role Start Date
End Date Percent Allocation Effort in Hours Cost Rate Bill Rate Track Time
Project Classifications
* Required
Error Message *Project Name *Class Category
4th Annual Nat Neuro Re Requesting Organization
*Class Code Code Percentage
Corporate Services: Other
Project Non-Labor Resources
* Required
Error Message *Project Name *Resource Name
*Expense Planned Amount
Task Resources
* Required

Error Message *Project Name Task Name

 *Resource Resource
*Task Number Type Name Resource Email
 Labor Resource Expense
Allocation Expense Resource Resource Actual Expense Resource
Primary Resource Percent Planned Amount Amount Remaining Amount
Task Dependencies
* Required
Task
Error Message *Project Name Name
 Predecessor Task *Predecessor Task Dependency
*Task Number Name Number Type Lag
Team Member Progress
* Required

Error Message *Project Name Task Name

 Actual Start Actual Finish Actual Effort in Remaining Effort in
*Task Number Date Date Hours Hours
 Physical
Percent Percent
Complete Complete
Project Codes
* Required
Project Attribute Value Set
Error Message *Project Name 01
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
02 03 04
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
05 06 07
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
08 09 10
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
11 12 13
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
14 15 16
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
17 18 19
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
20 21 22
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
23 24 25
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
26 27 28
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
29 30 31
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
32 33 34
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
35 36 37
Project Attribute Value Set Project Attribute Value Set Project Attribute Value Set
38 39 40
Project Numeric Attribute Project Numeric Attribute Project Numeric Attribute
01 02 03
Project Numeric Attribute Project Numeric Attribute Project Numeric Attribute
04 05 06
Project Numeric Attribute Project Numeric Attribute Project Numeric Attribute
07 08 09
Project Numeric Attribute Project Text Attribute Project Text Attribute Project Text Attribute
10 01 02 03
Project Text Attribute Project Text Attribute Project Text Attribute Project Text Attribute
04 05 06 07
Project Text Attribute Project Text Project Text Attribute Project Text Attribute
08 Attribute 09 10 11
Project Text Attribute Project Text Attribute Project Text Attribute Project Text Attribute
12 13 14 15
Project Text Attribute Project Text Attribute Project Text Attribute Project Text Attribute
16 17 18 19
Project Text Attribute
20
Task Codes
* Required

Error Message *Project Name Task Name *Task Number

Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
01 02 03
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
04 05 06
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
07 08 09
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
10 11 12
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
13 14 15
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
16 17 18
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
19 20 21
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
22 23 24
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
25 26 27
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
28 29 30
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
31 32 33
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
34 35 36
Task Attribute Value Set Task Attribute Value Set Task Attribute Value Set
37 38 39
Task Attribute Value Set Task Numeric Attribute Task Numeric Attribute Task Numeric Attribute
40 01 02 03
Task Numeric Attribute Task Numeric Attribute Task Numeric Attribute Task Numeric Attribute
04 05 06 07
Task Numeric Attribute Task Numeric Attribute Task Numeric Attribute Task Text Attribute
08 09 10 01
Task Text Attribute Task Text Attribute Task Text Attribute Task Text Attribute
02 03 04 05
Task Text Attribute Task Text Attribute Task Text Attribute Task Text Attribute
06 07 08 09
Task Text Attribute Task Text Attribute Task Text Attribute Task Text Attribute
10 11 12 13
Task Text Attribute Task Text Attribute Task Text Attribute Task Text Attribute
14 15 16 17
Task Text Attribute Task Text Attribute Task Text Attribute
18 19 20