Item Master

Unique alphanumeric value that identifies the item.

Code specifying what type the item is. Valid values for this field are in the code type UPCT on the code_head and code_detail tables.

This field will hold the format ID that corresponds to the items variable UPC. This value is only used for items with variable UPCs.

This column holds the prefix for variable weight UPCs. The prefix determines the format of the eventual UPC and will be used to decode variable weight UPCs that are uploaded from the POS. It is the clients responsibility to download this value to their scale systems.

Alphanumeric value that uniquely identifies the item/group at the level above the item. This value must exist as an item in another row on the item_master table.

Alphanumeric value that uniquely identifies the item/group two levels above the item. This value must exist as both an item and an item parent in another row on the item_master table.

Indicates if the item is a pack. A pack item is a collection of items that may be either ordered or sold as a unit. Packs require details (i.e. component items and qtys, etc.) that other items do not. This field is required by the database.

Number indicating which of the three levels the item resides. The item level determines if the item stands alone or if it is part of a family of related items. The item level also determines how the item may be used throughout the system.

Number indicating which of the three levels transactions occur for the items group. The transaction level is the level at which the items inventory is tracked in the system. The transaction level item will be counted, transferred, shipped, etc. The transaction level may be at the current item or up to 2 levels above or below the current item. Only one level of the hierarchy of an item family may contain transaction level items.

Indicator to aggregate inventory and sales for the item. Currently, this indiactor is used by allocation and MFP to aggregate inventory for items. For staple items this indictor should be N.

Diff_group or diff_id that differentiates the current item from its item_parent. For an item that is a parent, this field may be either a group (i.e. Mens pant sizes) or a value (6 oz). For an item that is not a parent, this field may contain a value (34X34, Red, etc.) Valid values are found on the diff_group and diff_id tables.

Indicator for the corresponding diff. Indicator to aggregate inventory and sales for an item at Parent/Diff level (e.g Style/Color or Style/Size ). This indicator is currently used by allocation and MFP.

Diff_group or diff_id that differentiates the current item from its item_parent. For an item that is a parent, this field may be either a group (i.e. Mens pant sizes) or a value (6 oz). For an item that is not a parent, this field may contain a value (34X34, Red, etc.) Valid values are found on the diff_group and diff_id tables.

Indicator for the corresponding diff. Indicator to aggregate inventory and sales for an item at Parent/Diff level (e.g Style/Color or Style/Size ). This indicator is currently used by allocation and MFP.

Diff_group or diff_id that differentiates the current item from its item_parent. For an item that is a parent, this field may be either a group (i.e. Mens pant sizes) or a value (6 oz). For an item that is not a parent, this field may contain a value (34X34, Red, etc.) Valid values are found on the diff_group and diff_id tables.

Indicator for the corresponding diff. Indicator to aggregate inventory and sales for a fashion item at Parent/Diff level (e.g Style/Color or Style/Size ). This indicator is currently used by allocation and MFP

Diff_group or diff_id that differentiates the current item from its item_parent. For an item that is a parent, this field may be either a group (i.e. Mens pant sizes) or a value (6 oz). For an item that is not a parent, this field may contain a value (34X34, Red, etc.) Valid values are found on the diff_group and diff_id tables.

Indicator for the corresponding diff. Indicator to aggregate inventory and sales for an item at Parent/Diff level (e.g Style/Color or Style/Size ). This indicator is currently used by allocation and MFP.

Number identifying the department to which the item is attached. The items department will be the same as that of its parent (and, by transitivity, to that of its grandparent). Valid values for this field are located on the deps table.

Number identifying the class to which the item is attached. The items class will be the same as that of its parent (and, by transitivity, to that of its grandparent). Valid values for this field are located on the class table.

Number identifying the subclass to which the item is attached. The items subclass will be the same as that of its parent (and, by transitivity, to that of its grandparent). Valid values for this field are located on the subclass table.

Status of the item. Valid values are: W = Worksheet: item setup in progress, cannot be used in system S = Submitted: item setup complete and awaiting approval, cannot be use in system A = Approved: item is approved and can now be used throughout the system D = Delete Pending, cannot be used in the system.

Long description of the item. This description is used through out the system to help online users identify the item. For items that have parents, this description will default to the parents description plus any differentiators. For items without parents, this description will default to null.

