Import Actions

When you import a project from a P6 XML or XER file, Oracle Primavera Cloud gives you the option create a new project, update an existing one, update the selected baselines and scenarios only, or skip importing a project. When importing a P6 XML or XER file containing multiple projects, you can set separate import actions for each project by specifying the import actions in the Import File step of the Import from P6 wizard. You can also specify the import actions and conflict actions for the imported workspace or project data objects in the Configuration step. The conflict actions are the actions the application takes when multiple matches are found for the same object.

Before you begin the import process, you must specify the target workspace into which the projects will be imported.

Note: XER refers to Oracle Primavera Proprietary Exchange Format (XER). It is a proprietary file format used by the P6 EPPM application.

Project Import Actions

Specify the import actions for each project and its baselines and scenarios in the P6 XML or XER file in the Import File step of the Import from P6 wizard.

Current Schedule: Select one of the following actions for each project included in the file:
- Create New Project: The project data is used to create a new project in Primavera Cloud. If the project already exists in the current workspace, the project will be imported into the target workspace with a numeric value appended to its project ID.
- Update Existing Project: The project data is used to update an existing Primavera Cloud project. This option is only available if a project with a matching project ID is found in the current workspace.
- Update Selected Baselines or Scenarios Only: The baselines or scenarios that you select for an existing project are updated in Primavera Cloud. The rest of the project data is ignored and is not imported.
  Note: When you select Do Not Import for a project, the project data is ignored and is not imported into Primavera Cloud. Global calendars assigned to the project will not be imported.
Baseline: For each baseline, specify if you want 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: For each scenario, specify if you want 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.

Data that can be imported from P6 includes objects stored at the Enterprise Data level and the project level. Most Enterprise Data in P6 is stored as workspace-level data in Oracle Primavera Cloud, although some project-specific data may be stored with the project. Workspace-level data is shared among the projects, child workspaces, and other objects in the workspace.

Note: Projects created in Primavera Cloud through P6 XML import have their project currency set to the parent workspace currency by default.

Workspace and Project Data Import Configuration Actions

You can set separate import actions for each workspace and project data type, providing greater control over the data that gets imported. You also have the ability to specify the action that the application takes when an object in the P6 XML or XER file already exists in Oracle Primavera Cloud or when multiple matching objects are found in sibling workspaces. Your import configuration settings can be saved and used the next time you run the import process.

Workspace Data Import Configuration Actions

Data objects in Oracle Primavera Cloud must be unique within each workspace hierarchy branch. During the import process, the application searches up and down the hierarchy of the target workspace to determine whether matching workspace objects already exist in the application. Workspace data import settings specify the action that is taken when a matching object is found in the application. Matching objects found in other workspaces in the hierarchy may need to be assigned or promoted to the target workspace to maintain existing data associations. Changes to an object's owning workspace are detailed in the list of import actions below. Separate import actions can be chosen for each workspace data type. The selected actions apply to all projects being imported from the P6 XML or XER file.

When configuring the workspace data import settings, you can choose from the following import actions:

Insert New: If a matching object is found, the object will be inserted into the target workspace as a unique record by appending a numeric value to the object. If no matching object is found, the object will be created as new.
Update Existing: If a matching object is found in the target workspace, its owning workspace will remain the same and the object will be updated based on the data from the import file. If a matching object is found in a higher-level workspace, its owning workspace will remain the same, but an association will be created with the target workspace. The object will not be updated because objects can only be updated from their owning workspace. If a matching object is found in a lower-level workspace, the application will attempt to promote its owning workspace to the target workspace and create an association with the workspace where the object was found. The promoted object will be updated based on the data from the import file. If no matching object is found, the object will be created as new.
Keep Existing: If a matching object is found at any level, the existing object will be kept and its data will not be updated. If the matching object is found in the target workspace, its owning workspace will remain the same. If the matching object is found in a higher-level workspace, its owning workspace will remain the same, but an association will be created with the target workspace. If the matching object is found in a lower-level workspace, the application will attempt to promote its owning workspace to the target workspace and create an association with the workspace where the object was found. If no matching object is found, the object will be created as new.
Do Not Import: The data type is ignored and is not imported. However, if a matching object is found, it will be kept as existing and any associated data (such as resource assignments) will be imported.
Note: To ensure codes are imported consistently, all workspace code types are imported with the same import action. If you change the import action for one workspace code type, Oracle Primavera Cloud automatically changes the import action for all other code types. This is necessary because workspace codes in Primavera Cloud can be associated with multiple object types, so allowing different actions for different code types may interfere with new and existing codes.

Conflict Actions

When importing a workspace data type using Update Existing or Keep Existing, the application automatically attempts to promote any matching object found in a lower-level workspace and create an association with the workspace where the object was found. Conflicts may occur if multiple matches of the same object are found in sibling workspaces. Promoting one of the matching objects to a common parent workspace will violate the application's hierarchy uniqueness requirements and cannot be done. In these scenarios, you can select alternate actions during import configuration to resolve potential promotion conflicts. A conflict action can be set for each workspace data type:

Insert New: The matching object will be inserted into the target workspace as a unique record by appending a numeric value to the object.
Fail Import: If a promotion fails, the import process will fail immediately and no data will be imported.
Do Not Import: The matching object is ignored and is not promoted or imported.

Separate conflict actions for each data type provide greater control over your imported data. For example, you may want to insert as new any matching calendars found in a lower level, but prevent the insertion of matching resources. You can set resource objects to fail the import, enabling you to manually resolve uniqueness conflicts before running the import again.

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.
All code conflict actions are set to the same option during the import process.

Project Data Import Configuration Actions

You can configure the action that is taken for each project data type imported with a project. The selected actions apply to all projects being imported from the P6 XML or XER file.

When configuring the project data import settings, you can choose from the following import actions:

Update Existing: If a matching object is found in the project, it will be updated based on data from the import file. If no matching object is found, the object will be created as new.
Keep Existing: If a matching object is found in the project, it will be kept and its data will not be updated. If no matching object is found, the object will be created as new.
Do Not Import: The data type is ignored and is not imported. However, if a matching object is found, it will be kept as existing and any associated data will be imported.

For activity, relationship, and resource and role data types, select Remove from Projects to remove an object from the project if the object does not exist in the P6 XML or XER file. This ensures that a project being updated is consistent with the data in the P6 XML or XER file.

Notes:

WBS Name and ID values must be individually unique among all siblings at each hierarchical level. On import, WBS ID values are checked for uniqueness and updated according to the import action selected for WBS data. If a WBS Name conflict occurs, the matching object will be inserted into the WBS hierarchy with a numeric value appended to the WBS Name.Project Baselines that are imported as baselines from P6 XML are imported with baseline categories included, if they have been assigned.

Last Published Tuesday, May 21, 2024