Below, you will find descriptions of the load parameters used in standard modules (load data fields)

DI000069 Resource

Name of the resource on which the selected load was created

DI001517 Resource ID

Code (ID) of the resource on which the selected load was created

DI001395 Project ID

Technical ID of the project to which the selected load record belongs

DI041559 Project

Functional ID of the project to which the selected load record belongs

Customizing details

  • The respective field in user modules is an output field. The ID is fetched from the project record (DI041317 in DT461) to the load record (DT472) via exit.

DI041609 Project

Functional ID of the project to which the selected load record belongs In input mode, a listbox for selection of a project is displayed on the respective field, e.g. for manual posting of project costs.

Customizing details

  • Unlike the eponymous DI041559, DI041609 is an incarnation. It allows you to add a listbox for selection of a project to the respective field at load level in user modules.

DI041593 Task

Functional ID or WBS code of the task to which the selected load record belongs, depending on the setting of the Show WBS code instead of ID global parameter.

Customizing details

  • The DI is fetched from DT463 Task to DT472 via exit.

DI041611 Task

Functional ID or WBS code of the task to which the selected load record belongs. In input mode, a listbox for selection of a task is displayed on the respective field, e.g. for manual posting of project costs.

Customizing details

  • Unlike the eponymous DI041593, DI041611 is an incarnation. It allows you to add a listbox for selection of a project to the respective field at load level in user modules.

DI060046 Task (functional)

Functional ID or WBS code of the task to which the selected load record belongs, depending on the setting of the Show WBS code instead of ID global parameter.

Customizing details

  • The DI is fetched from DT463 Task to DT472 via exit.

DI058231 Parent task name

Name of the parent task of the task to which the selected load record belongs.

DI058229 WBS code

WBS code of the task to which the selected load record belongs. WBS code marks tasks according to their hierarchic structure in the work breakdown structure.

DI001400 Position

Automatically incrementing position number which is allocated invisibly. Manual editing is not considered in this field.

Details

  • In standard, this field is hidden but the user can unhide it if required.

DI001509 Planned load

Initially planned load (hours worked or costs/revenues) of the selected resource in the selected load record (= on the selected day). In the Schedule module, the name of the respective data field for the revenue and cost resources is Planned costs.

Calculation

  • Planned load = Remaining load until the actual start date has been set.
    • If the actual start date has been set, Planned load remains unchanged while Remaining load is changed.

The parameter can be edited in the following modules by users with modification rights:

  • Schedule (Project/Proposal)
    • The respective data field is hidden by default and can be unhidden by the user if necessary.
  • Task 
    • The respective data field is hidden by default and can be unhidden by the user if necessary.

DI001510 Actual load

Actual load (hours actually worked or actual costs/revenues) of the selected resource in the selected load record (= on the selected day).

  • In the Schedule module, the name of the respective field for the revenue and cost resources is Actual costs, in the Post Costs and Post Revenues modules its name is Actual costs or Actual revenues.

The parameter can be edited in the following modules by users with modification rights:

  • For regular resources, the value is directly entered manually in the Time Recording module.
  • For cost and revenue resources, the Actual load values are entered in the Post Costs or Post Revenues modules. In these modules, the name of the respective field is Actual costs or Actual revenues.

DI001511 Remaining load

Remaining load (hours worked or costs/revenues) of the selected resource in the selected load record (= on the selected day). In the Schedule module, the corresponding data field for revenue and cost resources is named Remaining costs.

Remaining load means the planned load reduced by the actual load.

Details

  • The remaining load values are determined during Scheduling (Calculation of the Projects). As a result the Remaining effort value of the respective task resource is distributed to the individual load records (days or other time units). The way in which the effort is distributed is determined by the load profile stored on the task resource. For in-depth information on this subject as well as examples for effort distribution, please see Load Profiles and Load Distribution.
    • Exception: Resources with MAN load profile. In such cases, the remaining load value must be entered manually in the Remaining load field (Schedule in the With Load variant) for each load record.
  • If it is not possible to distribute the entire Remaining effort since the resource is already planned in other projects in this very period and the available capacity has already been exhausted completely or partially, the overload is indicated.
    • Caution: Here, different overload results may arise in the individual calculation of projects and replanning (calculation of all projects) depending on the priority of the projects. For more information, see Overload

The parameter can be edited by users with modification rights in the following modules (for resources with MAN load profile):

  • Schedule (project/proposal) in the With Loads and Entire Schedule module variants.
  • Task in the Resources area

Particularities

  • The distributed Remaining load values, in turn, are summed up below the scale per scale grid, e.g. per month, and in the line of the task resource below the scale. For further information, see Legend: Task Resource in the description of the Schedule module.
  • If the requests/approvals function is activated for resource planning, a red traffic light is displayed on the field below the scale when the approval limit is exceeded. 

