Product Lines Setup - Order field descriptions

Fields are presented in alphabetical order within each section.

Click the links below to jump to field descriptions for that section:

Ordering Units

Safety Allowance

Ordering

Frozen

Authorized Replenishment Path

Warranty

Seasonality

Terms

Ordering Units

Buying

The buying unit that applies to this product line if the buying unit differs from the Product Setup Stocking Unit. This should be the unit you use when you purchase this product line from the vendor.

For example, you may order by the roll but stock by the foot. Specify roll in the Buying field and foot in the Product Setup Stocking Unit field. The buying unit defaults during Purchase Order Entry and PO RRAR. When you specify a valid buying unit, the buying unit conversion is displayed to the right of the field and the description appears under the field.

When you perform a lookup on the Buying unit field, valid unit conversions for the current global product appear. You must display non-specific conversions. The unit conversions are set up in SA Table Code Value Setup.

Standard Pack

The quantity of the product line packed and sold by the supplier. Examples of a standard pack are box, carton, bundle, or roll, reel, or pallet. When you purchase quantities (for inventory), they should always be rounded-off to the nearest standard package.

The standard pack may be the same as the buying unit. If the standard pack differs from the buying unit, specify the standard pack. If the stocking unit is entered as the standard pack, a conversion factor of 1 is used. The system validates your entry in SA Table Code Value Setup.

The PO RRAR always rounds to the nearest standard pack. However, the Transfer Entry Recommended Replenishment Action Report does not use standard pack rounding.

Transfer

Allows for a transfer unit based on the shipping warehouse. When you specify a valid unit, the transfer unit conversion and description are displayed to the right of the field. The transfer unit is independent of the buying unit.

The Product Lines Setup record provides an optional method of establishing the transfer unit of measure. All products associated with the product line default the transfer unit of measure when you create transfers in Transfer Entry Recommended Replenishment Action Report, Transfer Entry, and when you add lines to the transfer in Transfer Entry Demand Center Entry. The standard unit of measure validation with the Product Extended Unit Conversion Setup and SA Table Code Value Setup records occurs. The functions that use Product Lines Setup defaults also default the transfer unit of measure where applicable.

When you set up superseded products, this includes:

Product Warehouse Product Setup
PD Administrator Automatic Pricing
Product Extended Product Cross Reference Setup

When you copy product lines in Product Administration Warehouse Copy Report and SA Administrator Cross Company Product Copy, the transfer unit of measure is also copied.

Safety Allowance

Amount

The amount of pad incorporated into the order point calculation to protect for a variance in the expected usage or lead time the next time this product line is ordered from the supplier. The safety allowance directly affects the order point and needs to be adjusted from time to time.

The safety allowance is considered a fixed asset that turns zero times. Therefore, do not add more safety than is necessary. Our recommendation is to use a 50% safety allowance. However, your experience with product lead times and other factors that contribute to the safety allowance calculation may call for a safety allowance less than or greater than 50%.

The average lead time is used to calculate the safety allowance, regardless of the prior or last lead times.

There are three conditions that may contribute to safety allowance variances:

Products with extremely erratic usage patterns.
Products with a totally unpredictable lead time.
Products for which you must provide 100 percent service.

The following formula uses the percentage or quantity entered in the Safety Allowance field in Product Warehouse Product Setup - Ordering. Product Administration Month End Processing Report uses this formula to recalculate the new safety allowance amount.

Safety Allowance %:

Safety Allowance / (Usage Rate * Average Lead Time)

Safety Allowance Quantity:

{Usage Rate * (Lead Time / 28)} * Safety Allowance %

When you save changes to Product Line Setup-Order, the actual safety allowance quantity ordered is calculated and displayed below the safety allowance if you specify a percent in the Amount field. If you specify a safety allowance quantity, the safety allowance percentage is calculated and appears.

Class

