Design of DB for forecasting values.

Question

Hi there,

I would like to listen to your suggestions about how I can design the tables if:

• I want to store Forecast and Actual values
• I don't need to track who makes the changes, because it will be the application.
• There will be data or several values for the same entity. Those records, some of them can be active and the rest will be put in quarantine and after a while, transfer to the archive.

Thank you for your answer in advance.

Regards,
Alvaro.

Answer 1

Hi @AC ,

Please refer to this: https://stackoverflow.com/questions/12392042/how-can-i-display-actuals-and-forecasts-in-the-same-period-in-a-report-without-i.
This is a similar thread.

Best regards,
Seeya

---

If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

It depends on the design of your "actual" tables. It is pretty standard to use the same table with a "modifier" or "period" to identify the values are forecast/budget values.

Answer 3

It's gonna be from the scratch. I'll have a table with the details of the entity, probably I'll use Temporal tables but for Forecast and Values, don't need to track all the data.