XER, XML & MPP Files

File > Export Starts the Export Wizard; It

Export is File > Export the Export wizard; not Send Project, File > Import, Job Services Export, or Check Out

P6 EPS / Projects tree. Enterprise nodes hold projects such as EC00515.
File, Export writes the project. It is not Export a Tracking layout.

What a planner means

Export is File > Export. Oracle File Menu: "Starts the Export wizard. Use the Export wizard to export projects, resources, or roles to other Oracle applications, Microsoft Project, or Microsoft Excel. You can also export projects in UN/CEFACT, IPMDAR, and CPP format." Enabled when the active window is "All." Corresponding toolbar: Action Toolbar. How-tos: File, Export.

This command is not File > Import (the Import wizard). See File > Import Starts the Import Wizard; It. It is not File > Send Project (creates an XER and emails it). See Send Project Creates an XER and Emails It; It. It is not Tools > Job Services Export (XER only; no format picker). See Job Services. It is not File > Check Out / Check In. See Check Out. It is not File > Exchange Data. It is not File > Send to Unifier. It is not the command-line "export or import projects as a service" path. It is not the XER field catalog. See XER Tables That Matter for a Viewer or Converter and P6 XML vs XER.

Action Toolbar Export row: "Starts the Export wizard. Use the Export wizard to export projects, resources, or roles to other Oracle applications, Microsoft Project, or Microsoft Excel." Menu command File > Export. That toolbar sentence does not reprint UN/CEFACT, IPMDAR, or CPP. File Menu does. Quote both. Do not collapse them. The Action toolbar is "not displayed" by default. "The import, export, check in, and check out icons on this toolbar display by default when you choose to show the toolbar." "The icons on this toolbar do not have corresponding shortcut keys."

Hot keys: Alt-F, E = Export. That is the File-menu hot key. Quote both the toolbar "no corresponding shortcut keys" sentence and Alt-F, E. Do not collapse them.

File > Import is a different command. Oracle File Menu: Import "Starts the Import wizard." Oracle did not print UN/CEFACT, IPMDAR, or CPP on the Import wizard format table. File Menu already printed those three on Export, not Import. See File > Import Starts the Import Wizard; It.

Send Project is a different command. File > Export XER how-to tip: "You can also export a project to an XER file and automatically email the file to another P6 Professional user. Choose File, Send Project." Send Project does not start this wizard. See Send Project Creates an XER and Emails It; It.

Job Services Export is a different path. File > Export XER tip: "When connected to a P6 Professional database: You can set up a job service to export your projects at a specified time." "You can export or import projects as a service through the command line." Those are not File > Export. See Job Services.

Check Out is a different command. File > Check Out starts the Check Out wizard (remote lock-and-copy). Export does not check the project out. See Check Out.

Professional wizard fields Oracle names

Oracle Exporting information using a wizard table (quote Oracle file-format and information-type names; do not invent others):

File FormatInformation TypePurpose (Oracle)
Primavera PM XERProjectExport complete project information to other P6 Professional 5.0 and later users
Primavera PM XERResource OnlyExport complete resource information to other P6 Professional 5.0 and later users
Primavera PM XERRole OnlyExport complete role information to other P6 Professional 5.0 and later users
Primavera P6 XMLProjectExport project and baseline information to other P6 Professional or P6 EPPM users.
Primavera Contractor XERProjectExport complete project information to Oracle Primavera Contractor 5.0 or 6.1
Primavera Contractor XERResource OnlyExport complete resource information to Oracle Primavera Contractor 5.0 or 6.1
Microsoft Project XMLProject and ResourceExport project information to Microsoft Project or other third-party applications
Microsoft Project MPXResource OnlyExport resource information for all resources to Microsoft Project or other third-party applications
Microsoft Project MPXProjectExport project information to Microsoft Project
XLSXActivitiesExport activity information to Microsoft Excel
XLSXActivity RelationshipsExport activity relationships, such as predecessor and successor IDs, to Microsoft Excel
XLSXExpensesExport activity expense information, such as expense item and activity ID, to Microsoft Excel
XLSXResourcesExport resource information to Microsoft Excel
XLSXResource AssignmentsExport resource assignment information to Microsoft Excel
UN/CEFACT XMLProjectExport project information in the Integrated Master Schedule (IMS) schema
IPMDARProject and Resource AssignmentsExport project and resource assignment information to a collection of JSON files.
CPPProjects and Resource AssignmentsExport project, calendar, and resource assignment information to a collection of JSON files.