Defaults to 1. If an invalid number is entered, enter a correct value between 1 and 13. A product class must be specified if the Order Method field is Class. The product classification method of ordering is another alternative to EOQ. These classes determine the quantity to order. There are 13 classes each product may fit into.

The Class field is updated by the Product Administration Inventory Classification and Rank Report. All inventory products are included in the classification, except those with less than 6 months of activity history. To manually set a product line's class, refer to the following field.

Quantity / Percent / Days

Indicate if the safety allowance should be calculated based on a percentage, quantity, or days.

Safety Allowance %:

Safety Allowance / (Usage Rate * Average Lead Time)

Safety Allowance Quantity:

{Usage Rate * (Lead Time / 28)} * Safety Allowance %

If you select Days, the days specified in the Amount field is converted to safety allowance quantity using the following formula:

Safety Allowance Quantity = Safety Allowance Days * (Usage Rate/28)

Ordering

Freight Expected

This field indicates whether freight charges are expected with a purchase order. It is used primarily by PO and AP clerks as a quick form of reference. The Freight Expected field is selected by default and must be deselected to indicate that charges are not expected. To provide flexibility and ease of use, the field is displayed on multiple windows: Purchase Order Entry, Product Line Setup, Vendor Ship From Setup, and Vendor Setup. It can be modified (deselected) from these windows.

Line Point/Max

The line point establishes the upper limit required for this product line to be reordered and is expressed in stocking units. The available quantity (see Order Point/Min) must be below the line point to be included on the PO/WT RRAR. This amount can be initially specified by you or it will be automatically calculated by Product Administration Month End Processing when 6 months of history is accumulated.

Set up a line point/max until you have 6 months of usage history for Product Administration Month End Processing Report to properly calculate the line point/max. The line point is the order point plus usage during the review cycle. The line point calculation for a vendor ARP is rounded to 1 if the result is less than 1 and the order method is not min/max.

The review cycle is the frequency with which a product line is purchased when the supplier offers a total order discount. The review cycle is calculated and becomes the planned frequency of purchasing all products in the product line. The total annual purchases for the product is divided by the target buying objective to obtain the total order discount.

365 divided by ( Total Annual Purchases ) = Review Cycle\Total Order Purchasing Target

For example:

365 divided by ( $350,000 purchased in the last 12 months) = 7.3 days

$7,000 Truckload Order gets freight paid

Method

The POERR and WTERR use the ordering method to determine the quantity to buy of this product when it is time to reorder. The order methods are:

If a product's ARP is a warehouse, the Product Warehouse Product Setup Order Method is not min/max, the Product Warehouse Product Setup Season Begin field is 0, and no PD Pricing Setup - Vendor record exists, you see the following message when you save the record:

Min/Max Recommended

If an active PD Pricing Setup - Vendor record exists and the order method specified on the Product Warehouse Product Setup record is not quantity break, and the Season Begin field is 0, the following message appears when you save the record:

A Product Discount Exists, Check Your Order Method (8606)

Each order method is described:

EOQ

The economic order quantity balances the cost of carrying inventory with the cost of going through a replenishment cycle, thereby finding the quantity to purchase that will develop the lowest outgoing cost for the item. EOQ should be used if the following conditions are present.

The price paid to the supplier does not vary when you buy more of this one item. There are no price breaks.
The usage rate of the item is higher than 1/2 unit per month.
The supplier's lowest permissible purchasing quantity is reasonable for you to attain. The square root of:

24 * Cost of Ordering (R) * Usage Rate

Cost of Carrying Inventory (K) * Unit Cost

R cost is the replenishment cost specified in Product Line Setup or Product Warehouse Description Setup. It is the cost of going through the replenishment cycle and is calculated to a cost per base unit.

K cost is the cost of carrying inventory. It is calculated as the amount the average base unit accumulated during the time you carry it on the shelf. In other words, how much did it cost you to carry this product in your inventory until you sold it? The carrying cost is also specified on the Product Line Setup or Product Warehouse Description Setup record.


