Known Issues

The known issues listed below refer to the application of PLANTA project. Further known issues can be found in the following documentation areas:

• Technology/Installation/Update
• Customizing

Known Issues

Known Issues with Solution

Project creation not possible after updating to DB 39.5.17

After updating to DB 39.5.17, no projects can be created under MSSQL.

• Reason:
  • Failure of the AddUUIDtoProjectStructure migration packet during update
• Solution: Please run the following script on the database: fix_project_structure_table.sql

Incorrect Display after Deletion of Presence Time in PLANTA pulse

Using extended time recording for PLANTA Hybrid and recording presence time in PLANTA pulse, may result in incorrect display when presence time is deleted in PLANTA pulse.
The value in the database will be deleted, however, the display below the scale will not be updated. In the Presence module, the correct value will be displayed.

Python error message when calculating a project with resources with incomplete period records from S 39.5.24

When calculating a project with one (or more) resources with incomplete periods, a Python error message is displayed from S 39.5.24. The Python message is preceded by a text message which informs about the abortion of the calculation and specifies the cause. After this message has been confirmed, the Python message will still be displayed but can be ignored. The cause for this message (inconsistent data), however, must be eliminated actively.

• Reason:
  • The problem arises when a project is calculated which contains one or more resources the period records of which are incomplete in the period for which the resource(s) is/are planned or when the resource has no periods at all, although the Start period and End period fields are filled. Both cases represent data inconsistencies.
• Solution:
  • Refresh period records for the resources concerned in the required period.

Scheduling

In parameter constellations where Requested start and Requested end lie in the past, Active today’s line = , Fixing = 1, it may occur that the Calc. end of a task lies before the Calc. start (e.g. when the set Actual start is in the past).

• Reason:
  • The conflict between the Fixing = 1 and Active today’s line = . In other words: The task is supposed to start today although it is frozen in the past.
• Solution:
  • Set the Split parameter = .

Behavior of remaining load when using MAN load profiles

If you use the MAN load profile and no actual dates have been set yet, the values will be transferred to Planned load when you enter the Remaining load manually but they will not be summarized to Planned effort.

• Workaround: copy the remaining effort to the planned effort after you have entered the remaining load and have calculated the schedule.

Effort bars are missing in the Resource Planning module

If a resource is not available on one of the days for which he/she is planned (i.e. does not have any Remaining effort ), the effort bar for the resource in the Resource Planning module will be missing for that day.

• Customizing solution:
  • Open data area 050314 in the Data Areas module.
  • Delete the entry for DI001364 in Filter from .
  • Save.

Updates after changes to resource structures

If a resource is put on in, or deleted from an existing resource structure, the available capacity and the utilization of a directly superordinate resource are updated automatically, while that of a higher structure level is not.

• Solution: In order to ensure an update at all structural levels, you have to unload and subsequently replan all projects in the Replanning (Calculation of all Projects) module.

Problems in the use of user-specific and general module variant favorites

If a module variant has been defined as a favorite for all users and then one user defines an individual module variant as his favorite, the previous favorite variant will be deactivated for all users.

• Customizing solution: The module variant that is to be selected for all users by default is not to be declared as a favorite. Instead, check whether the user has a user-specific favorite and then select the favorite or the required module variant respectively. For this purpose, include the following code in the on_initial_focus() method in the macro of the module:

standard_favorite= '2000000002' # <- Replace with the standard (not user-specific) favorite MV-ID

    module_rec405 = ppms.search_record(405, [mod_obj.get_id()], ['id'])
    mv_recs500 = module_rec405.get_children(500, di_list=['user', 'favorite', 'variant_id'])
    user_has_favorite = False
    for rec in mv_recs500:
        if rec.user.get_value() == ppms.uvar_get('@1') and rec.favorite.get_value():
            mod_obj.apply_mv_by_id(rec.variant_id.get_value())
            user_has_favorite = True
            break
    if not user_has_favorite:
        mod_obj.apply_mv_by_id(standard_favorite)

• The module variant ID that is to be applied as a favorite to all users must be specified as standard_favorite.

Print header is not displayed in print preview in a submodule.

In the print preview of a submodule, the print header or footer is not displayed.

• Customizing solution: Copy the following line to the on_load() method in the macro of the submodule in which the print header or footer is not displayed.

mod_obj.get_das()

Blurry font under Windows Server 2008 and Windows 7

The use of PLANTA under Windows versions Server 2008 and 7 results in fuzzy typeface. The reason for this is that the Roboto font used in PLANTA is not installed in these Window versions.

• Solution: Replace the Roboto font by a common font, e.g. Arial, in the \Resources\defaultSkingSettings file in the GlobalFontName:Roboto line in the Client directory.

For some tasks, Remaining duration is always at 1 and cannot be changed manually.

For some tasks, the manually allocated remaining duration is overwritten by a 1 after scheduling.

• Reason:
  • In certain planning constellations, it may occur that Planned duration is empty. In such cases, scheduling sets the Remaining duration to 1. If an actual start date is entered or if it already exists, the Remaining durationcannot be changed manually anymore. When trying to change it, it is reset to 1 in scheduling.
• Solution:
  • Unhide the Remaining duration field in the Schedule module.
  • Enter 1.
  • Allocate the required remaining duration.
  • Perform a scheduling.

Fixed Issues 

Time recording below the scale is not possible when working with multiple calendars  (resolved with DB 39.5.17)

If you use time recording variant 2 (global Time recording variant = 2 parameter) and have created multiple calendars in the Calendar module, the recording of hours worked will not be possible in the Time Recording module directly below the scale or a Python message will be displayed (MSSQL systems).

Error message which is displayed when users with portfolio role (portfolio modules) log on (resolved with DB 39.5.17)