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.

With the proimporter you simplify your daily work routine significantly.

Logic differences between Microsoft Project^® tasks and Oracle^® Primavera P6 EPPM activities are always a challenge for the import, because so far Oracle^® Primavera P6 EPPM does not consider these or only partly. 

Especially with more complicated processes, such as the Hammock Task, a logic bridging is necessary. A Hammock Task is a process that start and end dates are synchronized with the start date of another task and the end date of another subsequent task. In this way, a macro operation spans a certain phase of a schedule, which is to be considered super ordinate, for example, for resource planning or for certain evaluation purposes.

When importing to Oracle^® Primavera P6 EPPM, the database now does not recognize these Hammock Tasks from Microsoft Project^® as such and the information is lost during the import. The proimporter recognizes the information correctly and imports these tasks as Level of Effort activity to Oracle^® Primavera P6 EPPM. Thus, data loss can be avoided and the appointment chain can be imported cleanly. 

Elapsed Days are also a regular challenge for project managers. In Microsoft Project^® it is possible to ignore the duration of an activity in the stored calendar. This is especially useful for processes that - beyond the normal working day - also take place on weekends (e.g. drying concrete), or for machine availability that can last 24 hours a day. With the proimporter you import these edays directly from the MPP file into Oracle^® Primavera P6 EPPM. The tool uses a 24/7 project calendar for this purpose. This ensures that every day is a working day and that the deadlines are correctly met.

If you have any further questions, please do not hesitate to contact us.

Do you have any feedback? You are welcome to send us your suggestions via mail: This email address is being protected from spambots. You need JavaScript enabled to view it. or via our contact form. You can also use our chat function.  

At regular periods we also offer webcasts for our proimporter. You can find the schedule in our webcast notifications. Stay up to date. With our release notifications you will always be informed about the latest updates of the proimporter.

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.

However, these rights also entail obligations. So the Global Admin User has the responsibility to manage the proimporter users, because basically all Oracle^® Primavera P6 EPPM users are created by default as simple users in the proimporter.

As a Global Admin User, you have several possibilities

For example, you can upgrade normal users to Power Users or Global Admin Users. This can easily be done directly in the proimporter via the selection menu "Edit < Users".

This opens a pop-up window in which you now have various options at your disposal.

In the left tab, you can see the users who have different permissions as admins and power users in your Oracle^® Primavera P6 EPPM. In the right tabs, you can switch between the user modes "Power User" and "Global Admins".

If you now want to appoint a user as a "Power User", for example, select this user in the left tab and check that the "Power User" tab is selected on the right side. Now all you have to do is press the "Insert" button and the user you selected now has the permissions of a "Power User". Further configuration of permissions is not necessary.

Do you have any suggestions?

You are welcome to send us your suggestions via our contact form. You can also use the chat function on the proimporter website. At regular periods we also offer webcasts for our proimporter. The dates for this can be found on our website or you can follow us on our social media channels.

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.

Errors are detected and quickly corrected using a Quick Fix function.

The proimporter validates the file to be imported before the import for possible errors and displays them clearly. You receive a possible Quick Fix for each error. The user now has the following options:

On the one hand the user has the possibility to apply all Quick Fixes en bloc:

User can also select individual Quick Fixes and correct them:

As a third option, he can jump directly to an affected object and implement a solution other than the Quick Fix:

This is necessary, for example, when shortening an ID, because if it is no longer unique, it must be changed manually.

Do you have any suggestions?

You are welcome to send us your suggestions via our contact form. You can also use the chat function on the proimporter website. At regular periods we also offer webcasts for our proimporter. The dates for this can be found on our website or you can follow us on our social media channels.

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

Cooperation in consortium projects requires a regular exchange of schedule updates between partners. The challenge: the different partners work with different tools (partly with Microsoft Project^®, partly with Oracle^® Primavera P6 EPPM).

The final consolidation should take place in Oracle^® Primavera P6 EPPM. Previously you had to tell your partners that they should export their project as an XML-file in order to import it into Oracle^® Primavera P6 EPPM.

With the proimporter you can easily import MPP-files into Oracle^® Primavera P6 EPPM without having to export the project to another format.

The tool can also update existing projects. As with the initial import, you can specifically select the desired objects for the import.

The same applies for updates: Existing global data will never be overwritten in any setting.

Do you havee any suggestions?

You are welcome to send us your suggestions via our contact form. You can also use the chat function on the proimporter website. At regular periods we also offer webcasts for our proimporter. The dates for this can be found on our website or you can follow us on our social media channels.

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

If you are using Oracle^® Primavera P6 EPPM, then you may have probably already noticed that Oracle^® Primavera P6 EPPM baselines requires you to separate them from the original project - if desired - before exporting. Oracle^® Primavera P6 EPPM then stores them as independent project plans in the XER-file. This must be done manually. When importing directly to Oracle^® Primavera P6 EPPM, these must be manually added back to the original project as baselines after the import.

The proimporter intuitive user interface allows you to choose which baselines you want to import. 

The validation function of the proimporter verifies the number of allowed baselines in the database configuration. If this number is exceeded, you receive an error message and are free to decide which baselines you want to deactivate.

In this way, you can easily and clearly select the required baselines without exceeding in any way the data limits of the database configuration

Do you have any suggestions?

You are welcome to send us your suggestions via our contact form. You can also use the chat function on the proimporter website. At regular periods we also offer webcasts for our proimporter. The dates for this can be found on our website or you can follow us on our social media channels.