Wizard-summary notes Oracle printed (quote Oracle): "MPX/Microsoft Project XML/ XLSX formats do not support your complete set of project information." The same page also prints two "For information about the tables and fields that are converted, see the … Import/Export Data Map Guides" sentences (EPPM database vs Professional database). Do not invent other format tokens on that table.

The current Export wizard table does not name P3, Primavera Project Planner, or MPP. Do not invent those as wizard formats. Oracle Importing and exporting projects names on-premises P3 to XER (P330XERConvert.exe) / XER to P3 (XERP330Convert.exe) utilities. Those are not this wizard.

Oracle Import/Export file formats (same guide; quote Oracle):

  • XER — "The Oracle proprietary format (XER) supports all project, resource, and role information." "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 P6 XML — "enables you to share project and baseline information between P6 Professional or P6 EPPM databases."
  • XLSX — "enable you to share information with other spreadsheet applications."
  • MPX — "enables you to share information with Microsoft Project, as well as to integrate with other third-party tools."
  • Microsoft Project XML — "enables you to share information with Microsoft Project 2007, 2010, and 2013."
  • UN/CEFACT — "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)."
  • IPMDAR — "IPMDAR files enable you to export information to organizations that require IPMDAR format."
  • CPP — "CPP files enable you to export information to organizations that require CPP format."

Oracle XML vs XER export comparison (same page; quote Oracle):

FunctionalityXMLXER
Data formats"XML is an industry-standard format.""XER is proprietary."
Multiple projects"XML supports exporting multiple projects at once to a single XML file.""XER supports exporting multiple projects at once to a single XER file."
Baseline Export"XML supports the export of baselines.""XER does not support the export of baselines."
Job Services"XML does not.""XER supports scheduling exports on a regular basis as services."

That Job Services row is Tools > Job Services, not this wizard. See Job Services and P6 XML vs XER.

Export fields Oracle names (quote per format)

Oracle did not print one field list for every format. Quote the list on the how-to that names it. Do not copy XML Baselines to Export / Export all project level layouts onto XER. Do not copy XER version pull-down onto XML. Do not copy UN/CEFACT / IPMDAR "one project at a time" onto XER or XML.

Primavera PM - (XER) → Project — File, Export → Primavera PM - (XER) → "Select the appropriate version from the pull-down menu" → Project → "Mark the Export checkbox for all projects you want to export" → "Type the name of the export file and the location where the file will be saved" → Finish.

Notes Oracle printed on that how-to (quote Oracle; do not invent others):

  • "If you want to make backup copies of a project, export the project as an XER file (the Oracle proprietary format) then store the export file."
  • "When connected to a P6 Professional database: You can set up a job service to export your projects at a specified time."
  • "You can export or import projects as a service through the command line."
  • "If you export multiple projects in a single XER file, the interproject relationships between activities in the projects are preserved."
  • "You can also export a project to an XER file and automatically email the file to another P6 Professional user. Choose File, Send Project."
  • "When you export a project containing financial period performance data, only financial periods containing values for that project are exported. The module will not export all financial periods in the Financial Period dictionary."
  • External-relationship note: if the project was previously imported, contains relationships to external projects that do not exist in the database, and you scheduled it, "be sure that you scheduled the project with the Ignore Relationships To and From Other Projects option selected (in the Schedule Options dialog box)." "If you select this option when scheduling the project, the module will preserve the external activity dates."
  • "When connected to a P6 EPPM database: No risk data is exported when using XER format. Risk Categories are part of global data and are exported when using XER format."

