@Phil it has to take into consideration the date and item if it was available in a specific location and on a specific day. In fact, I have just figured...

@Phil if you can explain me the code I will appreciate. Also is there a chance to join/link on 3 fields:

F.[DMDUNIT] = A.[DMDUNIT]

AND F.[STARTDATE] = A.[DMDPostDate]

and F.[LOC] = A.[LOC]

@Phil the first one works just great. But is it possible to make sure that it is joined on 3 fields:

F.[DMDUNIT] = A.[DMDUNIT]

AND F.[STARTDATE] = A.[DMDPostDate]

and F.[LOC] = A.[LOC]

With Albertsons...

@Phil

When I change GROUP BY from A.[LOC] to F.[LOC] I have the reverse effect. Now my Actuals are correct, but Forecast is not.

Something is wrong with the GROUP BY. Depending...

@Phil I don't have such an issue with Actuals. Over there, I get the very same result as with a join.

@Phil Parkin but how come joined dataset has more rows? I am doing full outer join... i was always under the impression when we do it we return exactly the...

@pietlinden just corrected thank you!!!. Do you know how i can calculate what i wrote?

Phil thank you.

If someone may know, please let me know.

• This reply was modified 3 years, 2 months ago by  JeremyU.

@homebrew01 I have revised my question, I think I didn't phrase it correctly.

Hello Scott,

I think you must be right. Thank you.

What I am trying to show is that we sold 20 units. We forecasted we would sell 20.002. Total error between sold and forecasted is only 0.002. Sales VS FCST...

I start guessing, I need to sum all the fields

4) Inventory On Hand 5) On Order 6)Forecast Demand (POS) 7) Last Week Actual 8) Forecast Accuracy 9) Instock % 10) Projected Available Inventory...

Well, the table SCPOMGR.DMDUNIT  doesn't have a location column. It is a table that is basically just provides the item number and its description. There is no LOC information there.

It returns 234 rows. Sounds much more like truth.

Do you have any ideas?