Configure ATP to 'look through' multi-warehouse supply chain?

Hi,

We are setting our ATP to be the same as Lead Days which works fine if it is a supply chain that involves just a warehouse and a supplier. But if one warehouse is supplied by another warehouse which is supplied by a supplier, it does not work well.
E.g.
- Warehouse A sources from Warehouse B and transport lead time between them is 3 days.
- Warehouse B sources from the supplier and lead time is 2 months.
- If we have ATP set for Warehouse A as 3 days then this works well provided there is available stock at Warehouse B. But if there is no stock at Warehouse B then the ATP misleads sales people entering sales orders in Warehouse A.

Is there any way to configure AX so that a sales order can 'look through' the full supply chain to see when they get the product? ATP seems limited in usefulness when you have more than one step in your supply chain.

Thanks
Nick

  • Hi Nick

    That would be CTP I guess from your description, have you looked at that?
  • In reply to AdamRoue:

    Yes, seems ATP is the wrong tool for the described job. CTP should be able to handle that.
  • In reply to AdamRoue:

    Hi AdamRoue,

    Thanks for your response. We have previously looked at CTP and concluded that it would not work for us. That was a couple of years ago though, so I'll revisit it. I think we've built some mods around using ATP so this may be an issue we have to live with for go live date.

    Regards
    Nick
  • In reply to Chan Stevens:

    Hi Chan Stevens,

    Thanks for your response. As per my answer to AdamRoue, we have previously looked at CTP and concluded that it would not work for us. That was a couple of years ago though, so I'll revisit it. I think we've built some mods around using ATP so this may be an issue we have to live with for go live date.

    Regards
    Nick
  • In reply to Nick Colebatch:

    I'm curious about the background on the conclusion that CTP "didn't work" for you. In my experience when a client determines something is not working, it's typically due to lack of understanding on how something works, data/processes that are not capable of supporting the functionality, or have chosen to operate in a manner that defies accepted norms (aka best practices). Bugs exist, and there are also legitimate reasons why it might not be optimum use of resources to use certain functionality, but with something as complex as CTP and a bit of scarcity among implementation partners in terms of expertise in advanced supply chain planning, it's pretty easy to bugger up an attempt to use CTP satisfactorily.
Related
Recommended