Secondary descriptions of the item. This field can only be populated when system_options.secondary_desc_ind = Y.

Shortened description of the item. This description is the default for downloading to the POS. For items that have parents, this description will default to the parents short description. For items without parents, this description will default to null.

All upper case description of the item (same as upper(item_desc)). This field is not displayed in the on- line item maintenance dialog, but is used in item list of value search processing through out the system.

Indicates if the sub-transation level item is designated as the primary sub-transaction level item. For transaction level items and above the value in this field will be No.

Cost zone group associated with the item. This field is only required when elc_ind (landed cost indicator) is set to Y on the system_options table.

Unit of measure in which stock of the item is tracked at a corporate level.

Conversion factor between an Each and the standard_uom when the standard_uom is not in the quantity class (e.g. if standard_uom = lb and 1 lb = 10 eaches, this factor will be 10). This factor will be used to convert sales and stock data when an item is retailed in eaches but does not have eaches as its standard unit of measure.

Holds the size of the product printed on any packaging (i.e. 24 ounces). This field is used for reporting purposes, as well as by Oracle Retail Price Mangement to determine same sized and different sized items.

Holds the unit of measure associated with the package size. This field is used for reporting purposes and by Oracle Retail Price Management to determine same sized and different sized items.

Indicates if the item is a merchandise item (Y, N).

Merchandise shipped from the warehouses to the stores must be specified in this unit type. Valid values are: C = Cases I = Inner E = Eaches

Indicates if this item will be interfaced to an external forecasting system (Y, N).

The original retail price of the item per unit. This field is stored in the primary currency.

Manufacturers recommended retail price for the item. Used for informational purposes only. This field is stored in the primary currency.

This field indicates any special lable type assoctiated with an item (i.e. pre-priced or cents off). This field is used for reporting purposes only. Values for this field are defined by the RTLT code on code detail.

This field represents the value associated with the retail label type.

Holds the temperature information associated with the item. Valid values for this field are in the code type HTMP on the code_head and code_detail tables.

Holds the sensitivity information associated with the item. Valid values for this field are in the code type HSEN on the code_head and code_detail tables.

Indiactes whether the item should be weighed when it arives at a location. Valid values for this field are Y and N.

Identifies the wastage type as either sales or spoilage wastage. Sales wastage occurs during processes that make an item saleable (i.e. fat is trimmed off at customer request). Spoilage wastage occurs during the products shelf life (i.e. evaporation causes the product to weigh less after a period of time). Valid values are: SP = Spoilage SL = Sales Wastage is not applicable to pack items.

Average percent of wastage for the item over its shelf life. Used in inflating the retail price for wastage items.

Default daily wastage percent for spoilage type wastage items. This value will default to all item locations and represents the average amount of wastage that occurs on a daily basis.

Indicates that the dimensions of the product are always the same, regardless of the supplier. If this field is Y, the dimensions for all suppliers will be defaulted to the primary supplier/primary country dimensions. Editing of dimensions for the item will only be allowed for the primary supplier/primary country.

Indicates if pack item is a simple pack or not. This field will only be available if the item is a pack item. A simple pack is an item whose components are all the same item (i.e. a six pack of cola, etc). Valid values are: Y = Yes, this item is a simple pack N = No, this item is not a simple pack

Indicates if pack item contains inner packs. Vendor packs will never contain inner packs and this field will be defaulted to N. This field will only be available if the item is a pack item. Valid values are: Y = Yes, this pack contains inner packs N = No, this pack does not contain inner packs

Indicates if the item can be sold to end consumers. Certain item types like pack items or certain transformable items are configured as non-sellable, as they are not sold to end consumers. Valid values are Y or N.

Indicates if the item can be ordered from a supplier. Certain items like sellable packs, certain transformable items, or non-physical items (e.g. services) are configured as non-orderable, as they are not purchased in their sellable form from a supplier. Valid values are Y or N.

Indicates if pack item is a vendor pack or a buyer pack. A vendor pack is a pack that the vendor or supplier recognizes and sells to the retailer. If the pack item is a vendor pack, communication with the supplier will use the vendor pack number. A buyer pack is a pack that a buyer has created for internal ease of use. If the pack item is a buyer pack, communication with the supplier will explode the pack out to its component items. This field will only be available if the item is a pack item. If the pack item is not orderable this field must be NULL. Valid values are: V = Vendor B = Buyer

