Deployment Optimizer - Equal weightage for all the locations in the network

Question

Hello All,
I am having difficulty in assigning equal weightage for all the locations in the deployment network.  My scenario is as described below:
Deployment Source location: LOC1
Destination locations: LOC2, LOC3
I am running Heuristics to plan LOC2, LOC3 & LOC1, followed by
a Deployment Optimizer run at LOC1 to deploy to LOC2 & LOC3.
ATD quantity at LOC1 is always calculated after saftisfying the requirements at LOC1 and the remainder is deployed to LOC2 & LOC3 based on the cost settings.  This seems to be the case even if I don't run the heuristics at LOC1 and start deployment optimizer after running the heuristics at LOC2 and LOC3.
The need at this client place is that all three locations are equally important even though LOC1 is the only deploying source location.
This applies for all demand categories i.e. Sales orders, Forecast and forecast at all the three locations.
I would appreciate if anybody has done this kind of configuration before and let me know how to model this.
Thanks,
Venkat

Answer 1

Have you follow all this checking ?
If you think that you already follow all the steps, but the value is not as per your config, you can raise ticket to SAP about it.
But I suggest you to double check your computation.
To determine a vendor's price level, the system compares the vendor's effective price with the market price for the material.
   1. The system first checks whether the buyer has maintained a market price for the material or the material group.
   2. If not, the system calculates the market price which is equal to the average of the effective prices for all vendors supplying this material. Prices from purchase orders and prices for subcontracting are dealt with separately.
   3. The system then applies the effective price for the vendor from the conditions.
   4. The vendor's effective price is then compared with the market price and the percentage variance determined.
   5. The system then assigns a score to the variance in accordance with the settings made in Customizing.
   6. This score is valid for the material, that is, at info record level. Since the score the vendor receives for a subcriterion is based not on an individual material, but on the total of all the materials he supplies, the following steps are necessary:
   7. The system repeats the comparison between effective price and market price for each of the vendor's materials.
   8. The system calculates an average from the sum of the scores determined. This average represents the vendor's score for the subcriterion Price Level.
Edited by: w1n on Apr 19, 2010 2:35 PM