Good call - all rows seem to populate with either “m”, “s”, “z” or blank.
The forecast data all had blanks.
You have given me an idea though…we DMT the forecast data in, so there is no reason why (if possible) this field cannot be populated with an “F”.
UPDATE
Just checked on the forecast DMT section under the sales header and there is a column we can try called “DemandReference”…hopefully it will filter through to the sugpodtl table.
UPDATE: this reference doesn’t feed through to the sugpodtl table unfortunately.
Not really sure, but I think the DEMAND reference might be from EDI ??? So it may engage other logic.
yet, if the SugReason can be parsed you may have what you need. good luck
Try running MRP Pegging, and then compare the Peg table with the PO Suggestion table… you should be able to find which suggestions are pegged to a forecast.
it is an option in MRP, or you can run it separately from the menu.
When you run it, the process generates a set of tables that “peg” (link) each demand to each supply. This can be a one-to-many, or a Many-to-One link… in other words, multiple demands (Orders, forecasts, etc), can cause one Supply (PO, Job), or, one demand can be fulfilled by many supplies.
Basically it analyses the time phase to figure out how things link. This is an “old school” way of analyzing things, but works well. (see: Pegging report - Wikipedia for a mini article)
thank you for this…
at first glance it looks to be the PegDMDMst table and column name DemandType which holds an “F” presumably for forecast…other letters are J, S and W.
When i filter just the F - these are all parts ive used for forecast…so i should be able to just link this table with Sugpodtl and that will give me the answer i needed.
Thank you for your help.
UPDATE:.…it looks like the only real connections between SUGPODTL and PEGDMDMST are the partnum and qty which isn’t really a strong enough connection to be reliable.
Might be back to the drawing board on this one.