Global Settings (Project) MOD009DJ5

Access

PM Administration → Master Data → Project Settings → Global Settings

Information

In the Global Settings (Project) module you can configure global settings which are relevant only for the project area.
All global parameters used in the system, i.e. also parameters from other areas can be found in the Global Settings (All) module. In the description of the module in the PLANTA customizer help area you will find information on the editing and creation of global settings.

Note

If "0" is offered for selection as a parameter value and no value is defined for a particular parameter, it behaves as if it was set to "0".

E-Mail Dispatch

By clicking on the Test e-mail dispatch button, you can test the e-mail settings. A test e-mail will be sent to the logged-on user.

Parameter name	Parameter ID	Meaning and values	Default
System e-mail address	`default_email_sender`	Default sender e-mail address Usually the e-mail address of the user who is logged in is used as sender e-mail address. If the sender has no own e-mail address or if the e-mails are not sent from one person to another but are automatically sent by the system, e.g. in the course of a batchjob, the e-mail address specified here is used as sender e-mail address. This parameter is mandatory if you want to send your e-mail from PLANTA.
SMTP Server Address	`smtp_server_adress`	Here, the IP of the smtp server (the externally accessible address) is specified. This parameter is mandatory if you want to send your e-mail from PLANTA. If this parameter is not set, the E-Mail cannot be sent message is displayed when you try to send an e-mail from PLANTA. In order to guarantee reception and forwarding by the mail server, you may have to check or set particular settings of the mail server and client: Accepting and forwarding sender/recipient addresses. SPAM settings of mail server/mail client (e.g. in MS-Outlook, Lotus Notes). Possibly whitelists for sender and recipient addresses, mail host names/ mail host IP address. The SMTP server must support TLS. If the e-mail dispatch from PLANTA is used, it is possible to include a link to call up PLANTA project in the e-mails via individual customizing. If you want to have this option implemented in your system, please consult your PLANTA contact person. If no SMTP server is specified, `localhost` will be used by default.
SMTP Server port	`smtp_server_port`	Port on which the SMTP server listens This parameter is mandatory if you want to send your e-mail from PLANTA.	25
SMTP password	`smtp_password`	Optional: Password for authentication at the SMTP server
SMTP user name	`smtp_username`	Optional: User name for authentication at the SMTP server

Note

For information on the API which is used for e-mail dispatch, please click here.

Portfolio

Parameter name	Parameter ID	Meaning and values	Default
Relevant project budget in portfolio environment	`p_project_budget_portfolio_relevant`	The Relevant budget parameter in the portfolio environment controls system wide which project budget is relevant in the portfolio environment, i.e. which project budget is compared to the portfolio budget. Values 0 = Approved/Requested: Approved values from the current planning are compared to the portfolio budget as relevant budget. If no Approved value exists, the Requested value becomes the relevant budget. 1 = Project budget: Project budget values from the current planning are compared to the portfolio budget as relevant budget. 2 = Baseline: Baseline values (project costs/total effort from the baseline) are compared to the portfolio budget as relevant budget. 3 = Active status report: Costs SR / Effort SR values (project costs/total effort from the active status report) are compared to the portfolio budget as relevant budget. 4 = Total costs/effort from the current planning: Costs/effort values (Total costs/effort from the current planning) are compared with the portfolio budget as relevant budget.	0
Default portfolio image	`portfolio_default_image`	Here you can see the name of the image file which is used as default portfolio image. The default portfolio image is automatically inserted in the core data during the creation of a portfolio. The entered file must be located in the DefaultPicture directory. The Default.jpg default image is included in the scope of supply. If a new default image is defined as default image in this parameter, this new default image only applies to portfolios which will be created in the future. In existing portfolios which use the default image, the old default image will still be displayed.
Use of Controlling Reports in the Portfolio	`portfolio_use_controlling_reports`	Specifies whether controlling reports are to be used in the automatic assignment of status reports in the portfolio status. If they are not to be used, the last released status report from the respective project will be used. Values 0: Controlling reports are not used 1: Controlling reports are used	0
Show road map dates	`show_roadmap_dates`	If this parameter is activated, the dates of the last released road map are displayed in the Project Core Data module. If the project is assigned to several portfolios, the earliest roadmap dates will be displayed. Values 0: Roadmap dates are not displayed in the Project Core Data module 1: Roadmap dates are displayed in the Project Core Data module	1

Project

Parameter name	Parameter ID	Meaning and values	Default
Restrict selection for resource assignment	`listbox_ressource_466`	The parameter defines which resource types are displayed in the resource listbox (MOD009595). Values 0: Only the project team is displayed 1: All resource types (project team + internal employees, external employees, departments, skills) are displayed 2: The project team and all resources which are no resources and departments are displayed 3: The project team and departments are displayed The parameter does not influence the display in the revenue and cost resource listbox (MOD009BJC) The setting is used in the value range of DI051871 TDI: Restrict FC from DT467 Resource.	1
Change functional project ID globally	`change_project_functional_global`	Controls whether the functional ID is to be changed globally (e.g. also in already existing status reports). Values 0: The functional ID will not be changed globally 1: The functional ID will be changed globally	1
Edit Project Budget	`p_project_budget_edit`	Controls the input and maintenance of the project budget values (Budget (w/o SP), Requested (w/o SP) columns) and Liability values in the Budget module system-wide. Since Approved (w/o SP) values can only be edited and approved per year, they remain unaffected by this global parameter. The functions for transferring project budget values only apply to parameter settings 0-3. For further information, see the description of the Budget module. Caution Caution when changing the global setting for already existing project budget values. Depending on the initial global setting and the one to be applied, these values may get lost. When changing the global parameter, a message will be displayed which indicates the change. Please also note that a recalculation of the values is already carried out when the Budget module is opened. The values should therefore have already been checked when changing the global parameter. Values 0 = pending: Manual input/maintenance is possible at both annual and project level. Manual input at project level applies as long as no annual values are available. As soon as there are annual values, they overwrite the sum of the manually entered values at project level. 1 = only annual values: Manual input/maintenance is only possible at annual level. The annual values are automatically summarized at project level. 2 = only project values: Manual input/maintenance is only possible at project level. The project budget data fields at annual value level are output data fields. 3 = only baseline values: Manual input and maintenance are neither possible at project nor at annual value level. Automatic adoption of the Baseline (w/o SP) values in the project budget data fields, provided that a baseline has been created for the project. Exception: Liability column which behaves under this setting just like under setting 0. The values are updated when the Budget module is opened or after clicking on the Recalculate button. *4 = only Approved* values*: Manual input and maintenance are neither possible at project nor at annual value level. Automatic adoption of the approved Approved (w/o SP)* values in the project budget data fields, provided that annual values of the project have been approved. Exception: Liability column which behaves under this setting just like under setting 0. The values are updated when the Budget module is opened or after clicking on the Recalculate button.	1
Default project image	`project_default_image`	Here you can see the name of the image file which is used as default planning object image. The default project image is automatically inserted in the respective core data during the creation of a project, proposal, or idea. The entered file must be located in the DefaultPicture directory. The Default.jpg default image is included in the scope of supply. If a new default image is defined in this parameter, this new default image only applies for projects and proposals created in the future. In existing projects and proposals which use the default image, the old default image will still be displayed.
Default value for project posting type	`project_planning_default`	Default value for the posting type of the project Values 0: Actual postings up to the end of the current week: Recording of actual postings, actual costs, and actual revenues up to the last day of the current week. 1: Also future actual postings (overhead costs,...) Reporting of actual hours, actual costs, and actual revenues is also possible for future dates.	1
Default value for project status	`project_state_default`	Default value for project status Values 0: Template 1: Active 2: Inactive: 9: Archive	1
Show WBS code instead of ID	`show_psp_instead_of_id`	This parameter controls whether the functional ID of the task is displayed in the Task field instead of the WBS code. Values 0: the functional task ID is displayed in the Task field 1: The WBS code is displayed in the Task field. 2: The functional task ID is displayed in the Task field, which can be changed manually upon requirement Since the field is an output field by default, it must be changed to input field via customizing in order to be able to manually edit it. This must be redone after every database update.	1
Activate posting correction for PM profiles	`pm_booking_corrections_active`	If this parameter is activated, nocturnal postings are corrected for resource assignments with the global Load profiles for which underpostings/overpostings are corrected parameter, and during each scheduling, overpostings are corrected. 0 = The parameter is deactivated 1 = The parameter is activated
Load profiles for which underpostings/overpostings are corrected	`pm_booking_corrections_curves`	If the global Activate booking correction for PM profiles parameter is active, resource allocations with these load profiles are corrected. This should be a list with the names of the load profiles, separated by spaces
Use key date	`pm_booking_corrections_use_deadline`	Specifies whether the key date is used to correct underpostings (the global parameter "Activate booking correction for PM curves" must be active for this). 0 = The key date is not used, i.e. a check is made every night to see whether underpostings should be corrected 1 = underpostings are only corrected on the key date
Inherited project attributes	project_parameter_heredity	The template for this parameter lists project attributes or assigned objects that inherit their values in project structures from superordinate projects to sub-projects. Additional attributes can be included in the template if necessary. In PLANTA standard, the following project attributes are currently inherited: Project code, Cost center, Priority, Status, Customer, Customer manager, Planning type, Posting type , and Stakeholder. Caution: This global setting can only be found in the Global Settings (MOD009ABF) customizing module under Customizing → Master Data and can only be edited there.

Project Administration

Parameter name	Parameter ID	Meaning and values	Default
Update calendar: Number of years into the future	`calendar_shift_years_future`	This parameter serves to define by how many years the calendar is to be moved into the future if it is updated on a fix date. For more information, see the Calendar module. Here, a positive integer should be placed.	4
Update calendar: Number of years into the past	`calendar_shift_years_past`	This parameter serves to define by how many years the calendar is to be moved into the past if it is updated on a fixed date. For more information, see the Calendar module. Here, a negative integer should be placed.	-1
Load user-defined submodules	`load_userdefined_submodules`	Controls how the submodules of a main module are to be loaded. Values 0: in accordance with the customizing settings for submodules in the Display customizing parameter. 1: in accordance with the individual settings of the user in the Load parameter in the Further... module	1
PDF Export Path	`pdf_export_path`	Here, the path for the PDF export is stored which is triggered via the Extras → Generate PDF menu item. After selecting the menu item, a dialog is opened in which the target path defined here is displayed. You can consult it here, in the dialog, if necessary. If no path is defined in the PDF export path parameter, the desktop of the user will be used as a path (%HOMEDRIVE%%HOMEPATH%\Desktop). After confirmation of the default path or selection of another path, the export will be started. If the file already exists in the target, a respective dialog is opened. When printing the file, you can change different parameters like, e.g., format or paper size, via the print options.
Number of entries in quick start menu	`quick_launch_amount`	Here you can specify the number of planning objects which are displayed under "Recently viewed" in the User Menu. The number of objects to be displayed is only checked upon session start. If more objects than defined are opened within a session, they will all be displayed under Recently viewed .	10

Project Process

Parameter name	Parameter ID	Meaning and values
Default idea process model	`default_pm_model_idea`	These parameters control which process model is copied and pasted automatically when ideas/proposals/projects/requests are created. The ID of the required process model will be entered as a value.
Default proposal process model	`default_pm_model_intention`
Default project process model	`default_pm_model_project`
Default request process model	`default_request_model`

Resource Requests

Parameter name	Parameter ID	Meaning and values	Default
Resource requests active	`resource_staffing_is_active`	This parameter serves to set whether and in what context resource requests are to be active. The selected setting is automatically selected for newly created projects. Values 0: resource requests/approvals are inactive, i.e. all resources can be planned freely in the schedule. Modules and buttons which belong to resource requests/approvals are not visible. 1: Project resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at project level via the request/approval process. 2: task resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved at task level via the request/approval process. Note The parameter will be overwritten by the setting in the Resource requests field in the Project Core Data module. If the setting is changed retroactively, this change only affects projects which are newly created after the change has been made.	0
Exclude requested resources from planning	`resource_staffing_remove_req_res`	Specifies whether the requested (generic) resource will automatically be excluded from the planning when resource approval is applied. Values 0: the requested resource will not be excluded 1: the requested resource is excluded	1
Resource requests: Time grid	`resource_staffing_time_pattern`	Time grid within which resource requests can be created or approved. Values Set to months by default (value: 4). Depending on the selected time grid, the resources will be loaded with the corresponding load profile. 2: Day (PM_DAY load profile) 3: Week (PM_WEEK load profile) 4: Month (PM_MONTH load profile) 5: Quarter (PM_QUART load profile) Notes The time grid setting also has an influence on default values for the display period of the time scale in the resource request modules. Start of the time scale: Date of the first request End of the time scale: 2: Date of the first request + 27 days 3: Date of the first request + 96 days 4: Date of the first request + 364 days 5: Date of the first request + 454 days If the setting is to be changed after requests have already been created, a query will be displayed asking whether the existing requests are to be archived. The setting will only be saved upon confirmation. When changing the setting, the auxiliary `ApplyResourceRequestCustomizingChanges` migration packet, which adapts the modules to the selected setting, will be run automatically. When changing the setting, existing approval exceedance will be marked as read. You can see them in the Approval exceedance module.	4

Time Recording

Parameter name Parameter ID Meaning and values Default

Time recording variant

load_creation_variant

Controls the type of time recording in the Time Recording module
Values

1: Simple time recording. Hours worked are recorded below the time scale per day.
2: Simple time recording with comment. Hours worked are recorded below the time scale per day and a comment can be written for each entry.
3: Extended time recording (direct load recording) Working time is recorded directly in the load records. Several load records per day are possible.

2

Max actual hours/day

maximum_work_hours_per_day

This parameter serves to define the default value which will be stored when new employee resources (resource type = 1*) are created in the Max. actual hours/day field.

10

Reverse posting variant

posting_cancelation

Parameter for controlling the automatic Reverse Postings.
Values

0 = deactivate automatic reverse postings
1 = automatic reverse posting for exported loads ( SAP status = set)
2 = automatic reverse posting for approved loads ( Approval = set)
4 = automatic reverse postings for loads before the key date (if load date <= key date )
8 = automatic reverse postings for imported postings (Imported on or Imported by set or if there is a record in the pulse table in which PLANTA ID = UUID from DT472)

The parameter is a bitflag, i.e., should automatic reverse posting apply to multiple cases at once, the respective sum values must be used (e.g. "15" for automatic reverse posting in all cases mentioned above).

Show overview of possible combinations

Value	Export	Approval	Key date	Import
0	-	-	-	-
1	X	-	-	-
2	-	X	-	-
3	X	X	-	-
4	-	-	X	-
5	X	-	X	-
6	-	X	X	-
7	X	X	X	-
8	-	-	-	X
9	X	-	-	X
10	-	X	-	X
11	X	X	-	X
12	-	-	X	X
13	X	-	X	X
14	-	X	X	X
15	X	X	X	X

When you use the 4, 5, 6, 7, 12, 13, 14, 15 setting, the effect of the Time recording key date will virtually be softened. Data can be created manually before or after the key date and already existing postings can be corrected or deleted (e.g. incorrect ones). Automatic reverse postings are then created for them so that the changes can already be traced before the keydate. For this reason, the default value of 11 will be used in PLANTA standard, causing the effect of the key date to remain "hard".
Caution: If the value of this parameter is changed, the PLANTA service (PLANTA Server) must be restarted!

11

Hours to be worked and presence time

usage_plan_working_hours

Controls whether the hours to be worked function, the presence times function, or none of them is used in Time Recording.

Values

0: Hours to be worked function is deactivated and any customizing connected to it is switched off or hidden.
1: Trigger (not implemented)
2: Import (not implemented)
3: Hours to be worked function is activated and any customizing required for this is switched on/displayed in the respective modules.
4: Manual recording of presence time (time of arrival/leaving and breaks). Any customizing required for this is activated/displayed in the respective modules.

0