Importing Projects using Primavera XML Format

You can import projects and baselines using the Primavera XML format and create or update a project.

Note Avoid using the pipe character ( | ), or brackets ( < or > ) in the Project Name.

To import projects using Primavera XML format:

Click Projects.
On the Projects navigation bar, click EPS.
On the EPS page:
1. Click the Actions menu and select Import/Export Projects.
2. In the Import/ExportProject dialog box, click the Import tab.
3. On the Import tab:
  - In the Import Type list, select Primavera XML.
  - In the File field, click Browse.
4. In the File Upload dialog box, select a file and click Open.
5. On the Import tab:
  - Select a Template to use.
    Note If you need to create a template or modify an existing template, click Manage Templates.
  - Select an option for Import Action.
    If you selected Create New, click Select in the Import To field and select the EPS where you want to import the XML file.
    
    If you selected Update Existing, click Select in the Import To field and select the project where you want to import the XML file.
  - Select which Baselines to import.
    Note If you select to import with update existing and you select to import baselines, matching baselines will be updated with the data from the XML file according to the options in the selected template.
6. Click Import.

Tip

To understand how the import of secure codes is handled, see Secure Codes.
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 XML format.
You can import a Primavera XML file from within a zip file. If the zip file contains multiple XML files, only the file with the same name as the zip will be imported. If the zip contains only one XML file, the name of the zip and XML file need not match.
You can update baselines when you import a project and its baselines from an XML 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 as baselines, but will not be assigned as the project, primary, secondary, or tertiary user baseline.
The Activity Owner field shows the P6 EPPM user who owns the activity. If a Primavera XML 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 XML 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 XML 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.
If the currency stored in the XML file matches a currency in your database, you can select whether to import financial data using the base currency in your database or the currency present in the XML file. If you chose to use the XML rate, financial data is converted as follows:
- Cost imported = Cost in XML file * (Exchange rate in XML file / Exchange rate of the matching currency in your database)
- For example:
- Michelle Peterson in the London office exports a project to a Primavera XML file and sends the project file to her colleague Judy Billings in the Paris office. The XML file that Michelle generates, contains information about the view currency Michelle used and its exchange rate with the base currency in her database. When Judy receives the file, she imports it into her database using the option to import with the XML rate.
- Michelle's view currency is GB Pounds (£) and the base currency in her database is US Dollars ($). The exchange rate between GB Pounds and the base currency in Michelle's database is 0.79. Judy's database has a base currency of Euros (€), and the exchange rate between GB Pounds (£) and the base currency is 0.88.
- Costs are always stored in units of the base currency of the database. So to import the correct value in GB Pounds, P6 converts the costs in the XML file by multiplying by the exchange rate for GB Pounds in the XML file divided by the exchange rate for GB Pounds in Judy's database.
- In Michelle's database, Activity A1000 has a planned cost of £1,000. The cost is stored in the database in the base currency of US Dollars as $1,265.82. The Primavera XML file contains the cost of the activity in the base units as well as information about the ID, name, and exchange rate for GB Pounds in Michelle's database. When Judy imports the file, P6 converts the cost of Activity A1000 as follows:
- $1,265.82 × (XML exchange rate / destination exchange rate)
- = $1,265.82 × (0.79 / 0.88) = €1,136.36
- When Judy changes her view currency to GB Pounds (£), the value stored in the database is converted to the view currency by multiplying by the exchange rate for the view currency, so:
- €1,136.36 × 0.88 = £1000.00

Related Topics