SELECT * FROM Erp.ForecstDtl fd WHERE fd.CustNum = 6651 AND fd.PartNum = '5103758' AND fd.ForeDate = '01/23/2024' ORDER BY fd.ForeDate, fd.EdiUpdateDate ASC
When I open that part up in Time Phase, I see this:
Time Phase is only showing a demand of 1,500 for 1/23/2024, while the ForecstDtl table of the Database reflects a Forecast Quantity of 3,000.
The ForecstDtl Table shows a quantity of 3,000 (1,500 per line), but Time Phase only shows 1,500. Is this something that indicates that we are processing our EDI transactions incorrectly perhaps? Is there another primary key I should be looking at in ForecstDtl that is not registering in my mind for some reason?
We don’t consume forecasts yet, but I had a bunch in demand entry so I processed some of them. If I have the same custnum and partnum like you I do get two ForecstDtl records, but I get one combined quantity Forecast record that shows in timephase.
I tried to make two same day same part forecast entries and forecast is constrained by custnum, part and date, so you can only have a combined forecast record for all forecast details for a customer, part and date.
Working with a customer they found critical issue where Timephase is showing suggestions for forecast that has been deleted.
Working with tech support we were able to get a datafix for this critical issue.
We had to ID the parts to fix, Epicor did not provide the attached BAQ.
This came about from the recent upgrade in June.
When you look at time phase, there werer MRP unfirm jobs without a demand showing.
Very critical as these jobs were driving purchase suggestions for material.
The BAQ sums up all of the SourceFile “FC” in partdtl and compares it to forecast totals by part
