See also:

Release Notes: Version Overview Release Notes: all Database Versions Release Notes of individual database versions: DB 39.5.16 / DB 39.5.15 / DB 39.5.14 / DB 39.5.13 / DB 39.5.12 / DB 39.5.11 / DB 39.5.10 / DB 39.5.9 / DB 39.5.8 / DB 39.5.7 / DB 39.5.6 / DB 39.5.5 / DB 39.5.4 / DB 39.5.3 / DB 39.5.2 / DB 39.5.1 / DB 39.5.0

Version DB 39.5.11

Attention

• For DB 39.5.11, C 39.5.24 and S 39.5.26 are required.
• When updating a DB version < 39.5 to DB 39.5.11, performance issues occur during budget migration when there are several complex project structures. Therefore, please note this before updating to DB 39.5.11 #22611
• When updating to DB 39.5.11 under MSSQL, it may occur that the UnloadAndReplan migration packet fails due to a unique sequence problem. In such a case, please run the migration packet once more after completion of the migration.

Application

Notes

• In version DB 39.5.11, the hours to be worked function in the Global Settings has been deactivated by default. If you use this function and carry out an update to this DB version, you have to deactivate the function again after completion of the update. #21515
• The import of holidays has temporarily been removed from the Calendar module. #22241

Features

• Hybrid
  • PLANTA Hybrid has been implemented
• Portfolio
  • The dynamic calculation of the quality gate and todo item dates has been implemented. Further information #21166
  • In the Quality Gates module, small functional adjustments have been made: On the Date field a traffic light has been implemented and the traffic light on the Completed field has been changed. The Completed on field, which can be filled by the project manager (for further information, see also the AddQGDoneOnFieldForPL migration packet), has been added to both the todo items and the quality gates. #21496
  • The Documents module has been extended: Portfolio documents are now created and maintained in a categorized manner. They can as well be set to completed or be archived and then maintained in the respective module variants. #19951
  • In the Costs/benefit chart in the Info Board module the planned benefit is now taken as a reference value for comparison with total costs instead of the achieved benefit. #21778
  • In the Edit Period module, traffic lights have been implemented on the planning objects which signalize whether the budget of the respective planning object exceeds the budget of the portfolio and whether the planning object is contained in several portfolios. #20197
  • In the Status module, the behavior of the TBM checkbox has been changed insofar as it is now deactivated automatically if the WBS checkbox is deactivated. However, there is no dependency in activation. #20516
  • The Administer Portfolio Images module has been optimized. #20788 #20504
  • In the Portfolio Core Data module, the Copy QG template automatically parameter is implemented, which can be used to define whether the quality gate template is automatically copied to the planning object when it is copied to the portfolio. #20552

• Programs
  • In the Programs module, the bar for the visualization of the project/program date delays have been implemented. #20952
  • All newly created tasks in programs now receive the Master milestone setting by default. #21513
  • In the Program Core Data module, the Portfolio assignment area has been added, in which the assignments of the program to portfolios are displayed and can be maintained. #20772

