Best Practices for P6 Integration Related Topics: Best Practices for Importing/Exporting Data to/from P6 You need to consider some factors when you import and export data to and from Primavera P6. Activity Hierarchy Open Plan has an activity hierarchy while Primavera P6 has a flat activity collection. Baselines In Primavera P6, a baseline is a complete project. In Open Plan, only the baseline activity and resource usage tables are stored. Code and Resource Field Length If the code/resource field exceeds the 59 character limit that Open Plan can accept, it may rename it to fit. P6 Code Fields Open Plan imports the entire WBS code hierarchy when it imports a project. Multiple Assignments for the Same Resource To ensure that multiple assignments to the same resource on an activity get imported into P6 correctly, it is important to keep track of the options you are using when you import the XER file into P6. P6 Calendars Primavera P6 has three types of calendars: global, resource, and project. Updating Existing Data When You Import Data from an XER File into P6 By default, when you import data from an XER file into P6 and update an existing project, P6 keeps the existing values for the several fields. Update Existing Data When You Import Data from an XER File into P6 Use this procedure to change the fields that do not get updated when you import an XER file into P6 and update an existing project. Using Periods in ID Fields Deltek recommends that you refrain from using periods in the "local" segments of the P6 ID (such as PRJ.OR.USR.001). Using a Project Template for Your P6 Data Import To have a specific structure for your P6 data in Open Plan, create a new project in Open Plan with that structure before importing the data. Parent Topic: Oracle Primavera P6
