The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>ReleaseNotes>DatabaseReleaseNotes>ReleaseNotesDB3957
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.7

Application

Features
  • General:
    • A new matrix diagram for risks was implemented in several modules.
    • Cost trend analysis and effort trend analysis charts show the current data of the entire project structure immediately after opening. Hence, you do not have to refresh by clicking on the button of the same name.
    • The capital value (NPV (without subprojects) and NPV) is now calculated automatically. In the case of an update from DB < 39.5.0 to DB > 39.5.0, please consider the following notes.
    • The Close/Reset menu item has been renamed Update/Reset. The menu item symbol has also been changed.
    • The new @date_time(dd.MM.yy HH:mm:ss) variable has been copied to the print text of the footer of the standard print module (009AFA), so that the current print time is now displayed in the footer.
    • The problem, that for user-defined Skins each text was in capital letters, has been resolved.

  • R1:
    • When changing the period in the My Activities module, the scale is now adjusted to the newly selected period as well.
    • The Report to unplanned tasks button in the Work Reporting module has been renamed Post to other projects/tasks.

  • R41:
    • Links
      • If external links exist in a project and the status is changed from "Active" to "Archive" or "Inactive" in this project or in the project to which the links lead, the external links are converted to external tasks.
      • A message has been implemented that indicates, upon existence of external links in a subproject that are to be detached from the structure, that external links exist and asks whether they are to be deleted.
      • A message has been implemented that indicates, upon copying parts of the schedule, that the part to be copied contains links to tasks that are not copied.
      • New control routines have been implemented that check, upon insertion of new links or changes to the model parameter whether such changes are possible with the current project relationships. If changes are not possible, respective dialog messages are displayed.
    • The Stakeholder module has been deleted from the Project panel. The functionality has been moved to the Project Core Data module. In the course of this, a new function has been implemented: Generate team from schedule.
    • The Controlling Reports function has been implemented.
    • If a process model was selected and activated in the Process Status module, it can be deleted completely as long as no process steps have been edited.
    • In the status line of the Schedule module, the Scheduling completed message is now displayed after completion of the scheduling.
    • In the status line of the Replanning (Calculation of all Planning Objects) module, the individual calculation phases are displayed one after another. After terminating the replanning, the Replanning completed message is displayed.
    • In the Risks and Opportunities module, the values of the subprojects (if available) are considered accordingly. I.e. all values displayed here are summarized values of the displayed projects and their subprojects (if available).
    • The sorting of the Actual effort, Remaining effort, and Total effort fields in the Schedule module has been adjusted analogously to the Budget, Status, and Progress modules.
    • On the Remaining effort field, a check has been implemented, preventing the manual editing of this field when a resource assignment with MAN load profile is made. This is indicated by a message.
    • In the Resource Plan module, an option for allocating the effort of the resource has been implemented.
    • The Delta View module has been renamed Deviations and has been repositioned. It can no longer be opened via the Schedule module, but is now contained in the Project panel as an individual tab.
    • When copying the entire project structure in the Copy Entire Project Structure module, external links that lie within the structure are copied now as well.
    • In the Deviations module, the bars for project requested dates, project actual dates, and float and delay values are included in addition to the bars for calculated dates.
    • When you try to subordinate an existing project, which is currently active, to another project as a subproject, a dialog message is displayed, pointing out that the project to be subordinated is to be closed. The subordination of an active project is therefore not possible.
    • Due to the merger of the End date and Milestones areas to the Dates area in the Status and Status Report module, an auxiliary module is provided with the help of which the estimates and comments entered in individual areas can be merged. This is necessary when updating to DB 39.5.7.
    • The Milestone Overview (Project) and Milestone Overview (Program) modules have been improved:
      • Display of milestones has been extended
      • (Master)milestones of subprojects can be compared to the main project
  • R60:
    • In the Change Request (Program) module, the approved/rejected grouping has been inserted in the Completed requests category.
    • Programs can only be archived (Status=9) or deactivated (Status=2) if all projects assigned to the program have already been archived (Status=9) or deactivated (Status=2).

  • R70:
    • In the Portfolio module, the Year virt. field has been adjusted, so that periods can now also be selected if no project has been assigned before.
    • The Objective contribution by groups _, _Objective contribution all groups, Projects by objective and risk contribution and Resource simulation buttons have been moved from the Portfolio Period module to the Portfolio module.