• Project
  • If a week is entered for direct jump (Go to button) in the Work Reporting module which lies outside the resource calendar, a message indicating this is now displayed. #21472
  • The SAP WBS implementation (Create SAP WBS Elements, SAP WBS modules as well as the SAP Project Structure Import, SAP Plan Costs Export, SAP Plan Costs Import default interfaces) has been extended by account assignment elements. #20514 #21144
  • In the Reporting Hours Worked module, several minor adjustments have been made: Among other things, an option to filter by date (Extras Filter Criteria is activated) has been implemented. #22294
  • In the Utilization with Cause and Resource Utilization by Code modules, the display of the utilization has been restricted to active projects and projects with utilization diagram in a particular period. Furthermore, tasks with actual end are filtered out completely in the first module and displayed grayed out in the second. #21955 #21981
  • The Resource Overviews (Reports) have been included in the Resource Management role.
  • An option to update period records after changes have been made to resource parameters without deleting them. This solves the problem of vacation and absence data loss. For the procedure, click here. #16105
    • In addition, an info message has been implemented which notifies the user in case of resource parameters changes that the periods are to be updated. #20400
  • The area for creation of summary reports in the Check Status Report Creation and Project Applications module has been revised. #21169
  • In the Work Reporting Overview module, an option to change the work reporting display period and the scale by making changes to the from and to fields has been implemented. #21452 #21860
  • In the Absence and Absence of the Department modules, data is now summed per year and you can scroll to previous and following years dependent on the periods of the resources. #12408 #21432
  • The scheduling performance, especially that of the budget and cost scheduling has been improved substantially. For the detailed calculation matrix of all modules in question, see here. #20208
  • For groupings in the Multi-Project Board, etc., no more text constants are used, but instead the values of the listbox implemented on the Code data field. (Listbox category 00000009). When you use individual project codes, you now only have to adjust the listbox values. #21573
  • If the user has no write rights for a planning object, the You are not authorized to carry out this function dialog message is displayed. #20888
  • A dialog message has been implemented which notifies you, when you try to activate the Status reports: collective creation parameter on subprojects, that this function is available for main projects only. #20724
  • The Projects module has been extended by the display of proposals. Furthermore, the Priority parameter has been included in the module to enable project sorting by priority. #20283
  • In the Send Info module, the Info per field has been included additionally. Thus, in case the recipient is changed, it is immediately visible in what manner he or she receives the message. #20007
  • In the Progress module, a button has been implemented which automatizes the copying of forecasts. #19807
  • In the Risk Trend Analysis and Opportunity Trend Analysis modules the Risk and Opportunity fields will be displayed in the colors of the area of the risk or opportunity matrix in which the risk or opportunity is displayed in red, yellow, or green depending on its weighting and probability of occurrence. #20670
  • With the new customizing option for creating links between tasks in different data areas, you can now create cross-functional links from tasks to gates in the Project Schedule, and graphically from program tasks to tasks of the program projects in the Program Schedule. #21526
  • In the Subprojects module, it is now possible to move subprojects. #18077 #22177

• PM Administration
  • If a Leaving date is set for a person in the Persons module, it is inherited to the child attributes (person resource, resource, user, stakeholder). #19934 #7291
  • The maximum_work_hours_per_day gloabal setting via which the maximum number of working hours per day can be defined has been added. For this purpose, the AddMaxHoursColumnToEmployeePool migration packet must be run. #22158
    • For new resources, "10" is used as a default value from now on. In order to define the maximum number of hours worked for already existing resources as well, run the SetMaxHoursPerDay migration packet.
  • Since the selection of the Internal/external employee resource type during resource creation necessarily requires the selection of a person, the Person field is now marked as a mandatory field as soon as the resource type for a resource to be newly created has been set to Internal/external employee. #20866
  • The process actions for assigning stakeholders and evaluating risk values/objective contributions have been extended, so that the actions can be carried out more easily: Assign stakeholder and click on the Evaluate button to open the risk values and objective contributions in order to be able to evaluate them. #20815
  • Process rule 011000017 Change action planning object type + create baseline has been changed, so that process models which carry out a change of the planning object type (idea/proposal/project) during phase approval are no longer reset if there are still open phases. #21269

