Caution

  • Please note: the following topic only deals with standard ICOU. For information on the individual ICOU, please click here.

Update from DB 39.5.10 ≥ DB 39.5.11

Cost Recording on SAP WBS Elements

Notes

  • From DB 39.5.11, the costs are created on/imported to an account assignment element.
  • If you have already used the SAP WBS function in DB 39.5.10 and plan to update to DB 39.5.11, please contact your customer consultant. He/she will provide you with a migration packet which transfers the values created on the SAP WBS elements to a dummy account assignment element.

Update from DB 39.4.4.0 to DB 39.5.x

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.

Budget Modules: New Data Model

Information

  • With database status 39.5, the restriction to five cost type groups is canceled system wide and further cost type groups can be entered in the new DT280 table (Cost Type Groups module).
  • From this release on, all data fields that explicitly refer to a cost type group or that are based on these fields (virtually) are no longer supported by PLANTA.
  • In data tables DT281 to DT285, new data items have been created which map the data of each cost type group.
  • While in 39.4 five data items were grouped on one record, now five records are displayed in one of the new tables in 39.5.

Example

"Cost budget" per project:

  • DB 39.4 Earth
    • DT461 DI028309 Cost budget: int. personnel
    • DT461 DI028318 Cost budget: ext. personnel
    • DT461 DI028319 Cost budget: material costs
    • DT461 DI028324 Cost budget: investments
    • DT461 DI028329 Cost budget: Miscellaneous
  • DB 39.5 Venus
    • DT281 DI060178 Current cost budget (without SP) x 5 records

Budget Module in 39.4 Earth

Information

  • In 39.4, the cost type groups in this module were displayed horizontally and the Budget/Costs fields were displayed vertically.

Budget module in Earth (application)

Note

  • The data here stems from DT461 Project (or summarized from DT861 Project/Year). The table layout is created via form customizing.

Budget module Earth (module customizing)

Budget Module in 39.5 Venus

Information

  • In 39.5 this form has been dissolved and the display has been flipped – now, the cost type groups are displayed vertically and the Budget/Costs fields are displayed side by side. This enables the display of several cost type groups and also makes it easier for the user to display/hide fields.
  • The data for each project and cost type group are now located in DT281, the annual values are stored in data table 282. The summarization of the annual values to project level is done virtually via module customizing.

Budget module in Venus (user)

Budget module Venus (module customizing)

Customizing in Budget Areas of Other Modules

Note

  • The design of cost and budget areas of other modules must always be oriented towards that of the Budget module. This means:
    • Group headings like Costs and Effort are bold.
    • The Benefit+Revenues area is located below the effort.
    • The default font symbol is used (no grayed-out areas, or the like).

Budget Data Migration

Caution

  • Due to different data models you have to note the following when updating to DB 39.5.x:
    • Since there is no division into cost type groups but only a total value for project effort budget values in versions up to DB 39.5.0, it is migrated in the Budget (w/o SP) column of the Internal effort cost type group in versions from 39.5.0.
    • During migration, only approved annual values are transferred and summarized to the project. Annual values which are not approved are not considered.
    • Since benefit and revenue values in versions up to 39.5.0 in structured projects only exist per project and are not summarized, they are summarized to the respective fields (w/o SP fields) in 39.5.x and subsequently summarized to the structure fields in versions from DB 39.5.0.
    • From DB 39.5.0, the current project structure is displayed in the status reports. The displayed data, however, is that of the structure which has been active at the time of creation of the status report. This means: if a project has been detached from the structure afterwards, it will not be displayed in any of the status reports created up to this date, its values, however, will be displayed.

Update from version < DB 39.5.7 to version > DB 39.5.7

Parameter NPV

Information

  • In versions up to DB 39.5.7, the NPV and NPV (without subprojects) parameters were filled manually. The respective columns were real in PLANTA.
  • From DB 39.5.7, the parameters are calculated automatically by the program according to a stored formula. In the course of this, the columns were changed from real to virtual. However, the values input manually still exist in the database.

After the update, the old values can be accessed in the following way:

  • Create two new real DIs with column type = currency in DT461 in PLANTA.
  • Transfer the values from the old real data item columns DI023127 and DI041683 to the newly created columns directly on the database.

Estimates and Comments of the Status and Status Report modules.

Information

  • In database version 39.5.7, the End date and Milestones areas have been merged to a combined Dates area in the Status and Status Report modules.
  • As a result, only the estimate and comment values of one of the two data areas are further used. If the data of the other area is required as well, they can be fetched to the new fields after update via the Edit Status and Status Report Data module.