Calculating total demands from two tables

[mazigazi]

Greetings,

I am somewhat lost how to approach this problem that I have. In essence I want to calculate demands per material for specific date based on the number of projects on that date. for this I have 3 tables

Project Consumption Table (showing how much of each material is consumed for each project):

Material	Project A	Project B
Material 1	10	5
Material 2	3	1

Please note that new projects and material will be added in the future and the table will update accordingly.

Production Plan Table (shows how many times are the projects being produced on a specific date):

Project	1.1.2023	1.2.2023	1.3.2023
Project A	1	2	3
Project B	2	0	3

This table shows how many times a specific project will be produced on that day. As with the project consumption table it is updated with new projects.

Material Demands table is where I need calculation help (Total material demands on specific date):

Material	1.1.2023	1.2.2023	1.3.2023
Material 1	Formula? Result would be 20	20	45
Material 2	5	6	12

I would love to have an elegant solution without summing different lookups (eg. Index match match + index match match) as in reality there are multiple dozens of different projects and hundreds of materials, so preferably adding new projects and materials to tables would not "break" the formula. I believe it should be possible to achieve this with a clever use of SUMPRODUCT, but I have rarely used it, so I don't know how to approach it.

If you need any additional info I'd be glad to provide it.

Thanks so much for your help!
Mazi

 

[Automatrix]

You can do this using Power Query, if you re-arrange the first two tables a bit. Then it's a Full Outer merge on Project between them, yielding a table that has a line for each material-date combination, and then it's just calculations.

Book1
	A	B	C	D	E	F	G	H	I
1	Consumption
2	Material	Project	Per project		Material	Project	Per project	Date	Number
3	Material 1	Project A	10		Material 1	Project A	10	01/01/2023	2
4	Material 2	Project A	3		Material 1	Project A	10	01/02/2023	2
5	Material 1	Project B	5		Material 1	Project A	10	01/03/2023	3
6	Material 2	Project B	1		Material 2	Project A	3	01/01/2023	2
7					Material 2	Project A	3	01/02/2023	2
8	Plan				Material 2	Project A	3	01/03/2023	3
9	Project	Date	Number		Material 1	Project B	5	01/01/2023	2
10	Project A	01/01/2023	2		Material 1	Project B	5	01/02/2023	0
11	Project A	01/02/2023	2		Material 2	Project B	1	01/01/2023	2
12	Project A	01/03/2023	3		Material 2	Project B	1	01/02/2023	0
13	Project B	01/01/2023	2		Material 1	Project B	5	01/03/2023	3
14	Project B	01/02/2023	0		Material 2	Project B	1	01/03/2023	3
15	Project B	01/03/2023	3
Sheet3

 

[mazigazi]

You can do this using Power Query, if you re-arrange the first two tables a bit. Then it's a Full Outer merge on Project between them, yielding a table that has a line for each material-date combination, and then it's just calculations.

Book1
	A	B	C	D	E	F	G	H	I
1	Consumption
2	Material	Project	Per project		Material	Project	Per project	Date	Number
3	Material 1	Project A	10		Material 1	Project A	10	01/01/2023	2
4	Material 2	Project A	3		Material 1	Project A	10	01/02/2023	2
5	Material 1	Project B	5		Material 1	Project A	10	01/03/2023	3
6	Material 2	Project B	1		Material 2	Project A	3	01/01/2023	2
7					Material 2	Project A	3	01/02/2023	2
8	Plan				Material 2	Project A	3	01/03/2023	3
9	Project	Date	Number		Material 1	Project B	5	01/01/2023	2
10	Project A	01/01/2023	2		Material 1	Project B	5	01/02/2023	0
11	Project A	01/02/2023	2		Material 2	Project B	1	01/01/2023	2
12	Project A	01/03/2023	3		Material 2	Project B	1	01/02/2023	0
13	Project B	01/01/2023	2		Material 1	Project B	5	01/03/2023	3
14	Project B	01/02/2023	0		Material 2	Project B	1	01/03/2023	3
15	Project B	01/03/2023	3
Sheet3

This would be a possible solution, however I would wish to avoid Power Query, to have a lean live solution and to be able to input some additional logic to demand table (One-Time event demands, scrap based on supply etc.)

 

[mazigazi]

Also, headers with dates are dynamic always showing from - 6 months to +36 months, which you cannot have in "real table" headers.

 

[Automatrix]

Also, headers with dates are dynamic always showing from - 6 months to +36 months, which you cannot have in "real table" headers.

Another reason to use Power Query.