Importing Projects using Primavera XER Format
You can import projects and baselines using P6 Professional's native Primavera XER format and create or update a project.
Note:
- Avoid using the pipe character ( | ), or brackets ( < or > ) in the Project Name.
- P6 and P6 Professional handle the import of XER files slightly differently.P6The XML import options in P6 have a few extra options when compared to the XML import options in P6 Professional (Document Categories, Document Statuses, Locations, and WP and Docs). However the import options for XER files in P6 Professional allow less configuration than the XML import options. Also, in P6 Professional only users with the Admin Superuser global security profile or Project Superuser project security profile can import projects, whereas any user with the appropriate permissions can import projects in P6.
To import projects using Primavera XER format:
- On the
Navigation Menu, expand
Projects and click EPS. - On the EPS page:
Tip:
- You can manage XER and XML import templates separately from the importing and exporting process using the Manage Import Templates option on the Actions
menu of the EPS page.
- To understand how the import of secure codes is handled, see Secure Codes
- Risks in P6 Professional are stored in the ProjRisk table. ProjRisks are included in the XER file format and are imported from XER files into P6 EPPM, however ProjRisks are not visible in P6. If you need to import and export risk information, Oracle recommends you use XML format.
- You can see the status of the import in the View Service Status dialog box.
- You can import multiple projects as one file using Primavera XER format.
- You can update baseline when you import a project and its baselines from an XER file. When you select the Update Existing import action at the project level, matching baselines you import will be updated from the import file. Baselines you choose to import but which do not have a match in your database against the project you selected to update will be added to the project.
- The Activity Owner field shows the P6 EPPM user who owns the activity. If a Primavera XER file that includes the Activity Owner field is imported into a database, the Activity Owner data is imported only if the user already exists in the database.
- Stored performance data can be imported as long as the start and finish dates of periods match between the import file and the financial period calendar assigned to the project for all financial periods with data stored at the activity or assignment level.
- If the XER file was generated from a version earlier than release 20.4, when it is imported into release 20.4 or later rates for roles will be the same for all effective dates. If an XER file generated from release 20.4 or later is imported into a database with a version of 20.3 or earlier, only the rates which were effective at the time of export will be imported.
- The structure of an XER file doesn't include information about the EPS node the projects were exported from. Therefore it is not possible to import EPS level activity codes as EPS level codes, even if an XER file is being imported back into its origin database. If you export projects with EPS level activity codes to XER, when you import the XER file, the only import options you can choose for EPS Activity Codes and EPS Activity Code Values are Convert to Project or Ignore.