XER Resource Only / Role Only do not reprint the project Export-checkbox list. Resource Only: Primavera PM - (XER) → version → Resource Only → name and location → Finish. Role Only: Primavera PM - (XER) → version → Role Only → name and location → Finish. Oracle printed no Baselines to Export, layouts, or multi-project checkbox on those two how-tos.

Primavera Contractor - (XER) — wizard table names Project and Resource Only. Resource how-to fields Oracle named: File, Export → Primavera Contractor - (XER) → version pull-down → Resource Only → name and location → Finish. Note Oracle printed: "While both P6 Professional and Oracle Primavera Contractor 5.0 or 6.1 or later can import and export XER files, the formats of the XER files are different. Therefore, when exporting resources for use with Oracle Primavera Contractor 5.0 or 6.1 or later, you must select the Primavera Contractor - (XER) option instead of the Primavera PM - (XER) option." "You cannot import an XER file to an earlier version of Oracle Primavera Contractor than 5.0." Do not invent a Contractor Project field list Oracle did not print on a fetched how-to.

Primavera P6 - (XML) — File, Export → Primavera P6 - (XML). Fields Oracle named:

  • Baselines to Export — "Double click the Baselines to Export field." "In the Baselines to Export dialog box, mark the Export checkbox next to each baseline you want to export."
  • "Export XML file to a compressed file" — "if you want to export the XML file to a zip. If you select to export project layouts, these files will also be included in the zip."
  • "Export all project level layouts" — "Clear the option … if you do not need to include project level layouts with the export file."

Notes Oracle printed on that how-to (quote Oracle): "When connected to a P6 EPPM database, your administrator must enter the URL of the content repository into the P6 URL field on the General page of Application Settings in P6." "You can export multiple projects to a single XML file." "Global data that is assigned to the project is exported." Same Ignore Relationships / external-dates sentence as XER. "Manual future period buckets are exported when you export a project to an XML file." "XML files exported from PM version 7.0 and later can not be imported into PM version 6.1 and earlier." "You can export XML files without having access to all resources, but … If you export projects with resources that are outside of your access hierarchy, data that is exported will be limited since not all resources in the project can be loaded from the dictionary."

Microsoft Project — File, Export → Microsoft Project → "From the pull-down menu, select the type of file to which you want to export." Fields Oracle named:

  • Export checkbox — "Mark the Export checkbox of all projects you want to export."
  • Export File Name — "Double click in the Export File Name field if you want to change the name and location of the Microsoft Project file."
  • template — "Add a new template or modify the existing template (if necessary). The template contains options for exchanging data with Microsoft Project."

Notes Oracle printed on that how-to (quote Oracle): "If you are transferring data in XML format, you must map Cost-type custom fields in MSP to Cost-type UDFs in P6 Professional. Likewise, you must map Number-type custom fields in MSP to Number-type UDFs in P6 Professional." "If there is a mismatch in the custom mappings you define, you will receive an error during import or export." "To export manual future period values, you require Microsoft Project 2002 or a more recent version." "If you plan to exchange project data containing manual future period assignment values with Microsoft Project, you will achieve the most accurate conversion results using Microsoft Project 2003 or later." "The MPX file format does not support resource curves." "When you export project data, secure codes and secure code assignments related to the project are not exported." "P6 Professional does not export past period actual data to Microsoft Project."

Microsoft Project → Resource Only (MPX) — File, Export → Microsoft Project → MPX → Resource Only → name and location → template → Finish. Oracle titled that how-to "supported for MPX format." Do not invent an XML Resource Only path on that page.