• PLANTA link
  • The functionality of the SAP plan costs export and SAP plan costs import interfaces has been adjusted, so that the transfer of the costs/effort is now done via the account assignment element level. #20497
  • In the listbox on the HTTP method field in the Test Web Interfaces module, input only via listbox has been implemented to prevent users from making inputs which do not occur in the listbox. #22168
  • The new PPMSCSVModule module subclass for generating CSV files which can be read by PPMS 38. #21357
  • The new Administer Mapping Functions for administering the mapping functions of PLANTA link has been implemented. Here, you can add new functions to make them available for selection in the listbox of the interface configuration. #21332
  • In PLANTA link, a new standard configuration has been made available:
    • BAPI_BUS2054_GETDATA and BAPI_PROJECT_GETINFO, in order to open the BAPIs and import their data to the PLANTA SAP WBS Element Table. #21031
    • Conversion factor import for the import of conversion factors. #21463
  • The MtsModule class in the PLANTA link now recognizes value X as a valid input for checkboxes. #21575
  • The dimmer during PLANTA link transfer now shows a static text while the current status is written in the status line of the module. This causes a significant performance improvement. #21454 At all positions at which a configuration can be edited in PLANTA link, the single Configuration module is no longer displayed, but a new panel is opened instead. #20760
  • PLANTA link now writes an exact warning in the logfile if an external key field is filled incorrectly. #21087
  • The sequence of the mappings, if they are generated automatically with PLANTA link, now equates to the module customizing again. #21085
  • PLANTA link no longer runs validation checks for its configuration if a parameter is changed which is not linked to any validation step. An example for such a parameter is the filepath parameter of the CSVModule class. If an interface is opened outside PLANTA link via macro, it is no longer necessary to use a subclass which switches off the validation in order to achieve a gain in performance. #21069
  • When you try to change records which have already been transferred to SAP, a proper alert is now displayed instead of a Python error message. #21248
  • The AbsenceImportModule class of PLANTA link now writes a respective error message in the log if the module customizing does not meet the expectations of the class. #21086
  • The PLANTA link web entities now have a new, displayable VH SST attribute. The field shows how often a web entity is used in interfaces. #20152
  • The Logging module now shows the number of errors/warnings of the interface run. #22296
  • The ConvertDateToYear converter and the YearlyTrancheExists validator has been added as well as the existing MtsLiabilityModule class. For this purpose, the AddLiabilityPoolTable migration packet must be run. #20491

Bug fixes

• General functions
  • The problem that the changes made to the access rights did not immediately take effect when opening the modules for which the rights have been changed, but only in respective modules after refreshing via F7, has been resolved. #21410
  • The export to PowerPoint has been improved, a.o. as follows: #20757 #21325
    • The result of the chart export has been improved. #20843
    • The difference in the display of scales has been resolved. #20779
    • The incorrect export of planning objects (not all were exported) has been corrected. #20780
    • The display of bars and tables has been corrected. #20875
    • A message is displayed now if no charts are available. #20897
    • The error which caused the error message when exporting to PowerPoint if there was data in the clipboard at this time, has been resolved. #20901
    • The export of large data volumes has been optimized. #20674
    • When exporting a project with subprojects, the structure tasks are no longer copied along #21861
    • The problem that planned duration was exported instead of remaining duration has been resolved. #21061
  • The resource ID change can be carried out repeatedly if it has been initiated during the running scheduling. #20754
  • The project milestones in a PDF file with a portfolio status report show no other color than in the Dashboard. #21011