DI004327 Total load

Total load of the resource. It is determined in the Calculation of the project schedule (manual input not possible).

Calculation

DI001419 Actual costs

Actual costs of the selected resource in the selected load record (= on the selected day). In the case of revenue resources, the values saved in this field are actual revenues.

Details

  • At load level the actual calculation of the actual costs is carried out based on the reporting of hours worked and the respective conversion factors. See the calculation below. In the subsequent calculation of the project schedule, the values are summarized to the resource assignment, the task, and the project.

Calculation

Note

  • In PLANTA standard, the values for cost and revenue resources in the Actual costs and Remaining costs fields are equal since cost and revenue resources in PLANTA standard always have conversion factor = 1 and their loads are planned in monetary units.
See also: Budget and Cost Planning in PLANTA project

DI001413 Planned costs

Planned costs of the selected resource in the selected load record (= on the selected day). In the case of revenue resources, the values saved in this field are planned revenues.

Details

  • At load level, the actual calculation of planned costs is carried out based on the planned resource load and the respective conversion factors. See the calculation below. In the subsequent calculation of the project schedule, the values are summarized to the resource assignment, the task, and the project.

Calculation

Note

  • In PLANTA standard, the values for cost and revenue resources in the Planned costs and Planned load fields are equal since cost and revenue resources in PLANTA standard always have conversion factor = 1 and their loads are planned in monetary units.
See also: Budget and Cost Planning in PLANTA project

DI001426 Remaining costs

Remaining costs of the selected resource in the selected load record (= on the selected day). In the case of revenue resources, the values saved in this field are remaining revenues.

Details

Calculation

Note

  • In PLANTA standard, the values for cost and revenue resources in the Remaining costs and Remaining load fields are equal since cost and revenue resources in PLANTA standard always have conversion factor = 1 and their loads are planned in monetary units.
See also: Budget and Cost Planning in PLANTA project

DI001432 Total costs

Total costs of the selected resource in the selected load record (= on the selected day).

Calculation

Note

  • The revenue resource values in this field are revenues.
See also: Budget and Cost Planning in PLANTA project

DI056942 Total costs by resource type

Total costs of the selected resource (except revenue resource) in the selected load record (= on the selected day). Is used in modules in which a comparison of costs and revenues is provided.

DI040999 Total revenues by resource type

Total revenues of the selected revenue resource in the selected load record (= on the selected day). Is used in modules in which a comparison of costs and revenues is provided.

DI001438 Comment

You can enter a comment text here.

The parameter can be edited in the following modules by users with modification rights:

DI001444 Completed

This parameter is currently without function.

DI001491 Overload

Overload of the resource per load record or as a sum of all load records (depending on the module)

Calculation

  • Remaining load value which has not been planned within the available capacity.

Notes

  • The overload values are only functionally conclusive if a replanning of all planning objects has been carried out upfront (the calculation of the schedule of the planning object in question alone is not sufficient) since replanning also considers the priority of the planning objects when loading the resources.
    • Example: Project A with priority 2 and project B with priority 1 share resource x at the same time. If project A is calculated individually first and then project B is calculated individually as well, resource x is loaded in project A first. The free remaining capacity, if there is any, is provided by project B, and if it is not sufficient for allocating the planned hours to project B, overloads are created. In replanning, projects are loaded reversely, starting with project B, followed by project A, so that possible overloads are displayed in project A, not in project B.
Caution
  • In some modules, overload values are displayed in days, so that rounding differences in the displayed numbers may occur, or the overload value is not displayed at all, although an overload record exists (e.g. for overloads of less than one day).

DI001518 Cost type

ID of the cost type of the load record

Details

  • The summarization of costs to the cost type groups and the visualization in cost and budget modules, e.g. in the Budget module, is based on the cost type of the load records.
  • The cost values of the load records on which the cost type is missing are not considered in cost and budget modules, e.g. in the Budget module.
  • Each new load record automatically inherits the cost type of the corresponding resource, however, it does not inherit the default resource cost type but the cost type from resource assignment level. Please observe further peculiarities of inheritance under Notes.

Notes

