The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help

Legends

This topic is a collection of all legends used in the entire PLANTA Wiki and serves as an including source.

Required Dates

Up to DB 14		Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Program Core Data).
From DB 14		Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data sheet (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).

Calc. Dates

Up to DB 12	Calculated dates	The bar color is defined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are determined in the calculation of the schedule of the respective planning object. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
From DB 12	Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
From DB 14	Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.

Actual Dates

Up to DB 12	Actual dates		Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
From DB 12	Actual dates		Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
From DB 14	Actual dates	The bar is white hatched. The background color depends on the Code of the planning object.	Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.

Master Milestones

Up to DB 12	Master milestones	with date delay without date delay	Tasks are defined as master milestones in the Schedule module.
From DB 12	Master milestones	without date delay with date delay	Tasks are defined as master milestones in the Schedule module.
From DB 14	Master milestones	without date delay with date delay	Tasks are defined as master milestones in the Schedule module.

Gates

Up to DB 14	Gates	Gate without date delay Gate with date delay Main gate/main milestone	Gates are master milestones of planning objects. Without date delay means: Total float 0 With date delay means: Total float < 0 Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
From DB 14	Gates	Gate without date delay Gate with date delay Main gate/main milestone	Gates are master milestones of planning objects. Without date delay means: Total float 0 With date delay means: Total float < 0 Gates are only displayed in the schedule module if the Schedule with gates checkbox has been activated in the Project Core Data in the core data module of the respective planning object.
From DB 12	Quality Gates		Quality Gates are the items given from the portfolio and are only displayed in planning objects if they are assigned to this planning object in the portfolio to which the planning object belongs.

Dates from Status Reports

Up to DB 12	Calculated dates from status report		Calc. start and Calc. end of the planning object from the selected status report.
From DB 12	Calculated dates from status report	The color of the bar equates to that of the project code (see the legend above), however, it is slightly lighter.	Calc. start and Calc. end of the planning object from the selected status report.
From DB 13	Calculated dates from status report		Calc. start and Calc. end of the planning object from the selected status report.

External Links

From DB 15		external links	outgoing incoming

From DB 15

external links

outgoing

incoming

Unchanged

		Float		Float is available if the calculated end date (Calc. end) of the planning object is earlier than the requested end date (Requested end).
		Date delay		A date delay occurs if the calculated end date (Calc. end) of the planning horizon is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
		Calculated project dates		Calc. start and Calc. end of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
		Calculated dates of the programs		Calc. start and Calc. end of a program are calculated by clicking on the calculation button or by selecting the respective menu item.
		Master milestone date delay		A master milestone date delay occurs if its Calc. end is later than its Latest end.

Project Legend (Complete)

ProjectsMOD0099G2 Projects2GroupingsMOD009ALG MyWatchlistMOD009AG3 MyWatchlistMOD009C9K (Program)

From DB 39.5.15

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates	The bar is white hatched. The background color depends on the Code of the planning object.	Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.
external links	outgoing incoming

From DB 39.5.14

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates	The bar is white hatched. The background color depends on the Code of the planning object.	Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) in the calculation of the schedule of the respective planning object.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

From DB 39.5.12

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates		Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

Up to DB 39.5.12

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates		Actual start and Actual end (if there is any, otherwise Latest time recording date) of a planning object. They are determined from the actual dates of the tasks (Actual start/Actual end) when calculating the schedule of the respective planning object.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	With date delay Without date delay	Tasks are defined as master milestones in the Schedule module.

Project Legend (Semi Complete)

MyPlanningObjectsMOD0099RB CriticalProjectsMOD009AIR

From DB 39.5.14

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates	The bar is shaded in white. The background color depends on the Project Code.	Actual start and, if available Actual end, otherwise Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

From DB 39.5.12

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	Without date delay With date delay	Tasks are defined as master milestones in the Schedule module.

Up to DB 39.5.12

