again, thanks for the response.  I think we are going to work with our developer to see if we can capture the association between the SO and the WO.  Obviously the MRP system knows that relationship because it creates it but there does not seem to be a record or index recorded that we can use.  Otherwise, I'll take your advice and look at some of the other ways we define our system and processes, such as how often we run MRP etc.

Thanks, DT

That can be a little tricky. The relationship between a WO and SO can be established using the Customer PO entered on the SO as well as the WO (you can create a WO from SO), or it can be established using an Estimate or with Product Configurator. These last features are a roundabout way to get to the routing and/or WOs though.

If you are looking strictly at MRP, a SO contributes to the demand forecast for an item, but that might be aggregated into the total demand for the item which I seem to recall is related to the settings you use. If there is a relationship between the MRP version and the sales order, it is going to be based in the tmfMRPDetail_HAI table.

That can be a little tricky. The relationship between a WO and SO can be established using the Customer PO entered on the SO as well as the WO (you can create a WO from SO), or it can be established using an Estimate or with Product Configurator. These last features are a roundabout way to get to the routing and/or WOs though.

If you are looking strictly at MRP, a SO contributes to the demand forecast for an item, but that might be aggregated into the total demand for the item which I seem to recall is related to the settings you use. If there is a relationship between the MRP version and the sales order, it is going to be based in the tmfMRPDetail_HAI table.