As early as July 2019, we reported on the Quick Fix function (https://www.proimporter.de/en/artikel/quick-fixes) that the proimporter offers. XER and MSP files can contain data elements that can cause various problems when imported into the Oracle® Primavera P6 database.

Importing EPS activity codes to Oracle^® Primavera P6 EPPM can rapidly become complex. With the proimporter you can easily import activity codes on EPS level.

A company usually has a lot of projects. This is often accompanied by many resources. For your project success it is essential to use the right resources in the right place. In order to be able to take this into account in cross-project planning, different master data are necessary. This includes working hours, hourly rates, roles, affiliations to departments, locations or departments or similar. All this information is stored in the resource tree.

Do you have too much data waste in your Oracle^® Primavera P6 EPPM database? Find out in our free webcast which advantages you will have with the proimporter.

In order to solve a recurring task as efficiently as possible under the same conditions, #templates are a popular means. Whether it is the template for the business letter to write invoices or a template that can be used to process the same piece of material identically over and over again.

You probably used a project management system like Oracle^® Primavera P6 EPPM or Microsoft Project^® because you have to coordinate many projects. It is therefore inevitable that many and probably similar projects are created in a project database.

Calendars are particularly important for project planning. Globally administered calendars ensure that company-wide working times are taken into account in project planning. A falsification of global calendars can massively falsify the planning of the affected projects - when it comes to contract milestones, this can lead to high penalties in extreme cases.

In Oracle^® Primavera P6 EPPM there is a strict separation between the Work Breakdown Structure (WBS) and the activities. This separation does not exist in Microsoft Project^®. The transition between structural elements and processes is practically fluid.

Elapsed Days from MSP only can be imported manually to Oracle^® Primavera P6 EPPM, yet. With the proimporter you import Edays cleanly, automatically and without any additional effort.

A Global Admin User has access to all proimporter functions. He can also create global objects. This setting is particularly suitable for project managers and administrators who want to manage and import users, calendars, database connections or similar.

There are a lot of data that are not compatible with the Oracle^® Primavera P6 EPPM database extension. The most popular errors are too long ID's, too many baselines to handle or the import of unused calendars. In order to detect and correct such errors without much manual effort, the proimporter offers a validation module containing quick fixes.

Existing projects can be updated quickly and easily with the proimporter - even with MPP-files.

The proimporter recognizes automatically baselines in your import-file. Choose by yourself which baselines should be imported.

Importing files into Oracle^® Primavera P6 EPPM seems easy and fast at first glance. But who has already looked a little closer knows, that the program unfortunately does not offer some important features. There are different import actions for Primavera P6, but only for certain objects and not for all levels.

Especially in project work, it is essential that several employees, internally as well as externally, can access the same database. Changing or deleting the settings of relevant data is something you want to avoid. With the proimporter you can determine in detail which employees have which impact on the import.

Generate a baseline automatically before each project update with the proimporter of proadvise