Meaning	Color	Comment
Requested dates		Requested start and Requested end are defined in the Key dates area in the corresponding core data module (Project Core Data, Idea Core Data, Proposal Core Data, Program Core Data).
Calculated dates	The color of the bar is determined by the code of the planning object. Code A Code B Code C Code D Code E	Calc. start and Calc. end of a planning object are calculated by clicking on the calculation button or by selecting the respective menu item. In the Planning Objects (In Table Form) module, the code of planning objects is defined and can be changed; for projects and proposals this can also be done in the Project Core Data and Proposal Core Data modules.
Actual dates		Actual start and, if available, Actual end, in any other case the Latest time recording date of a project are calculated by clicking on the calculation button or by selecting the respective menu item.
Float		Float is available if the calculated end date (Calc. end) is earlier than the requested end date (Requested end).
Date delay		A date delay occurs if the calculated end date (Calc. end) is later than the requested end date (Requested end). The date delay bar immediately follows the bar for calculated dates and is customized with a color gradient so that the red color has various shades.
Master milestones	With date delay Without date delay	Tasks are defined as master milestones in the Schedule module.

Simulation Legend

From DB 39.5.14

Meaning	Color	Comment
Requested dates		Requested start and Requested end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Simulated dates	The color of the bar is determined by the selection made in the Color in simulation field.	Changed (simulated) dates (Simulation: start and Simulation: end) of a planning object
Calculated dates		Calc. start and Calc. end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Actual dates	The bar is shaded in white. The background color is determined by the selection made in the Color in simulation field.	Actual start and Latest time recording date of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.

From DB 39.5.13

Meaning	Color	Comment
Requested dates		Requested start and Requested end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Simulated dates	The color of the bar is determined by the selection in the Color in simulation field	Changed (simulated) dates (Simulation: start and Simulation: end) of a planning object
Calculated dates		Calc. start and Calc. end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Actual dates		Actual start and Latest time recording date of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.

Up to DB 39.5.13

Meaning	Color	Comment
Requested dates		Requested start and Requested end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Simulated dates	The color of the bar is determined by the selection in the Color in simulation field	Changed (simulated) dates (Simulation: start and Simulation: end) of a planning object
Calculated dates		Calc. start and Calc. end of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.
Actual dates		Actual start and Latest time recording date of a planning object in the simulation/road map. The dates stem from the status report which was used as a source for the simulation.

Task Legend

From DB 39.5.15

Symbol	Meaning	Color	Comment
	Task requested dates		Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
	Calculated dates of the tasks	Uncritical Critical	Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can be critical as well.
/	Milestones/ Master milestones	/ Without delay / With delay / With actual end	Without delay means: Total float 0 With delay means: Total float < 0
	Calculated dates of the summary tasks		A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
	Actual dates	The respective bars are white hatched if the Splitting parameter is deactivated, and gray hatched if the parameter is activated.	Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or by setting it manually.
	Latest dates		Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
	Task date delay		A date delay occurs if the Calc. end of a task is later than its Latest end.
	Overlapping		Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
	Calculated dates of the external tasks	Uncritical Critical	Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can be critical as well.
	Calculated dates of the external summary tasks
/	Milestones/master milestones of the external summary tasks	/ Without delay / With delay	Without delay means: Total float 0 With delay means: Total float < 0
	External link	outgoing incoming

From DB 39.5.14

Symbol	Meaning	Color	Comment
	Task requested dates		Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
	Calculated dates of the tasks	Uncritical Critical	Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
/	Milestones/ Master milestones	/ Without delay / With delay / With actual end	Without delay means: Total float 0 With delay means: Total float < 0
	Calculated dates of the summary tasks		A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
	Actual dates	The respective bars are white hatched if the Splitting parameter is deactivated, and gray hatched if the parameter is activated.	Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or by setting it manually.
	Latest dates		Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
	Task date delay		A date delay occurs if the Calc. end of a task is later than its Latest end.
	Overlapping		Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
	Calculated dates of the external tasks	Uncritical Critical	Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
	Calculated dates of the external summary tasks
/	Milestones/master milestones of the external summary tasks	/ Without delay / With delay	Without delay means: Total float 0 With delay means: Total float < 0

From DB 39.5.12

Symbol	Meaning	Color	Comment
	Task requested dates		Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
	Calculated dates of the tasks	Uncritical Critical	Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