Usage Rate	=	20 per month
Unit Cost	=	$7.00
R Cost	=	$5.00
K Cost	=	.30
EOQ	=	Square root of: 24 * 5.00 * 20/ .30 * 7.00
EOQ	=	Square root of: 120 * 20/ 2.1
EOQ	=	Square root of: 2400/ 2.1
EOQ	=	Square root of: 1142.86
EOQ	=	34 (rounded off)

For this item, the most profitable quantity to buy (as long as the cost and usage rate remain constant) is 34 units.

Class

The product classification method is an alternative to EOQ. All inventory products are included in the classification, except those with less than 6 months of activity history, inactive products, and labor products. Order as needed (OAN) products may be excluded during Product Administration Inventory Classification and Rank if you decide to exclude them.

There are 13 classes each product may fit into. The product's class determines the quantity to order. Product class must exist if the order method is class.

The following table provides the standard breakdown of the classes. You can use SA Admin Options - Products - Replenishment to manually set the percentages if you have unusual inventory items that do not coincide with the standard percentages.


Top	7.5%	of the products	Class 1
Next	7.5%		Class 2
Next	10%		Class 3
Next	10%		Class 4
	8%		Class 5
	8%		Class 6
	8%		Class 7
	8%		Class 8
	8%		Class 9
	8%		Class 10
	8%		Class 11
Last	9%		Class 12
	100%

The product class is determined by the Product Administration Inventory Classification and Rank Report. Classes 1, 2, 3, and 4 account for 35 percent of your inventory but 90 percent of the annual movement of money through inventory! The order quantity is determined by multiplying the usage rate times the product class number, then rounding to the nearest standard pack. Class 13 products are the products that fall below the Dead Stock Level you specify in SA Admin Options - Products - Replenishment.

After your products have been classified, replenish according to the following formula.

Class * Monthly Usage Rate


Class	Months Supply to Purchase	Turns per Year to Expect
1	1	12
2	2	6
3	3	4
4	4	3
and so on	and so on	and so on

The classification method approximates the results you would get with EOQ. Classification is easier to understand but EOQ gives a precise turnover result on each product. EOQ develops about one more turn per year than the classification method.

If you are using the classification method and there are changes in the lead time or review cycle, the order quantity will not be adjusted. The order quantity is calculated by usage rate times product class. If the usage rate changes, the order quantity is adjusted. Usage rates may be changed due to stock-outs, which cause a lower order quantity and thus a higher stock-out rate.

Min/Max

The min/max or order-up-to method is used in place of Class or EOQ when the branch may order one product at a time and has a very short lead time, usually less than one week. This method is used most often when products in a branch are resupplied from a central warehouse. When the net available reaches the minimum quantity set, an amount is ordered to bring the net available up to the maximum quantity set. This method works well because the lead times are very short.

Formulas for classifications and EOQs work well in a range of usages and lead times that could be considered normal. Extremes in usage or lead time cause the formulas to be incorrect. Branch items with very short resupply lead times from a central warehouse are good examples of the low-end extreme.

While your branches may skew your formulas set for normal usages and lead times, they should also be providing you with a higher turnover rate than your central warehouse. By utilizing the push system, items are pushed out from the main warehouse to those branches it supports. They receive replenishment stock automatically when the system determines it is needed.

The first step involves classification of stock items. If management decides that a branch's inventory investment should turn 12 times a year, the individual classes must turn as follows:


Class 1	20 (times per year)	Class 7	6 (times per year)
Class 2	18	Class 8	5
Class 3	16	Class 9	4
Class 4	12	Class 10	3
Class 5	10	Class 11	2
Class 6	8	Class 12	1
		Class 13	0

If a product is class 1 in the branch, its replenishment quantity (when resupplied from the central warehouse) is 1/20th of a year's supply. A class 2 product's quantity is 1/18th, and so on. For the class 1 product the difference between min and max is 1/20th of a year's supply, for example:


