- Choose File, Import.
- Choose Primavera P6 - (XML). Click Next.
- Select the file you want to import. Clear the option "Import all project level layouts" if you do not need them to be included with the project. Click Next.
- Click the Import Action field and use the drop-down menu to choose how the project data is imported.
Select Update Existing Project to add any new or modified data in the XML file to an open project.
Select Create New Project to create a new project without changing existing projects.
Select Ignore this Project to not import the selected projects. - When P6 Professional is connected to an EPPM database, click the Currencies import in field and use the drop-down menu to choose how currencies are imported.
Select Base Rate to import cost data in the base rate for your database. Choose this option if you do not want costs to be converted using the exchange rates in the XML file and your database.
Select XML Rate to import cost data and convert it using the exchange rate in the XML file and your database. Choose this option if you want cost to be converted to account for differences in the exchange rate between the originating database for the XML file and your database.
- Double click the Import To field and specify where to import the project.
- Double click the Baselines to Import field. In the Baselines to Import dialog box, mark the Import checkbox next to each baseline you want to import. Click OK, then click Next.
Note: If you select to import with the update existing option 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. 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.
- If you chose to create a new project, double click the Financial Period Calendar Field. In the Select Financial Period Calendar box, select an appropriate financial period calendar (if necessary).
- Choose the data to import by adding or editing a template in the Update Project Options dialog box (if necessary).
In the Update Project Options dialog box, you can search for templates using the Search field. As you type, it will filter only those templates that match the text in this field. - Click Edit to launch the Import Options dialog box.
- On the Basic tab of the Import Options dialog box, modify the selected option by choosing the action to take when the same data exists in the import file and the project being updated. If resource security is enabled, some restrictions apply when importing activity resource assignments.
Select the action to perform during the import process. Mark the Delete checkbox to remove unreferenced data (that is, data in the project you are updating but is not included in the import file) from the project. (The Delete field applies only to relationships to external projects, thresholds, activities, activity relationships, and activity resource assignments. Global data types are not affected by this setting.) - On the Advanced tab of the Import Options dialog box, modify global data, including codes, UDFs, calendars, and resources, as necessary.
Note: This tab is disabled if multiple projects are being imported. However, if you select the "Ignore this Project" option for all projects but one, this tab is enabled.
- Click Save to update the existing template or click Save As to create a new template with a unique name. Click Next.
- Click Finish.
Notes
- You can import a compressed file in zip format if it contains a single Primavera XML file.
- When you import an XER project file that contains financial periods, the financial periods in the XER file must exactly match the financial periods in the financial period calendar assigned to the project. If they do not match, no past period actual data will be imported.
- When you import a project that contains relationships to external projects that do not exist in your database, the module will preserve the external activity dates when you schedule the project if you select the Ignore Relationships To and From Other Projects option in the Schedule Options dialog box.
- The following applies only when you choose Update Existing as the Resource import action: When you import a shared resource calendar and a personal resource calendar with the same name already exists in the database, the data from the shared calendar updates the personal resource calendar by the same name, but the personal resource calendar remains a personal resource calendar. Likewise, when you import a personal resource calendar and a shared resource calendar with the same name already exists in the database, the data from the personal resource calendar updates the shared resource calendar by the same name, but the shared resource calendar remains a shared resource calendar.
- Subsequent to the import, there may be unassigned personal resource calendars depending on the import action you selected for resources and calendars during the import operation; these calendars can be deleted.
- To import an XML file that contains updates to your personal resource calendar, you must have the Add/Edit/Delete Resource Calendars privilege. Otherwise any updates to your personal resource calendar are not imported.
- When connected to a P6 EPPM database: Risk data from P6 is imported when using XML format.
- When connected to a P6 Professional database: Risk data is imported when using XML format.
- You can import XML files without having access to all resources, but the following restrictions apply:
- If the XML file contains resources that are in your hierarchy, these will be imported.
- If the XML file contains new resources, these will be imported as long as the new resources are in your hierarchy.
- You can choose to not import any new resources by choosing the “Do Not Import” option for Resources. Choosing the “Do Not Import” option for Resources causes the system to import the assignments of any existing resources in your hierarchy. In this case, any new resources in the XML file are ignored by the importer.
- If the XML file contains resources that are not in your hierarchy, no items are imported. The system cancels the entire import process and issues an error.
- If the XML file contains resources in your hierarchy that are in conflict with existing resources outside of your hierarchy in the database, no items are imported. The system cancels the entire import process and issues an error.
When connected to a P6 EPPM database: For more information on defining access to resources, see the P6 EPPM Application Administration Guide.
When connected to a P6 Professional database: For more information on defining access to resources, see the P6 Professional Installation and Configuration Guide.
- When connected to a P6 EPPM database: 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