Project Setup#
Projects in Microsoft Dynamics 365 Business Central1 are dynamic business transactions that extend over a longer period of time. These can be planned, controlled and invoiced in detail with the help of activities and budgets.
You can track the use of working hours, machine running times and material for individual projects. This is managed via project tasks and their associated project plan lines, via which the expenses and revenues are managed.
A project consists of a three-tier structure:
| Stage | Description |
|---|---|
| Project | Bracket with the essential key data |
| Project tasks | Project tasks subdivide the project into different tasks, such as project management, incidental project costs, design and development, production, but also meetings, for example. |
| Project plan lines | Project plan lines represent the means for task completion such as items, resources, or even item |
The development of a project can thus be traced down to the smallest detail.
In addition, with the help of integrated invoicing in the Accounts Receivable & Sales and Accounts Payable & Purchasing modules, all related revenues and expenses are recorded.
The project structure and its processes are shown in a diagram below:
Establishment projects#
In the "Project setup" the necessary settings for the later project creation and implementation are made.
In the following the fields are explained to you on the basis of the table below:
Inforegister General#
| Field | Description |
|---|---|
| Automatic posting of project item prices | Cost changes are automatically regulated as soon as the batch processing "Stock reg. fakt. Sett. Prices" is executed. |
| Apply consumption link by default | Specify whether project items are linked to project planning lines by default. |
| Allow budget/billed line definition | Specifies whether the type of project lines can be "Budget and Billable" by default. |
| WIP Standard Method | Sets the default method to be used for calculating the circulating stock. |
| Default WIP booking method | Defines how to apply the default working capital method when posting the working capital in the G/L item. |
| Default project booking group | Sets the default booking group to be applied when creating a new project. |
| Logo position on documents | Sets the position of the company logo on the business documents. |
Inforegister numbering#
| Field | Description |
|---|---|
| Project numbers | Specifies the number series to be used for assigning the numbers of a project. |
| Project WIP numbers | Specifies the number series to be used for assigning the numbers of the project GDP documents. |
Inforegister plant engineering#
| Field | Description |
|---|---|
| Project type Dimension | If you define a dimension here, you can define in the project types which dimension value for the dimension should be assigned to a project by the system when assigning the project type. By setting project type dimensions, you can create analyses about your projects according to the dimension value. |
| Check resource qualification | When entering a resource in the project plan lines, the system checks whether the necessary qualifications for an activity type are available. The following selections are available: No check is made when resources are used Planning onlyWhen maintaining project plan lines, the resource is checked against the necessary qualifications Booking onlyIt is checked for the sufficient qualification at the time of booking Planning and BookingCombination of Planning Only and Booking Only |
| Sale position no. from project plan lines | If the check mark is set, the project task is transferred to the sales document as item no., otherwise the item is calculated individually for each order. |
| Use dimensions from project references | If the checkmark is set, the dimensions defined in the referenced project plan line are used instead of the standard dimension line determination of the tables concerned. |
The switch takes into account the following tables:
- purchase Row
- FA line
- FA Components
- Stock transfer
- Assembly order
- Assembly order items
Information register production#
| Field | Description |
|---|---|
| When the project status changes, automatically change the FA status to | You can use this switch to specify whether any existing production order should also be changed from status to status when the status of the project is changed, and if so, to which FA status. |
Inforegister Logistics#
| Field | Description |
|---|---|
| Create project storage location | For the procurement and logistics processes, you use this to specify whether the system should create a project storage location for each project. The project storage location hereby represents the place of performance of the project. |
| Stock entry | entry storage location code For the procurement and logistics processes you define here a warehouse from which the warehouse setup for the financial accounting is to be copied. The field "Stock entry one location code" can only be maintained if the storage location creation is activated ("Create project storage location"). |
| Preferred transit code | For the procurement and logistics processes, enter the transit code for the project warehouse transfer route here. The "Preferred transit code" field can be maintained only if the storage location creation ("Create project storage location") is enabled. |
| Preferred delivery code | For the procurement and logistics processes, enter the delivery agent code for the project warehouse transfer route here. The field "Preferred delivery code" can only be maintained if the storage location creation ("Create project storage location") is activated. |
| Preferred carrier transport code | For the procurement and logistics processes, enter the delivery agent transport type code for the project warehouse transfer route here. The field "Preferred delivery transport code" can only be maintained if the storage location creation ("Create project storage location") is activated. |
Inforegister Outlook ToDos#
| Field | Description |
|---|---|
| Step CRM task | If you are working without a project outline, use this field to specify the increment for creating new project tasks. |
| Separator CRM task | If you work without a project breakdown, use this field to specify the separator for creating new project tasks. |
| Counter CRM task | If you work without project breakdown, set the counter for creating new project tasks in this field. |
Inforegister Commitment#
| Field | Description |
|---|---|
| Smallest FA status for target cost consideration | Define here from which FA status the target costs are to be displayed as planned costs. |
Inforegister Version comparison#
| Field | Description |
|---|---|
| First archiving version no. | In this field, specify the first archiving number of a version number assignment. |
| If only in left version, If only in right version, If version identical, If versions different, |
If subordinate line differs You can use these fields to specify the visual display in the version comparison. You can choose from: None: Display in black font color (serves as an identifier that no deliberate setup has been done yet) Standard: Display in black font color StandardAccent: Display in blue font color Strong: Display in black font color, bold StrongAccent: Display in blue font color, bold Attention: Display in red font color, italic AttentionAccent: Display in blue font color, italic Favorable: Display in green font color, bold Unfavorable: Displayed in red font color, italic, bold Ambiguous: Displayed in yellow font color Subordinate: Displayed in gray font color |
| Compare only set up fields | With this switch you can globally define whether only set up fields should be compared or possibly individual comparison setups should be allowed via the "Version comparison field setup". If the switch is activated, individual comparison setups can be made via the "Version comparison field setup" via the "Consider in field comparison" column. If the switch is deactivated, the "Consider in field comparison" column is not editable. |
Project accounts#
In the projects for plant construction, consumption and sales postings are displayed on a project chart of accounts, which is used for project controlling. The selection of the corresponding project accounts is controlled via the project account setup.
Project Chart of Accounts#
The project chart of accounts is used for project controlling and contains all sales and cost accounts that are to be used for a differentiated project view. The project chart of accounts is not dependent on the FIBU chart of accounts.
In the "Account type" field you can choose between five options:
| Field | Description |
|---|---|
| Account | A bookable account can be selected. |
| Headline | Text line in which a heading can be entered as a structure feature. |
| Total | A sum defined by the "Total" field. |
| From-Sum | An initial marker for a totaling project account series that ends with the To Total account type. |
| To-Sum | An end marker for a totalizing project account series that starts with the From Total account type. The total is defined using the Totalization field. |
After you have set up the project account, select "Actions" > "Indent Chart of Accounts" in the ribbon. Then select the "Yes" option in the message window.
Project account setup#
The procedure is almost identical to setting up the posting matrix in the financial accounting area.
The project account setup determines the project accounts to which consumption and revenue are posted or budgeted in plant construction. The project account setup is a matrix that defines the consumption and sales accounts for product posting groups.
The project type is taken from the project card when accessing the project account setup. The activity type, on the other hand, is taken from the project task line.
If no match is found using the project type, activity type and product posting group, an error message appears.
Each project item is assigned either a consumption account or a sales account depending on its item type (consumption or sales). The field contents of the project item are used to determine the project account.
Project Roles#
The project roles define in the later projects which role (e.g. project manager) the resource takes in the respective project.
To define the project roles in advance, call them up via the user search. Via "New" in the menu ribbon you can create a new project role with the help of the table below.
| Field | Description |
|---|---|
| Code | Assign a meaningful abbreviation for the project role. |
| Description | Assign a description for the project role. |
| Type | Assign an applicable type. You can choose from the following: • Responsible • Project Manager • Sale to contact no. • Invoice to contact no. |
Service type#
It is important for the later task planning in the projects to set up the activity types. To do this, call up the activity types via the user search.
Via "New" in the menu ribbon you can define a new service type with the help of the table below.
| Field | Description |
|---|---|
| Code | Assign a meaningful abbreviation for the activity type. |
| Description | Assign a description for the service type. |
| Type | Specifies the type that the record is. You can choose from the following: • Account • Headline • Total • From-Sum • To-Sum |
| Counting up | Here you can now specify the interval or other filter specification of numbers of the service type. The results of the specified service type are added to a total balance. For the From sum or Heading type, this field must be left blank. For the To-total type, the field is automatically filled when the chart of accounts is indented. Only the types that are between a From total and a To total are added together. |
| Qualifications | Indicates the number of qualifications required for the service type. Via a LookUp on the number, qualifications can be assigned to the activity type and already existing ones are displayed to you. Further information on the subject of qualifications can be found in the section of the same name. |
| Usage | NoneThere is no task scheduling, the fields are not editable in the project task. Task planningYou can enter planning directly in the project tasks. ForecastThere is no task planning, the fields are not editable in the project task. BothYou can enter planning directly in the project tasks. |
| Type planning | Via the type of planning you determine the type with which the task planning is to be entered in the planning line. You can choose from the following: - Resource - Article - G/L account |
| Planning no. | Via the planning no. you determine, depending on the type of planning, with which account the task planning is to be displayed in the planning line. |
| Work type code | Specifies the work type code for the activity type. |
| Art Forecast | Specifies the type forecast for the service type. You can choose from the following: • Resource • Article • G/L account |
| Forecastnr. | Specifies the forecast no. in the context of the "Type Forcast" field. |
| Forecast work type code | Specifies the forecast work type code. |
| Cross country skiing articles | Identifies a project task with the assigned activity type as a "long-run item". |
Project types#
When creating a new project, you can define the type of project by assigning a "project type". Here you can already enter some data such as a project template, order type or similar.
To define the project types in advance, call up the project types via the user search. Via "New" in the menu ribbon you can define a new project type with the help of the table below.
| Stage | Description |
|---|---|
| Code | Assign a meaningful abbreviation for the project type. |
| Description | Enter a description for the project type. |
| Project booking group | Enter the project booking group for the project type to be used when assigning the project type. Please note that if the "Template project no." is maintained (see below), this information is ignored. (see below) this information will be ignored. |
| Project number series | Specify the project number series for the project type to be used when creating a project and assigning the project type. |
| Template Project No. | Specifies the project no. to submit the project for the project type. |
| Project type Dimension value | Specifies the dimension value for the project type. |
| Dimension code | Specifies the dimension code. |
| Dimension Value Prefix | Specifies the dimension value prefix. |
| Task breakdown | Specifies a task breakdown for the project type. Please note that if the "Template project no." is maintained (see above), this information is ignored. (see above) this information will be ignored. |
| Reserve | Specifies the reservation method for the project type. The following are available for selection: • Never • Optional • Always |
| Order type | In the project type, you can set up an order type for the creation of sales documents, if required. This will be used when creating the documents. |
Project breakdown#
The project structure helps you to enter and maintain your project tasks quickly and efficiently with predefined numbering.
Call up the "Project outline" via the user search.
Via "New" you can create a new project outline using the table and procedure below.
| Field | Description |
|---|---|
| Code | Define a unique code for the record here. |
| Description | Define a short description for the outline here. |
| Status | Indicates the status of the outline. The following are available for selection: • New • Certified • In development • Expired Note Please note that only project members with the status "Certified" can be used in the processes. |
To define the outline for the created dataset, call up the "Outline structure" menu item via the ribbon.
| Field | Description |
|---|---|
| Level | Level or indentation of the task. |
| Description | Enter a description for the layer here |
| Increase | Define with which intervals the system should assign tasks, 1 for one step, 10 for ten steps etc. Based on the increment, the Counter field is initialized. |
| Counter | Here you can define with which value the level should be started and how wide the level can be. For example, enter 001 if the layer can reach a maximum value of 999. Please note that the Project task field only has a maximum width of 20 characters. |
| Separator | Define a separator here, e.g. period, comma, hyphen |
| Count type | • Numeric • Alphanumeric please specify alphanumeric if your counter contains letters. |
| Bookable | Specify whether it is possible to post on the level |
| Example | Represents the current definition, as a project task. |
Project Document Text Template#
For easy editing/creation of the document texts in the projects, you can define project text templates in which you specify how and when which data record is to be printed in which document.
Note
Please note that pre- and post-texts on the project tasks are not passed on to subsequent documents. This is only possible with texts on project plan lines.
To do this, call up the "Project document templates" via the user search.
Via "New" you can create a new project document template using the table below.
| Field | Description |
|---|---|
| Project table | Use this field to specify for which table the definition is valid. The following selection is available: • Project Task • Project planning line |
| Line type | Use this field to specify for which line type the definition is valid. The following selection is available: • Budget • Invoiceable • Budget and Invoiceable |
| Position | In this field, specify how the definition is valid for which position. The following selection is available: • Pretext • Post text |
| Service Contract Offer | Printing In this field, specify whether the text should be printed on Service contract offer. |
| Service contract printing | Use this field to specify whether the text should be printed on the service contract. |
| Service offer printing | Use this field to specify whether the text should be printed on the service offer. |
| Service Order Printing | Use this field to specify whether the text should be printed on the service order. |
| Service Geb. Invoice Printing | Use this field to specify whether the text should be printed on the service invoice. |
| Service Geb. Credit Print | Use this field to specify whether the text is to be printed on the service credit note. |
| Service Geb. | Delivery Print In this field, specify whether the text is to be printed on the service delivery. |
| Service work ticket printing | In this field, specify whether the text should be printed on service work ticket. |
| VK offer pressure | In this field, specify whether the text should be printed on VK offer. |
| VK Order Printing | Use this field to specify whether the text should be printed on VK Order. |
| VK Geb. Invoice Print | Use this field to specify whether the text should be printed on VK Geb. Rechnung. |
| VK Geb. credit print | Use this field to specify whether the text should be printed on VK Geb. Gutschrift. |
| VK Blanket order printing | Use this field to specify whether the text should be printed on VK Blanket Order. |
-
Microsoft, Microsoft Dynamics, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies. ↩