Preparing to Export
The following items are actions or considerations you should take prior to export to ensure the P6 XML or XER file that is created is viable for use in Primavera Cloud.
- Check P6 Version Compatibility: Confirm that the P6 XML or XER file that will be created is from a supported version of P6. To learn more about supported product versions, consult the Client System Requirements document available on Oracle Help Center.
- Confirm Security Permissions: In order to perform a P6 XML or XER export, users are required to have either the Admin Superuser global security profile, which enables complete access to all global information and all projects, or the Export Project Data project security privilege, which grants a user the ability to export projects to which they have access.
The data included in the export process depends on the level of access granted to the user running the export. For example, if a user does not have access to the financial data or resources associated with a project, then the data that is exported will be limited because not all financial data or resources in the project will be accessible. Consider having a user with the Admin Superuser profile export the project.
- Single P6 Database vs. Multiple P6 Databases: Depending on your P6 implementation, you may have one or more databases containing projects. If multiple P6 databases exist, and all are being transitioned to Primavera Cloud, it may be beneficial to merge them into a single P6 instance first, and then produce a single, comprehensive export file. While it is possible to import multiple P6 XML or XER files into a single Primavera Cloud instance, more work may be required to align objects such as codes, calendars, and resources.
Prior to exporting from P6, take a thorough inventory of projects you want to import. If multiple P6 databases exist, determine if there is consistency across their respective enterprise data and configurations.
- Example 1: A company has multiple P6 users with separate databases. User 1 may keep track of Project Sponsor as a code, while User 2 may also keep track of Project Sponsor, but as a user defined field (called a "configured field" in Primavera Cloud). It may be more efficient to align these separate objects before exporting your data.
- Example 2: User 1 and User 2, with their own P6 database instances, each maintain a code called "Site", but they contain unique code values. Update Existing is the preferred import option for this scenario. If imported separately, Primavera Cloud will import the values from both instances of P6 into a single code.
- Avoid Calendar Conflicts: Ensure calendars in P6 are uniquely named such that they will not conflict with existing calendars in Primavera Cloud. After importing the calendars, you can reassign and rename them if necessary.
- External Project Relationships: To ensure that external relationships (also called "inter-project" or "cross-project" relationships) are maintained during import, Oracle recommends that you export a single, comprehensive P6 XML or XER file when possible. Exporting a subset of related projects will break any relationships with projects that are excluded from the export.
- Field Length Limits: Primavera Cloud supports code fields up to 60 characters and user defined fields (UDFs) up to 30 characters. List UDFs are supported up to 128 characters.
Last Published Tuesday, May 21, 2024