On this page
An XER file is a Primavera P6 exchange format. It carries structured project data, not just a picture of the Gantt chart. A reviewer needs to know which projects, activities, relationships and calendars arrived, what the receiving tool imported and what happened when it recalculated them.
Oracle’s P6 importing and exporting guide documents supported exchange workflows. Match the guidance to the versions and applications involved; successful import alone does not establish identical calculation behavior.
Preserve the received file
Retain the original attachment or download in a controlled location. Record sender, receipt time, transmittal reference, filename, project identity and stated data date. A file hash can help identify the exact bytes later, but it does not prove who created them or whether their contents are accurate.
Perform review work on a copy. Keep names clear enough that a colleague can distinguish the original submission, imported model, recalculated result and any experimental scenario.
Received XER → imported review copy → recalculated comparison → documented findings.
Retain each step’s identity and warnings so a later reviewer can follow the transformation.
Reconcile the import
| Check | Why it matters |
|---|---|
| Project selection | A file can contain more than the project you intend to review |
| Activity identity | Names can repeat; stable source IDs matter for comparisons |
| Relationship endpoints | Missing external activities can change the understood network |
| Calendar assignments | Substitution can move dates without changing durations |
| Dates and status | Confirm the data date and representative actual and remaining dates |
| Import warnings | Unsupported or skipped data needs a visible disposition |
Use sample activities from different parts of the network rather than checking only the first few rows. Include a milestone, a progressed activity, a constrained activity and an activity on a different calendar where those exist.
Compare stored and recalculated results
Suppose a fictional imported equipment activity displays a Friday finish, while a review recalculation produces Monday. Start with its calendar, shifts, predecessor timing, constraints and calculation options. Do not immediately overwrite the Friday result or label the sender wrong.
Record both results and the explanation. If the difference remains unresolved, say so. The report should identify which findings depend on recalculated dates and which come directly from the imported records.
Make the handoff reproducible
Package the source identifier, import configuration, warnings, calculation settings and finding register together. Include a short note on unsupported features. Avoid claiming full P6 parity merely because the file opened or some dates matched.
Read P6 settings and the schedule audit checklist next. Visit the resource library for the broader learning path, or the os.construction Schedule guide for current import and review behavior.
Share this article