• Portfolio
  • The quality gate symbols are immediately visible in the Quality Gates module below the scale after the quality gates have been copied to a project. A previous scheduling run in the project is no longer required. #20890
  • The incorrect program behavior in the visualization of unsaved changes (*) and in the storage query when trying to remove an active quality gate template from the portfolio, has been corrected. #21184
  • The bars in portfolio road maps can no longer be moved. #20983
  • The problem that some cost/effort charts in portfolio status reports converted to PDFs did not contain any data, has been resolved. #21013
  • The planning object type when using filters in the portfolio info board is now considered. #20956
  • When activating/deactivating the planning objects in a budget period of a portfolio and subsequently updating the period, the data of the portfolio is always updated along. #21475
  • Cause of the error message which was displayed when attempting to export an empty simulation (without data) to PowerPoint has been resolved. #21912
  • The displayed master milestones in the Active report and Baseline lines in the planning object charts in PDFs of portfolio status reports are no longer reversed. #21010
  • The incorrect data on which the charts in the Budget and Costs per Portfolio, Project, and Year module are based have been corrected. #21370
  • Projects which contain quality gates can now be deleted. #21345
  • The incorrect display of the time interval to the master milestone on the quality gates in the Schedule module has been corrected. #20535
  • In the Quality Gates module, no more requests are displayed and no more quality gates can be copied in for requests. #21462
  • When trying to select a status report for a planning object to create a portfolio report, the respective message is displayed again and no empty dialog is displayed any longer if the planning object has no released status reports but possesses project applications. #21001
  • The cause of the Python error message which occurred in the Administer Portfolio Images module when trying to delete images, has been eliminated. #21243
  • The problem, that the Python error message which occurred in the Status module when trying to change the estimate of planning objects without status report selection has been resolved. #21268
  • The behavior of the date listboxes in the Info Board has been corrected, e.g. an input check has been implemented, so that the from date cannot be later than up to. #20861
  • The double use of the Priority parameter in the Proposal Core Data module has been corrected. #21296
  • In the Quality Gates module, the quality gate symbols disappear after opening and closing the tree structure of the tasks. #20988
  • The planning objects of the portfolio for which the WBS checkbox has been deactivated are no longer considered in the Risks/opportunities area of the respective status report. #20516
  • The Completed value of the quality gates is calculated correctly. #20986
  • When you open the Portfolio Core Data module, no more error occurs when the assigned profile image has been deleted in the mean time. #20874
  • In the Time&Budget matrix in the Portfolio Status Report, no more ideas are displayed. #20449
  • The wrong dialog message which was displayed when assigning planning objects to portfolios if the planning objects were already assigned to other portfolios, which, however, used different quality gate templates, has been corrected. 21425
  • The cause of the error message which was displayed in the Portfolio Core Data module when selecting a quality gate template from the Active template module has been eliminated. #21907

• Programs
  • The user rights check for status reports of programs has been corrected, so that users without respective rights can no longer release and delete status reports. #21073
  • Newly created programs contain the Planning early parameter and are therefore no longer set to Planning late by default. #21176
  • Newly created program applications are displayed in the Program Applications module and no longer as status reports in the Status module. #18500
  • The cause of the error message which occurred when clicking on the Refresh button in the Program Application module has been eliminated. #20879