Monthly Usage	=	100
Annual Usage	=	1200
Class	=	1
Replenishment Quantity	=	60
Difference between min and max	=	60

When the net available quantity for this product reaches the minimum, the central warehouse ships 60 units to the branch. The inventory-amount turnover objective is forced on the branch. They receive smaller quantities on high-class products to force the amount involved to turn faster.

Quantity Break

A quantity break method should be specified if any of the Price/Discounting records for this product are based on quantity breaks in PD Pricing Setup - Vendor. If any other order method is used, quantity breaks are calculated in addition to the regular discount. This can become quite complicated; therefore, keep them separate. If a Price/Discounting record exists with quantity breaks and the order method is not Quantity Break, a warning message appears each time you update this record. The quantity break method also requires a carrying cost (K) to exist.

Example:


A Quantity	B Price	C Total Investment	D Holding Cost	E Investment Holding Cost	E / A Net cost per Unit
1	$10.00	$10.00	-	$10.00	$10.00
10	9.00	90.00	1.31	91.31	9.13
25	8.50	212.50	7.75	220.25	8.81
50	7.50	375.00	27.35	402.35	8.05
100	6.50	650.00	94.79	744.79	7.45
200	6.25	1250.00	364.58	1614.58	8.07
Usage Rate = 10/Month		K = 35% per Year

As you can see in the chart above, the quantity break at 100 produces the lowest net unit cost of all the options.

Blanket Order

The blanket order method specifies this product is generally ordered from a vendor on a blanket order. In this situation, the ordering controls are established by you. As you enter each blanket order, you control the order quantities and the timing of the deliveries.

If the quantity available in your warehouse is below the established levels, the PO/WT RRAR includes the blanket order product. The report notifies you the product is already on a blanket order and a blanket release needs to be made to increase your product availability.

Human Method

The human method should be used for seasonal products but can be used for other types of products as well. The Product Administration Month End Processing Report ignores all products with a human order method. Set the product's order controls so the PO/WT RRAR includes the product when availability is below established levels.

Set up a default in Product Line Setup - Order. When you specify the Vendor and Product Line values in Product Warehouse Product Setup-New, the data on the Product Line Setup record that matches the vendor and product line is used to populate the corresponding fields on the new Product Warehouse Product Setup record. This ensures the initial data for any new Product Warehouse Product Setup record associated with that product line is created with the same default data. This speeds up the creation of the record because you have less data to specify on a new record.

Order Point/Min

The order point establishes the lowest quantity you should have available for sales and transfers.

You must initially set this amount or it will be automatically calculated by Product Administration Month End Processing Report each time it is performed. Set up an order point/minimum initially because Product Administration Month End Processing Report does not calculate an order point until 6 months of history exists.

In Product Warehouse Product Setup, the following formula is used to calculate order point:

Usage * Lead Time + Safety Allowance / 28 days

The order point consists of enough material (usage rate) to take care of customers during the time required to obtain the product line (lead time), plus a measured amount of pad (safety allowance). Additional quantities for this product line can be ordered at any time between the line point and order point, but when the order point or minimum is reached, replenishment must be initiated if the safety allowance is to protect you. Although the safety allowance is only needed half the time, it becomes a fixed number in the order point calculation.

When the order point is calculated to be greater than 5, the value is rounded up to 1 to enable the line point calculation to be correct.

A min/max order method may be used if a warehouse has a short lead time (less than one week). This order method is also recommended when using a central warehouse to replenish remote sites in push mode. If the min/max order method is used, the order point is considered to be the minimum amount below which an order must be placed.

Order Qty

Represents the quantity to be ordered the next time stock must be purchased from the supplier. The quantity should be enough to hold you over until the next replenishment cycle. This quantity should initially be specified by you until 6 months of history exists. At that point, Product Administration Month End Processing Report automatically determines the quantity for all order methods except blanket order or human.

Override Reason

If the order quantity is overridden, an override reason can be specified to explain why the quantity was changed.


