Import Project Plan Process

The Import Project Plan process imports project plans from third-party applications in the interface table to Project Management. The process creates project plans based on the data loaded into the open interface table.

You must load the import data to the PJT_PROJECT_PLAN_XFACE interface table and run this process.

Note: You can load data to interface tables using predefined templates and the Load Interface File for Import scheduled process, which are both part of the External Data Integration Services for Oracle Cloud. For more information about file-based data import, see the File-Based Data Import (FBDI) for Project Management guide.

From the navigator, select the Scheduled Processes menu and specify the process name, date and time to run the Import Project Plan process.

The process validates the project plan data and creates project plans in Project Management. The errors and warnings for the invalid project plan data are tracked in a report for the Import Project Plan process. Review the errors and fix the issues. Load the data from CSV file into the interface table again and resubmit the process.

Note: We recommend that you use the Import Projects process to create projects.

Importing Project Plan Process Report

After the Import Project Plan process completes, review the output report to view the successful transactions and the errors and warnings. If errors exist, review and resolve the issues before submitting the process again. If warnings exist, take note of the details, and make corresponding corrections directly in Project Management in the Manage Project Plan page. You can broadly classify the errors into the following types:

  • Basic data validation errors such as some required attribute missing, or invalid values.

  • Data consistency between records, such as task with the same identifier having different names in different records.

  • Data referential issues, such as a specified parent task identifier doesn’t exist.

  • Data integrity issues with the current application data, such as import of a project fails because a project with the same name already exists in the target database.