DT472 Load
From DB 39.5.12
DI000069 Resource
Name of the resource on which the selected load was created
Up to DB 39.5.12
DI000069 Resource name
Name of the resource on which the selected load was created
From DB 39.5.12
DI001517 Resource ID
Code (ID) of the resource on which the selected load was created
Up to DB 39.5.12
DI001517 Resource
Code (ID) of the resource on which the selected load was created
DI001395 Project ID
Technical ID of the project
DI041559 Project
Functional ID of the project to which the selected load record belongs
Customizing details
- The respective field 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 the user modules, the respective field is a listbox for selection of a project, e.g. for
manual posting of project costs.
Customizing details
- Unlike DI041559 which has the same name, DI041609 is an incarnation. It enables you to add a listbox for selection of a project to the respective field on project level.
DI041593 Task
Functional ID of the task or the WBS code of the task to which the selected load record belongs, depending on the setting of the
show_psp_instead_of_id global parameter.
Customizing details
- The DI is fetched from DT463 Task to DT472 via exit.
DI041611 Task
Functional ID of the task to which the selected load record belongs. In the user modules, the respective field is a listbox for selection of a task, e.g. for
manual posting of project costs.
Customizing details
- Unlike DI041593 which has the same name, DI041611 is an incarnation. It enables you to add a listbox for selection of a project to the respective field on load level in user modules.
DI060046 Task (functional)
Functional ID of the task or the WBS code of the task to which the selected load record belongs, depending on the setting of the
show_psp_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 the Standard, this field is hidden but can be displayed if necessary.
DI001509 Planned load
Initially planned load of the resource in the selected load record.
In the
Schedule module, the respective data field for the revenue and cost resources is named
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 by users with modification rights in the following modules:
- Schedule (project/proposal)
- The respective data field is hidden by default and can be displayed by the user if necessary.
- Task
- The respective data field is hidden by default and can be displayed by the user if necessary.
DI001510 Actual load
Actual load (hours actually worked) of the selected resource in the selected load record (= on the selected day).
- In the Schedule module, the respective field in the revenue and cost resources is named Actual costs, in the Cost Posting, Revenues Posting modules it is named Actual costs or Actual revenues.
The parameter can be edited by users with modification rights in the following modules:
From DB 39.5.14
- For regular resources, the value is either directly entered manually in the Time Recording module.
- or is calculated by the program from the times entered in the from/to fields.
- For cost and revenue resources, the Actual load values are entered in the Cost Posting or Revenue Posting modules. In these modules, the respective field is named Actual costs or Actual revenues.
From DB 39.5.13
For regular resources the value is either entered directly or manually
- depending on the global setting in the Time Recording module
- or is calculated by the program from the times entered in the from/to fields.
For cost and revenue resources, the Actual load values are entered in the Cost Posting or Revenue Posting modules. In these modules, the respective field is named Actual costs or Actual revenues. From DB 39.5.13
For regular resources, the value is either entered manually in the Work Reporting module in the course of time recording or calculated by the program from the times entered in the Reporting Hours Worked module.
For cost and revenue resources, the Actual load values are entered in the Cost Posting or Revenue Posting modules. In these modules, the respective field is named Actual costs or Actual revenues.
DI001511 Remaining load
Remaining load of the selected resource in the selected load record (= on the selected day).
In the
Schedule module, the respective data field for the revenue and cost resources is named
Remaining costs.
Remaining load means the planned load reduced by the actual load.
Details
- The remaining load values arise during calculation of the schedule. As a result, the Remaining effort value (DT466) is summarized and allocated to the individual load records in accordance with the stored load profile.
- Exception: Resources with MAN load profile. For this purpose, the remaining load value must be entered manually for each load record in the Remaining load field (Schedule module in the With load variant).
- 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.
- Warning: Here, different overload results may arise in the individual calculation of projects and recalculation (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 Load module variants
- Task in the Resources area
Up to DB 39.5.5
DI004327 Actual+remaining load
Total load of a resource
Calculation
From DB 39.5.13
DI001419 Actual costs
Actual costs of the selected resource in the selected load record (= on the selected day).
The revenue resource values in this field are actual revenues.
Details
- On load level, the actual cost calculation is done on the basis of resource reporting (Actual load) and respective conversion factors. In the 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 Actual 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.
From DB 39.5.5
DI001419 Actual costs
Actual costs of the selected resource in the selected load record (= on the selected day).
The revenue resource values in this field are actual revenues.
Details
- On load level, the actual cost calculation is done on the basis of resource reporting (Actual load) and respective conversion factors. In the 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 Actual 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.
Up to DB 39.5.5
DI001419 Actual costs load
Actual costs of the current load record of the resource.
The revenue resource values in this field are actual revenues.
Details
- Actual costs are determined in the calculation of the project schedule on the basis of resource work reporting (actual load) and respective conversion factors. For a description of the calculation procedure, see here.
Calculation
Note
- In PLANTA Standard, the values for cost and revenue resources are equal in the Actual costs load and Actual load fields since cost and revenue resources in PLANTA Standard always have conversion factor = 1 and their loads are planned in monetary units.
From DB 39.5.13
DI001413 Planned costs
Planned costs of the selected resource in the selected load record (= on the selected day).
The revenue resource values in this field are planned revenues.
Details
- On load level, the actual calculation of planned costs is done on the basis of planned resource load and respective conversion factors. In the 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.
From DB 39.5.5
DI001413 Planned costs
Planned costs of the current load record of the resource.
The revenue resource values in this field are planned revenues.
Details
- On load level, the actual calculation of planned costs is done on the basis of planned resource load and respective conversion factors. In the 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.
Up to DB 39.5.5
DI001413 Planned costs load
Planned costs of the current load record of the resource.
The revenue resource values in this field are planned revenues.
Calculation
Note
- In PLANTA Standard, the values for cost and revenue resources are equal in the Planned costs load and Planned load fields since cost and revenue resources in PLANTA Standard always have conversion factor = 1 and their loads are planned in monetary units.
From DB 39.5.13
DI001426 Rem. costs
Remaining costs of the selected resource in the selected load record (= on the selected day).
The revenue resource values in this field are actual 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.
From DB 39.5.5
DI001426 Rem. costs
Remaining costs of the current load record of the resource.
The revenue resource values in this field are actual revenues.
Details
- On load level, the actual calculation of remaining costs is done on the basis of planned resource load and respective conversion factors. In the 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 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.
Up to DB 39.5.5
DI001426 Remaining costs load
Remaining costs of the current load record of the resource.
The revenue resource values in this field are actual revenues.
Calculation
Note
- In PLANTA Standard, the values for cost and revenue resources in the Remaining costs load 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.
DI001432 Total costs
From DB 39.5.5
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.
Up to DB 39.5.5
Total costs of the resource for each load record
Calculation
Note
- The revenue resource values in this field are revenues.
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 by users with modification rights in the following modules:
DI001444 Completed
This parameter is currently without function.
DI001446 Time from
From DB 39.5.14
The parameter is no longer used in PLANTA Standard.
Up to DB 39.5.14
Time at which the work was started
Note
- Is only to be entered in the course of the entry of hours worked and serves to calculate the Actual Load
DI001447 Time to
From DB 39.5.14
The parameter is no longer used in PLANTA Standard.
Up to DB 39.5.14
Time at which the work was finished
Note
- Is only to be entered in the course of the entry of hours worked and serves to calculate the Actual Load
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 that has not been planned within the available capacity.
Notes
From DB 39.5.28
- The overload values are only conclusive if a replanning has been carried out for all planning objects upfront (the calculation of the schedule of the affected planning object 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.
Up to DB 39.5.28
The overload values are only conclusive if a replanning has been carried out for all planning objects upfront (the calculation of the schedule of the affected planning object 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.
Apart from the priority of the projects that share a resource at the same time in individual calculation, incorrect overload representation may also occur due to incorrect determination of the free capacity of the resource in individual scheduling. For details, see here.
Attention
- In some modules, overload values are displayed in days, so that rounding differences may occur in the displayed numbers, 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 cost type of the load records is applicable to the summarization of the costs to the cost type groups and to the display 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
From S 39.5.12
- The cost type can be changed both as default value in the master data of the resource (Default cost type) and on both levels 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.
- If the cost type of the resource assignment (DT466) is changed, it is transferred to all new load records (DT472) of the resource assignment. In order for the cost type to be applied to the existing load records as well, the schedule of the project must be recalculated. (NEW unloading no longer necessary).
- Exempt therefrom are actual load records and manually created load records (i.e. those with MAN load profile). They are neither changed during unloading nor during calculation of the project schedule and must be adjusted manually if necessary.
- If the default cost type of the resource is changed, the new value is used as a default value for all resource assignments (DT466) that are created afterwards. The cost type 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.
From S 39.5.2
- The cost type can be changed both as default value in the master data of the resource (Default cost type) and on both levels 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.
- If the cost type of the resource assignment (DT466) is changed, it is transferred to all new load records (DT472) of the resource assignment. 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 and subsequently be recalculated.
- Exempt therefrom are actual load records and manually created load records (i.e. those with MAN load profile). They are neither changed during unloading nor during calculation of the project schedule and must be adjusted manually if necessary.
- If the default cost type of the resource is changed, the new value is used as a default value for all resource assignments (DT466) that are created afterwards. The cost type 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.
The parameter can be edited by users with modification rights in the following modules:
- Schedule (project/proposal) in the With Load or Entire Schedule module variants (display must be activated)
- Task in the Resources area
- The respective data field is hidden by default and can be displayed 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.
From DB 39.5.0
DI001519 Load date
Date of the load record
Up to DB 39.5.0
DI001519 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 the pool table to the target
- Unknown status
- Status of the record is unknown
New from DB 39.5.7
DI003399 Exported on
Here, the date on which the export of the load record is carried out in PLANTA
link is entered automatically for each exported load record.
New from DB 39.5.7
DI003402 Exported by
Here, the user that carries out the export in PLANTA
link is entered automatically for each exported load record.
New from DB 39.5.7
DI063670 Imported on
Here, the date on which the export is carried out in PLANTA
link is entered automatically for each imported load record.
New from DB 39.5.7
DI063672 Imported by
Here, the user that carries out the import of the load record in PLANTA
link is entered automatically for each imported load record.
New from DB 39.5.13
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
Notes
- The cost center can be changed both as a default value (Default cost center) and on both levels 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.
- 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 and subsequently be recalculated.
- Exempt therefrom are actual load records and manually created load records (i.e. those with MAN load profile). They are neither changed during unloading nor during calculation of the project schedule and must be adjusted manually if necessary.
- 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.
The parameter can be edited by users with modification rights in the following module:
- Schedule module in the Entire Schedule or With Load module variants
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.
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: Display DA
DI040103 472: OLAP 1 - 040101
DI040104 472: OLAP 1 - txt
DI040537 Resource type
DIs no longer used from DB 39.5.0
The DIs listed below are no longer used from DB version 39.5.0.
DI001492 Work for resource
DI028469 Column
Column equates to the cost type group to which costs are summarized in the user modules. In the Standard, there are 5 columns equating to 5 cost type groups:
. 