Indicates if pack item is receivable at the component level or at the pack level (for a buyer pack only). This field is required if pack item is an orderable buyer pack. This field must be NULL if the pack is sellable only or a vendor pack. This field will only be available if the item is a pack item. Valid values are: E = Eaches (component level) P = Pack (buyer pack only)

Holds any comments associated with the item.

Holds a value that restricts the type of shipment methods that RCOM can select for an item.

This field will contain a value of Y if the item is eligible to be gift wrapped.

This field will contain a value of Y if the item should be shipped to the customer is a seperate package versus being grouped together in a box.

Date/time stamp of when the record was created. This date/time will be used in export processing. This value should only be populated on insert - it should never be updated.

Holds the Oracle user-id of the user who most recently updated this record. This field is required by the database.

Holds the date time stamp of the most recent update by the last_update_id. This field is required by the database.

This field indicates whether the user has called the itemuda form. Since users may delete defauted UDAs, this will prevent these from being automatically displayed whenever the user enters the itemuda form.

This indicator will show that an item is associated an item transformation. The item will be either the sellable item or orderable item in the transformation process.

Indicates whether or not inventory will be tracked for the item. In some cases, non-physical items (e.g. services) or consignment items are configured as non-inventoried. Valid values are Y or N.

This determines how catch weight items are ordered. Valid values are: F - fixed weight V - Variable weight Valid values are held on the CODE_DETAIL table with a code type = ORDT

This indicates the method of how catch weight items are sold in store locations. Valid values are: V - variable weight each L - Loose weight Valid values are held on the CODE_DETAIL table with a code type = STPE

This is the deposit item component type. A NULL value in this field indicates that this item is not part of a deposit item relationship. The possible values are - E - Contents A - Container Z - Crate T - Returned Item (Empty bottle) P - Complex pack (with deposit items) The Returned item is flagged only to enable these items to be mapped to a separate GL account if required.

This holds the container item number for a contents item. This field is only populated and required if the DEPOSIT_ITEM_TYPE = E.

This field indicates if the deposit amount is included in the price per UOM calculation for a contents item ticket. This value is only required if the DEPOSIT_ITEM_TYPE = E. Valid values are: I - Include deposit amount E - Exclude deposit amount

Only used if AIP is integrated. Determines which case sizes to extract against an item in the AIP interface. Applicable only to non-pack orderable items.

This column will hold catch weight type for a simple pack catch weight item. The value is based on the component items order_type and sale_type: 2 - order_type = Variable Weight, sale_type = Loose Weight 4 - order_type = Variable Weight, sale_type = Variable Weight Each The column will be set only at the time of Item approval. It will be used by the ReIM Invoice Matching process

A grocery item attribute used to indicate whether an item is perishable or not.

This indicates to show the stock on hand at pack level in down stream applications when it is called in POS from SIM.

This is to indicate that the pack item should post the transaction at pack level in SIM. If this indicator is checked in RMS, SIM will track pack item at the pack level. If the indicator is not checked in RMS, SIM will store inventory at the component level.

UOM for Catchweight Items. Oracle Retail target column CATCH_WEIGHT_UOM on ITEM_MASTER.

Product classification is informational only in RMS, but is used by RWMS to determine how to pack customer orders : such as to determine products that may not be able to be packaged together. Classifications are set up as codes in RMS and should be configured as part of an implementation to include classifications that are applicable for each retailer. Examples of classifications may include fragile, toxic, heavy, etc.

This field contains the brand associated to an item

This column holds the User id of the user who created the record.

The item type as used the the Allocation product.

This field contains the current selling unit retail of the item.

This field contains the current selling UOM of the item.

This internal field holds the status prior to deletion of item. Item will be reinstated to this value if ever reinstated.

This optional field will support capture of a more descriptive writeup about the item targeted largely for platforms like Ecommerce platforms, Marketplaces, Order Management Systems etc.

This field impacts how up charges default to transfers and allocations when an item is added. When set to 'D', department-level up charges are applied if item-level up charges are not defined for the item/from-location/to-location combination. When set to 'I', only item-level up charges are applied; department-level up charges are not inherited.