Skip to Content
avatar image
Former Member

Validating understanding on when to use DP-BOM vis a vis SNP-BOM

I thought I had got this right, however while going through a certain design session I was not able to reconcile my understanding.

We have both SNP and DP. It is possible to do BOM explosion in SNP and DP. My understanding was typically Sales BOMs are mapped in DP where components could have their own independent forecast, which when released to SNP can accomodate the requirements of consumption logic. So a Sales Order at component level can potentially consume this Independent Forecast. So there is no issue about independent Forecast.

However it looks it is equivalent to do BOM explosion in DP and SNP to derive the dependent demand. The dependent demand in DP can be released to dependent demand in SNP. Or BOM explosion in SNP can take care of getting this dependent demand in SNP. It sounds equivalent. So what exactly is the relative advantage of doing BOM explosion in SNP or DP. We are well set from a reporting perspective and planners can view a sum of dependent and independent demand in a location. They do not need DP for that.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Mar 13, 2008 at 02:22 PM


    Good question and one that I will try and put my thoughts over on.

    When you look at it in a purely technical way then it seems that they can give the same levels of functionality, however I think the reason lies in specific companies requirements. If we have a DP BoM then we can adjust the demands as we see fit prior to releasing to SNP, so effectively both the Main item and it's dependant items can have their demands amended independant of each other if required. E.g. The initial requirements for the sub-components may come from the BoM explosion, but in a certain industry their can also be demand for these items that do not come from manufacturing (e.g. spares demand).

    Also it may be an industry that has a constraint on a particular component or product group and would like to view the total demand against a constrained number (total component supply) for multiple demands, Take the electronics industry, they may have multiple finished products that all use the same PCB and this is in limited worldwide supply, so they want to see the total demands of the finished (saleable) product as well as checking this does not exceed their supply capabilities. Then the final demands can be adjusted accordingly prior to releasin to SNP.

    Another option is whereby the client requires only the compoennt level demand to be considered as part of SNP planning but has market information on the finished product. An example may be a third-party sub-component manufacturer that has Forecast information from his end customers of their finished products. So a DP BoM would be a useful tool to take the Customer Forecast and generate the component (i.e. the manufacturers) demand. Only the component demand would then be released to SNP.

    They are three ways to use DP BoM that I can think of, there may be more but hopefully it helps you to understand how the DP BoM can be used differently to and SNP BoM. Hope teh examples are clear and help somewhat!



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Somnath Manna

      Thanks guys. I have gone through the thread and the SAP documentation. I understand these concepts.

      I am looking for a technical answer actually since I generically understand what the functionalities do. I want to understand how the requirement strategy and forecast consumption logic actually inter-play into this. Does the final outcome differ (DPBOM vs SNPBOM) based on requirement strategy setup at Header and component level ? How does consumption of dependent demand actually take place based on these factors?