The following table lists the layout that is acceptable by the third-party demand forecasting software.
Field Name |
Description |
|
Begin |
End |
Length |
Decimals |
Item Number |
Test Item |
|
1 |
28 |
28 |
N/A |
Item Descr. |
Cell Phone White |
|
29 |
58 |
30 |
N/A |
U of M |
EACH |
|
59 |
62 |
4 |
N/A |
Warehouse |
NJ |
|
63 |
67 |
5 |
N/A |
Season Ind. |
22 |
|
68 |
69 |
2 |
N/A |
Lot Sens. |
40 |
|
70 |
72 |
3 |
N/A |
Vendor |
09 |
|
73 |
81 |
9 |
N/A |
ABC Class |
A |
|
82 |
82 |
1 |
N/A |
Qty on Hand |
140000 |
(=14) |
83 |
96 |
14 |
4 |
Qty on Order |
50000 |
(=15) |
97 |
110 |
14 |
4 |
QTY Comm. |
160000 |
(=16) |
111 |
124 |
14 |
4 |
History 1 |
480000 |
(=48) |
125 |
138 |
14 |
4 |
History 2 |
580000 |
(=58) |
139 |
152 |
14 |
4 |
History 3 |
420000 |
(=42) |
153 |
166 |
14 |
4 |
History 4 |
540000 |
(=54) |
167 |
180 |
14 |
4 |
History 5 |
820000 |
(=82) |
181 |
194 |
14 |
4 |
History 6 |
900000 |
(=90) |
195 |
208 |
14 |
4 |
History 7 |
700000 |
(=70) |
209 |
222 |
14 |
4 |
History 8 |
500000 |
(=50) |
223 |
236 |
14 |
4 |
History 9 |
320000 |
(=32) |
237 |
250 |
14 |
4 |
History 10 |
380000 |
(=38) |
251 |
264 |
14 |
4 |
History 11 |
500000 |
(=50) |
265 |
278 |
14 |
4 |
History 12 |
460000 |
(=46) |
279 |
292 |
14 |
4 |
Volume |
10000 |
(=10) |
293 |
302 |
10 |
3 |
Lot Size |
20 |
(=20) |
303 |
308 |
6 |
0 |
Vendor min. |
100 |
(=100) |
309 |
322 |
14 |
4 |
Unit Cost |
2900000 |
(=29.00) |
323 |
336 |
14 |
5 |
Group I |
|
|
337 |
340 |
4 |
N/A |
Group II |
|
|
341 |
344 |
4 |
N/A |
Super Vendor |
|
|
345 |
353 |
9 |
N/A |
M-T-D |
20 |
(=20) |
354 |
359 |
6 |
0 |
Weight |
31000 |
(=31) |
360 |
369 |
10 |
3 |
Shelf min. |
100000 |
(=10) |
370 |
383 |
14 |
4 |
Back Order |
100000 |
(=10) |
384 |
397 |
14 |
4 |
Remove Flag |
(D will remove the item) |
|
398 |
398 |
1 |
N/A |
Itm Lead Time |
16 |
(=16) |
399 |
402 |
4 |
0 |
Item Number - This is the product code.
Item Descr .- This is the description of the product code.
U of M - This is the default purchase unit of measure of the product that is assigned on the Unit of Measure tab in Product Maintenance.
Warehouse - This is the warehouse location for which you are creating the buying information.
Season Ind. - This is the product’s seasonal code, if one exists. The software uses the Seasonal Class field on the Buying tab in Product Location Maintenance.
Vendor - This is the supplier code and name of the product, it is the primary supplier defined on the Buying tab in Product Maintenance.
Qty On Hand - This is the total quantity on hand for the product at the specified warehouse location.
Qty On Order - This is the total quantity on order for the product at the specified warehouse location.
Qty. Comm. - This is the quantity that has been committed (allocated) for the product at the specified warehouse location.
History 1 through 12 - These are used in storing the product's sales history for the past 12 months starting with the most recent month.
Vendor Min - This is the minimum quantity the vendor allows you to purchase in the unit of measure specified for the product.
Unit Cost - This is the cost of the product in the unit of measure specified for the product.
M-T-D - This is the most recent month’s sales history. This should be the current month.
Weight - This is the unit weight of the product.
Shelf Min. - This is the minimum shelf quantity for the product. The software uses the quantity entered in the Safety Stock field on the Buying tab in Product Location Maintenance.
Backorder - This is the backorder quantity for the product at the specified warehouse location.
Itm Lead Time - This is the lead time for the product as defined on the Buying tab in Product Location Maintenance. Lead times can also be defined for a supplier-product record in Supplier Product Maintenance.
NOTE The import layout allows you to store up to 12 months of sales history. If you require greater than 12 months, you will need to load months 13 through 24 into the third-party demand forecasting software. The import format cannot be used to accomplish this task. Products that are defined as seasonal items (seasonal code) may require you to have a 24-month sales history in the third-party demand forecasting application to provide proper buying information.