Skip to content

Run a Forecast#

The recording of unplanned costs and revenue changes is understood as a forecast.

These plan changes are initially presented as comprehensible proposals and can then be converted into binding plan budgets and plan revenues or reversed if necessary.

The forecasting process is an approval procedure that ranges from the recording of unplanned events to their planned and accepted budget effectiveness and, if necessary, back again.

In Microsoft Dynamics 365 Business Central1 the plan values in project plan lines are differentiated according to their line type: budget and billable to G/L accounts, items and resources and cost/sales amounts.

The forecast item table corresponds to their structure and therefore forms a rudimentary project plan line. In KUMAVISION factory365, these forecast items are supplemented by the project accounts in the same way as the project plan lines and can also be called up and edited in the project account schema.

Project Forcast post#

You can access the "Project forecast items" page via the hyperlink in the forecast fields of the project tasks or in the project chart of accounts. Alternatively, you can open it via a function call in the ribbon of the project plan lines.

Project forecast items are consecutive items that form a cost or sales amount as difference items per project, project task by line type: budget or billable for G/L account, item and resource with respective number and description.

Depending on the project account setup and type of line, project accounts for sales or consumption are determined. These can be edited. A forecast item is considered an unplanned value as long as it has not been registered.

Field Description
No. No. Specifies a consecutive number for the respective item.
Line type Indicates the line type of the items. A distinction is made between "Budget" and "Billable".
Project no.
Project task no.
Indicates the respective project number / project task number from which the item was created.
Project contract item no. Specifies the project contract item number of the project plan line during registration.
Accept The checkbox is deactivated for an active unplanned forecast. The item is therefore freely editable.

As soon as the item is registered, it can no longer be edited.

If the project plan line is deleted, the checkbox is deactivated again and the
item is freely editable again.
Kind Specifies the type that was set up in the activity type of the project task as the default value in the field: Use = Forecast and planning type: Article, G/L account, resource and forecast no..
No. Specifies the number of the article, G/L account, resource.

Note:
A project account setup is required for the project type, activity type and product posting group used.
Forecast purchase price Is determined from the difference value to the previous cell value. The subsequent project plan line receives this value as the cost price (MW) with quantity.
Forecast sales amount Is determined from the difference value to the previous cell value. The subsequent project plan line receives this value as the sales price (MW) with quantity = 1.
Forecast date Is initialized from the period start date of the forecast matrix. The planning date of the subsequently registered project plan line follows from this.
Description for argumentation Specification of an argumentation.

The argumentation is necessary for the registration of the item.
Consumption contr. Is preset according to the project account setup for the line type: "Budget" and is freely editable.
Consumption account Name Specifies the name from the field in the project account plan.
Sales account no. Is preset according to the project account setup for the line type: "Invoiceable" and is freely editable.
Sales account name Specifies the name from the field in the project chart of accounts.

Forecast Matrix#

Open the project task lines in the project via the ribbon. You can find the forecast matrix on the "Project task lines" page in the "Project forecast matrix" info tab.

The values in the matrix are filtered values from the project task. In the matrix, new forecast values can be entered or changed for the "Forecast budget" and "Forecast sales" matrix rows.

The value change of a matrix cell is determined as a further forecast item with the key to the project task, its activity type and the forecast type and number found there according to the date of the matrix cell. This results in a new forecast item by type and number, date and difference amount on a pre-assigned project account of the project task. The item is then freely editable and can also be registered individually after entering the reason.

Forecast registration#

The "Register project forecast items" function is available both in the project ribbon and on the "Project forecast" page for selected forecast items. To register, you need an argumentation and a project account.

Registering forms, groups several forecast items into a project plan line, sets the forecast item as accepted and writes the project contract item number of the plan line to the registered forecast items. The newly formed project plan line receives the order type "Deviation" and now forms the accepted plan change.

The registered forecast items have been accepted, have received a link to the project plan line and can neither be edited nor deleted. These items are now available as archive items.

The new project plan line remains editable and can be changed or deleted. Deleting the project plan line resets the forecast items, they are editable again and can also be deleted.


  1. Microsoft, Microsoft Dynamics, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies.