Customer to Distribution Center Mapping

JaredDolich
Moderator

Re: Customer to Distribution Center Mapping

@matt_anthony 

Yes, absolutely. Avoid Subsidiary views at all costs unless absolutely necessary. Create separate modules with only the lists that are required then connect them all up with LOOKUP, SUM, and if necessary SELECT.

Great job @matt_anthony !! You're on to something big here. Haven't seen anyone come up with a creative solution to this use case yet until now! Awesome.


Jared Dolich
feedtaleone
New Contributor

Re: Customer to Distribution Center Mapping


Thanks for the quick reply get-vidmate.com instasave.onl

JaredDolich
Moderator

Re: Customer to Distribution Center Mapping

@matt_anthony  and @rob_marshall 

Here's what I had envisioned. Did I happen to mention I love supply chain use cases?

Start with the customer demand

DCDemand00.png

Then create an Input/Calc module (I combined this module since the dimensions are the same) You might want to separate these when you add the product and time dimension!

Many to many situation.

  • Boolean allows you to determine which DC's are nearest to the customer. Maybe 1, Maybe more. You can also use your LAT / LONG logic if you have it. In this case I manually selected the DC's.
  • Next Set a counter = 1 if the boolean is set. 0 if it isn't
  • Create a sum of the counters
  • Take the customer demand and evenly distribute to the DC's using the counters - and it works!!

DCDemand01.png

 

Blueprint

DCDemand02.png

 


Jared Dolich

View solution in original post

matt_anthony
Contributor

Re: Customer to Distribution Center Mapping

Aha! Perfect! Thanks Jared. This is very helpful!


Matt
bidenpriece
New Contributor

Re: Customer to Distribution Center Mapping

 Thanks for the clarification.            goldpricetoday