Forecast

This module allows you to define a forecast and track its objectives from Dolibarr. Once the forecast is defined, you can track its progress using graphs.

Overview

The module allows you to define forecast values ​​over a period and track their evolution.

To do this, we define an SQL query to retrieve the actual values ​​and compare them to the forecast as time progresses.

It is finally possible to make a configurable monitoring page accessible (we select the tables and curves that we wish to display) from the Dolibarr menus.

Settings

The module is not configured from the native administration page, but from the forecast definition page in the patas-tools menu.

Settings Menu

The module is configured via a menu. The choices are as follows: Forecast - menu title: Allows access to the forecasts as they were configured New Forecast: Allows you to create a new forecast List of Forecasts: Displays the list of defined forecasts and allows you to modify them Import a Forecast: Allows you to retrieve a forecast exported in XML format

How It Works

Creating a New Forecast

The screen for creating a new Forecast is divided into two parts:

The first section (on the right) allows you to define the forecast's presentation page: its title its position in a menu (or not) access rights...

The second part corresponds to the forecast data elements. an SQL query to track the actual targets you wish to monitor. the date field over which you wish to perform the monitoring periods. the type of period you wish to display (day, week, month, quarter, year). the date range (start and end) corresponding to the period you wish to monitor.

It is therefore necessary to have a good understanding of the structure of Dolibarr tables (or to contact a person or company with this expertise).

Please note, to bypass SQL injection protection, you should replace the word SELECT in your SQL query with #SEL#

Once this screen is validated, we arrive at the forecast in draft state

Forecast Edit Screen

You can modify the values ​​previously entered and specify whether you want to display the values ​​from the previous period. The example below shows the creation of new groups.

The left-hand setting will display the forecast in the native third-party menu.

The SQL query here selects the list of third-party data. The datec field here corresponds to the creation date of the third-party, but there are others that can be used in the table according to needs (e.g., update, etc.). The period from January 1st to December 31st and the monthly grouping will allow for monthly tracking of the progress of objectives. It will be possible to display the values ​​from the previous year.

Once the screen is validated, it is then possible to generate the periods according to the definitions. You will be able to select whether or not to display the previous year's values.

The [Edit Values] button at the bottom of the table allows you to enter the desired forecast values.

Entering Forecast Values

In our example, the number of new thirds will be forecasted at 2 each month except July and August. You can also enter additional information for the forecast as a reminder. As the forecast progresses, you can also enter a comment on the period covered.

Forecast Examples

Billing Tracking

1. SEL# sum(total_ht) from llx_facture

Tracking Receipts (and/or Expenses)

1. SEL# sum(amount) as tt from llx_bank where amount > 0 and fk_account = 1

Paramétrages d'affichage du Forecast

Once this entry is made, it will be possible to select the tables and graphs that you wish to view on the forecast page.

Graphique de corrélation (optionnel)

Lors de la création d'une fiche Forecast, il vous est demandé de sélectionner une requête SQL correspondant aux informations que vous souhaitez afficher.

Un nouvel onglet est également disponible uniquement lors de de la modification d'une fiche forecast : il vous permet de définir une requête SQL de corrélation. Cette requête secondaire permet d’ajouter une courbe supplémentaire dans les graphiques, afin de corréler les données affichées par la requête principale (requête SQL de la liste) avec les données issues de cette nouvelle requête.