The cost type can be changed both as default value in the master data of the resource (default cost type) as well as at resource assignment and load level of a project (cost type of the resource assignment and cost type of the load) at any time. However, the impact of the changes must be considered.

  1.  Resource assignment level of a project: If the cost type of a resource assignment is changed,
    1. the new cost type will furthermore be applied to all new load records.
    2. the new cost type will be applied to existing remaining loads in the next calculation of the project schedule.
    3. this does not affect existing actual loads since the old cost type is retained and must be adjusted manually if necessary.
  2. Load level of a project: If the cost type is only changed on individual remaining load records, it keeps taking effect as long as the project schedule is not newly calculated, otherwise it will be overwritten with the resource assignment cost type gain. If actual loads with the changed cost type are created by recording hours worked or if the cost type is changed on already existing actual loads, the changed cost type will still be retained after calculation of the project schedule and will not be overwritten by the resource assignment cost type.
  3. Default cost type of the resource When you change the default cost type of the resource in the Master Data, a query is displayed asking whether the cost type of this resource is to be changed in resource assignments which exist in projects. 
    • If you answer the query with Yes, the new cost type will be changed in all existing assignments of this resource in all projects concerned. Consequently, the specifications made under item 1 Resource assignment of a project apply. 
    • If the query is answered with No, the cost type of the existing resource assignment will not automatically be changed but the new value will be used as a default value for all assignments of this resource which are furthermore newly created. 

The parameter can be edited in the following modules by users with modification rights:

  • Schedule (project/proposal) in the With Loads and Entire Schedule module variants (display must be activated manually).
  • Task in the Resources area
    • The respective data field is hidden by default and can be unhidden by the user if necessary.
  • Time Recording

Things to note in individual customizing

  • Since the loads inherit the cost type from the resource assignment, @DI001393 must be specified in the module customizing for the Cost type data field in the Default value parameter. Non consideration will result in incorrect (invalid) load records.
See also: Create and assign cost types

DI001519 Load date

Date of the load record

DI001525 Project name

Name of the project to which the selected load record belongs

DI001527 Cost type name

Name of the cost type of the selected load record. For detailed information on the cost type of the loads, see Cost type

DI001658 Task name

Name of the task to which the selected load record belongs

DI060750 SAP status

This parameter controls the locking of particular load records (DT472). This prevents load records from being changed retrospectively after import or export. Upon export and import of load records, PLANTA link sets a numeric value in the respective field. For the text value corresponding to the numeric value, please refer to DI061212 Export status].

DI061212 Export status

Here, the text for the DI060750 SAP status parameter is displayed.

Values

  • New record
    • The record is new in DT472 Load
  • Locked
    • The record was exported from DT472 to the pool table and is therefore locked for changes in DT472.
  • Transferred
    • The record was imported (transferred) from pool table to target table
  • Unknown status
    • Status of the record is unknown
See also: Interface template: Load Export

DI003399 Exported on

Here, the date on which the export is carried out in PLANTA link is entered automatically for each imported load record.

DI003402 Exported by

Here, the user who carries out the export in PLANTA link is entered automatically for each exported load record.

DI063670 Imported on

Here, the date on which the export is carried out in PLANTA link is entered automatically for each imported load record.

DI063672 Imported by

Here, the user who carries out the import of the load record in PLANTA link is entered automatically for each imported load record.

DI065292 Canceled/reverse posting

Marks the canceled postings (actual loads) and the corresponding reverse postings. For further information on reverse postings, please click here.

DI007783 Resource cost center

Code (ID) of the cost center of the resource load record

Details

Note

  • The cost center exists both as a default value (default cost center) and at both levels of a project (cost center of the resource assignment and cost center of the load).
    • If the default cost center of the resource is changed (DT467), the new value is used for all resource assignments (DT466) that are created afterwards. The cost center of existing resource assignments, however, is not changed automatically, but equates to the default cost type applicable at the time of insertion of the resource assignment. It must be changed manually if required.
    • If the cost center of the resource assignment (DT466) is changed, it is applied to all new load records (DT472) of the resource assignment in the calculation of the project schedule. In order for the cost type to be applied to the existing load records as well, the schedule of the project must first be unloaded (Edit → Unload schedule menu item) and subsequently be recalculated (Edit → Unload schedule menu item).
      • Actual load records and manually created load records (i.e. those with MAN load profile) are exempt. They are neither changed during unloading nor in the calculation of the project schedule and must be adjusted manually if necessary.

The parameter can be edited in the following module by users with modification rights:

  • Schedule, in the Entire Schedule module variant and With Loads

Things to note in individual customizing

  • Since the loads inherit the cost center from the resource assignment, @DI009063 must be specified in the Load data area in the module customizing for the Resource cost center data field in the Default value parameter. Non consideration will result in incorrect (invalid) load records.
See also: Create and edit cost centers

DI041078 Manager

Manager of the project to which the selected load record belongs

DI003394 Expenses, km, actual load <> 0

Customizing information

  • Parameter which is used to filter data in the customizing of various user modules that contain actual loads (postings).

DI040995 Period: Date (MON)

Monthly display for grouped display of loads per month, e.g. in the Check Reported Hours module

DI002694 Load month

DI008782 Code

DI009064 Current cost center for resource

DI040100 TDI: show DA

DI040103 472: OLAP 1 - 040101

DI040104 472: OLAP 1 - txt

DI040537 Resource type