/	Milestones/ Master milestones	/ Without delay / With delay / With actual end	Without delay means: Total float 0 With delay means: Total float < 0
	Calculated dates of the summary tasks		A summary task is a task in the structured schedule which consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
	Actual dates		Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
	Latest dates		Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
	Task date delay		A date delay occurs if the Calc. end of a task is later than its Latest end.
	Overlapping		Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
	Calculated dates of the external tasks	Uncritical Critical	Calc. start and Calc end of the external tasks are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
	Calculated dates of the external summary tasks
/	Milestones/master milestones of the external summary tasks	/ Without delay / With delay	Without delay means: Total float 0 With delay means: Total float < 0

From DB 39.5.11

Symbol	Meaning	Color	Comment
	Task requested dates		Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
	Calculated dates of the tasks	Uncritical Critical	Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
/	Milestones/ master milestones	/ Without delay / With delay / With actual end	Without delay means: Total float 0 With delay means: Total float < 0
	Calculated dates of the summary tasks		A summary task is a task in the structured schedule that consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
	Actual dates		Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
	Latest dates		Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
	Task date delay		A date delay occurs if the Calc. end of a task is later than its Latest end.
	Overlapping		Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
	Calculated dates of the external tasks	Critical Uncritical	Calc. start and Calc. end of the external tasks are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
	Calculated dates of the external summary tasks
	Milstones/master milestones of the external tasks

Up to DB 39.5.11

Symbol	Meaning	Color	Comment
	Task requested dates		Requested start and Requested end of a task can be defined in the corresponding data fields in the Schedule module or they can be entered directly and graphically in the Gantt chart.
	Calculated dates of the tasks	Uncritical Critical	Calc. start and Calc. end are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
/	Milestones/ Master milestones	/ Uncritical / Critical / With actual end	Uncritical means: Total float 0 Critical means: Total float < 0
	Calculated dates of the summary tasks		A summary task is a task in the structured schedule that consists of subtasks and summarizes them. Information on the summary task, such as duration and dates, is determined automatically from the sub-tasks.
	Actual dates		Actual start and, if available, Actual end, otherwise Latest time recording date of a task, are calculated from the respective dates of the resources assigned to the task by clicking on the calculation button or by selecting the respective menu item or it is set manually.
	Latest dates		Latest start and Latest end of a task are calculated by clicking on the calculation button or by selecting the respective menu item.
	Task date delay		A date delay occurs if the Calc. end of a task is later than its Latest end.
	Overlapping		Overlapping = Possible date delay of task successor when using soft links. For more information, see here.
	Calculated dates of the external tasks	Critical Uncritical	Calc. start and Calc. end of the external tasks are calculated by clicking on the calculation button or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
	Calculated dates of the external summary tasks
	Milstones/master milestones of the external tasks

From DB 39.5.13

	Calculated dates of the tasks from status report	Calculated dates of the tasks from status report Calc. start and Calc. end of the tasks from the selected status report.
	Calculated dates of the summary tasks from status report	Calc. start and Calc. end of the summary tasks from the selected status report.
/	Milestones/master milestones of the tasks from the status report

From DB 39.5.12

	Calculated dates of the tasks from status report	Uncritical Critical	Calculated dates of the tasks from status report Calc. start and Calc. end of the tasks from the selected status report.
	Calculated dates of the summary tasks from status report		Calc. start and Calc. end of the summary tasks from the selected status report.
/	Milestones/master milestones of the tasks from status report	/ Without delay / With delay	Without delay means: Total float 0 With delay means: Total float < 0

Up to DB 39.5.12

	Calculated dates of the tasks from status report		Calc. start and Calc. end of the tasks, the milestones, and the master milestones from the selected status report.
	Calculated dates of summary tasks from status report		Calc. start and Calc. end of the summary tasks from the selected status report

Utilization Diagram Legend

Utilization Diagrams Without Overloads

From DB 39.5.15

Meaning	Color	Comment
Planned load (remaining load) of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
Actual load of the resource(s)		The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, in turn stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet. The limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.

From DB 39.5.14

Meaning	Color	Comment
Planned load (remaining load) of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
Actual load of the resource(s)		The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, in turn stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet. The limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.