Override Reason	Description
Human	The order quantity was set manually and is not overridden by Product Administration Month End Processing Report.
Max Weeks Su	The order quantity calculated by Product Administration Month End Processing was overridden by the value in the Max Weeks Supply field in Product Line Setup or Product Warehouse Description Setup.
Min Weeks Su	The order quantity calculated by Product Administration Month End Processing Report was overridden by the value in the Min Weeks Supply field in Product Line Setup or Product Warehouse Description Setup.

When you specify the override code, the override description appears to the right of the field. The override reasons are set up in SA Table Code Value Setup.

Roll Up OAN Usage

You can determine whether you want order-as-needed (OAN) product usage included in the usage rollup for the parent warehouse on a product-by-product basis when you are using the rolled up usage method. The default is not to include OAN products.

To include OAN products, select Roll Up OAN Usage in Product Warehouse Product Setup - Ordering. The field only appears if the parent warehouse usage is set to Rolled Up Usage, the warehouse product status is OAN, and the ARP is Warehouse or Central Warehouse.

The Roll Up OAN Usage field also appears in Product Line Setup - Order and provides the default for the field when you are setting up warehouse products associated with a product line.

Surplus Calc

The flexibility to calculate with actual monthly usage is available by using the Surplus Calc functionality in Product Warehouse Product Setup - Ordering and Product Line Setup - Order. Use the Surplus Calc drop-down field to choose between:

Usg (Product Warehouse Product Setup Usage Rate)
AMU (Actual Monthly Usage)

These options control the calculation method used when you run the Product Surplus Stock Report to analyze long-term surplus inventory. They allow you to define a long term surplus calculation method, even at the product level.

You can retain the default, Usg, to continue to use this method to calculate long-term usage:

Usg = Total Usage / Total # of Months

where

Total Usage is the amount of the product sold in the time period specified in the Months field.
Total # of Months is the time period specified in the Months field.

Or, if you select AMU, the Product Surplus Stock Report calculates a rolling actual monthly usage:

AMU = Past 12 Months (periods 2-13) / 12 x Number of Months for Long Term Calc

where

Past 12 Months (periods 2-13) is the amount of the product sold in the last 12 months (typically periods 2-13, as calculated the last time you ran Product Administration Month End Processing Report and as displayed in the Usage Information window).
12 represents a 12-month time period.
Number of Months for Long Term Calc is the time period set in the Product Surplus Stock Report option of the same name.

Both methods impact only the long-term surplus calculation; short-term surplus calculation is unchanged. You should review your product lines and products to determine which ones should use which surplus calculation method. For example, you could use the Product Line Setup - Order Surplus Calc setting, AMU, as a default. Then, all product records created in Product Warehouse Product Setup - Ordering under that product line going forward also are set for AMU. You can still manually change the setting on a product level. Whatever Surplus Calc is set in Product Warehouse Product Setup- Ordering is displayed in the other functions.

Usage Months

Indicate the number of months that should be used to recalculate the usage rate by Product Administration Month End Processing Report. The standard default is 6 months.

The usage rate is not calculated on a product line with less than six months of history, but the entire six months does not need to be used. You may also elect to use more than six months of history to recalculate the usage rate, although, you are limited to a maximum of 12 months.

If you have seasonal products, Product Administration Month End Processing Report will look at your Season Begin and Season End dates and go back twelve months, then forward the number of months you specify here. This method produces an equivalent season for you.

Frozen

Months

The number of months the product will be frozen. Each time Product Administration Month End Processing Report is performed, the number of months is decreased until it expires. The month it expires, Product Administration Month End Processing Report picks up the warehouse product and begins processing the record. All new products are automatically set to 6 since at least six months of history must exist before the ordering controls can be established.

If the number of months frozen is 99, the product is frozen indefinitely and ordering controls are never recalculated by Product Administration Month End Processing Report.

Do not manually adjust this field. However, if it is necessary, access it directly from this function or via Product Administrator Update Frozen Conditions.