Spreadsheet - (XLSX) — File, Export → Spreadsheet - (XLSX). Fields Oracle named: subject area(s); project checkbox ("If exporting resources only, you will skip this step in the wizard."); template ("specifies the fields you want to export"; "You can create a filter to export only a portion of the activities in the project"; columns / filter / sort per subject area; default template if you do not add a new one); name and location ("If you have selected more than one subject area to export, each subject area will appear in a separate worksheet in the same spreadsheet file.").

Notes Oracle printed on that how-to (quote Oracle): "You can right-click in the Activity Table in the Activities window and select Export to Excel to instantly export activity data for the open project." That right-click path is not this wizard. Dedicated page: "P6 Professional will export the columns displayed in the Activity Table for the open project." "You must choose File, Export to export multiple projects to Microsoft Excel." "You can export baseline fields to Microsoft Excel." Further XLSX-wizard notes: Sub-unit checkbox in User Preferences Time Units must be cleared; first-row field names "Do not edit"; required fields cannot be removed from the template; "If you change the sheet name in the export file, you will not be able to import its data into P6 Professional."; "You can export financial period (past period actual) data to an XLSX file; however, past period actual data is ignored when you import an XLSX file to P6 Professional."; lowest-level cost-account name on Resource Assignments.

Sheet names Oracle printed (do not invent others): Activities = TASK; Activity Relationships = TASKPRED; Expenses = PROJCOST; Resources = RSRC; Resource Assignments = TASKRSRC. "You should not modify the sheet names. To import successfully, P6 Professional must recognize the sheet names."

UN/CEFACT (XML) — File, Export → UN/CEFACT (XML). Fields Oracle named: "Verify that the currently opened project is listed"; "Add a new template or select an existing template"; name and location. Tips Oracle printed: "You can only export one project at a time." "Export templates are only available when connected to a P6 EPPM database." Do not copy that EPPM-templates sentence onto XER, XML, or MSP.

IPMDAR — "Schedule and summarize the project you want to export." File, Export → IPMDAR. Fields Oracle named: "Verify that the currently opened project is listed"; "Add a new template or select an existing template"; name and location. Tips Oracle printed: "You can only export one project at a time." "The IPMDAR export generates a collection of JSON files which constitute the IPMDAR data."

CPP Format — "The projects you want to export must be scheduled and summarized." File, Export → CPP Format. Fields Oracle named: Baselines to Export; Select Baseline dialog ("choose Project Baselines or All Projects, select the baseline or project to assign as the baseline and click Assign"); Validate ("view the validation report"); template. Opening sentence: "export project to a .zip file containing the multiple JSON files that constitute the CPP data." Note Oracle printed: "After the export job has been processed, choose Tools, Job Status to download the project files from the Job Status dialog box." That Job Status sentence is on the CPP how-to. Do not invent that every File > Export format uses Job Status. See Job Services.

Privileges Oracle names on these pages

Quote the pages. Do not invent a single "Export" privilege.

  • Export Project Data — Oracle Importing and exporting projects: "You must have the 'Export Project Data' project privilege to export projects." Oracle EPPM About Importing and Exporting Projects reprints Export Project Data. Professional Project Privilege Definitions (page fetched) does not reprint that name. Quote both. Do not pick a winner.
  • Add/Edit/Delete Microsoft and Primavera Templates — "templates that are used to import and export data to and from Microsoft Excel, Microsoft Project, Primavera XML, and Primavera XER formats."
  • Administer Job Services — "set up the Apply Actuals, Batch Reports, Export, Schedule, and Summarize services to run at specific time intervals using the Job Service." That is Tools > Job Services, not this wizard.

EPPM — do not copy File > Export onto the web

Do not copy Professional File > Export / Action Toolbar / Alt-F, E / Export wizard format table onto EPPM web.

Oracle EPPM About Importing and Exporting Projects names import/export file formats, export settings, import templates, and project scheduled services. That page does not print File > Export or the Professional Export wizard. EPPM path Oracle printed for XER: Projects → EPS → Actions → Import/Export Projects → Export tab → Export Type Primavera XER. Fields Oracle named there: Template (Manage Templates); Export Type; Project (Select); Export.