From DB 39.5.12

Meaning	Color	Comment
Planned load (remaining load) of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
Actually incurring load (actual load) of the resource(s)		The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of the resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

From DB 39.5.8

Meaning	Color	Comment
Planned load of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Planned code 1 to Planned code 5 columns.
Actually incurring load (actual load) of the resource(s)		The values for the histogram bar are taken from the Used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of the resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by utilization bars.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general basic load defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top margin of the bar will be visible despite overlapping by utilization bars.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

Up to DB 39.5.8

Meaning	Color	Comment
Planned load of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actually incurring load (actual load) of the resource(s)		The values for the histogram bar are taken from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load value defined for the resource in the Resource Data Sheet.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, again, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.

Utilization Diagrams With Overloads

From DB 39.5.15

Meaning	Color	Comment
Planned load (remaining load) of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actually incurring load (actual load) of resource(s)		The values for the histogram bars are calculated from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by load data.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by load data.
Overload of resource		The overload value displayed in the red bar in percentage is calculated from the availability of the resource (Summarized available capacity) and its planned load (Summarized planned).

From DB 39.5.14

Meaning	Color	Comment
Planned load (remaining load) of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actually incurring load (actual load) of resource(s)		The values for the histogram bars are calculated from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by load data.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load defined for the resource in the Resource Data Sheet. The limiting line at the top of the bar will be visible despite of overlapping by load data.
Overload of resource		The overload value displayed in the red bar in percentage is calculated from the availability of the resource (Summarized available capacity) and its planned load (Summarized planned).

From DB 39.5.12

Meaning	Color	Comment
Planned load of the resource(s) in projects	The color of the bar is determined by the code of the projects. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actual load of resource(s)		The values for the histogram bars are calculated from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by load data.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by load data.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.
Overload of resource		The overload value displayed in the red bar in percentage is calculated from the availability of the resource (Summarized available capacity) and its planned load (Summarized planned).

From DB 39.5.8

Meaning	Color	Comment
Planned load of resource(s) in the projects	The bar color is determined by the project code. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actual load of resource(s)		The values for the histogram bars are calculated from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by load data.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load defined for the resource in the Resource Data Sheet. NEWThe limiting line at the top of the bar will be visible despite of overlapping by load data.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.
Overload of resource		The overload value displayed in the red bar in percentage is calculated from the availability of the resource (Summarized available capacity) and its planned load (Summarized planned).

Up to DB 39.5.8

Meaning	Color	Comment
Planned load of resource(s) in the projects	The bar color is determined by the project code. Code A Code B Code C Code D Code E	The code is defined in the Project Core Data module of the respective project. The values for the histogram bars are each calculated from the Summarized planned code 1 to Summarized planned code 5 columns.
Actual load of resource(s)		The values for the histogram bars are calculated from the Summarized used column from the period records of the resource(s) (DT468). The values in the period records, however, stem from the working time recording of the resources (DT472).
Available capacity of resource(s)		The values for histogram bars are calculated from the Summarized available capacity column from the period records of the resource(s) (DT468). The value in DT468, however, comes from the general Available capacity defined for the resource in the Resource Data Sheet.
Basic load of resource(s)		The values for the histogram bar are calculated from the Basic load (factor value 3) column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general basic load value defined for the resource in the Resource Data Sheet.
Factor 4 of resource(s)		The values for the histogram bar are calculated from the Factor value 4 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 4 defined for the resource in the Resource Data Sheet.
Factor 5 of resource(s)		The values for the histogram bar are calculated from the Factor value 5 column from the period records of the resource(s)(DT468). The value in DT468, however, comes from the general value of factor 5 defined for the resource in the Resource Data Sheet.
Overload of resource		The overload value displayed in the red bar in percentage is calculated from the availability of the resource (Summarized available capacity) and its planned load (Summarized planned).

Resource/Task 1 Legend

From DB 39.5.14

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	The color of the bar is determined by the code of the respective project. For the meaning of the individual code colors, see the histogram scale.	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Calculated dates of the selected resource for the selected task in the selected project	The bar is white hatched.	Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.

