You also have the ability to specify the action that the application takes when an object in the P6 XML or XER file already exists in Oracle Primavera Cloud or when multiple matching objects are found in sibling workspaces.
You can set separate import actions for each workspace and project data type, providing greater control over the data that gets imported. Note: Projects created in Primavera Cloud through P6 XML import have their project currency set to the parent workspace currency by default. Workspace-level data is shared among the projects, child workspaces, and other objects in the workspace. Most Enterprise Data in P6 is stored as workspace-level data in Oracle Primavera Cloud, although some project-specific data may be stored with the project.
It is a proprietary file format used by the P6 EPPM application.ĭata that can be imported from P6 includes objects stored at the Enterprise Data level and the project level. Note: XER refers to Oracle Primavera Proprietary Exchange Format (XER). Before you begin the import process, you must specify the target workspace into which the projects will be imported. In P6 XML or XER files that contain multiple projects, you can set separate import actions for each project. When you import a project from a P6 XML or XER file, Primavera Cloud gives you the option to create a new project, update an existing project, ignore the project and not import it, or update baselines only.
0 kommentar(er)