• Project
  • The problem caused by a Python message when a resource without defined cost type (cost type = -) attempted to report hours worked to an overhead cost project, has been resolved. #22018
  • The cause of the Attempt to use a DtpRecord instance which has already been deleted! error message in the Reporting Hours Worked module when deleting several load records for a record on which the resource has previously not been planned, has been eliminated. #22119
  • The problem, that an error message was displayed when trying to report vacation for a resource which had longer periods than its parent resource has been resolved. #21638
  • The different display of revenue and cost resources in the Schedule module, depending on whether the Insert Revenue and Cost Resource or Assign Revenue and Cost Resources (dialog modul) was used, has been corrected. #19948
  • Planning objects can also be deleted if they are used in simulations/road maps. #21615
  • The problem with the display of data in the Gantt chart of the Cost Reports and Effort Reports modules has been resolved. Now both total costs and cost budget are displayed by cost type groups and with appropriate coloring. #22024
  • The approval for status reports which is created via the Summary creation: status reports function can be canceled again. #21631
  • Department resources no longer receive Work = for days for which at least one of the employee resources has reported absence or vacation. To correct the incorrect data resulting from this error, please run the 22092 migration packet. #22092
  • In the My Planning Objects and Reporting Hours Worked modules, completed projects are no longer displayed. #21721
  • In the Resource Planning module, the effort can no longer be allocated from/to periods. A message has been implemented which notifies the user when trying to allocate effort from/to a resource that allocation is not possible due to missing resource periods. #19822
  • After export of actual load from PLANTA, all records (not only the fields with actual loads) are locked for editing. Now an alert is output when you try to change the exported record in the Reporting Hours Worked module. #21727
  • In the Subprojects module, the button for changing the functional ID has been included again. #21493
  • When using the Idea and Proposal process model, another info can be sent via the approval of another phase if the dialog for conversion of an idea to a proposal or of a proposal to a project is confirmed upon approval of the project. #21231
  • When reimporting the projects previously exported from PLANTA project to Microsoft Project, it is no longer tghe case that only one task is reimported. #21601
  • In the PLANTA project vs. Microsoft Project module, quality gates are no longer displayed like normal tasks. #21211
  • Changing the value for the manual cost entry to manual now causes a respective change to the scheduling behavior again (from capacity scheduling to time scheduling). #21522
  • In the Dashboard module, milestone charts of projects which contain more than 999 tasks are displayed. #21389
  • The length of DI063942 SAP WBS element name in pool data table DT964 has been adjusted to that of the original table DT963 (50). #21576
  • The message which indicates tasks which cannot be included when partially copying schedules with links is now displayed again. #21506
  • Accessing planning objects from the Resource Planning and Skill Requests modules for the same user no longer results in different rights settings. #20041
  • For the Category listbox in the Risks/Opportunities module, input only via listbox has been activated. #21294
  • In the Programs module, the IDs of the quality gates of the superior program are displayed. #20849
  • The double availability of department resources which only occurred in DB version 39.5.10 has been resolved. #20070
  • In the module variants of the Risks/Opportunities module, the correct number of opportunities is displayed. #21063
  • For the Dashboard module, the up to filter value has been increased, so that the Activities area is displayed constantly again. #21309
  • The manual entry of the % completed value for the todo items of the quality gates in the With Quality Gates module variant in the Schedule module is possible again, provided that the value to be entered is contained in the listbox. #21057
  • In the Resource Planning module, the bars for planning objects with code E are displayed in the correct color. #20943
  • The Remaining effort field in the Resource Plan module is no longer on output, so that it can be edited by users with the respective rights again. #21090
  • In the Stakeholder area in the Project Core Data module, the correct phone field has now been included. #21099
  • The date delay in the date bar in the Budget overrun: effort of the Critical Projects module is now visualized (red bar). #20113
  • In a new program, newly created tasks remain displayed after clicking on the Update (F7) button. #20974
  • During PowerPoint export, a temp folder in which the files can be stored is now displayed. As a result, the export no longer fails in the case of missing write rights for a local folder. #21046
  • In the Remaining Effort and Costs module, the functional project ID is displayed correctly when grouping by projects. #20922
  • An error which occurred when creating subordinate employees via the Fast Creation of Employee Data module, and which caused the Factor amount/period field to remain empty, has been resolved. #20940
  • Controlling reports can now have the last released status. #20694
  • The missing links on the task IDs in the Schedule module of the program have been implemented. #20860
  • The problem, that proposals for which the Status reports: summary creation checkbox was activated were not displayed in the Check Status Report Creation and Project Applications module regardlessly, even if they did not contain any status reports in the period searched for, has been resolved. #20756
  • The error that the grouping field in the By priority module variant in the Risks/Opportunities was empty although the respective values were available in the risks and opportunities, has been corrected. #20591
  • In the Budget module, the value is now updated in the Abs. costs field in the Revenues area after recalculation and not only after reopening the module. #20162
  • In the Send info module, the decimal places of the forecast values are taken into consideration. #20506
  • In the Activities area in the Dashboard module, quality gate todo items are no longer taken into consideration. Here, only task todo items are considered. #20884
  • The quality gate todo items are displayed in the Quality Gates module variant of the Schedule module again as soon as they are set to 100 % completed. #20880
  • If a new resource is created, but no periods are defined for it at first, a period record with the creation date of the resource is created anyway; based on the entries in the Start period/End period fields which are automatically filled with today’s date upon creation of a new resource. #20916
  • In the Stakeholder area in the Project Core Data module, the road map dates are now displayed. #20891
  • When you carry out a part string search in the Object Filter module, the listbox on the Filter criteria field is no longer case sensitive. #20153
  • Status reports can be deleted again under MSSQL. The Python error which occurred during deletion has been resolved. #21422
  • The moving of subprojects in the Subprojects module is now possible again. #18077
  • If the from and to fields in the Reporting Hours Worked module is set to 0, now 0 h are calculated instead of 24 h. #21918
  • In the Reported hours worked: current week area in the Reporting Hours Worked module, the project manager now only sees the reported hours worked for the current project and not those for other projects if he/she has opened it before via the Report hours worked context menu command on a stakeholder resource in the Project Core Data module. #22297
  • The wrong sequence of the process steps in projects, proposals, and ideas after copying the template has been corrected. #22019
  • The problem which was caused by the ORA-01843: not a valid month error message which occurred when canceling a process model under particular database requirements has been resolved. #22211
  • In the listbox on the Priority field (DI006508 and DI057914) now the high, medium, and low values are displayed in a standardized manner.