Bug fixes

  • General:
    • The performance of the object filter in modules of the Multi-project board and Cost overviews panels has been improved.
    • The problem, that the values of the Probable damage DIs were not calculated correctly in the current planning, and that Probable damage and Probable gross profit were not calculated correctly in the status reports, has been resolved. See also FixReportChanceCalculation migration packet.
    • The problem with the value range of DI061212 Export status that resulted from missing text constants has been resolved.
    • The problem, that the benefit values entered in the Project Core Data were not summarized to the Budget module if the manual cost input parameter was active, has been resolved.
    • The Python error message when trying to create and save a new module variant has been resolved.
    • The problem, that the Costs and Effort budget values in DT461 also contained the values of the deactivated cost type groups, has been resolved.
    • The problem, that opening a project via the Go to menu item caused a Python error message while the process model of another project was open, has been resolved.
    • The problem, that no replanning but only a capacity scheduling was carried out in the Replanning (Calculation of all Planning Objects) module, has been resolved.
    • The Python error message that occurred when changing the functional ID if the " ' " sign was used for the new ID, has been resolved.
    • The IndexError: list index out of range error message that occurred in certain constellations when using Extras Go to to open a project has been fixed.
    • The problem, that spaces could be saved when changing the functional ID, has been resolved.
    • The missing space in the {total_sent} / {amount_of_records} sent - {received} received - {failed} failed status message has been inserted.
    • The problem, that the access to particular projects does not work for resources the access code of which contains wild cards in the Access to projects field, has been resolved.
    • The IE: org.hibernate.TransactionException: commit failed- parent key not found error message that occurred when deleting recently posted costs in the Cost Posting module has been fixed.
    • The trace back error message that occurred when opening an archived project has been fixed.
    • The problem, that a project was able to assign itself as a subproject, has been resolved.
    • The problem, that in the project list of the projects, projects that were already assigned to a portfolio were displayed as well, has been resolved.
    • The problem, that no links were possible in projects that have been assigned to programs, has been resolved.
    • The problem, that projects that are dependent on other projects cannot be assigned to the programs, has been resolved.
    • The sporadically occurring problem with the PSP code update for structured tasks has been resolved..
    • The error message that occurred in the Check Reported Hours module when clicking on the Filter button while the Until field was not filled has been resolved.
    • The error messages that occurred if the Replanning (Calculation of all Planning Objects) module was opened, one of the projects displayed in the list was subsequently deleted in another session and the replanning was initiated in the first session afterwards has been fixed. In this context, a check has been implemented that prevents that deleted planning objects remain in the calculation list, or that a project is deleted during replanning.

  • R1:
    • The problem, that in the My Activities module only Calc. end and no Calc start was considered when filtering the tasks for the selected period, has been resolved.
    • The problem, that in the Reporting Hours Worked module, the behavior of the Actual load and from/to data fields differed in different records, has been resolved.
    • The problem, that when changing the absence reason from vacation to sickness in the Absence module, the respective field was set empty each time, has been resolved.
    • The problem, that sent info in the Info module cannot be marked as read by the sender and can therefore not be displayed in the recipient's mailbox, has been resolved.
    • The problem, that changing an already saved absence reason (e. g. Absence to Sickness) in the Absence module "reactivated" the availability of the respective resource on the day in question, has been resolved.
    • The problem, that when selecting an absence reason in the Absence module (e.g. maternity leave) only Absence or Vacation was displayed, has been resolved.
    • The problem, that the Send Info module can be opened several times in a row via CTRL + B, has been resolved.

  • R41:
    • Dashboard:
      • The problem, that the cost deviation in the Dashboard module was not displayed for all projects, has been resolved.
      • The Python error message resulting from an error in the value range of DI059708 has been resolved.
    • Project Core Data:
      • The Python error message that occurred in the Send Info module after clicking on the Send button has been resolved.
      • The problem, that after creating a new risk category, the category in the Category name of the Project Core Data module is not displayed, has been resolved.
      • The error message that occurred when clicking on the End evaluation button in the Idea Core Data, Proposal Core Data, and Project Core Data modules has been resolved.
      • The problem, that the Locked checkbox in the Proposal Core Data module was not editable and therefore reporting to proposals was not possible, has been resolved.
      • The problem, that the records in the Select Stakeholders module could be moved with Drag&Drop, has been resolved. Moving is no longer possible.
    • Budget :
      • The problem, that when using the manual cost input model parameter, the gross profit values entered in the Project Core Data module were not copied to the Budget module, has been resolved.
      • The problem, that the summarized values were not deleted accordingly on project level when using the p_project_budget_edit global parameter = 1 after deleting the budget values on the yearly tranches, has been resolved.
      • The problem, that the revenues were summarized from the wrong columns from DT472 (from the effort columns instead of the cost columns) to the revenue columns in DT461 and DT861, so that in the case of conversion factors > 1, wrong values were contained in DT461 and DT861, has been resolved.
      • The problem, that the values in the deviation fields in the Budget and Critical Projects modules differed, has been resolved.
      • The problem, that the summarized values on project level were not deleted, although all values in all yearly tranches were deleted, has been resolved.
      • The Python error message that occurred when opening the Budget module while the project_budget_approved_edit parameter in global settings was set to 1 has been resolved.
      • The problem, that the budget of the projects assigned to the program in the Budget (Program) module was not summarized to the Cost budget column (DI060180 and DI060493), but to the Program budget column (DI060178 and DI060491), has been resolved.
      • The problem with the display of cost/effort budget graphics in the Cost Reports and Effort Reports modules of the structured projects (only main project data was displayed) has been resolved.
    • Schedule:
      • The problem, that the data in the Milestone trend and Master milestone trend variants was not displayed immediately when changing to the variants, but only after saving in the Configure Trend Analysis module, has been resolved.
      • The problem, that the bars for actual dates were covered by the bars for calculated dates due to a wrong sequence of the bar DIs in the module customizing, has been resolved.
      • The problem, that users were able to open and edit tasks in the Task module, for which they have no rights, has been resolved.
      • The error message that occurred when saving after copying a new schedule to a new project in the Schedule module has been fixed.
      • The problem, that resources in the Schedule module have been assigned to tasks that have created reportings to non-planned tasks in the Reporting Hours Worked module but have not been saved, has been resolved.
      • The problem, that after changing the functional ID of a project the gates in the Schedule of this project are not displayed, although the Schedule with gates checkbox is activated, has been resolved.
      • Different period filters in different areas in the Utilization with Cause module were standardized.
    • Task
      • The problem, that the LB in the Resource name field in the Todo item area displayed the stakeholders of another project, has been resolved (Filter @D15 replaced by @L30).
      • The error message that occurred in the Task module when saving after adding a new task document has been fixed.
      • The problem, that no task documents could be created or saved, as well as the Exception listed below that occurred in this context, have been resolved.
        • Under Oracle: ORA-02291: Integrity constraint ([DB_USER].FKDT815ID441) broken - parent key not found or ORA-02291: Integrity constraint ([DB_USER].FKDT815ID441) broken - parent key not found
        • Under MSSQL: The INSERT instruction is in conflict with the FOREIGN KEY restriction 'FKDT464ID441'. The conflict occurred in the [DB_USER] database, table 'dbo.DT441', column 'DI000446'.
    • Include subproject into the structure:
    • Todo Items:
      • The Python error message that occurred when opening the Edit task context menu command has been fixed.
    • Microsoft Project :
      • The problem, that the export to MSP cannot run correctly due to a missing background module, has been resolved.
      • The problem, that incorrect data is displayed in the PLANTAProject vs. Microsoft Project module, has been resolved.
      • The problem, that structure tasks were displayed in the PLANTAProject vs. Microsoft Project module, has been resolved.
      • The problem, that after export the same message was written in the logfile several times (depending on how often it was output), has been resolved. Now the message is written once and the number of outputs is specified.
      • The ORA-02091: transaction was reset\nORA-02291: integrity contraint error message, that occurred when importing an XML file in the Microsoft Project module, has been fixed.
    • Status and Status Report:
      • The problem, that the trend arrows in the Status did not display positive trends, has been resolved.
      • The problem, that the trend arrows in the Status module displayed deviations immediately after the creation of a baseline if no changes had been made yet, has been resolved.
      • The problem, that in the Status module of the subprojects the status reports of the subprojects were not displayed, although they existed, has been resolved.
      • The problem, that for structured projects in the Status Report module, data of the parent project was partially displayed in the charts of the subprojects, depending on the project level from which the status report was opened, has been resolved.
      • The problem, that a project can be deleted despite assignment of a project status report to a portfolio status report, has been resolved.
      • The problem, that the costs in status reports varied if the status reports were created from different source modules, e.g. from the Status and Check Status Report Creation and Project Requests modules, has been resolved.
      • The problem, that costs and effort trend charts were only displayed if a baseline and a released status report existed, has been resolved.
      • The different length of the Category fields in the opportunity and risk tables (DT812, DT810) as well as in the respective report tables (DT872, DT831), which lead to a Python error message if values were entered in live tables that were longer than the length of the fields in the report tables, has been standardized. See also FixReportColumnLengths migration packet.
      • The problem with the wrong reference of the traffic light and the respective deviation values in the Dates area was resolved in the Status and Status Report modules. Now the traffic light refers to the worst of both deviation values (project end date or master milestone end date).
      • Cost trend and effort trend charts in the Status and Status Report modules can now be structured, i.e. in the respective charts the data of the selected project and summarized data of all of its subprojects is contained.
    • Deviations:
      • The problem, that the negative deviations were not displayed, has been resolved.
      • The problem, that the Number of deviating tasks field was calculated incorrectly, has been resolved.
      • The problem, that the tasks that did not contain any effort were marked as new as well (e.g. milestones), has been resolved.
      • The problem, that the Total effort field in the No longer exists in the current planning area did not contain values, has been resolved.
    • Risks/Opportunities
      • The problem, that the risks and opportunities deactivated or deleted in the Risks/Opportunities module are displayed in the Status and Status Report modules regardless, has been resolved.
      • The problem, that the values in the Probability and Possible fields in the Status module of the main project were not updated after the respective fields were changed in a subproject, has been resolved.
      • In Risks/Opportunities (Project) and Risks/Opportunities (Ideas/Proposal), the fields in the area bars that only display the sum values from all (active and inactive) risks and opportunities were replaced by new, correct project fields (DT461) to which the values from individual, only active risks and opportunities are summarized.
    • Project Application:
      • The sorting of the project phases in the Status Report and Project Application modules has been corrected. Attention: This applies to status reports/project requests that are newly created from now on. In those already created, the sequence remains the old one. See also AddMissingColumnsInDT877 migration packet.
      • The error message that has occurred in the Project Applications module when clicking on the Create project application has been fixed.
    • Process Status:
      • The problem, that the info that was sent from the Process Status module (e.g. when submitting the phase) was not displayed in the Inbox area but under Read info in the Info module, has been resolved.
      • The Python error message that was displayed in the Process Status module when activating a process model while a value that is neither a valid resource ID nor a valid Python ID that contains a resource ID was specified as a Placeholder in the Process Model Templates module.
      • The problem, that in the project request created via the Create project request process step in process model 8 (proposal) no costs and effort was displayed, has been resolved.
      • The error message that occurred in the Process Status module when assigning a process model to a project while another project was also open for process model assignment has been resolved.
      • The missing tree structure in the Completed phases area in the Process Status module has been added.
      • Problems with the part string search in the Resource name listbox in the Process Status module.
      • The problem, that when copying a project, the process steps of the source project are copied as well, has been resolved.
      • The problem, that a Python Exception message was displayed when you stored two records with identical data in the Cost Posting module and try to delete one of them, has been resolved.
    • Resource Requirements
      • The problem, that filtering by date via the from/to fields did not take effect, has been resolved.
    • Remaining Effort and Costs
      • The Python error message that occurred when trying to update the grouping has been resolved.
    • Earned Value Analysis: Divers problems have been resolved:
    • Overview and evaluation module
    • The problem, that the Object Filter module behaved erroneously if a filter was created for which no objects were found, has been resolved.
    • The problem, that after creation of a new resource via the Fast Creation of Employee Data module, the values of the from and to fields were not displayed in the Start period and End period fields of the Resources module, has been resolved.
    • The error message that occurred after clicking on the Include in chart button in the Cost Trend Analysis has been fixed.
    • The problem, that when canceling the release of a status report in the Check Status Report Creation and Project Applications, the This function is only available for released status reports. message was erroneously displayed, has been resolved.

  • R50:
    • The problem, that a multi-project manager can edit and delete requests without having request-manager rights, has been fixed.

  • R60:
    • The problem, that under MSSQL the project data is not summarized to programs after clicking on the Recalculate button in the Budget module, has been resolved.
    • The problem, that when carrying out a Replanning