From DB 39.5.12

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	The color of the bar is determined by the code of the respective project. For the meaning of the individual code colors, see the histogram scale.	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from working time recording of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.

Up to DB 39.5.12

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	The color of the bar is determined by the code of the respective project. For the meaning of the individual code colors, see the histogram scale.	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the working time recording of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.

Resource/Task 2 Legend

From DB 39.5.14

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	Upper bar part: The color of the bar is determined by the code of the respective project For the meaning of the individual code colors, see the histogram legend. Lower bar part: Uncritical task Critical task	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
Calculated dates of the selected resource for the selected task in the selected project	The bar is white hatched.	Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the working time recording of the respective resource (DT472) or edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Task date delay		A date delay occurs if Calc. end of a task is later than its Latest end.

From DB 39.5.12

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	Upper bar part: The color of the bar is determined by the code of the respective project For the meaning of the individual code colors, see the histogram legend. Lower bar part: Uncritical task Critical task	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Task date delay		A date delay occurs if Calc. end of a task is later than its Latest end.

From DB 39.5.11

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	Upper bar part: The color of the bar is determined by the code of the respective project For the meaning of the individual code colors, see the histogram legend. Lower bar part: Uncritical task Critical task	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Task date delay		A date delay occurs if Calc. end of a task is later than its Latest end.

Up to DB 39.5.11

Meaning	Color	Comment
Task requested dates		Requested start and Requested end of a task are defined in the Schedule module.
Calculated dates of the selected resource for the selected task in the selected project	Upper bar part: The color of the bar is determined by the code of the respective project For the meaning of the individual code colors, see the histogram legend. Lower bar part: Uncritical task Critical task	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item. Uncritical means: Total float > 0 Critical means: Total float 0 Since in PLANTA project the setting of requested dates on tasks leads to Total float = 0, tasks that do not necessarily lie on the critical path can also be critical.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Latest task dates		Latest start and Latest end of a task are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Task date delay		A date delay occurs if Calc. end of a task is later than its Latest end.

Resource/Task 3 Legend

From DB 39.5.14

Meaning	Color	Comment
Calculated dates of the resource for the selected task in the selected project	The color of the bar is determined by the code of the corresponding project. Code A Code B Code C Code D Code E	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project	The bar is white hatched.	Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Date of tasks, risks and opportunity measures and process steps		The date value for the bar is calculated: for the todo items from the Date (DT804) field for the risks measures from the Date (DT811) field for the opportunity measures from the Date (DT813) field for the process steps from the Date (DT499) field.

From DB 39.5.12

Meaning	Color	Comment
Calculated dates of the resource for the selected task in the selected project	The color of the bar is determined by the code of the corresponding project. Code A Code B Code C Code D Code E	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Date of tasks, risks and opportunity measures and process steps		The date value for the bar is calculated: for the todo items from the Date (DT804) field for the risks measures from the Date (DT811) field for the opportunity measures from the Date (DT813) field for the process steps from the Date (DT499) field.

Up to DB 39.5.12

Meaning	Color	Comment
Calculated dates of the resource for the selected task in the selected project	The color of the bar is determined by the code of the corresponding project. Code A Code B Code C Code D Code E	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Date of tasks, risks and opportunity measures and process steps		The date value for the bar is calculated: for the todo items from the Date (DT804) field for the risks measures from the Date (DT811) field for the opportunity measures from the Date (DT813) field for the process steps from the Date (DT499) field.

Resources/Task 4 Legend (since only in MOD My Todo Items, none from DB 12 tabs)

Meaning	Color	Comment
Calculated dates of the resource for the selected task in the selected project	The color of the bar is determined by the code of the corresponding project. Code A Code B Code C Code D Code E	Calc. start, and Calc. end of a resource in a task (resource assignment) are calculated by clicking on the calculation button in the toolbar or by selecting the respective menu item.
Actual dates of the selected resource for the selected task in the selected project		Actual start and last Latest time recording date of a resource in a task (resource assignment) are calculated from the reported hours worked of the corresponding resource (DT472) or are edited manually.
Date of todo items, risks and opportunity measures and process steps		The date value for the bar is calculated: for the todo items from the Date (DT804) field for the risks measures from the Date (DT811) field for the opportunity measures from the Date (DT813) field for the process steps from the Date (DT499) field.

Todo Items Legend

Symbol	Meaning	Comment
	Todo item date	The date value for the bar is calculated from the Date (DT804) field.

Migration Packets from S 39.5.17 Legend

Legend

indicates that the migration packet has not been executed yet.
indicates that the migration packet has run successfully.
indicates that the migration packet has failed. The failure of a migration packet may have several reasons:
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
  - If this is the case, the packet will not be changed. The packet is considered failed.
    - In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
    - If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
    - As a result, it is moved from the Failed/open packets area to the Completed Packets module.
- Many help packets check the customizing for problems.
  - If they fail, this means that the customizer must become active.
  - As a result, the positions listed in the logfile have to be checked and modified.
  - If the cause for the failure has been eliminated, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
NEW signalizes that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
NEW signalizes that this migration packet is not relevant for the current update type due to version dependencies.
means that this migration packet has been skipped. This status is not used at the moment.

Migration Packets up to S 39.5.17 Legend

Legend

signalizes that the migration packet has not been executed yet.
means that this migration packet has been skipped.
signalizes that the migration packet has failed. The failure of a migration packet may have several reasons:
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
  - If this is the case, the packet will not be changed. The packet is considered failed.
    - In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
    - If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
    - As a result, it is moved from the Failed packets area to the Completed Packets module.
- Many help packets check the customizing for problems.
  - If they fail, this means that the customizer must become active.
  - As a result, the positions listed in the logfile have to be checked and modified.
  - If the cause for the failure has been fixed, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
means that a migration packet has run successfully.

Attachments