Reason

Choose a reason or accept the reason automatically determined by Product Administration Month End Processing Report . Six frozen reasons are provided in SA Table Code Value Setup. You can define additional reasons. A frozen reason gives an explanation as to why the warehouse product line has been frozen.

These reasons are automatically set up in SA Table Code Value Setup:


Reason	Description
New Product	The warehouse product will be frozen if it does not have a sufficient number of months used to calculate the usage rate as established in Product Warehouse Product Setup. All new products are automatically set to n. The ordering controls for this product should be reviewed monthly or with each review cycle until there is enough history to calculate the usage rate.
USG < ½ Un	If the average usage over the number of months’ usage calculation is less than ½ unit, this frozen reason applies. Products with this frozen reason may be candidates for removal from inventory. These should be reviewed periodically.
Usage Except	This frozen reason indicates the monthly sales is greater than or equal to the sum of the last 5 months’ usage, and at least 5 units are sold, and the item cost is greater than the SA Admin Options - Products Min Cost for Determining Exceptional Usage option. With this frozen reason, you should determine how much of the extraordinary usage should be excluded from normal usage calculations.
Ext Stockout	If a warehouse product is stocked out for 15 consecutive days, the current month will have the usage updated. The Product Warehouse Product Setup - Usage Override usage field should be adjusted to accurately reflect the actual usage rate as though the stock out had not occurred.
50% Var-LT	The product is frozen if the new average lead time is 50% less than or greater than the last lead time
Zero LT	The product is frozen if the average lead time is zero, or if the `Last Lead Time – Prior Lead Time` is greater than 180 days and the last lead time equals zero.

In Product Warehouse Product Setup, this field is not updated by Product Administration Month End Processing Report if the # of Months Frozen field is 99.

The Frozen Reason field in Product Line Setup - Order sets the default frozen reason for the system. The default is based on the vendor and product line entered in the Load Defaults From window that appears when you set up a new warehouse product in Product Warehouse Product Setup.

Authorized Replenishment Path

Push/Pull

Does the ARP warehouse supplying this product automatically replenish your stock when you need it, or do you place orders with the warehouse to be replenished? If the warehouse automatically determines when you need more stock and pushes it out to you, select Push. If you control your product supply, select Pull

Type

The ARP, authorized replenishment path, is the preferred method this product line is supplied and replenished to your warehouse. There will be exceptions, but follow the ARP as much as possible. Generally, do not arbitrarily change the source from which you obtain the product line. For example, do not randomly order the product line from another warehouse one time, from the manufacturer another time, and from a dealer yet another time. This sort of activity contributes to an unmanageable inventory.

The products in this line can be received:

From a specific vendor or warehouse
Supplied from a central warehouse
Assembled on a prebuilt kit work order
Supplied under a VMI (Vendor Managed Inventory) agreement with a vendor

Vendor replenishment paths will always resupply this product line from the vendor listed in the field below. The product line is included on the PO RRAR when it needs to be replenished.

If you choose Warehouseor Central Order, this product line is included on the WT RRAR when it needs to be replenished and is replenished from the warehouse specified in the ARP Whse field. If you choose Kit, the product line must be a prebuilt kit (designated in Product Setup), and this product line is included on the KP RRAR rather than on the WT RRAR or PO RRAR.

A product line managed under a VMI agreement is ignored by the PO/WT RRAR processes, but product data is reviewed by the vendor who will determine when the product should be replenished. The Purchase Entry VMI Initial Product Data Load Report is used only at the beginning of a VMI program. Purchase Entry VMI Product Activity Data EDI 852 Report tracks inventory changes for products with an ARP of VMI and is usually transmitted (via EDI) to the vendor daily.

Note: Use caution if you set the ARP field to VMI because every product record created for this product line contains an ARP of VMI. The PO RRAR does not review these Product Warehouse Product Setup records. Therefore, if you are using the ARP field as a default for newly created product records, specify the standard method of replenishing the majority of products and manually change the Product Warehouse Product Setup records for those products that contain a different ARP.