, the budget and cost data of programs in the Budget module was not refreshed, has been resolved.
    • The problem of several entries in the user menu after pressing F7 has been resolved.
    • The error message that occurred in the Status module when creating a Program Status Report or a program baseline has been resolved.
    • The problem, that when creating a new program, the Program Core Data module was not displayed correctly, has been resolved.
    • The problem, that the Cost budget, Total effort, Effort budget DIs are not filled for programs, has been resolved.
    • The Unhandled Python Exception in macro 009AK2 Python error message that occurred when clicking on the Update button in the Program Application and Program Status Report modules has been fixed.
    • The problem, that the milestone/master milestone trend graphics in the Status module only displayed the values from the last status report, has been resolved.
    • The error, that the The planning object contains no load records. message was displayed when creating or releasing program status reports, has been fixed.

  • R70:
    • The problem, that when deleting a newly created, not yet used group in the Portfolio Listbox Values module, the One or several listbox values are already used in the portfolio evaluation criteria and risk checklists and can therefore not be deleted. message was erroneously displayed, has been resolved.
    • The problem, that when using the p_project_budget_portfolio_relevant global parameter = 1 under MS SQL, the project budget was not transferred to the Relevant column, has been resolved.
    • The problem, that in the Objective Contribution by Groups and Objective Contribution all Groups modules a Python error message was displayed if the Cost budget requested or Cost budget approved value was selected in the Bubble listbox in the Portfolio Analysis, Scoring module, has been resolved.
    • The problem, that the p_project_budget_portfolio_relevant under MSSQL did not work properly, has been resolved.
    • The problem, that in the Portfolio module in the Risks and Assigned planning objects areas different IDs were displayed for the same planning objects, has been resolved.
    • The problem, that the Client in the Portfolio Status Report module crashed when clicking in the empty chart, has been resolved.
    • The missing OLE symbol for the manual estimate (thumb right) in the Edit Portfolio Status Report module has been added.
    • The problem with non-existent data in charts in the Objective Contribution all Groups module, has been resolved.
    • The problem, that the source data for the charts was displayed in the Portfolio Overview module, has been resolved.
    • The error message that has occurred in the Portfolio Overview module when extending several portfolios has been fixed.
    • Problems with the deletion of portfolio assignments, the assignment of the portfolios to projects, and the opening of portfolios from the My Portfolios module have been resolved.
    • The error message that occurred in the Portfolio Analysis, Scoring module when clicking on the Objective contribution all groups and Objective contribution buttons has been fixed.
    • The problem, that when assigning a planning object to the portfolio, the "One of the selected projects is already assigned to a program." error message was erroneously displayed in the Assign Projects, Ideas, or Proposals to Portfolio module if none of the selected planning objects were assigned to a program, has been resolved.
    • The problem, that in individual modules in the Projects, Proposals, Ideas, and Programs panel, the assignment of objects to groups ... with portfolio assignment and ... without portfolio assignment is carried out incorrectly, has been resolved.
    • The problem, that in the Delete module project status reports are also displayed under program status reports, has been resolved.
    • The problem, that in the Portfolio Period module the links on planning objects for which the functional ID <> technical ID does not work, has been resolved.
    • The Python error message that occurred when trying to delete an evaluation criterion from the Evaluation Criterion module has been fixed.

  • Administration:
    • The problem, that the absence of the resources was not considered in the creation of the periods, has been resolved.
    • The problem, that after activating the Earned Value Analysis in the Model and Model Parameters module, the The planning object contains no load records. message was displayed, has been resolved.
    • The Python error message that occurred in the Cost Types module when pressing the F1 key while the Cost type class field was focused has been fixed.
    • The problem, that the required cost type group could not be activated, although all assignments to cost types were removed due to the existing but invisible assignment to cost types "-", has been resolved.
    • The problem, that when clicking on the Reset password button in order to reset a password, no feedback was given by the program if no entry was available for the smtp_server_adress parameter in the Alpha (120) field in the Global Settings, has been resolved.
    • The problem, that an e-mail address is not copied from the e-mail field to the Internal e-mail field in the Persons module, has been resolved.
    • The problem with the deletion of skills in the Skills module, has been resolved.
    • The problem, that the Resource field is not cleared after the resource ID change in the Resource ID Change module, and hence the resource ID change could be started again for the same resource, has been resolved.
    • The error message that occurred when opening the Planning Objects (in Table Form) module has been fixed
    • The problem, that when clicking on the Create status report button in the Check Status Report Creation and Project Applications module, status reports are created that do not contain the changes at the time of creation, has been resolved.
    • The problem, that in the Absence module (view module) the absence and vacation values that contained half days were rounded up to full days and thus displayed deviating values compared to the Absence module (editing module), has been resolved.

