The following is the is description of the Demand buckets in Parts Profile and how the demands are calculated.
IntelliDealer Demands Buckets.
1) 24 demand buckets in the file PARTMAST
2) OFC reclass uses demands
3) OFC codes logic uses demands buckets, not bin trip buckets
4) Demand buckets appear on IntelliDealer Parts Profile screen.
5) Details on how demands are calculated are below
Demand Calculation
- The logic used for Demand calculation is 1 demand per part per sales order/requisitions, per sign, regardless of the number of lines the part is on or the number of times the part is back ordered or invoiced. This means if there are two sales and one return there is no demand logged because there is ultimately one negative demand and one positive demand, which offset. Based on this the dealer may decide to not allow users to add parts to an invoiced sales order/parts invoice.
- For parts sales through equipment & rental it is 1 demand per line item per invoice.
- IntelliDealer shows the demand buckets in the Parts Profile screen.
- Branch transfers will never record demands. This would be anything cost coded as 'Transfer' or NSC 'T'
- The PARTLS table will determine if lost sales record demands.
- One time sales will not record demands. This would be anything cost coded as a 'One time Sale' or NSC 'A'
- Deere percent of fill calculations use line items for this calculation, so there is no reference to demand buckets.
- Work order adjustments are treated as demands based on the following logic (Demand calculation change - March 2009 )
- If '$W/O ADJ$' is in the ship via field, then do not include these records in the demand calculation since this is an adjustment to an existing line
- If '$W/O ADJ/REV$' is in the ship via field, then include these records in the demand calculation since this is reversing the original line
- Surplus returns can be setup to be handled as abnormal sales so that no demand details are affected.
Note: All Dealers should be ensuring that lost sales are being captured properly. As part of the process, we check to see if the part is loaded more than once on the document and if so we wait to handle the demand value until that first line is processed. So if the first line is cancelled or removed, the system would miss the demand for any subsequent line for that part. IntelliDealer has a switch that will not allow the users to clear a line and will require the line to be processed as a lost sale. The PARTLS table can be configured to determine which lost sale values affect demands. The capture of demands is also critical in the sending of the proper data all inventory replenishment interfaces such as CNH AMAX, AGCO API, Volvo MMI, John Deere JDPrism and Komatsu RIM 2.0.