An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
A coherent assortment of items:
Introduced at the same time.
For one brand (manufacturer).
For one season and year.
For one market.
A collection is marketed during a limited period of time. A collection can be segmented; for example, a collection might consist of items for men, women, and children. A single item can belong to several collections at the same time.
For example, 50, 100, or 1000 styles may be in one collection.
You may also use collections for catalogs.
A way to manage changes to style items and groups of style items that should not inherit the changes for specific fields where changes have already been applied.
If you make changes to child style items, then the properties that you change become exceptions so that changes made at the parent level are not inherited. Exceptions are exempt from inheritance so that they are not overwritten. The system validates exceptions by field and not by record.
For example, if you specify a price for a shirt at style item root level 0, then this price is inherited by the child style items. If you change the price for the shirt with an extra large (XL) size, then any further changes to price at a higher level will not be inherited by the XL size shirt.
Style item data passes from the style item root level 0 (parent item) to the child-level style items. The child level style item inherits its characteristics from the style item root level 0 item at the time of both item creation and item modification.
A label must contain made-in, composition, and user cleaning code information for a style item. You can define one or several compositions for each style item. For example, in the apparel industry, you define the composition of the main fabric and lining used in the style item.
An option that is a selectable characteristic of an item, for example, a pocket on a shirt, color, or zipper.
An option may also be referred to as a variable.
An item that is assembled from characteristics such as style, fabric, color, length, and other variables. Items can be up to 10 levels deep.
A code that represents the parent style item (or first level) in a multi-level structure of style items. You can have up to 10 levels starting at level 0 through level 9 in an item structure. The parent item is the first level in the multi-level item structure, and it is termed as style item root level 0. The style item root level 0 stores the style item definitions. The basic attributes defined at the first level are inherited by the lower level (or children) style items in the hierarchy.
For example, jeans (JEA) are setup as style item root level 0. A child item of the jeans is JEA.BLACK.ZIP.28.30, which is a pair of black jeans with a zipper, a waist of 28 inches, and length of 30 inches.