• PM Administration
  • The resources for which a Left on date is set in the future are displayed in the modules which filter by Left on date again. Only resources for which the Left on date is smaller than or equal to today’s date are filtered out. #19754
  • In the Persons module, persons with set Left on date are no longer displayed in the Base module variant, but in the Persons left module variant. #21614
  • The Insert Resource context menu has been removed from the Resource ID Change module. #20809
  • After renaming a user there will be no more confusion between the former and the current name for user, stakeholder, and person resource name. #20349
  • The cause of the KeyError: 30 Python error message which occurred when deleting SAP WBS assignments in the Create SAP WBS Elements module has been eliminated. #22002
  • The deletion of elements in the Create SAP WBS Element module as well as the related dialog messages have been fixed. #21826

• PLANTA link
  • Under MSSQL it is possible to delete log files in web interfaces again. #22027
  • Clicking on the Test interface button with invalid records no longer leads to an error message. #22029
  • The incorrect behavior due to which newly created configurations which were marked as templates could be displayed and deleted in the Open Configurations module has been fixed. #21242
  • An error which occurred when opening the PLANTA link Logging module in the Calendar module has been resolved. In the course of this the PLANTA link logging was configured in a way that it is only opened if the user possesses the PLANTA link 01100028 role. #22241
  • The problem that in mappings which use several relative parameters errors occurred when using non-string data types has been resolved. #21888

• Request
  • The empty lines which were displayed for some cost centers in the listbox on the Filter criterion field in the Object Filter Request module have been fixed. #20931

Customizing and Technology

Features

• In the Overview of all Previous Runs module, packet dependencies and database system dependencies of the packet are displayed in addition to the customizing dependencies. #21423
• When setting a field to Invisible data window (window 9) in the module customizing, the Filter criteria and DF options parameters are automatically deactivated. #21060
• In the module customizing, an option to automatically set the data area positions in accordance with the defined structure has been implemented. For this purpose, a respective button has been implemented in the Modules module. #2361
• An option to display the database occupancy level for inactive data tables and data tables and views which are available in the database but not in PLANTA has been added to the 000230 PLANTA Data Table module. #20324
• Updates of older DB releases in which newer tables are still missing have been made more secure by loading the data dictionary in a first step before the data for the new tables is imported. #21733
• The values in the listbox on the Action ID field in the Data Areas module have been supplemented by frequently used macros. #20679
• A new function has been added in the Data Dictionary module, with the help of which columns which do not yet exist in PLANTA project can be created as DIs. #20976
• Listboxes have been added to the Effect ID, Window, and Use filter on fields in the Option Module for MV. #21453
• Object Use
  • For Python macros as place of use, the IronPython script, the DF configuration, as well as process rules are checked.
  • For modules as place of use, both the belonging work areas (in which the module occurs) and menu items as well as user and roles with startup macros are checked.

