The Project Management application allows you to export project and work package actions to Microsoft Project and then edit the actions in Microsoft Project. After you have edited the project in Microsoft Project, you can import the Microsoft Project file back into the Project Management application and post the data to the database. The project/work package actions are then available to be viewed and edited in Project Management.
It is important to note that when you import the file, you first import it for review purposes. While you are reviewing the imported data you can choose to clear the data and make changes before you import again. After you are satisfied with your imported data, you post the data. When you post the data, the data is copied to the Project Management database. After the data is copied to the Project Management database, it is available for editing in Project Management.
To import from Microsoft Project,access the Management Console using any of the Process Navigator Management Console tasks, and then select the Import/Export tab. You can access the Management Console from Process Navigator tasks for the Plan, Procure, or Execute processes.
For information on exporting project/work package actions from the Project Management application to Microsoft Project, see the Exporting to Microsoft Project topic.
When you import an Microsoft Project .xml file to Project Management, the file is uploaded to the ARCHIBUS Projects table actions_xfer field or Work Packages table actions_xfer field, depending on whether you are importing a project's actions or a work package's actions. Data from this field is then extracted and copied to the ARCHIBUS Action Items Transactions table. This data is then available for you to view in the Import Project task Actions Transactions panel.
For information on the database tables used for importing projects and work packages from Microsoft Project, see the Importing from Microsoft Project Tables topic.
The Project Management fields listed below are updated when the Microsoft Project file is imported. Project ID, Work Package ID, and Action ID are imported for identification purposes. The remaining fields are updated, based on the edits that were made in Microsoft Project. For a mapping of Project Management fields to Microsoft Project fields, see the Exporting to Microsoft Project topic.
Note: It is only possible to import into Project Management project/work packages actions that have one of the following statuses: N/A, Requested, Planned, Scheduled, or In Progress.
The following Project Management Action Status changes may occur when you import a file from Microsoft Project:
After reviewing data in the Actions Transactions panel, if you click the Clear button, all extracted data is cleared from the Action Items Transactions table, and is no longer displayed in the view.
When you click the Post button, the action items that you imported to the Action Items Transactions table are copied to the Action Items table. The data is then available to be viewed and edited in Project Management.
The following Project Management Action Status changes may occur when you post a file:
If you originally exported all of a project's actions, then you import all of the project's actions back into Project Management.
To import all project actions from Microsoft Project to Project Management:
The Management Console appears with the Select Project tab selected.
The Export Project tab becomes selected. All of the actions for the selected project are displayed.
Note: At this point the .xml file has been imported into a review table, the Action Items Transactions table, so that data is visible. To save this data to the database, you must post the data.
If you originally exported the actions from a specific work package, then you import the work package's actions back into Project Management.
To import work package actions from Microsoft Project to Project Management:
The Management Console appears with the Select Project tab selected.
All of the work packages for the selected project are listed.
Note: At this point the .xml file has been imported into a review table, the Action Items Transactions table, so that data is visible. To save this data to the database, you must post the data.