Whse

The warehouse resupplying this product line to your warehouse. The ARP warehouse must be a different warehouse than the warehouse storing this product line, or an error message appears and you must correct it.

The warehouse must exist in Product Warehouse Description Setup.

Warranty

Length

The length of warranty is the actual period of time the warranty is valid. For example, 2 days, 2 months, or 2 years.

Warranties are useful for serialized products. The warranty expiration date is stored with each serialized product set up in Product Extended Serial Number Setup. If a serialized product is returned, you will know the original date of sale and the date the warranty expires to determine if charges can be applied for repairing/handling the product.

If the products in this product line carry a warranty, specify the most common time period. This becomes the standard default when creating new warehouse products in Product Setup from catalog records and may be overridden when necessary. This field is not used by Product Line Setup or Product Warehouse Product Setup for any other setup defaults.

Period

The warranty period is represented by days, months, or years. This field works with the Length field. The warranty period describes if the warranty is good for a specific number of days, months, or years.

This becomes the standard default when creating new warehouse products in Product Setup from catalog records and may be overridden when necessary. This field is not used by Product Line Setup or Product Warehouse Product Setup for any other setup defaults.

Seasonality

Avg Lead Time

The total time required to replenish this product line from the date the order is placed to the first receipt of the product line from its ARP source. The initial purchase of an item is the only time non-ARP lead times are updated. Weekend days are included in the average lead time. The average lead time is used to calculate the order point during Product Administration Month End Processing Report.

Order Qty

The quantity to be ordered the next time stock must be purchased from the supplier during your out-of-season months. For seasonal product lines, the order quantity increases when the product line is in season and decreases when it is out of season. The quantity should be enough to meet demand until the next replenishment cycle.

Override Reason

If the order quantity is overridden, an override reason can be specified to explain why the quantity was changed. The override reason can be manually specified or Product Administration Month End Processing Report automatically assigns one of these reasons:


Override Reason	Description
Human	The order quantity was set manually and will not be overridden by Product Administration Month End Processing Report.
Max Weeks Supplu	The order quantity calculated by Product Administration Month End Processing Report was overridden by the value in the Max Weeks Supply field from the Product Line Setup or Product Warehouse Description Setup record.
Min Weeks Supply	The order quantity calculated by Product Administration Month End Processing Report was overridden by the value in the Min Weeks Supply field from the Product Line Setup or Product Warehouse Description Setup record.

Set up a default in Product Line Setup - Order. The default is based on the vendor and product line specified in the Load Defaults From window that appears when you set up a new warehouse product.

Review Days

The number of days prior to the selling season that you must begin reviewing the seasonal product.

The Product Seasonal Product Analysis Report uses this field to determine when it should print the product on the report for your review. You can increase or decrease this field to suit your needs. Factors may include how often you generate the Product Seasonal Product Analysis Report or the lead times for this product.

Terms

Discount

Indicates that this product line does not receive a unique line-based terms discount. If this option is not selected, it indicates product-specific cash terms are applicable in Sales Order Entry. If product-specific cash terms exist for this product line, specify the percent applicable in the field immediately to the right. In order for product-specific cash terms to be functional, the SA Table Code Value Setup Terms Over field must be selected to allow terms override by line item.

You can change from line-based to order-based discounts. However, you cannot change from order-based to line-based discounts. If terms are line based, whole order and other order-based discounts are subtracted from the Sales Order Entry terms and multiplied by the SA Table Code Value Setup percent.

Discount %

If product-specific terms discounts are used in Sales Order Entry, specify the percent of the terms in this field. Product-specific terms discount are only used if the term is established as line based in SA Table Code Value Setup. If you have established line-based terms in SA Table Code Value Setup and the discount percent for this product differs from the standard terms percent set up in SA Table Code Value Setup, specify a terms discount percent here.