Customizing and Technology

Features
  • General
    • The following improvements have been made to the Check Database Consistency:
      • Hyperlinks:
        • Use (DI, DT, primary key) is corrected.
        • For hyperlinks that do not exist in the hyperlink DT, the ID in the reference DT is set to 0.
        • Non server-based hyperlinks without URL and name (text) are deleted.
        • For server based hyperlinks, the URL or the name is generated automatically.
      • I-texts:
        • Use (DI, DT, primary key) is corrected. "Object protection:
        • Logfile: "Datatable without rwd" was changed to "Datatable has protection DIs, but without values"
        • No more empty DTs are checked
        • Only DTs with a value in "pos_os" are checked (without pos_os, no object protection).
    • The DT listbox in the Data Dictionary module was extended by the variable name.
    • In DT806, the relation to DT463 was removed and the respective relations were added in the module customizing of the standard modules that use this table. If you use individual modules with these tables, their customizing must be checked and adjusted if necessary.
    • The behavior of the DF behavior parameter for data items of class 16 (Hyperlink) and for the background DI, has been changed.
      • When assigning a hyperlink data item to a data area, the value in the DF behavior is automaticaly set to "h".
      • When assigning the DI025581 background data item to a data area, the value in the DF behavior field is automaticaly set to "a", but can be changed manually afterwards.
    • If a DI is deactivated, it is displayed grayed-out in the Data Dictionary module and in the listbox on the DI field in the Data Areas module.
    • The Form editor menu item Define tab order has been removed.
    • The column type of DI059758 from DT324 has been changed from NUMBER to NUMBER(10,0).
    • For the creation of a status report, you can now use respective column names in the customizing instead of the DI numbers in SQL statements.
    • A dialog message that warns users when trying to reactivate data items deactivated by PLANTA has been implemented.
    • In the PLANTA Module Customizer, a new module (Object Use) has been implemented that serves to find the objects in the PLANTA customizer.
    • In the Database Schema Export module, a check has been implemented. If an incorrect or invalid path is entered, the Invalid path message is displayed.
  • PLANTA link:
    • The PLANTA link role has been revised and designed more user-friendly. For this purpose, some modules have been changed and new modules have been added.
    • In the current version, PLANTA makes two new interface templates available: Project import and Main project export.
    • In the Configuration module, individual mapping elements can be inserted subordinate to an existing mapping element via the new Insert child mapping button.
    • The validation mechanism has been improved: It is now checked whether one and the same module is used several times in a configuration (simultaneously in different functions, e.g. as source and target, or as pool and target).
    • The connection to an SAP system is established once, so that it can be used by different modules and does not have to be established anew each time a module is opened.

