| XSD Element Name |
XSD Element Data Type |
XSD Min Occurs |
XSD Max Occurs |
XSD Element Description |
Mapping for Item_Hdr in BDI-RXM application. |
| BDI-RXM's Table Name |
BDI-RXM's Column Name |
Integration API(RIB or/and RSB or/and RSL) |
BDI-RXM's Column Length |
Is Column Required in BDI-RXM's API? |
BDI-RXM's API Description |
| item |
varchar225 |
1 |
1 |
ID of item. Data will always be present in this field. |
RXMDI_ITEM_HDR |
item |
BDI |
25 |
Yes |
item id |
| item_parent |
varchar225 |
0 |
1 |
ID 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. |
RXMDI_ITEM_HDR |
item_parent |
BDI |
25 |
Yes |
ID identifies the item/group at the level above the item. |
| item_grandparent |
varchar225 |
0 |
1 |
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. |
RXMDI_ITEM_HDR |
item_grandparent |
BDI |
25 |
Yes |
Identifies the item/group two levels above the item |
| pack_ind |
varchar21 |
1 |
1 |
This field indicates if the Item is a pack. A pack is a type of Item that acts as a collection of other Items. Packs can either be sold together (e.g. pack goumey chef gift basket consisting of: 1 bottle organic olive oil, 1 bottle truffle oil, 1lb organic coffee, 1 box speciality herbal tea, ...) and/or ordered together (kelly sun 2015 holiday pajama assortment is pack that consists of 8 sets of girls pajamas, each of which has a different design; these items are bought as a pack but sold as units). Packs will have a Y value. Regular items will have a N value. |
RXMDI_ITEM_HDR |
pack_ind |
BDI |
1 |
Yes |
Indicates if item is a pack |
| simple_pack_ind |
varchar21 |
1 |
1 |
This field indicates if the pack item is a simple pack. A simple pack is a collection that consists of multiple of the same item (e.g. it is possible to buy either one unit of a granola bar, or the display box of 20 granola bars - the display box is a pack item itself with a unique UPC; often the full box has a slightly different price than the individual items * qty). Only simple packs will have a Y value. Both complex packs (which consist of a mixture of different items) and regular items will have a N value. |
RXMDI_ITEM_HDR |
simple_pack_ind |
BDI |
1 |
Yes |
This field indicates if the pack item is a simple pack |
| item_level |
number1_0 |
1 |
1 |
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 concept is best explained with typical (although not exhaustive) examples. Staple items generally have a item level = 1 UPCs for Staple items generally have an item level = 2 (and the staple item will be the UPCs parent item). Fashion styles generally have an item level = 1. Fashion skus generally have an item level = 2. If UPCs for fashion skus generally have an item level = 3. Valid values are 1, 2 and 3. This field will always have data. |
RXMDI_ITEM_HDR |
item_level |
BDI |
1 |
Yes |
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. |
| tran_level |
number1_0 |
1 |
1 |
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 inventoried, counted, transferred, shipped, etc. Only one level of the hierarchy of an item family may contain transaction level items. The concept is best explained with typical (although not exhaustive) examples. Staple items generally have a TranLevel = 1. UPCs for Staple items generally have an TranLevel = 1 (inventory txns occur at the staple sku level; sales of the item roll up to the parent staple sku). Fashion styles generally have a TranLevel = 2 (the style itself is not sold/inventoried). Fashion skus generally have an TranLevel = 2 (the fashion sku is sold/inventoried). If UPCs for fashion skus generally have an TranLevel = 2 (the fashion sku is sold/inventoried). There are some rare cases in vendor managed inventory where the TranLevel = 3. Valid values are 1, 2 and 3. This field will always have data. |
RXMDI_ITEM_HDR |
tran_level |
BDI |
Number(1,0) |
Yes |
Number uniquely identifying the class node which the item belongs to |
| inventory_ind |
varchar21 |
1 |
1 |
This indicator is used to determine if inventory is held for the item/item family. Inventory is held for most items. However, inventory is not held (value = N) in some special cases, such as: Concession items (items that are sold by independent in location concessions), Consignment items (items are are not owned by the retailer; financial and inventory processing occurs after the item is sold to a consumer), Containers sold then returned for deposit and some items that are transformed for sale. Valid values are Y and N. This field will always have data. |
RXMDI_ITEM_HDR |
inventory_ind |
BDI |
1 |
Yes |
This indicator is used to determine if inventory is held for the item/item family |
| diff_1_level |
varchar26 |
0 |
1 |
This field will contain either ID or GROUP, based on whether the diff_1 is a group diff or a diff id. |
RXMDI_ITEM_HDR |
diff_1_level |
BDI |
6 |
Yes |
This field will contain either ID or GROUP, based on whether the diff_1 is a group diff or a diff id. |
| diff_1_type |
varchar26 |
0 |
1 |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. Valid values are stored in the DIFF_TYPE table. |
RXMDI_ITEM_HDR |
diff_1_type |
BDI |
6 |
Yes |
Changes you made may not be saved. |
| diff_1 |
varchar210 |
0 |
1 |
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). |
RXMDI_ITEM_HDR |
diff_1 |
BDI |
10 |
Yes |
Changes you made may not be saved. |
| diff_2_level |
varchar26 |
0 |
1 |
This field will contain either ID or GROUP, based on whether the diff_2 is a group diff or a diff id. |
RXMDI_ITEM_HDR |
diff_2_level |
BDI |
6 |
Yes |
This field will contain either ID or GROUP, based on whether the diff_2 is a group diff or a diff id. |
| diff_2_type |
varchar26 |
0 |
1 |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. Valid values are stored in the DIFF_TYPE table. |
RXMDI_ITEM_HDR |
diff_2_type |
BDI |
6 |
Yes |
This field will hold a value of the types of differentiators contained in this differentiator group |
| diff_2 |
varchar210 |
0 |
1 |
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). |
RXMDI_ITEM_HDR |
diff_2 |
BDI |
10 |
Yes |
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). |
| diff_3_level |
varchar26 |
0 |
1 |
This field will contain either ID or GROUP, based on whether the diff_3 is a group diff or a diff id. |
RXMDI_ITEM_HDR |
diff_3_level |
BDI |
6 |
Yes |
This field will contain either ID or GROUP, based on whether the diff_3 is a group diff or a diff id. |
| diff_3_type |
varchar26 |
0 |
1 |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. Valid values are stored in the DIFF_TYPE table. |
RXMDI_ITEM_HDR |
diff_3_type |
BDI |
6 |
Yes |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. |
| diff_3 |
varchar210 |
0 |
1 |
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). |
RXMDI_ITEM_HDR |
diff_3 |
BDI |
6 |
Yes |
diff 3 |
| diff_4_level |
varchar26 |
0 |
1 |
This field will contain either ID or GROUP, based on whether the diff_4 is a group diff or a diff id. |
RXMDI_ITEM_HDR |
diff_4_level |
BDI |
6 |
Yes |
diff_4 |
| diff_4_type |
varchar26 |
0 |
1 |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. Valid values are stored in the DIFF_TYPE table. |
RXMDI_ITEM_HDR |
diff_4_type |
BDI |
6 |
Yes |
This field will hold a value of the types of differentiators contained in this differentiator group, such as S - size, C - color, F - flavor, E - scent, P - pattern. |
| diff_4 |
varchar210 |
0 |
1 |
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). |
RXMDI_ITEM_HDR |
Fill table column name. |
BDI |
6 |
Yes |
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). |
| dept |
number4_0 |
1 |
1 |
Number identifying the department in the merchandise hierarchy to which the item belongs. If the item has a parent, the parent and item will belong to the same department. This data is required |
RXMDI_ITEM_HDR |
dept |
BDI |
4 |
Yes |
Number identifying the department in the merchandise hierarchy to which the item belongs |
| unique_class |
number10_0 |
1 |
1 |
Number uniquely identifying the class node which the item belongs to. Class is not unique ID the merchandise hierarchy. The combination of Dept/Class is unique, but requires use of a composite key. The composite key is generally used in user interfaces. The unique ID can be used in back end processing or in systems that can not have a composite key for a node in the merchandise hierarchy. |
RXMDI_ITEM_HDR |
unique_class |
BDI |
Number(10,0) |
Yes |
Number uniquely identifying the class node which the item belongs to |
| class |
number4_0 |
1 |
1 |
Number identifying the class in the merchandise hierarchy to which the item belongs. If the item has a parent, the parent and item will belong to the same department and class. Class is not a unique ID (e.g. every department can have a class 1). This data is required. |
RXMDI_ITEM_HDR |
class |
BDI |
4 |
Yes |
Number identifying the class in the merchandise hierarchy to which the item belongs. If the item has a parent, the parent and item will belong to the same department and class. Class is not a unique ID (e.g. every department can have a class 1). This data is required. |
| unique_subclass |
number10_0 |
1 |
1 |
Number uniquely identifying the subclass node which the item belongs to. Subclass is not unique ID the merchandise hierarchy. The combination of Dept/Class/Subclass is unique, but requires use of a composite key. The composite key is generally used in user interfaces. The unique ID can be used in back end processing or in systems that can not have a composite key for a node in the merchandise hierarchy. |
RXMDI_ITEM_HDR |
unique_subclass |
BDI |
Number(10,0) |
Yes |
Number uniquely identifying the subclass node which the item belongs to |
| subclass |
number4_0 |
1 |
1 |
Number identifying the subclass in the merchandise hierarchy to which the item belongs. If the item has a parent, the parent and item will belong to the same department, class and subclass. Subclass is not a unique ID (e.g. every department/class can have a subclass 1). This data is required. |
RXMDI_ITEM_HDR |
subclass |
BDI |
Number(4,0) |
Yes |
Number identifying the subclass in the merchandise hierarchy to which the item belongs |
| status |
varchar21 |
1 |
1 |
Item life cycle status of the item. At this time, this field will always contain the character A as only approved items are exported. |
RXMDI_ITEM_HDR |
status |
BDI |
1 |
Yes |
Item life cycle status of the item |
| description |
varchar2250 |
1 |
1 |
Primary description of the item in the integration langauge of the system. This value is required. |
RXMDI_ITEM_HDR |
description |
BDI |
250 |
Yes |
Primary description of the item in the integration langauge of the system |
| secondary_item_desc |
varchar2250 |
0 |
1 |
Secondary descriptions of the item. This field can only be populated when system_options.secondary_desc_ind = Y. |
RXMDI_ITEM_HDR |
secondary_item_desc |
BDI |
250 |
Yes |
Secondary descriptions of the item |
| short_desc |
varchar2120 |
1 |
1 |
Shortened item description. This value is required. |
RXMDI_ITEM_HDR |
short_desc |
BDI |
120 |
Yes |
Shortened item description. |
| brand_name |
varchar230 |
0 |
1 |
This field contains the brand associated to an item. |
RXMDI_ITEM_HDR |
brand_name |
BDI |
30 |
Yes |
brand associated to an item. |
| merchandise_ind |
varchar21 |
1 |
1 |
Indicates if the item is a merchandise item (Y, N). Merchandise items are generally physical items (things that must be shipped/received and of which there is an inventory). Non merchandise items are often items which do not have inventory. Common examples include extra fees for service (extended warranties, alterations) or endlessly available items (downloads, in app purchases of bonus content, subscriptions). All items, both merchandise and non-merchandise are exported from RMS. This value is required. |
RXMDI_ITEM_HDR |
merchandise_ind |
BDI |
1 |
Yes |
Indicates if the item is a merchandise item (Y, N) |
| primary_ref_item_ind |
varchar21 |
1 |
1 |
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 N. For sub transaction level items, this field may be either Y (if the current record is a primary UPC) or N (if the current record is not the primary UPC). |
RXMDI_ITEM_HDR |
primary_ref_item_ind |
BDI |
1 |
Yes |
Indicates if the sub-transaction level item is designated as the primary sub-transaction level item |
| cost_zone_group_id |
number4_0 |
0 |
1 |
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. |
RXMDI_ITEM_HDR |
cost_zone_group_id |
BDI |
4 |
Yes |
Cost zone group associated with the item. |
| standard_uom |
varchar24 |
1 |
1 |
Unit of measure in which stock and or financials of the item is tracked at a corporate level. Unit of measure reference values may have to be manually synced between the systems as this is foundation data that is not currently bulk integrated out of Merch. This value is required. |
RXMDI_ITEM_HDR |
standard_uom |
BDI |
4 |
Yes |
Unit of measure |
| uom_conv_factor |
number20_4 |
0 |
1 |
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). |
RXMDI_ITEM_HDR |
uom_conv_factor |
BDI |
Number(20,4) |
Yes |
Conversion factor between an Each and the standard_uom when the standard_uom is not in the quantity class |
| package_size |
number12_4 |
0 |
1 |
Holds the size of the product printed on any packaging (i.e. 24 ounces). |
RXMDI_ITEM_HDR |
package_size |
BDI |
Number(12,4) |
Yes |
Holds the size of the product printed on any packaging (i.e. 24 ounces). |
| package_uom |
varchar24 |
0 |
1 |
Holds the unit of measure associated with the package size. |
RXMDI_ITEM_HDR |
package_uom |
BDI |
4 |
Yes |
Holds the unit of measure associated with the package size. |
| store_order_multiple |
varchar21 |
0 |
1 |
Merchandise shipped from the warehouses to the stores must be specified in this unit type. Valid values are: C = Cases I = Inner E = Eaches |
RXMDI_ITEM_HDR |
store_order_multiple |
BDI |
1 |
Yes |
Merchandise shipped from the warehouses to the stores must be specified in this unit type |
| forecast_ind |
varchar21 |
1 |
1 |
Indicates if sales forecasts should be produced for this item. Valid values are:Y, N. Data is required in this field |
RXMDI_ITEM_HDR |
forecast_ind |
BDI |
1 |
Yes |
Indicates if sales forecasts should be produced for this item |
| currency_code |
varchar23 |
1 |
1 |
The currency code of the for retail values. This value is required. |
RXMDI_ITEM_HDR |
currency_code |
BDI |
3 |
Yes |
The currency code of the for retail values |
| original_unit_retail |
number20_4 |
0 |
1 |
The original retail price of the item per unit. This field is stored in the primary currency. |
RXMDI_ITEM_HDR |
original_unit_retail |
BDI |
Number(20,4) |
Yes |
The original retail price of the item per unit. |
| mfg_rec_retail |
number20_4 |
0 |
1 |
Manufacturers recommended retail price for the item. Used for informational purposes only. This field is stored in the primary currency. |
RXMDI_ITEM_HDR |
mfg_rec_retail |
BDI |
Number(20,4) |
Yes |
Manufacturers recommended retail price for the item. |
| retail_label_type |
varchar26 |
0 |
1 |
This field indicates any special lable type assoctiated with an item (i.e. pre-priced or cents off). |
RXMDI_ITEM_HDR |
retail_label_type |
BDI |
6 |
Yes |
This field indicates any special label type associated with an item. |
| retail_label_value |
number20_4 |
0 |
1 |
This field represents the value associated with the retail label type. |
RXMDI_ITEM_HDR |
retail_label_value |
BDI |
Number(20,4) |
Yes |
This field represents the value associated with the retail label type. |
| item_aggregate_ind |
varchar21 |
1 |
1 |
This field holds an indicator of whether the retailer wants to aggregate inventory and sales for the item with the inventory and sales of other child items. For staple items, this indicator is always set to N. For fashion items, this indicator may be Y. If this indicator is Y, the retailer may also define which diff positions should be aggregated into item/diff combinations. Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. Data is required in this field |
RXMDI_ITEM_HDR |
item_aggregate_ind |
BDI |
1 |
Yes |
This field holds an indicator of whether the retailer wants to aggregate inventory and sales for the item with the inventory and sales of other child items |
| diff_1_aggregate_ind |
varchar21 |
1 |
1 |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the first Diff defined for the item (e.g Style/Color). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. Data is required in this field. |
RXMDI_ITEM_HDR |
diff_1_aggregate_ind |
BDI |
1 |
Yes |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the first Diff defined for the item (e.g Style/Color) |
| diff_2_aggregate_ind |
varchar21 |
1 |
1 |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the second Diff defined for the item (e.g Style/Waist Size). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. Data is required in this field. |
RXMDI_ITEM_HDR |
diff_2_aggregate_ind |
BDI |
1 |
Yes |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the second Diff defined for the item (e.g Style/Waist Size). |
| diff_3_aggregate_ind |
varchar21 |
1 |
1 |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the third Diff defined for the item (e.g Style/Inseam). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. Data is required in this field. |
RXMDI_ITM_HDR |
diff_3_aggregate_ind |
BDI |
1 |
Yes |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the third Diff defined for the item (e.g Style/Inseam) |
| diff_4_aggregate_ind |
varchar21 |
1 |
1 |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the fourth Diff defined for the item (e.g Style/Pattern). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. Data is required in this field. |
RXMDI_ITEM_HDR |
diff_4_aggregate_ind |
BDI |
1 |
Yes |
This field holds an indicator (Y/N) of whether the retailer wants to aggregate inventory and sales for the item by the fourth Diff defined for the item (e.g Style/Pattern). |
| item_number_type |
varchar26 |
1 |
1 |
This field holds a code descriptor of the type of item number. Valid values for this field include but are not limited to: ITEM (Oracle Retail Item Number), UPC-A (UCC12), UPC-AS (UCC12 with Supplement), UPC-E (UCC8), UPC-ES (UCC8 with Supplement), EAN8 (EAN/UCC-8), EAN13 (EAN/UCC-13), EAN13S (EAN/UCC-13 with Supplement), ISBN10 (ISBN-10), ISBN13 (ISBN-13), NDC (NDC/NHRIC National Drug Code), PLU (PLU), VPLU (Variable Weight PLU), SSCC (SSCC Shipper Carton), UCC14 (EAN/UCC-14), MANL (Manually Created Item Number). This information is required. |
RXMDI_ITEM_HDR |
item_number_type |
BDI |
6 |
Yes |
This field holds a code descriptor of the type of item number. |
| format_id |
varchar26 |
0 |
1 |
This field will hold the format ID that corresponds to the items variable UPC. This value is only used for items with variable UPCs. |
RXMDI_ITEM_HDR |
format_id |
BDI |
6 |
Yes |
This field will hold the format ID that corresponds to the items variable UPC |
| prefix |
number2_0 |
0 |
1 |
This column holds the prefix for variable weight UPCs. |
RXMDI_ITEM_HDR |
prefix |
BDI |
Number(2,0) |
Yes |
This column holds the prefix for variable weight UPCs. |
| rec_handling_temp |
varchar26 |
0 |
1 |
Holds the temperature information associated with the item. |
RXMDI_ITEM_HDR |
rec_handling_temp |
BDI |
6 |
Yes |
Holds the temperature information associated with the item. |
| rec_handling_sens |
varchar26 |
0 |
1 |
Holds the sensitivity information associated with the item. |
RXMDI_ITEM_HDR |
rec_handling_sens |
BDI |
6 |
Yes |
Holds the sensitivity information associated with the item. |
| perishable_ind |
varchar21 |
0 |
1 |
A grocery item attribute used to indicate whether an item is perishable or not. |
RXMDI_ITEM_HDR |
perishable_ind |
BDI |
1 |
Yes |
A grocery item attribute used to indicate whether an item is perishable or not. |
| waste_type |
varchar26 |
0 |
1 |
Identifies the wastage type as either sales or spoilage wastage. Valid values are: SP = Spoilage SL = Sales Wastage is not applicable to pack items. |
RXMDI_ITEM_HDR |
waste_type |
BDI |
6 |
Yes |
Identifies the wastage type as either sales or spoilage wastage |
| waste_pct |
varchar26 |
0 |
1 |
Average percent of wastage for the item over its shelf life. Used in inflating the retail price for wastage items. |
RXMDI_ITEM_HDR |
waste_pct |
BDI |
6 |
Yes |
Average percent of wastage for the item over its shelf life |
| default_waste_pct |
number12_4 |
0 |
1 |
Default daily wastage percent for spoilage type wastage items. |
RXMDI_ITEM_HDR |
default_waste_pct |
BDI |
Fill column length. |
Yes |
Default daily wastage percent for spoilage type wastage items. |
| constant_dim_ind |
varchar21 |
1 |
1 |
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. This field will always have data. |
Fill application table name. |
constant_dim_ind |
BDI |
1 |
Yes |
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. |
| contains_inner_ind |
varchar21 |
1 |
1 |
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. |
RXMDI_ITEM_HDR |
contains_inner_ind |
BDI |
1 |
Yes |
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. |
| sellable_ind |
varchar21 |
1 |
1 |
Indicates if item may be sold as a unit. If it is Y then the item will have its own unique unit retail. If it is N then the item will not have a unit retail. This field will always have data. |
RXMDI_ITEM_HDR |
sellable_ind |
BDI |
1 |
Yes |
Indicates if item may be sold as a unit |
| orderable_ind |
varchar21 |
1 |
1 |
Indicates if item may be ordered as a unit. Valid values are:Y = Yes, this item/pack may be ordered from a single supplier; N = No, this item/pack may not be ordered from a single supplier. Non orderable items might be transformed or produced (in house bakery items) by the retailer. Examples might include (but are not limited to): ground beef item is not orderable because the retailer orders a side of beef and transforms it into ground beef or in house bakery items are not orderable because the retailer produces them in house. This field will always have data. |
RXMDI_ITEM_HDR |
orderable_ind |
BDI |
1 |
Yes |
Indicates if item may be ordered as a unit. |
| pack_type |
varchar21 |
0 |
1 |
Indicates if pack item is a vendor pack or a buyer pack. |
RXMDI_ITEM_HDR |
pack_type |
BDI |
1 |
Yes |
Indicates if pack item is a vendor pack or a buyer pack. |
| order_as_type |
varchar21 |
0 |
1 |
Indicates if pack item is receivable at the component level or at the pack level (for a buyer pack only). |
RXMDI_ITEM_HDR |
Fill table column name. |
BDI |
1 |
Yes |
Indicates if pack item is receivable at the component level or at the pack level (for a buyer pack only). |
| item_service_level |
varchar26 |
0 |
1 |
Holds a value that restricts the type of shipment methods that RCOM can select for an item. |
RXMDI_ITEM_HDR |
item_service_level |
BDI |
Number(1,0) |
Yes |
Holds a value that restricts the type of shipment methods. |
| gift_wrap_ind |
varchar21 |
1 |
1 |
This field will contain a value of Y if the item is eligible to be gift wrapped. If not explicitly defined, this field will default to N. This field will always have data records. |
RXMDI_ITEM_HDR |
gift_wrap_ind |
BDI |
1 |
Yes |
This field will contain a value of Y if the item is eligible to be gift wrapped |
| ship_alone_ind |
varchar21 |
1 |
1 |
This field will contain a value of Y if the item must be shipped alone to consumers. If not explicitly defined, this field will default to N. This field will always have data records. |
RXMDI_ITEM_HDR |
ship_alone_ind |
BDI |
1 |
Yes |
This field will contain a value of Y if the item must be shipped alone to consumers |
| item_form_ind |
varchar21 |
1 |
1 |
This field will contain a value of Y if the item is associated with an item transformation. The item will be either the sellable item or orderable item in the transformation process. Transformations include a side of beef (orderable transformation item) cut into steaks/ground beef etc (sellable transformation items). This field will always have data. |
RXMDI_ITEM_HDR |
item_form_ind |
BDI |
1 |
Yes |
This field will contain a value of Y if the item is associated with an item transformation. The item will be either the sellable item or orderable item in the transformation process |
| catch_weight_ind |
varchar21 |
1 |
1 |
Indicates whether the item should be weighed when it arrives at a location. Valid values for this field are Y and N. This field will always have data |
RXMDI_ITEM_HDR |
catch_weight_ind |
BDI |
1 |
Yes |
Indicates whether the item should be weighed when it arrives at a location. Valid values for this field are Y and N. This field will always have data |
| catch_weight_type |
varchar21 |
0 |
1 |
This column will hold catch weight type for a simple pack catch weight item. |
RXMDI_ITEM_HDR |
catch_weight_type |
BDI |
1 |
Yes |
This column will hold catch weight type for a simple pack catch weight item. |
| catch_weight_order_type |
varchar26 |
0 |
1 |
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 |
RXMDI_ITEM_HDR |
catch_weight_order_type |
BDI |
6 |
Yes |
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 |
| catch_weight_sale_type |
varchar26 |
0 |
1 |
This indicates the method of how catch weight items are sold in store locations. |
RXMDI_ITEM_HDR |
catch_weight_sale_type |
BDI |
6 |
Yes |
This indicates the method of how catch weight items are sold in store locations |
| catch_weight_uom |
varchar24 |
0 |
1 |
UOM for Catchweight Items. |
RXMDI_ITEM_HDR |
catch_weight_uom |
BDI |
4 |
Yes |
UOM for catch weight items |
| deposit_item_type |
varchar26 |
0 |
1 |
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. |
RXMDI_ITEM_HDR |
deposit_item_type |
BDI |
6 |
Yes |
This is the deposit item component type |
| container_item |
varchar225 |
0 |
1 |
This holds the container item number for a contents item. This field is only populated and required if the DEPOSIT_ITEM_TYPE = E. |
RXMDI_ITEM_HDR |
container_item |
BDI |
25 |
Yes |
This holds the container item number for a contents item. This field is only populated and required if the DEPOSIT_ITEM_TYPE = E. |
| deposit_in_price_per_uom |
varchar26 |
0 |
1 |
This field indicates if the deposit amount is included in the price per UOM calculation for a contents item ticket. |
RXMDI_ITEM_HDR |
deposit_in_price_per_uom |
BDI |
6 |
Yes |
This field indicates if the deposit amount is included in the price per UOM calculation for a contents item ticket. |
| soh_inquiry_at_pack_ind |
varchar21 |
1 |
1 |
This field indicates if stock on hand inquiries from downstream systems should be allowed at the pack level for this item. It will default to N for non pack items. This field will always have data. |
RXMDI_ITEM_HDR |
soh_inquiry_at_pack_ind |
BDI |
1 |
Yes |
This field indicates if stock on hand inquiries from downstream systems should be allowed at the pack level for this item |
| notional_pack_ind |
varchar21 |
1 |
1 |
If this indicator is Y, SIM and other downstream systems should track pack inventory at the pack level. If the indicator is N, SIM and other downstream systems will track inventory at the component level. It will default to N for non pack items. This field will always have data. |
RXMDI_ITEM_HDR |
notional_pack_ind |
BDI |
1 |
Yes |
If this indicator is Y, SIM and other downstream systems should track pack inventory at the pack level |
| comments |
varchar22000 |
0 |
1 |
Holds any comments associated with the item. |
RXMDI_ITEM_HDR |
comments |
BDI |
2000 |
Yes |
Fill this description. |
