You can import and export between P6 Professional and other applications using the following file formats:
- The Oracle proprietary format (XER) supports all project, resource, and role information developed using the P6 Professional or P6 EPPM suite of project management tools. The Primavera PM XER file format enables you to export data between P6 Professional release 5.0 or more recent versions, for use within P6 Professional. The Contractor XER format is supported to import data from Contractor 4.0 and subsequent versions into PM, as well as export data to Contractor 5.0 or 6.1 and later.
- Primavera's P6 XML format enables you to share project and baseline information between P6 Professional or P6 EPPM databases.
- XLS files enable you to share information with other spreadsheet applications.
- MPX format enables you to share information with Microsoft Project, as well as to integrate with other third-party tools.
- Microsoft Project XML format enables you to share information with Microsoft Project 2007, 2010, and 2013.
- The file format you select when you import or export determines the type of information you can share.
- UN/CEFACT Schema XML files enable you to export information to organizations that require UN/CEFACT format, such as the Defense Contract Management Agency (DMCA).
Differences Between XML and XER Export Formats
The following table compares the features and benefits of both formats for exporting project data. An X represents that a particular format is better suited for that functionality.
Functionality | XML | XER |
---|---|---|
Data formats XER is proprietary. XML is an industry-standard format. | X |
|
Multiple projects XER supports exporting multiple projects at once to a single XER file. XML supports exporting multiple projects at once to a single XML file. | X | X |
Baseline Export XER does not support the export of baselines. XML supports the export of baselines. | X |
|
Job Services XER supports scheduling exports on a regular basis as services. XML does not. |
| X |
Differences Between XML and XER Import Formats
The following table compares the features and benefits of both formats for importing project data. A checkmark represents that a particular format is better suited for that functionality.
Functionality | XML | XER |
---|---|---|
Security XML always enforces individual user security settings, and never violates your security restrictions. If there is a security conflict, the import will try to continue and ignore data that a user should not have access to; if it is not possible to continue while ignoring data, the import is stopped. Security is never bypassed when updating data. XER allows updates to all data if you have the Import Project Management XER and MPX security privilege set. | X |
|
Exclusive Project Access XML always opens a project as exclusive, and will stop the import if it cannot gain exclusive access. This ensures that other users are not changing data during the import process. XER accesses projects as shared, which means other users can update data in the middle of the import process. | X |
|
Committing Data XML will not commit partial data. If an import action for a specific transaction fails before all data is committed, XML rolls back the data; global and project-specific imports are treated as separate transactions. XER can end up with partial commits of data. | X |
|
Work Shift Handling XML replaces any existing work shifts. XER tries to insert work shifts, which can potentially corrupt your shift decisions. | X |
|
Multiple projects XER supports importing multiple projects at once from a single XER file. XML supports importing multiple projects at once from a single XML file. | X | X |
Baseline Import XER does not support the import of baselines. XML supports the import of baselines. | X |
|