Bug fixes

  • General
    • Problems with adjusting the database schema, that occurred when updating the database from 39.4.4.0 to 39.5.x, have been resolved. The ModifySchemaTables migration packet was corrected.
    • The Python error message that occurred when clicking on the Open macro editing button in the Edit Board Settings module, has been resolved.
    • The problem with missing owner licenses on some standard objects, which e.g. entailed that no entry was found in the Wiki via F1, has been resolved.
    • The following error message has been fixed: Database schema does not match System Customizing / Data Dictionary: No DB lenghts specifications in DT: V_DT430_DT472 * Column: POS, Type: NUMBER * Column: SAP_STATE, TYPE: NUMBER.
    • The problem, that the Reload system customizing button was displayed after filtering in the Data Items module, has been resolved.
    • The problem, that the changes to the submodules (DT404) did not entail that the respective parent modules were displayed in the MOD listbox in the Modules or Modules of the Last 30 Days modules, has been resolved.
    • The Python error message that occurred in the Users module when clicking on the Reset password button while the smtp_server_adress parameter was not set correctly in the Global Settings module has been fixed.
    • The Python error message that occurred in the Check Database Consistency module when clicking on the Carry out check button while the Consistency check field was not filled has been resolved.
    • The Python error message that occurred in the Define Incarnation/Fetch Exit module when clicking on one of the two buttons while the Fetch DT and Fetch DI fields were not filled has been resolved.
  • PLANTA link
    • An error in PLANTA link, that lead to incomplete records being saved, has been resolved.
    • The problem with the wrong sorting when using the MtsExportPoolLoadModule Python module subclass and the sorted = 1 parameter, has been resolved.
    • The problem, that the Execution module was not focused when repeatedly selecting it from the context menu, has been resolved.

