Basic Product Setup
How to configure a basic product.
Last updated
How to configure a basic product.
Last updated
For details on the various fields, see the Manual for the Product Window. This page won't go into all of them, just the ones that are not standard.
A Product appears in windows and forms using a lookup editor that displays the identifier for the Product, usually its value and name together. When you need to enter a product in the editor, the editor tries to match the data entered with one of the four key identifiers: the Value, Name, Universal Product Code (UPC) or Stock Keeping Unit (SKU). For users who are familiar with the products and can memorize one of these, its a simple matter to enter the data.
A laser scanner can also be used to populate the editor from a label on the product using one of these fields. If you are using a laser scanner, setup one of these fields to match the output of the scanner.
The goal should be to enable users and scanners to uniquely identify the product with a simple entry. If the entry is ambiguous and relates to more than one product, the Product Info window will appear. While helpful, this takes time and can quickly become annoying if entering large amounts of data.
A reference field, the version number of the Product is used when assets are delivered. The Version Number is copied to the Asset.
These fields are helpful for summarizing reports. See and for more info. The Product Category is mandatory.
The Summary Level field is intended to allow a tree of products to be defined and used in reporting. Where the summary level product is identified in a report, the results will be based on the child products. The Summary Level field can be set in the Product window but the selection of child products is done in the Tree Maintenance window. See for more info.
Part of the Global Tax Management menu, the Tax Type field is not used in the core system but is available if you need to develop a Global Tax Management system to treat complex tax cases. Some Localizations may use this field.
The sales rep or User responsible for this product. Used for reference only.
The mail template is used when this Product relates to an Asset or Item that can be delivered by e-mail as a URL to a download location. The mail template can be used to provide information about the product or to asset. The Mail Template is used in the Asset Delivery process to deliver customer assets electronically.
Enter the weight of the product. This field only appears if the Product Type is "Item". The weight is used in calculating the total weight of an order or shipment, in estimating the cost of shipping or applying landed costs. There are no units for the Weight so you will need to have a system wide definition for which unit to use.
Enter the volume of the product. This field only appears if the Product Type is "Item". The volume is used in calculating the total volume of an order or shipment, in estimating the cost of shipping or applying landed costs. There are no units for the Volume so you will need to have a system wide definition for which unit to use.
Select the appropriate Freight Category. The Product Freight Category is used in the order and shipping documents to determine which Shipper to use and the estimated costs of the shipment based on the product weight. Freight Categories are defined in the Freight Category window and Shippers in the Shipper window. Each Shipper can be associated with a number of Freight Categories. The actual Shipper used and the final Freight Category are set on the Shipping document.
Select this field if the product can be drop shipped (sent direct from the vendor to the customer.) For reference only.
Select if the product is to be held and tracked in inventory. This field will only appear if the Product Type is "Item".
The default location for the product in storage. This field will only appear if the item is Stocked. This is the Locator that will be used when the product is first added to a Material Receipt Line IF the Locator Warehouse and the Warehouse identified on the Material Receipt are the same. If they Warehouses are different, the default Locator for the Warehouse will be used.
For Production Light, if the Production header is created from an Order Line, the Product Locator will be used. When the Production BOM is created, the BOM line products will also use the Product Locator.
Other than setting default values in a few documents, this field does not control the location in storage at all.
These fields provide information about how the Product fits into inventory locations. The fields are not used other than for information and reference.
If a Bill of Materials (BOM) is defined on the BOM tab of the Product Window, the Bill of Materials checkbox will be selected and the Verify BOM button and Verified checkbox will be visible. After the BOM is entered, you can click the Verify BOM button and the system will check the BOM products and processes making sure there are no recursive products in the BOM tree. Once the BOM has been verified, the Verified checkbox will be selected.
Any BOM defined for the product will not be available to use unless the Verify BOM process is completed and the Verified checkbox is selected.
This field appears if the Product has a BOM. If selected, the contents of the BOM will be added to the Invoice print out, not as new line items but as details of the master product. This does not affect the invoice document - no lines are added. It only affects the invoice Print or Print Preview output.
This field appears if the Product has a BOM. If selected, the BOM details will be added to the Pick List for the Product. This does not affect the shipment document - no lines are added. It only affects the Pick List Print and Print Preview output.
The same caution as for Print detail records on invoice applies.
These fields indicate if the Product is purchased or sold or both. As a rule of thumb, if the product is not purchased but is sold, it must be manufactured and will usually have a BOM associated with it. On the other hand, if the product is purchased but not sold, it will usually be consumed somehow, typically as a component in another product.
The Purchased flag is used when calculating replenishment plans. Requisitions are created for purchased products.
The Sold field is not used much. It is used to limit the display of products in the Point of Sale (POS) and web store. Otherwise, it is for reference only.
The Discontinued field shows if the product will no longer be produced or purchased. When a product is discontinued, it will not appear in the POS. When the field is selected, the User who made the change is recorded.
If the Product Type is set to "Expense type", the Expense Type field will appear and will contain the related Expense Type. Expense Type products are not created in the Product Window but can be viewed. They are created in the Expense Type window.
If the Product Type is set to "Resource", the Resource field will appear and will contain the related Resource. Resource products are not created in the Product Window but can be viewed. They are created in the Resource window.
Select to exclude this product from Auto Delivery via a process. Auto delivery can occur if the Customer (Business Partner) has a Delivery Rule other than "Manual". Selecting Exclude Auto Delivery on the Product window will prevent automatic delivery of this product. This is useful where the product is sensitive, potentially dangerous or stock levels are likely to be insufficient. A product that should be excluded from air freight would be a good example.
The Exclude Auto Delivery flag is ignored if the Business Partner Delivery Rule is "Force" or if the Order is one of the following document types, all of which over-write the Delivery Rule with "Force":
On Credit Order,
Warehouse Order,
POS Order, or
Prepay Order.
The Image URL and Description URL are used in the Web Store. The Image URL is used to display the image of the product and the Description URL is used as a link for the Product Name.
These numbers are used to calculate the Good For Days, Shelf Life Days and Shelf Life Remaining values shown in the Attribute Instance dialog.
The Good For Days (GFD) is calculates as
where ASI.GuaranteeDate is the Guarantee Date of a particular Attribute Set Instance of this Product, SysDate is the current system date and MGD is the Product Min Guarantee Days.
The Shelf Life Days (SLD) is simply
and Shelf Life Remaining Percent (SLRP) is
where GD is the Product Guarantee Days and GD > 0. If GD <= 0 the SLRP is shown as 0.
Enter the Attribute set used by the product and the template Attribute Set Instance. The Attribute Set Instance field will not be enabled until the Attribute Set field has a suitable value.
This field should be selected if the product will be shown in the Web Store by default. The product must also have the Is Self-Service field selected and meet the requirements of that field. Products that are not selected as part of the Web Store but that are on the same price list and that have the Is Self-Service field selected can be shown in the Web Store Shopping Basket.
Selecting the field is required to display the product in the Web Store, by default if the field Featured in Web Store is also selected. The product must also be Active, Sold and be on a suitable price list with a Standard Price greater than zero.
After the basic product fields are generated here, if the product is similar to another product, the Copy From Product button at the bottom of the form can be used to copy a number of the subordinate tab data from that product to this one.
The current Product record needs to be saved. When you click the Copy From Button, a dialog will appear where you can select the source product. Click the Confirm button and the following data will be copied from the selected product:
Product Prices
Substitutes
Related Products
Warehouse Replenishment Rules
Product Business Partner Info
Product Download Info
Select the appropriate Tax Category. See the description of for more information about the Tax Category.
Select the appropriate Revenue Recognition type. This field only appears if the Product is sold. The field is currently for reference only. See for more info.
Enter the UOM in which the product will be stored. This needs to be the smallest UOM that will be used for the Product. See for more information about using UOMs and the conversion from one to the this "Product" UOM.
Select the appropriate product type. See for more information about the possible choices.
On an Invoice or Order, non-stocked products that have a BOM will have the BOM tree "exploded" - meaning expanded - when the document is prepared. In this case the BOM line products will be added to the document as if they were additional products. The BOM Valid From and Valid To dates must agree with the document date, Date Promised for orders and Date Invoiced for invoices, and the BOM Search Key field needs to match the Product Search Key field. See for more information.
If the product has multiple BOMs, all of the BOM lines will be printed on the Invoice, even the inactive ones. See issue .
If the Product is purchased and also has a BOM, the behavior is not consistent across all replenishment processes. In some cases a requisition will be generated instead of a manufacturing order. In others, the manufacturing order will come first. See .
Enter the Subscription Type. Subscription Types are created and managed in the Subscription Type window. The value is for reference only. Subscription management has not been implemented. See .
For more information about these fields, see