What is the Impact of Project Data Types 'Calendars' and 'Activity Codes' Options During the XER Import Process?
(Doc ID 2309152.1)
Last updated on JANUARY 03, 2023
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 15.2.9.0 and laterPrimavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.2.9.0 and later
Primavera P6 Professional Project Management - Version 15.2.9.0 and later
Information in this document applies to any platform.
Goal
The purpose of this document is to explain and give examples on the impact of the 'Project' Data Types 'Calendars' and 'Activity Codes' during the XER import process, and show examples of how these options also impact 'Global' Calendars and 'Global' Activity Codes and Values.
Question #1. Project Data Type - Calendars. If an activity's Global Calendar in the XER file already exists in the P6 database during XER import what happens to the existing P6 Global calendar's holidays and exceptions if they are different from the incoming XER project's Global Calendar settings?
Question #2. Project Data Type - Activity Codes. If the Activity Code in the XER matches (e.g., RESP) but the existing P6 database value's description do not match what happens. For example A Code = RESP with a value of TJ and a description of Tom Jones, and the incoming XER has same Code Name value (TJ) but the description is Tim Johnson?
Question #3. Project Data Type - Activity Codes. If the Activity Code in the XER matches (e.g., RESP) but the existing P6 database value's do not match what happens, e.g. A. Code = RESP with a value of TJ , and the incoming XER has same Code Name (RESP) but no value of TJ, is the TJ value deleted in the existing P6 database?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |