Global Settings (Project) MOD009DJ5

Relevant project budget in portfolio environment

p_project_budget_portfolio_relevant

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: Cost/Effort values (costs/effort total from the current planning) are compared to the portfolio budget as relevant budget.

Use of Controlling Reports in the Portfolio

portfolio_use_controlling_reports

Values

• 0: Controlling reports are not used
• 1: Controlling reports are used

Show road map dates

show_roadmap_dates

Values

• 0: Roadmap dates are not displayed in the Project Core Data module
• 1: Roadmap dates are displayed in the Project Core Data module

Restrict selection for resource assignment

listbox_ressource_466

• 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 setting is used in the value range of DI051871 TDI: Restrict FC from DT467 Resource.

Change functional project ID globally

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

Edit Project Budget

p_project_budget_edit

Values

• 0 = pending: Manual input and maintenance is also possible at project and annual value level. The annual values are summarized on project level automatically. As soon as a value has been entered for a cost type group on annual value level, the value is overwritten on project level by the sum of the year values.
• 1 = Only annual values : Manual input and maintenance is only possible at annual value level. The project budget data fields on project level are output data fields. The annual values are summarized on project level automatically.
• 2 = only project values: Manual input and 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 current values in the project budget data fields. This requires that a baseline has been created for the project. The value update takes place when the Budget module is opened.
• 4 = only Approved values: Manual input and maintenance are neither possible at project nor at annual value level. Automatic adoption of the approved Approved values in the project budget data fields, provided that annual values of the project have been approved. The value update takes place when the Budget module is opened.

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.

Default value for project status

Values

• 0: Template
• 1: Active
• 2: Inactive:
• 9: Archive

Show WBS code instead of ID

show_psp_instead_of_id

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.

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.

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.

Load user-defined submodules

load_userdefined_submodules

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

PDF Export Path

Number of entries in quick start menu

quick_launch_amount

Here, the number of planning objects can be specified which is displayed under "Recently viewed" in the Benutzermenü.

The number of objects to be displayed is only checked upon session start, so that if within a session more objects than defined are opened, they will all be displayed under  Recently viewed .

SMTP Server Address

smtp_server_adress

If you want to use the PLANTA e-mail function (to directly send e-mails), you must store the IP of the smtp server (externally accessible address) here.

• 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.
    • For automatic password dispatch, the sender address must be adjusted in the template code of the smtp_server_adress parameter ( to do so, extend the parameter line). The template code field is filled with "no-reply@planta.de" by default.
    • The e-mail address of the currently logged-on user will be used as sender address for the dispatch of project information.
  • 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.

If the PLANTA e-mail function is used, it is possible to add a link to PLANTA project to e-mails via individual customizing. If you want to have this option implemented in your system, please consult your PLANTA contact person.

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.

Resource requests active

Values

• 1: 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 visible.
• 2: Project resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved on project level via the request/approval process.
• 3: Task resource requests/approvals are active, i.e. resources with activated Approval required parameter must be approved on task level via the request/approval process.

Note

• 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.
  • When changing the setting, existing approval exceedance will be marked as read. They can be looked at in the Approval Exceedance module.
• The parameter will be overwritten by the setting in the Resource requests field in the Project Core Data module.

Exclude requested resources from planning

resource_staffing_remove_req_res

Values

• 0: the requested resource will not be excluded
• 1: the requested resource is excluded

Resource requests: Time grid

resource_staffing_time_pattern

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)

Note

• The time grid setting also has an influence on default values for the display period of the time scale in the resource request modules.
  • Time scale start: Date of the first request
  • Time scale end:
    • 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.
  • When changing the setting, existing approval exceedance will be marked as read. They can be looked at in the Approval exceedance module.

Time recording variant

load_creation_variant

• 1: Simple time recording. Working hours per day are recorded below the scale.
• 2: Simple time recording with comment. Working hours per day are recorded below the scale 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.

Max actual hours/day

maximum_work_hours_per_day

Reverse posting variant

posting_cancelation

• 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).

 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!

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.