XER, XML & MPP Files
P6 XML vs XER
P6 XML vs XER; when each is used; EPPM vs Professional
Two Oracle exchange formats. Do not confuse P6 XML (Primavera PMXML) with Microsoft Project XML (MSPDI). They are not the same XML.
What the field is
- XER: Oracle proprietary. "Enables you to export data between P6 Professional release 5.0 or more recent versions, for use within P6 Professional." Also used to move projects into EPPM. Native Professional exchange. Can hold multiple projects in one file. Can be scheduled as a job service (Oracle's export table).
- P6 XML: "Enables you to share project and baseline information between P6 Professional or P6 EPPM databases." Industry-standard XML. Multiple projects in one file. Not a job-service export (Oracle's table).
Use XML when you need baselines, stricter security, or a rollback-safe import. Use XER when talking to older Professional workflows or a job-service export.
Export comparison (Oracle Professional table)
| P6 XML | XER | |
|---|---|---|
| Format | Industry-standard | Proprietary |
| Multiple projects | yes | yes |
| Baselines | yes | no |
| Job service export | no | yes |
Import comparison (same table)
| P6 XML | XER | |
|---|---|---|
| Security | Always enforces user security | Superuser can update all data |
| Project access | Exclusive; stops if it cannot | Shared; others can edit mid-import |
| Commit | Rolls back a failed transaction | Can partial-commit |
| Work shifts | Replaces existing | Tries to insert; can corrupt shifts |
| Multiple projects | yes | yes |
| Baselines | yes | no |
What it is not
P6 XML is not MSPDI. A typical project XER does not carry Project Baseline bars the way P6 XML does (Professional comparison table). Do not invent a BASELINE XER table.
Oracle: "P6 and P6 Professional handle the import of XER files slightly differently."
- Professional XER import: only Admin Superuser or Project Superuser. Thinner option set than XML.
- EPPM (P6 web) XER import: any user with the appropriate permissions. Uses the same import-option set as XML.
- EPPM XER import help also describes selecting baselines to import from an XER. That contradicts the Professional comparison table. Write both. For a viewer/converter, do not claim a typical XER carries snapshot bars the way P6 XML does.
- ProjRisks travel in XER into EPPM but are not visible in P6 web. Oracle recommends XML for risk data.
- Activity Owner imports only if that user already exists in the target.
Calculation engines are intended to match. Do not claim a float-formula difference without a citation.
Must not
- Confuse P6 XML with Microsoft Project XML (MSPDI).
- Claim a typical XER carries baseline bars the way P6 XML does (Professional table).
- Collapse EPPM and Professional XER import into one behavior.
- Invent a
BASELINEXER table. - Use XER to move risk data you expect to see in P6 web.