Topic attachments
I	Attachment	History	Size	Date
png	A.png	r1	0.3 K	2015-06-18 - 10:46
png	AOBAus.png	r1	0.3 K	2020-02-21 - 10:47
png	AOBEin.png	r1	0.3 K	2020-02-21 - 10:47
png	ActDB12.png	r3 r2 r1	0.2 K	2018-10-19 - 10:34
png	ActDB14.png	r3 r2 r1	0.3 K	2020-02-24 - 10:45
png	B.png	r1	0.3 K	2015-06-18 - 10:46
png	C.png	r1	0.3 K	2015-06-18 - 10:46
png	CalcCritDB12.PNG	r2 r1	0.3 K	2018-10-09 - 09:41
png	CodeADB12.PNG	r1	0.2 K	2018-10-09 - 08:59
png	CodeADB14.png	r2 r1	0.2 K	2019-06-13 - 13:56
png	CodeBDB12.PNG	r1	0.2 K	2018-10-09 - 08:59
png	CodeBDB14.png	r2 r1	0.2 K	2019-06-13 - 13:56
png	CodeCDB12.PNG	r1	0.2 K	2018-10-09 - 08:59
png	CodeCDB14.png	r2 r1	0.2 K	2019-06-13 - 13:56
png	CodeDDB12.PNG	r1	0.2 K	2018-10-09 - 08:59
png	CodeDDB14.png	r2 r1	0.2 K	2019-06-13 - 13:56
png	CodeEDB12.PNG	r5 r4 r3 r2 r1	0.1 K	2018-10-09 - 09:05
png	CodeEDB14.png	r2 r1	0.2 K	2019-06-13 - 13:56
png	CodeHisto.png	r1	0.4 K	2015-07-17 - 12:09
png	CriticNew.PNG	r3 r2 r1	0.4 K	2018-01-18 - 11:32
png	D.png	r1	0.3 K	2015-06-18 - 10:47
png	DauerProjekt.PNG	r1	0.4 K	2015-07-23 - 13:02
png	E.png	r1	0.3 K	2015-06-18 - 10:47
png	ExtSum.PNG	r1	0.3 K	2015-09-10 - 19:09
png	ExtTA.PNG	r6 r5 r4 r3 r2	0.3 K	2015-09-10 - 19:14
png	ExtTAUncrit.PNG	r2 r1	0.2 K	2015-09-10 - 19:12
png	Faktor4.png	r1	0.4 K	2015-07-17 - 12:09
png	Faktor5.png	r1	0.3 K	2015-07-17 - 12:09
png	Grundlast.png	r1	0.3 K	2015-07-17 - 12:09
png	GrundlastAbDb8.png	r1	0.2 K	2016-08-31 - 03:30
png	GrundlastLinie.png	r1	0.2 K	2016-08-31 - 01:38
png	GrundlastLinieDB14.png	r2 r1	0.2 K	2019-06-25 - 08:47
png	GrundlastLinieDB15.png	r1	0.2 K	2020-02-21 - 10:40
png	HMS.png	r1	0.5 K	2020-03-05 - 13:19
png	HMSred.png	r1	0.4 K	2020-02-20 - 15:30
png	Ist.png	r1	0.3 K	2015-06-18 - 10:47
png	IstBel.png	r1	1.0 K	2015-07-17 - 12:09
png	IstHisto.png	r3 r2 r1	0.3 K	2018-10-19 - 10:21
png	IstTermine.PNG	r2 r1	0.3 K	2017-09-20 - 10:41
png	Kalk.png	r1	0.5 K	2015-06-18 - 10:47
png	KalkDB12.PNG	r3 r2 r1	0.4 K	2018-10-09 - 09:49
png	KalkExtDB12.PNG	r2 r1	0.3 K	2018-10-19 - 07:58
png	KalkExtSammelDB12.PNG	r1	0.2 K	2018-10-09 - 11:55
png	KalkExtredDB12.png	r1	0.3 K	2018-10-09 - 12:08
png	KalkPRDB12.PNG	r2 r1	0.4 K	2018-10-09 - 09:34
png	KalkPRDB14.png	r2 r1	0.3 K	2020-02-24 - 10:46
png	KalkPRG.PNG	r2 r1	0.4 K	2015-09-22 - 19:08
png	KalkPRVG.PNG	r1	0.6 K	2015-07-20 - 12:11
png	KalkPRVGDB12.png	r1	0.5 K	2018-10-19 - 11:18
png	KalkPRVGDB14.png	r2 r1	0.5 K	2020-02-24 - 13:21
png	KalkSB.PNG	r1	0.3 K	2015-07-22 - 12:02
png	KalkSBDB12.png	r3 r2 r1	0.3 K	2018-10-10 - 11:42
png	KalkSBDB13.png	r1	0.3 K	2018-12-13 - 14:25
png	KalkSim.PNG	r1	0.3 K	2017-09-07 - 09:06
png	Kap.png	r1	0.3 K	2015-07-17 - 12:08
png	KapLinie.png	r1	0.2 K	2016-08-31 - 03:02
png	KapLinieDB14.png	r2 r1	0.2 K	2019-06-13 - 14:12
png	KapLinieDB15.png	r1	0.2 K	2020-02-21 - 10:40
png	LampeGelb.png	r1	0.5 K	2015-07-23 - 12:12
png	LampeGrau.png	r1	0.6 K	2015-07-23 - 12:13
png	LampeGruen.png	r1	0.5 K	2015-07-23 - 12:13
png	LampeRot.png	r1	0.5 K	2015-07-23 - 12:13
png	LampeWeiss.png	r1	0.5 K	2015-07-23 - 12:13
png	Linie.png	r1	0.2 K	2016-08-31 - 03:08
png	MMSCritNew.PNG	r1	0.4 K	2018-01-18 - 12:47
png	MMSDB12.png	r1	0.3 K	2018-10-09 - 09:54
png	MMSDB14.png	r1	0.3 K	2019-06-13 - 13:22
png	MMSExtDB12.PNG	r1	0.3 K	2018-10-19 - 07:11
png	MMSExtDB13.png	r1	0.3 K	2018-12-14 - 10:07
png	MMSGrey.PNG	r1	0.3 K	2018-10-09 - 07:07
png	MMS_erl.PNG	r1	0.5 K	2015-09-11 - 18:33
png	MMS_krit.PNG	r2 r1	0.5 K	2015-09-11 - 18:09
png	MMSbig.png	r1	0.5 K	2020-03-05 - 13:19
png	MMSdoneDB12.png	r2 r1	0.3 K	2018-10-18 - 11:47
png	MMSextRedDB12.png	r1	0.3 K	2018-10-19 - 07:10
png	MMSredDB12.png	r2 r1	0.3 K	2018-10-09 - 10:18
png	MMSredDB14.png	r2 r1	0.3 K	2019-11-28 - 13:36
png	MMSredbig.png	r1	0.5 K	2020-03-05 - 13:19
png	MS.PNG	r1	0.5 K	2015-09-11 - 18:06
png	MS.png	r1	0.6 K	2015-06-18 - 10:47
png	MSCritNew.png	r1	0.4 K	2018-01-18 - 12:48
png	MSDB12.png	r1	0.3 K	2018-10-09 - 09:53
png	MSDB14.png	r1	0.3 K	2019-06-13 - 13:42
png	MSExternal.PNG	r1	0.3 K	2018-08-29 - 11:49
png	MSGrey.PNG	r1	0.3 K	2018-10-09 - 07:07
png	MS_erl.PNG	r2 r1	0.5 K	2015-09-11 - 18:34
png	MSdoneDB12.png	r3 r2 r1	0.3 K	2019-11-28 - 13:27
png	MSextDB12.png	r1	0.3 K	2018-10-19 - 07:10
png	MSextDB13.png	r1	0.3 K	2018-12-14 - 10:07
png	MSextRedDB12.png	r1	0.3 K	2018-10-19 - 07:10
png	MSgreen.PNG	r2 r1	0.5 K	2015-09-11 - 17:58
png	MSred.PNG	r1	0.5 K	2015-09-11 - 18:01
png	MSredDB12.png	r2 r1	0.3 K	2018-10-09 - 10:19
png	MSredDB14.png	r2 r1	0.3 K	2019-11-28 - 13:34
png	Milestone.PNG	r1	0.4 K	2015-07-17 - 17:20
png	Puffer.png	r3 r2 r1	0.2 K	2020-02-24 - 10:46
png	QG.png	r1	0.4 K	2020-02-20 - 16:02
png	Sammel.PNG	r1	0.3 K	2015-07-17 - 17:22
png	SammelExtVGDB12.png	r1	0.2 K	2018-10-19 - 07:02
png	SammelExtVGDB14.png	r1	0.3 K	2020-02-24 - 11:48
png	SammelVGDB12.PNG	r4 r3 r2 r1	0.2 K	2020-02-24 - 11:48
png	SammelVGSB.PNG	r1	0.3 K	2015-07-22 - 12:22
png	SammelVGSBDB12.png	r2 r1	0.2 K	2018-10-19 - 06:58
png	Sim.PNG	r1	0.2 K	2017-09-07 - 09:06
png	SymbolDreieck.png	r1	0.6 K	2015-07-23 - 16:00
png	SymbolHaekchen.png	r1	0.6 K	2015-07-23 - 16:00
png	SymbolLampe.png	r1	0.7 K	2015-07-23 - 16:00
png	SymbolLupe.png	r1	0.6 K	2015-07-23 - 16:00
png	Ueberlappung.PNG	r1	0.3 K	2015-07-21 - 17:06
png	Ueberlast.PNG	r1	0.3 K	2015-10-12 - 13:08
png	Unkritisch.png	r1	0.4 K	2015-07-17 - 17:19
png	VGKalk.png	r1	0.5 K	2015-07-17 - 17:19
png	VGueberkrit.PNG	r3 r2 r1	0.2 K	2020-02-24 - 10:46
png	Verzug.png	r3 r2 r1	0.3 K	2020-02-24 - 10:46
png	Wunsch.png	r1	0.3 K	2015-06-18 - 10:45
png	WunschDB14.png	r1	0.3 K	2019-06-13 - 12:58
png	aufgabenbeschreibung.PNG	r1	0.4 K	2015-07-21 - 17:05
png	kritisch.png	r1	0.3 K	2015-07-17 - 17:19

39.5 Venus Current EN

PLANTA project

PLANTA pulse

PLANTA project

Suche in Topic-Namen
Suche in Topic-Inhalten