Is there a way to access the Demand Workbench through a BAQ?
Yes. It is possible to use DemandHeadImport, DemandDetailImport as well as DemandScheduleImport
Thank you for responding.
I have pulled together a BAQ that pulls in the Demand Workbench. But it seems that it is pulling everything including the kitchen sink 
!
I would like my BAQ to pull just what has come in for the day - not the entire history of the Order/Part.
I cannot find a Date field that is populated to filter on.
Any suggestions? Thanks in advance!
As Epicor does not indicate a PO Date field (distinct from the Sales Order date field), we have added this information in a Demand Header UD Date field.
A similar UD Date field could be used to store the receipt date for each inbound EDI transaction, which would then be available for BAQ processing.
As Epicor does not indicate a PO Date field (distinct from the Sales Order date field), we have added this information in a Demand Header UD Date field.
A similar UD Date field could be used to store the receipt date for each inbound EDI transaction, which would then be available for BAQ processing.
Unfortunately I do not know much about UD Tables or UD Fields.
Can you suggest some “understandable” documentation on how to create them and use them?
Much appreciated thank you so much for replying!
User-Defined (UD) fields are already set up by Epicor for miscellaneous values.
Usually, ten fields each are allocated for dates, numbers, checkbox values, etc., and are available for BAQ or other processing.
The UD value should be initialized upon receipt within your EDI process (Gentran, Epicor EDI, or other).
Your BAQ could be updated to include a recent date range.
User-Defined (UD) fields are already set up by Epicor for miscellaneous values.
Usually, ten fields each are allocated for dates, numbers, checkbox values, etc., and are available for BAQ or other processing.
The UD value should be initialized upon receipt within your EDI process (Gentran, Epicor EDI, or other).
Your BAQ could be updated to include a recent date range.
Ah…got it.
I did find a way to narrow down my list. I got to thinking that if I told the BAQ to ONLY return the ImportID from each Table it might just return what was imported from EDI.
It seems to have worked…I’m going data diving to verify it did just that! 
Thank you again for your assistance!