EPPM About Importing format list (quote Oracle): CPP; Oracle Primavera XML or XER; Microsoft Project XML; UN/CEFACT; IPMDAR; Excel. That is the EPPM page, not the Professional Export wizard table.

EPPM scheduled import/export is Administration → Scheduled Services, not this command. EPPM Scheduled Services can export XER or XML. Professional Job Services Export is XER only. See Job Services.

XER

Export is a command. When the format is Primavera PM XER, it writes a project XER. It is not an XER table.

Oracle's project XER data map TOC lists no EXPORT, EXPORTWIZARD, EXPWIZ, or EXPORTCFG table. Do not invent one.

The file File > Export writes, when the format is Primavera PM XER, is a normal Primavera PM XER (PROJECT / TASK / …). See XER Tables That Matter for a Viewer or Converter and P6 XML vs XER. This note is the wizard, not a second field catalog.

PROJECT.checkout_flag / checkout_user_id / checkout_date are Check Out status, not proof the planner used File > Export. See Check Out.

A Viewer parse of one project XER cannot reconstruct format, version pull-down, Export checkbox, Baselines to Export, layouts, template, or whether the planner used File > Export, Send Project, Job Services Export, command-line export, or EPPM Import/Export Projects. After it runs you may see an XER (or another format Oracle named) on disk — that is the file, not a stored wizard row.

Microsoft Project

Desktop Project has File > Save As > Browse then the Export Wizard. Microsoft: "The Export Wizard and Import Wizard help you transfer project data between Project and other programs." Formats Microsoft named on that page: Excel (workbook or PivotTable report); text-only (tab delimited); comma-separated values (CSV); Extensible Markup Language (XML). "Choose File > Save As." "In the Save As type box, select the file format that you want to export data to." "Follow the instructions in the Export Wizard." XML note: "You can export only an entire project to XML format. Project maps the data automatically, without the Export Wizard." Applies to Project Online Desktop Client / Project Professional / Project Standard (page fetched).

They are not the same command. P6 File > Export starts the P6 Export wizard (formats Oracle named above). Project File > Save As starts Project's Export Wizard (Excel / text / CSV / XML). Microsoft did not print File > Export as a P6 analog, XER, UN/CEFACT, IPMDAR, or CPP. Do not invent one.

Oracle's Export wizard names Microsoft Project XML and Microsoft Project MPX. Oracle did not name MPP as an Export wizard format. Do not claim P6 File > Export writes a native MPP. Do not claim MPXJ can write a real MPP.

Don't

  • Treat File > Export as File > Import, as Send Project, as Job Services Export, as command-line export-as-a-service, as Check Out / Check In, or as File > Exchange Data / Send to Unifier.
  • Invent an EXPORT / EXPORTWIZARD / EXPWIZ XER table, or treat checkout_flag as "the planner exported this file."
  • Invent P3, MPP, or other tokens as Professional Export wizard formats. Oracle's current wizard table names Primavera PM XER, Primavera P6 XML, Primavera Contractor XER, Microsoft Project XML, Microsoft Project MPX, XLSX, UN/CEFACT XML, IPMDAR, and CPP.
  • Copy XML Baselines to Export / layouts onto XER, or copy XER version pull-down onto XML. Quote the list on the how-to that names it.
  • Invent exporter quirks, column maps, or format behavior Oracle did not print. This note is the wizard, not XER Tables That Matter for a Viewer or Converter.
  • Copy File > Export / Alt-F, E / the Professional format table onto EPPM web, or treat EPPM Import/Export Projects / Scheduled Services as this command.
  • Collapse Professional "XER does not support the export of baselines" with XML Baselines to Export. Quote both.
  • Claim a Viewer reconstructed format, template, or Export checkbox from an XER.
  • Map this command to MSP File > Save As Export Wizard and call them the same.
  • Claim MPXJ writes a real MPP.

Sources

Back to top