Hi,

You should consider to formulate, with words, the business rules you need to apply. Because based on the 3 examples there is a lot of guessing required (like your "GHI" which ends before to start, assuming your dates are written in a consistent way adopting the American standard of MM/DD/YYYY).
Having an example is good, but it should then cover all the cases, otherwise you also need to write the business logic you would like to implement.

Overall, if you do join your "contract details" with a full time dimension using the start date and end date as join condition on the month (applying the required business logic you need as apparently you want to stop at the month before to end date), you can then easily do the split assigning Amount / number of months as the monthly amount for each row resulting from the join.

There is nothing in the product "generating" rows out of nowhere, therefore you need a query to generate those rows for you.

If you have your "contract details" in a table, and you have a time dimension in a different table, by joining them together, you can generate the rows you need.

Just to give you an idea of what I mean:

SELECT …

FROM "contract details" c, "time dimension" t

WHERE t.date BETWEEN c."start date" AND c."end date"

This will generate all the rows representing the various months of existence for a project. Of course you need to add the logic to handle the month level (depends on your time dimension), the logic you want on when it should finish (before the month of the "end date") etc.

If you can use full SQL with an Oracle database you can skip the "time dimension" part and make that one up with a select level from dual connect by level < 100 and then turn this into a time dimension with one month per row.

Depending on what your data sources are, you can do that directly in a query, or using a data flow if needed. Just in a workbook you will probably struggle because the modelling is too basic I would say (while the semantic model could handle that easily).