Migration Packets

Category Packet name Function Type
Mandatory packet DeleteIndices Deletes indexes that were adjusted and recreated during schema generation.  
Mandatory packet CreateDataitemsForAccountedReports Creates necessary DIs for the controlling reports  
Help packet PlaceholderCheckPacket Carries out a correction of the incorrect dash records in the course of a database consistency check  
Help packet HyperlinkCheckPacket
ItextCheckPacket 		Each carry out a correction of the incorrect hyperlinks and a correction of the incorrect I-texts in the course of a database consistency check  
Mandatory packet AddSchemaExtensions Creates indexes and constraints that do not result from the PLANTA customizing  
Mandatory packet UpdatePeriodAggregationQuery Resolves the problem, that the basic load in the Resource Planning module was only summarized to the next parent level. See also the migration packet of the same name in S 39.5.17  
Mandatory packet MoveTablesToDifferentSchema Moves the DT874 and DT875 tables from the Q3B schema to the Q5B schema and adjusts the automatic number for DI000443.  
Mandatory packet FixEarnedValueSubprojects Corrects the display of the Earned Value Analysis module data of the structured projects Bugfix
Mandatory packet AdjustWrongColumnLength Corrects the length of some columns  
Mandatory packet FixReportChanceCalculation Corrects the calculation of the Probable damage and Probable gross profit parameters in status report tables  
Mandatory packet DeleteInconsistentStandardData Deletes inconsistent standard data in order to secure the integrity of the database  
Mandatory packet SetOwnerLicenseForZZZRecords Changes all owner license entries ZZZ to 011  
Mandatory packet AddIndexesOnColumnsForDataTableListbox Adds indexes on columns, that are used in the data table listbox in order to improve the performance of loading the data tables.  
Mandatory packet DeleteStandardConstraintsAfterDBImport Deletes all standard constraints on the standard columns including Unique Constraints and primary keys.  
Mandatory packet UnloadAndReplan Carries out an unload and subsequently a replanning of all active planning objects after a DB update.
  • Note: If the packet fails, you have to check the status of the A_CreateConstraints migration packet. If there are still incorrect constraints, they must be corrected before the UnloadAndReplan migration packet is run again.
  
Help packet EnableConstraints Activates all constraints. It is only required for the validation of the non validated constraints after data correction if A_CreateConstraints failed. Subsequently changes the status of the A_CreateConstraints migration packet to completed. Must only be run after all data which was reported in A_CreateConstraints has been corrected.  
Mandatory packet A_CreateConstraints Creates constraints after the DB import
Mandatory packet DeleteStandardConstraints Deletes all constraints on the standard columns, except unique constraints and primary key before the DB import  
Mandatory packet AddMissingIndexes Adds missing indexes  
Mandatory packet CorrectOwnerLicense Corrects records with missing owner license  
Mandatory packet SetLanguageDT462 Adds language codes to the primary key of DT462  
Mandatory packet ShortenCRCColumns Shortens the length of the CRC fields in the hyperlink tables to 10 according to the length in the database  
Mandatory packet AddNewIndexes Creates new indexes for the improvement of the performance  
Mandatory packet ChangeLanguageOfPeriodCreation Optimizes the generation of resource periods  
Mandatory packet AddLogTimestampColumn Adds time stamp column in particular SQL queries  
Mandatory packet SetDistriblistEmpty Deletes all distribution list headers from DT405  
Mandatory packet AddNewRiskChanceSums Creates new columns for project risks and opportunities in DT461  
Mandatory packet AddMissingCostColumns Creates missing revenue and gross profit columns in DT835 Budget/Co/Benefit for each Year/Report  
Mandatory packet AddMissingColumnDT343 Creates the missing column (DI063743) in DT343 SQL procedure code  
Mandatory packet AddProjectPoolTable Creates data table 567 Project pool in the database  
Mandatory packet A_AddMissingColumnsInMP Adds new columns to DT566. For this purpose, see the 14635 entry.  
Mandatory packet B_AddMissingColumnValuesInMP Creates necessary values in the new columns in DT566  
Mandatory packet AddMissingColumnsInDT877 Adds missing columns in DT877 Object process/report. For this purpose, see the 14022 entry.  
Mandatory packet AddMissingColumnValuesInDT470 Adds values in the new Type column in DT470. For this purpose, see the 14504 entry.  
Mandatory packet AddAMissingColumnInDT470 Adds a new column (Type) in DT470 Cost type. For this purpose, see the 14504 entry.  
Mandatory packet FixCostTrendsAndEVA Corrects a view, that serves as a data source for cost trends and Earned Value Analysis. This resolves the problem that charts displayed planned costs in baselines and status reports for other reports Bug fix
Mandatory packet FixPeriodCreation Resolves the problem when creating the periods for resources the ID of which is longer than 20 characters  
Mandatory packet FixReportColumnLengths Corrects the field length of DI 008876 and 029636 in order to fix inconsistencies between status reports and live data  
Mandatory packet AddCostsLastReportPerYear Corrects incorrect calculations of benefit-costs and revenues-costs in the Objecive Contribution all Groups  
Mandatory packet AddIndexOnPoolTables Sets indexes on the Status and Transferred on columns in all pool tables in PLANTA link  
Mandatory packet AddNewInterfaceParameterFields Adds new interface parameters: Hidden and Locked
Mandatory packet AddNewStampFields Adds data fields in which the export/import user and the import/export date is stamped upon export/import of load records in PLANTA link  
Mandatory packet AddMissingListboxValueColumns Adds listboxes on the Object field of the mapping elements according to the mapping element type  
Mandatory packet AddNewInterfaceSQLObjects Creates new PLANTA link tables and columns  
Mandatory packet FixCrcColumnLength Corrects the column width of the crc columns in hyperlink tables  
Mandatory packet FixViewColumnLength Corrects the specification of the column length of "Pos" and "SAP state" in the V_DT430_DT472 view  
Mandatory packet FixProgramTrafficLights Fixes the problem, that the Cost Budget, Total effort, Effort budget IDs are not filled for programs which results in incorrect traffic light display in the Status and Program Status Report modules  
Mandatory packet CreateViewMapping Creates the MAP_DBA_VIEWS tables that are used in the Object Use module  
Mandatory packet CreateFederalStateColumn Creates the FEDERAL_STATE column in DT430  
Mandatory packet ExtendDescriptionColumn Enlarges the Description column in DT560  
Mandatory packet AddIndexesOnColumnsForModuleListbox Completes indexes for columns in connection with the MOD module listbox in the Modules module  
Mandatory packet DeleteUnnecessaryMigrationPackets Deletes the FixDT093ValueRanges and FixTimeBudgetMatrix migration packets  
Mandatory packet AddingProbabiltyAndDmgdimensionDIs Completes missing columns in the DT810, DT831 and DT461 tables that are necessary for the new risk charts  
Mandatory packet RemoveVersionColumn Removes the version column from the migration rule table. See also A_ReplaceOldFrameworkCustomizing, B_SucceedPreviousMigrationFramework, and ReplaceOldFrameworkCustomizingVenus. Feature
Mandatory packet FixV_EVA_VG Corrects the FixV_EVA_VG view  
Mandatory packet z_AdjustSchema Carries out adjustments to the schema  
Mandatory packet DeleteStandardConstraintsQ1BandQ2B Deletes all constraints to standard columns in Q1B and Q2B, except Unique Constraints and primary key  
Mandatory packet FixLoadAutoNumber Corrects the function for the creation of automatic numbers of work reportings  
Mandatory packet DeleteWrongOLEs Deletes wrong OLEs that have the same number  
Mandatory packet FixColumnPrecisions Corrects incorrect specifications on the column accuracy  
Mandatory packet DeleteStandardIndices Deletes indexes of UUIDs, that are subsequently created during schema generation after database import. Furthermore, some standard indexes that are no longer required are removed. Bug fix
Mandatory packet ZZZSetDatabaseVersion Sets the database version to 39.5.7  

         PLANTA project







 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl