Import P6 XML or XER Data into Oracle Primavera Cloud

Importing Projects from P6 - Video

Import P6 data from a P6 XML or XER file into your Oracle Primavera Cloud environment. For each project included in the file, you can specify whether you want to create a new project, update an existing project, update the selected baselines or scenarios of the project, or skip importing the project. For projects you choose to import, you can specify how individual workspace and project object types are imported into the application. When the import is complete, you can view a log file to see the results of the process. Before you import a project, ensure you have the required workspace security privileges to import and add a new project into the workspace and the required project security privilege to edit existing projects.

The P6 XML and XER import process supports a variety of P6 data objects and import actions for transferring your data to Primavera Cloud. Each import action has its own set of rules to describe how your data is impacted during the process. Refer to the P6 XML/XER Import Objects and P6 XML/XER Import Actions topics for detailed information on import objects and actions.

This topic describes the import process and the project import actions in the Import From P6 wizard. The import process includes two main steps:

1. Import File: In this step, choose the file to import and specify the project import actions and import details.
2. Configuration: In this step, for the projects you selected to import, specify how individual workspace and project object types should be imported into the application. You can also specify conflict actions, that is, the actions to take when multiple matches are found in the application for the same kind of data.

Before You Begin

• If you are importing an XER file into Primavera Cloud, ensure the decimal symbol setting for currency values in P6 is set to dot(.) instead of comma(,).
• If you use the Standard Data Exchange Format (SDEF), use the SDEF conversion utility to convert your SDEF files to XER before importing them to Primavera Cloud. To learn how to convert SDEF files to XER, see My Oracle Support article (DOC ID: 902710.1).

To import project data from a P6 XML or XER file:

1. In the object selector, select ﱆ Project, and then select View Projects List.
2. On the Projects page, in the workspace tree, select a destination workspace for the imported project.

   Notes:

   • You must be within the context of the workspace where you want to import the file. Selecting a workspace name in the grid will not change the workspace context.
3. Select Actions , and then select Import from P6.
4. In the Import From P6 wizard, complete the following steps:
   1. In the Import File step, in the Select an XML or XER File field, select a file to import.
   2. (Optional for XER) From the Locale drop-down list, select your preferred locale (language), if the locale setting in Primavera Cloud does not match your browser language setting.

      Selecting the appropriate locale encodes and preserves the content from the XER file while importing it.

      Note: You can upload a valid P6 XML or XER file, or, for faster performance, upload a compressed file containing the P6 XML or XER file. Uploading multiple P6 XML or XER files within a compressed file is not supported. The maximum file size that you can import is 1 GB.

   3. In the Project Import Actions section, specify an Import Action for each project (current schedule) and any baselines and scenarios in the file.
      1. Current Schedule:
         • Import As: Select either Project, Baseline, Scenario, or Do Not Import.
      2. Baseline:
         • Import with Project: Select the check box to indicate whether you want to import the baseline along with the project.
         • Import As: Select either Baseline, Scenario, Project, or Do Not Import.
      3. Scenario:
         • Import with Project: Select the check box to indicate whether you want to import the scenario along with the project.
         • Import As: Select either Baseline, Scenario, Project, or Do Not Import.
   4. In the Import Details panel, depending on your chosen import option for current schedule, specify its import details.
      • Project: Select to create a new project, update an existing one, or update the selected baselines or scenarios only, and then specify the project ID.
      • Baseline: Select to create a new baseline or update an existing one, and then select the project with which the baseline should be imported and specify the baseline name.
      • Scenario: Select to create a new scenario or update an existing one, and then select the project with which the scenario should be imported and specify the scenario name.
      • Do Not Import: The project will not be imported.

        Notes:

        • Because of differences in how data is managed in P6 and Primavera Cloud, you cannot revert changes made to a baseline if that baseline was imported from a P6 XML file.
        • Baseline categories can only be imported using P6 XML. This allows you to migrate projects and project baselines from P6 while retaining any categories that might be assigned, and to make them available to assign to other baselines in the workspace. A baseline must be imported as a baseline for baseline categories to migrate successfully. Users must have the workspace level Import XML privilege to import objects.
5. Select Next.
6. In the Configuration step, complete the following steps:
   1. In the Workspace Data section, specify the following for each item:
      • Import Action: Select an import action for each workspace item.
      • Conflict Action: Select an alternate action to take when multiple matches are found in the application.

        Notes:

        • Because configured fields must be unique across the application for each object type, they do not support promotion or conflict actions. The conflict action is set to Not Applicable for configured fields.
        • Because workspace-level codes can be associated with multiple object types, importing code types with different import actions may interfere with new and existing codes. For example, assume an existing code is associated with both activities and resources. Choosing to insert new activity codes and update existing resource codes may cause unintended changes to the existing code. To prevent these unintended changes, all workspace-level code import actions and conflict actions are synchronized during the import process. This ensures that all codes are imported consistently.
        • Conflict action options are available for workspace data items with an import action of Update Existing or Keep Existing.
   2. In the Project Data section, specify the following for each item:
      • Import Action: Select an import action for each project item.
      • Remove from Projects: Select this option to remove objects in Oracle Primavera Cloud that do not exist in the P6 XML or XER file. This option is available for the activities, relationships, and resources and roles project data items.

        Note: Configuration options of projects do not apply to baselines and scenarios. If baselines or scenarios are selected to be imported, the data is automatically updated during the import.

7. (Optional) Select Save Configuration to retain these settings for future use.
8. Select Finish to start the import process.

   After the import process completes, you can review the import log to view data and statistics about the process, as well as any errors encountered that need to be resolved. You can access the import log from the system notification you receive when the process is complete or from the Manage Services page.

9. Reschedule the project and recalculate costs before making any project updates.