How to create and use project types
Product line
Standard
|Expert
Operating mode
CLOUD ABO
|ON-PREMISES
Modules
Services & CRM
Budget & Phases
Purchases
Resource Planning
Business Intelligence
Each project is assigned to a project type and assumes the properties of the project type.
You can find the project types in the folder Settings > Projects > Project types. The purpose of the project type is to predefine the properties of project groups. For example, you can specify whether the assigned projects are productive, you can predefine the currency and VAT type, or you can predefine allocations of payment types, users, service types, expense types or outlay types. For example, a project type can be used to summarize projects of individual branches.
To create new project types, right-click on the Project types folder and select New > Project type.
Description |
Description of the project type. Under this description, the project type is later assigned to the project |
Language |
If a language is set for the project type, projects apply the language of the project type. However, it is only useful to define a fixed language for the project types if the project types are used, for example, to represent country subsidiaries.
|
Currency |
Default currency saved for assigned projects. This value is assigned to the project when set on the project, but can be changed there. ??? |
VAT type |
Defaults to the default VAT type from the System settings, but can be overridden at this level. Defines the default for the assigned projects, on which the VAT type can be overridden. If the VAT type appears in green font, it has been overridden at this level. If it appears in black font, it corresponds to the saved default VAT type. |
Active |
Projects can only be assigned to active project types. |
Productive |
This setting controls whether the projects of this type are productive or unproductive. Can be used in evaluations, e.g. in Business Intelligence module. |
Users must be assigned to a project type |
Affects the projects available for entering per user (bearbeiter.erfprojekte). A distinction is made for each project type as to whether or not the user allocation is compulsory. If yes, the projects of this project type only appear in the drop-down list when the user is allocated directly to the project type or a project. If under System settings > Project > you activate the setting Users must be allocated to projects, this applies to all project types, regardless of whether or not this option is set on the project types. |
Defaults for services |
At this level, the information about external rate, cost rate, user rate and per diem can be explicitly defined for projects of this type. If set, these values overwrite the values in the rate table. |
Properties for the accounting extensions can be defined on the project type, which overwrite the information from the system controls and apply to all assigned projects. These settings appear in the hierarchy immediately after the System settings.
In addition, a payment type (for VESR data) can be assigned. This is used as a setting for the payment type on the project and is activated when the customer has not defined any payment type on the project.
Starting from version 5.8, the invoice has a derived attribute called DebiKurs. This calculates the exchange rate for the invoice relative to the client currency (instead of Vertec key currency).
If a separate client and a proprietory currency is set on the relevant project type under the FAR connection/Datenbank Fibu, the DebiKurs??? is calculated based on this currency. Otherwise, the posting (like in versions before 5.8) passes on the exchange rate to the Vertec key currency.???
Here, you can allocate users to the project type. This happens for the following reasons:
You can limit service types, expense types and outlay types on specific project types.
Service types, expense types and outlay types that are explicitly allocated to one or more project types only appear on the projects of the project types to which they are assigned. For all others, they no longer appear unless they are reallocated at the lower level via phase allocation. Service types, expense types and outlay types that are not allocated to any project types appear everywhere.
| Expression | Result | Class |
|---|---|---|
| <Projekt>.typ | Assigned project type | Project type |
| projekttyp->select(produktiv) | List of all productive project types | Projectt type (list) |
| <Projekt>.projekttyp For backwards compatibility. As of version 5.3, no longer used. |
0: productive, according to project type setting 1: unproductive, according to project type setting 2: if it concerns the product project type (created by conversion to version 5.3 and explicitly assigned if projects of the type productprojectwere assigned in an older version. |
Integer, calculated (only read access) |