Bug fixes

• The incorrect customizing of data table 974 SAP project structure/report has been fixed. #21235
• The use of the Object Use module has been improved and errors have been resolved, e.g.
  • the problem, that the traffic light DIs could not be found.
  • the error which occurred if the search string used to search for Python files generates a result which is too extensive. #20729 #20740 #20744
• The irritating Please check input status line message which was displayed during database consistency check has been removed. #20667
• The cause of the Python error message which occurred when trying to create an incarnation has been eliminated. #20054 #21012
• The Links without tooltip module variant has been removed from the Modules module. #20136
• The problem, that no input was accepted in the Variables for manual search lists field when creating new variables, has been fixed (the problem only occurred in DB 39.5.10). #21029
• Separate values are now used for the threshold values on the cost and effort traffic lights. The @G286 and @G287 variables are used for costs and the @G292 and @G293 variables for effort. #19980
  • In case you wish to continue the @G286 and @G287 variables for both costs and effort, please run the optional ChangeEffortThresholds migration packet after database update.

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	CreateMSSQLViews	Creates views which are required for the calculation of the recursive sums in the SAP-WBS tables in MSSQL =		#20514
Mandatory packet	AddPulseMappingTable	Inserts new tables for the hybrid implementation	Feature	#21604
Mandatory packet	AddPulseFlagForWebInterfaces	Inserts a new flag for web interfaces	Feature	#22130
Mandatory packet	AddQGDoneOnFieldForPL	Adds new Completed on: manager columns in DTs 804 and 463.	Feature	#21496
Mandatory packet	AddCtgConstraints	Adds the external keys of DT281-DT284 in DT280 to ensure that in the first mentioned data tables no records on the cost type groups exist which are not available in DT280.	Feature	#22092
Mandatory packet	AddFunctionalPortfolioId	Creates a new DI for the functional portfolio ID in DT870. At first, the functional ID is not contained in the user modules and cannot be changed. The function is scheduled for one of the following releases.	Feature	#20251
Mandatory packet	SetDfWithLengthOfResName	Extends the DF length of DI000246 and all dependent DIs (incarnations/exits) to 200. Adjusts the DF width of the respective data fields in all modules.	Feature	#20827
Mandatory packet	AddLiabilityPoolTable	Adds the new pool table DT559 for liability import.	Feature	#20491
Mandatory packet	ResolveSAPPSPAAEPacket	Sets the CreateTableSapPspAae migration packet (DB 39.5.10) to completed if the table it creates already exists.	Feature	#21059 #22409
Mandatory packet	AddMaxHoursColumnToEmployeePool	Creates the MAX_HOURS column for the Fast Creation of Employee Data for the new DI065035 Max. hours/day in the employee pool on the database.	Feature	#22158
Help packet	SetMaxHoursPerDay	Fills the Max. actual hours/day field for all existing employee resources (resource type = 1*) with the stored value in the maximum_work_hours_per_day global setting.	Feature	#22158
Mandatory packet	CreateCriticalPathDI	Creates DI064739 in DT463, with the help of which tasks are marked by the scheduling which lie on the critical path.	Feature	#21020
Mandatory packet	UpdateWorkFlag	Corrects the incorrect data produced by copying the absence data to the department resources.	Bugfix	#22092
Mandatory packet	ForceCtgCleanup	Runs the CleanupOldKoAGrFields migration packet if it has not yet been run during the update from Venus (DB 39.5).	Bugfix	#22278
Mandatory packet	CreateCriticalPathDI	Creates DI064739 in DT463, with the help of which tasks are marked by the scheduling which lie on the critical path.	Bugfix	#21020
Optional packet	ChangeEffortThresholds	Resets the variables for the threshold values of the cost and effort traffic lights used from DB 39.5.11 to those used prior to DB 39.5.11 @G286 and @G287.	Bugfix	#19980