Our customers' wishes are important to us. With this release, we have therefore focused entirely on the activity codes at EPS level and made improvements to usability and performance.
As a project manager, you will probably often receive sub-project plans from your consortium partners, which you afterwards send to your customers in form of a consolidated total schedule. To insert these subproject plans into your project plan - without changing global data - EPS activity codes are typically used for attributes. These have the advantage of being project-spanning, but not globally applied. This allows you to build higher-level structures into which subprojects can be assigned without having to create new global codes for each new consortium project.
Importing EPS activity codes to Oracle® Primavera P6 EPPM quickly becomes complex. Either you overwrite your EPS activity codes, or you have to prepare the XER file to avoid damaging EPS activity codes. For example, EPS activity codes can also be lost if only one linked project is imported. With the proimporter you avoid these errors and reduce the effort of an import, because with Release 19.9 it imports all EPS activity codes to Oracle® Primavera P6 EPPM. In addition, you receive the following further advantages with the proimporter:
- Avoid identical code names on different EPS nodes by analyzing the database before importing.
- You will receive an error message for identical code names with recommended action (e.g. changing the code name or adding a prefix).
In addition, minor performance and usability improvements have been made:
With calendars, it is possible to define so-called exceptions. Previously, these exceptions were not displayed with their names in the respective calendars. Now you can see the type of exception by taking a closer look at the user interface.
If you have any further questions, please do not hesitate to contact us.
At regular intervals we also offer webcasts for our proimporter. You can find the dates for these in our webcast announcements.