Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
B
Appendix: Flat File Mapping
This appendix describes the mapping from the RMS and RPM flat file format to the Xstore database format. Details are provided for the following mappings:
-
RMS Diff Group Detail
-
RMS Diff Group Header
-
RMS Diffs
-
RMS Item Header
-
RMS Item Location
-
RMS Merchandise Hierarchy
-
RMS Organizational Hierarchy
-
RMS Related Item Detail
-
RMS Related Item Header
-
RMS Store
-
RMS Store Address
-
RMS VAT
-
RMS VAT Item
-
RPM Clearance Price
-
RPM Regular Price
-
RPM Promotions
RMS Diff Group Detail
Table B-1 describes the RMS Diff Group Detail mapping.
Table B-1 RMS Diff Group Detail Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always DIFFGRPDTL. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-1 of B-111
Appendix B RMS Diff Group Header
Table B-1 (Cont.) RMS Diff Group Detail Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: DIFFGRPDTLCRE - Creation of diff group group header information. DIFFGRPDTLMOD - Modification of diff group header information. DIFFGRPDTLDEL - Deletion of diff group header information. Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 | DiffGrou pId | This field holds the ID of the diff group. Data will always be present in this field. | Character | 10 | rms_diff_gr oup_detail | DIFF_GR OUP_ID | VARCHAR 2(10 CHAR) | NA | NA |
| 3 | DiffId | This field holds a unique number ID for the diff. Data will always be present in this field. | Character | 10 | rms_diff_gr oup_detail | DIFF_ID | VARCHAR 2(10 CHAR) | NA | NA |
| 4 | DisplayS eq | Optional sequence to describe the order in which diffs within the diff group should be displayed in user interfaces. Data is optional in this field. | Character | 4 | rms_diff_gr oup_detail | DISPLAY_ SEQ | NUMBER( 4) | NA | NA |
| N A | NA | NA | NA | NA | rms_diff_gr oup_detail | CREATE_ DATE | TIMESTA MP(6) | now() | NA |
| N A | NA | NA | NA | NA | rms_diff_gr oup_detail | UPDATE_ DATE | TIMESTA MP(6) | now() | NA |
RMS Diff Group Header
Table B-2 describes the RMS Diff Group Header mapping.
July 29, 2026 Appendix B-2 of B-111
Appendix B RMS Diff Group Header
Table B-2 RMS Diff Group Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 Family | Value is always DIFFGRPHDR. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 1 Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: DIFFGRPHDRCRE - Creation of diff group group header information. DIFFGRPHDRMOD - Modification of diff group header information. DIFFGRPHDRDEL - Deletion of diff group header information. Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 DiffGrou pId | This field holds a unique number ID for the differentiator group. As primary ID, DiffGroupId cannot be modified. Data will always be present in this field. | Character | 10 | rms_diff_gr oup_head | DIFF_GR OUP_ID | VARCHAR 2(10 CHAR) | NA | NA |
| 3 DiffGrou pDesc | Description of the differentiator group (for example: Men’s Shirt Sizes, Women’s Shoe Sizes, Girls Dress Sizes, Shower Gel Scents, Yogurt Flavors, and so on). Data will always be present in this field in the DIFFGRPHDRCRE and DIFFGRPHDRMOD records. | Character | 120 | rms_diff_gr oup_head | DIFF_GR OUP_DES C | VARCHAR 2(120 CHAR) | NA | NA |
July 29, 2026 Appendix B-3 of B-111
Appendix B RMS Diffs
Table B-2 (Cont.) RMS Diff Group Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 4 DiffTypeI d | This field holds a value of the types of differentiators contained in this differentiator group including, but not limited to: S - size C - color F - flavor E - scent P - pattern Data will always be present in this field in the DIFFGRPHDRCRE and DIFFGRPHDRMOD records. | Character | 6 | rms_diff_gr oup_head | DIFF_TYP E | VARCHAR 2(6 CHAR) | NA | NA |
| 5 DiffType Desc | Contains the description of the differentiator type. Data will always be present in this field in the DIFFGRPHDRCRE and DIFFGRPHDRMOD records. | Character | 120 | NA | NA | NA | NA | Ignored. It is already captured in the diff id tab. |
| N A NA | NA | NA | NA | rms_diff_gr oup_head | CREATE_ DATE | TIMESTA MP(6) | NA | NA |
| N A NA | NA | NA | NA | rms_diff_gr oup_head | UPDATE_ DATE | TIMESTA MP(6) | NA | NA |
RMS Diffs
Table B-3 describes the RMS Diffs mapping.
Table B-3 RMS Diffs Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always DIFFS. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-4 of B-111
Appendix B RMS Diffs
Table B-3 (Cont.) RMS Diffs Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 1 Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: DIFFCRE - Creation of diff information. DIFFMOD - Modification of diff information. DIFFDEL - Deletion of diff information. Data will always be present in this field. | Character | 15 | NA | NA | NA | Determines action. | |
| 2 DiffId | Contains the unique ID of the diff. Data will always be present in this field. | Character | 10 | rms_diff_id s | DIFF_ID | VARCHAR 2(10 CHAR) | NA | Also used to populate rms_diff_gro up_detail for the default Diff Group membership. |
| 3 DiffDesc | Contains the text description of the diff. Data will always exist in this field for DIFFCRE and DIFFMOD. | Character | 120 | rms_diff_id s | DIFF_DES C | VARCHAR 2(120 CHAR) | NA | NA |
| 4 DiffType | Contains the type code for the diff. All diffs belong to one and only one type. Data will always exist in this field for DIFFCRE and DIFFMOD. | Character | 6 | rms_diff_id s | DIFF_TYP E | VARCHAR 2(6 CHAR) | NA | Also used to populate rms_diff_gro up_head for the default Diff Group. |
| 5 DiffType Desc | Contains the description of the diff. Data will always exist in this field for DIFFCRE and DIFFMOD. | Character | 120 | rms_diff_id s | DIFF_TYP E_DESC | VARCHAR 2(120 CHAR) | NA | Also used to populate rms_diff_gro up_head for the default Diff Group. |
July 29, 2026 Appendix B-5 of B-111
Appendix B RMS Diffs
Table B-3 (Cont.) RMS Diffs Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 6 | Industry Code | Can optionally hold the unique code used by industry standards to identify the differentiator. For example, in the US, the National Retail Federation defines a standard Color and Size Codes that gives retailers, vendors, and manufacturers a common language for product color and size identification for EDI purposes. This supplements the information conveyed by UPC codes. For example, mens pants size combination 32x32 has an NRF code number 10492. | Character | 10 | NA | NA | NA | NA | Ignored. |
| 7 | Industry Subgrou p | Can optionally hold a sub-grouping code used by industry standards to further identify the differentiator. For example, in the US, the National Retail Federation uses a subgroup for colors (for example, purple is defined as 500; dark purple represents a range from 501 to 509, medium purple represents a range from 510 to 519, bright purple represents a range from 520 to 529, and so on). | Character | 10 | NA | NA | NA | NA | Ignored. |
| N A | NA | NA | NA | NA | rms_diff_id s | CREATE_ DATE | TIMESTA MP(6) | now() | NA |
| N A | NA | NA | NA | NA | rms_diff_id s | UPDATE_ DATE | TIMESTA MP(6) | now() | NA |
July 29, 2026 Appendix B-6 of B-111
Appendix B RMS Item Header
RMS Item Header
Table B-4 describes the RMS Item Header mapping.
Table B-4 RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always ITEMS. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 1 | Type | Value is always FULLHDR when the program is run in full mode. In delta mode, valid values are: ITEMHDRCRE ITEMHDRMOD ITEMHDRDEL Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 | Location | For corporate level files, this field holds the string CORPORATE. In location specific files, this field holds the numeric ID of the store of WH. | Character | 10 | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | ORG_CO DE, ORG_VAL UE | VARCHA R(30) | ”*“ | DimensionV alue and DimensionTy pe are only used for Style items. |
| 3 | Item | ID of the item. This field will always have data. | Character | 25 | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | ITEM_ID, DIMENSI ON_SYST EM | VARCHA R(60) | NA | DIMENSION _SYSTEM is populated with ItemID for Style items. |
July 29, 2026 Appendix B-7 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 4 | ItemPare nt | ID of the parent of the item. ItemParents can be used as a mechanism to group items together. The ItemParent will also exist as an Item in another row. Data is optional in this field for many items. | Character | 25 | itm_item, itm_item_c ross_refer ence | PARENT_I TEM_ID, ITEM_ID | VARCHA R(60) | NA | If the record represents a UPC item, an itm_item_cro ss_reference record is created. Otherwise, the parent is stored in itm_item.par ent_item_id. If a UPC item, ItemParent is set in itm_item_cro ss_reference .item_id, and the item is stored in itm_item_cro ss_reference .manufactur er_upc. |
| 5 | ItemGran dparent | ID of the grandparent of the Item. ItemGrandparents can be used as a mechanism to group items together. The ItemGrandparent will also exist as an Item in another row. Data is optional in this field for many items. | Character | 25 | NA | NA | NA | NA | Ignored. |
| 6 | PackInd | 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 have a Y value. Regular items have an N value. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-8 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 7 | SimpleP ackInd | 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 (for example, 10 pack of the same item). Only simple packs have a Y value. Both complex packs (which consist of a mixture of different items) and regular items have an N value. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-9 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 8 | ItemLeve l | Number indicating in 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 the following 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 is the UPC’s parent item). Fashion styles generally have an item level = 1. Fashion skus generally have an item level = 2. UPCs for fashion skus generally have an item level = 3. Valid values are 1, 2, and 3. This field will always have data. | Number | 1 | NA | NA | NA | NA | Used to distinguish Item from Style, and UPC from Item. |
July 29, 2026 Appendix B-10 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 9 | TranLeve l | Number indicating which of the three levels of transactions occur for the item’s 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, and so on. Only one level of the hierarchy of an item family may contain transaction level items. The concept is best explained with the following typical (although not exhaustive) examples. Staple items generally have a TranLevel = 1. UPCs for staple items generally have a TranLevel = 1 (inventory transactions 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). UPCs for fashion skus generally have a TranLevel = 2 (the fashion sku is sold/ inventoried). | Number | 1 | NA | NA | NA | NA | Used to distinguish Item from Style, and UPC from Item. |
July 29, 2026 Appendix B-11 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| TranLeve l (Continu ed) | There are some rare cases in vendor- managed inventory where the TranLevel equals 3. Valid values are 1, 2, and 3. This field will always have data. | ||||||||
| 10 | Inventory Ind | This indicator is used to determine if inventory is held for the item/item family. Inventory is not held (value = N) in some cases, such as: Concession items that are sold by independent in location concessions. Consignment items that are not owned by the retailer; financial and inventory processing occurs after the item is sold to a consumer. Containers sold/ returned for deposit. Some items that are transformed for sale. Valid values are Y and N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | itm_item | NOT_INV ENTORIE D_FLAG | NUMBER( 1,0) | NA | When N, then 1; otherwise 0. |
July 29, 2026 Appendix B-12 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 11 | Diff1Leve l | This field describes whether the Diff1 information represents a Diff Group or Diff ID. A Diff Group is a collection of possible Diff IDs. When assigned to a parent item, the diffs in the diff group limit the possible diff IDs that can be assigned to a child of the parent item. Valid Values are GROUP and ID. Data is optional in this field for many items. | Character | 6 | NA | NA | NA | NA | Used to identify Style Item. When GROUP, DataLoader fetches RMS DIFF Group Details to create Dimension System information. When ID, DataLoader fetches the Default DIFF Group for the Diff1Type. |
| 12 | Diff1Type | This field contains the type of the Diff1 information. Valid values can be configured by the retailer. Common examples include: C - Color WS - Waist Sizes F - Flavor SC - Scent Note that these examples are not consistent or required. They are presented here simply to help explain the field. Data is optional in this field for many items. | Character | 6 | itm_item_d imension_t ype | DIMENSI ON | VARCHAR 2(30 CHAR) | NA | Only used when Diff1Level is provided. |
July 29, 2026 Appendix B-13 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 13 | Diff1 | This field contains the ID of the Diff1 information. If the Diff1Level is GROUP, this field contains a Diff Group ID. If the Diff1Level is ID, it contains the ID of a diff (a size, color, and so on.) This field is optional. | Character | 10 | itm_item | DIMENSI ON1 | VARCHAR 2(60 CHAR) | NA | NA |
| 14 | Diff2Leve l | This field describes whether the Diff2 information represents a Diff Group or Diff ID. A Diff Group is a collection of possible Diff IDs. When assigned to a parent item, the diffs in the diff group limit the possible diff IDs that can be assigned to a child of the parent item. Valid values are GROUP and ID. Data is optional in this field for many items. | Character | 6 | NA | NA | NA | NA | Used to identify Style Item. When GROUP, DataLoader fetches RMS DIFF Group Details to create Dimension System information. When ID, DataLoader fetches the Default DIFF Group for the Diff2Type. |
July 29, 2026 Appendix B-14 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 15 | Diff2Type | This field contains the type of the Diff2 information. Valid values can be configured by the retailer. Common examples include: C - Color WS - Waist Sizes F - Flavor SC - Scent Note that these examples are not consistent or required. They are presented here simply to help explain the field. Data is optional in this field for many items. | Character | 6 | itm_item_d imension_t ype | DIMENSI ON | VARCHAR 2(30 CHAR) | NA | Only used when Diff2Level is provided. |
| 16 | Diff2 | This field contains the ID of the Diff2 information. If the Diff1Level is GROUP, this field contains a Diff Group ID. If the Diff1Level is ID, it contains the ID of a diff (a size, color, and so on). Data is optional in this field for many items. | Character | 10 | itm_item | DIMENSI ON2 | VARCHAR 2(60 CHAR) | NA | NA |
July 29, 2026 Appendix B-15 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 17 | Diff3Leve l | This field describes whether the Diff3 information represents a Diff Group or Diff ID. A Diff Group is a collection of possible Diff IDs. When assigned to a parent item, the diffs in the diff group limit the possible diff IDs that can be assigned to a child of the parent item. Valid values are GROUP and ID. Data is optional in this field for many items. | Character | 6 | NA | NA | NA | NA | Used to identify Style Item. When GROUP, DataLoader fetches the RMS DIFF Group Details to create the Dimension System information. When ID, DataLoader fetches the Default DIFF Group for the Diff3Type. |
| 18 | Diff3Type | This field contains the type of the Diff3 information. Valid values can be configured by the retailer. Common examples include: C - Color WS - Waist Sizes F - Flavor SC - Scent Note that these examples are not consistent or required. They are presented here simply to help explain the field. Data is optional in this field for many items. | Character | 6 | itm_item_d imension_t ype | DIMENSI ON | VARCHAR 2(30 CHAR) | NA | Only used when Diff3Level is provided. |
July 29, 2026 Appendix B-16 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 19 | Diff3 | This field contains the ID of the Diff3 information. If the Diff1Level is GROUP, this field contains a Diff Group ID. If the Diff1Level is ID, it contains the ID of a diff (a size, color, and so on). Data is optional in this field for many items. | Character | 10 | itm_item | DIMENSI ON3 | VARCHAR 2(60 CHAR) | NA | NA |
| 20 | Diff4Leve l | This field describes whether the Diff4 information represents a Diff Group or Diff ID.A Diff Group is a collection of possible Diff IDs. When assigned to a parent item, the diffs in the diff group limit the possible diff IDs that can be assigned to a child of the parent item. Valid values are GROUP and ID. Data is optional in this field for many items. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-17 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 21 | Diff4Type | This field contains the type of the Diff4 information. Valid values can be configured by the retailer. Common examples include:C - Color WS - Waist Sizes F - Flavor SC - Scent Note that these examples are not consistent or required. They are presented here simply to help explain the field. Data is optional in this field for many items. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 22 | Diff4 | This field contains the ID of the Diff4 information. If the Diff1Level is GROUP, this field contains a Diff Group ID. If the Diff1Level is ID, it contains the ID of a diff (a size, color, and so on). Data is optional in this field for many items. | Character | 10 | NA | NA | NA | NA | Ignored. |
| 23 | Dept | Number identifying the department in the merchandise hierarchy to which the item belongs. If the item has a parent, the item’s department will be the same as that of its parent. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Number | 4 | itm_item | MERCH_L EVEL_2 (or configured level) | VARCHAR 2(60 CHAR) | NA | D is always appended to the value. The value is used to look up the parent from the loc_org_hier archy to populate merch_level _1. |
July 29, 2026 Appendix B-18 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 24 | Class | Number identifying the class in the merchandise hierarchy to which the item belongs. If the item has a parent, the item’s class will be the same as that of its parent. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 25 | UniqueCl ass | Number uniquely identifying the class node to which the item belongs. Class ID is not unique in the level of the merchandise hierarchy. The combination of Dept/ Class is unique, but requires the use of a composite key. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Number | 10 | itm_item | MERCH_L EVEL_3 (or configured level) | VARCHAR 2(60 CHAR) | NA | C is always appended to the value. |
July 29, 2026 Appendix B-19 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 26 | Subclass | Number identifying the subclass in the merchandise hierarchy to which the item belongs. Subclass ID is not unique in the level of the merchandise hierarchy. The combination of Dept/ Class/Subclass is unique. If the item has a parent, the item’s class will be the same as that of its parent. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 27 | UniqueS ubclass | Number uniquely identifying the subclass node to which the item belongs. Subclass ID is not unique in the level of the merchandise hierarchy. The combination of Dept/ Class/Subclass is unique, but requires the use of a composite key. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records | Character | 10 | itm_item | MERCH_L EVEL_4 (or configured level) | VARCHAR 2(60 CHAR) | NA | S is always appended to the value. |
July 29, 2026 Appendix B-20 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 28 | Status | Item life cycle status of the item. For this release, this field always contains the character A as only approved items are exported. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 29 | ItemDes c | Long description of the item. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 250 | com_transl ations | TRANSLA TION | VARCHAR 2(4000 CHAR) | NA | If Location is CORPORAT E, the com_translat ions record is created using ItemDesc. |
| 30 | Seconda ryItemDe sc | Secondary description of the item. Data is optional in this field. | Character | 250 | NA | NA | NA | NA | Ignored. |
| 31 | ShortDe scription | Shortened item description. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 120 | NA | NA | NA | NA | Ignored. |
| 32 | BrandNa me | This field contains the brand associated to an item. Data is optional in this field. | Character | 30 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-21 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 33 | Merchan diseInd | 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 field will always have data for all records. | Character | 1 | NA | NA | NA | NA | If N, then NON_PHYS ICAL item so the record is skipped. |
| 34 | Primary RefItemI nd | Indicates if the sub- transaction 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). This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-22 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 35 | CostZon eGroupId | Cost zone group associated with the item for ELC calculations. Data is optional in this field. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 36 | Standard UOM | Unit of measure in which stock of the item is tracked at a corporate level. Unit of measure may have to be manually synchronized between the systems as this is foundation data that is not currently bulk integrated out of Merchandising. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 4 | NA | NA | NA | NA | Ignored. |
| 37 | UOMCon vFactor | Conversion factor between an Each and the standard_uom when the standard_uom is not in the quantity class (such as if standard_uom = lb and 1 lb = 10 eaches, this factor will be 10). This factor is 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. Data is optional in this field. | Number | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-23 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 38 | Package Size | Holds the size of the product printed on any packaging (for example, 24 ounces). This field can be used for reporting purposes and to determine same sized and different sized items. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 39 | Package UOM | Holds the unit of measure associated with the package size. This field can be used for reporting purposes and to determine same sized and different sized items. Data is optional in this field. | Character | 4 | NA | NA | NA | NA | Ignored. |
| 40 | StoreOrd Multi | Merchandise shipped from the warehouses to the stores must be specified in this unit type. Valid values are: C = Cases; I = Inner; E = Eaches. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 41 | ForecastI nd | Indicates if sales forecasts will be produced for this item. Valid values are: Y, N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-24 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 42 | OriginalR etail | The original retail price of the item per unit. This field is stored in the primary currency of the Merchandising systems. Data is optional in this field. | Number | 20 | NA | NA | NA | NA | Ignored. |
| 43 | OriginalR etailCurr encyCod e | The currency code of the OriginalRetail. Data is optional in this field. | Character | 3 | NA | NA | NA | NA | Ignored. |
| 44 | MfgRecR etail | Data is optional in this field. | Number | 20 | itm_item | LIST_PRI CE | NUMBER( 17,6) | NA | NA |
| 45 | MfgRecR etailCurr encyCod e | The currency code of the MfgRecRetail. Data is optional in this field. | Character | 3 | NA | NA | NA | NA | Ignored. |
| 46 | RetailLa belType | This field indicates any special label type associated with an item (that is, pre- priced or cents off). This field is used in RMS for reporting purposes only. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 47 | RetailLa belValue | This field represents the value associated with the RetailLabelType. Data is optional in this field. | Number | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-25 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 48 | ItemAggr egateInd | 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 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. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 49 | Diff1Aggr egateInd | 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 (such as Style/Color). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-26 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 50 | Diff2Aggr egateInd | 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 (such as Style/Waist Size). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 51 | Diff3Aggr egateInd | 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 (such as Style/Inseam). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-27 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 52 | Diff4Aggr egateInd | 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 (such as Style/Pattern). Aggregated sales and inventory planning data can be used for inventory decision making and other reporting. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-28 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 53 | ItemNum berType | 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 - SBN-10 ISBN13 - ISBN-13NDC - NDC/ NHRIC - National Drug Code PLU - PLU VPLU - Variable Weight PLU SSCC - SSCC Shipper Carton UCC14 - EAN/ UCC-14 MANL - Manual This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-29 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 54 | FormatID | This field holds the format ID that corresponds to the item’s variable UPC. This value is only used for items with variable weight PLU/ variable weight UPCs (ItemNumberType = VPLU). Valid values include, but are not limited to: A 1-4-6-1 B 1-5-5-1 C 1-4-6-1 D 1-5-5-1 E 2-4-5-1 F 2-4-5-1 G 2-5-4-1 H 2-5-5-1 I 2-4-6-1 J 2-4-6-1 K 2-5-5-1 In the case of a type A, this means the total barcode will be at least 6 digits. The prefix of the barcode will be 1 digit in the first position. The item ID is 4 digits and will be in digits 2 to 5 of the barcode. The variable weight will start in digit 6 of the barcode and be at least 1 (possibly more digits). Data is optional in this field, and can only exist for the ItemNumberType = VPLU. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-30 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 55 | Prefix | This column holds the prefix for variable weight UPCs. The size of the prefix (1 or 2 digits) depends on the FormatID. The prefix is used to standardize variable weight UPCs. Data is optional in this field, and can only exist for the ItemNumberType = VPLU. | Number | 2 | NA | NA | NA | NA | Ignored. |
| 56 | RecHand lingTemp | Holds the temperature information associated with the item. Valid values include, but are not limited to: FRIDGE - Keep Refrigerated at 35°F/ 1.6°C FROZEN - Keep Frozen at 0°F/-18C ROOM - Keep at Room Temperature Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 57 | RecHand lingSens | Holds the sensitivity information associated with the item. Valid values include, but are not limited to: AERO - Aerosol Container - flammable COMPUS - Combustible EXPLOD - Explosive FRAG - Fragile TOXIC - Toxic Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-31 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 58 | Perishabl eInd | Grocery item attribute used to indicate whether an item is perishable. Valid values are Y and N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 59 | WasteTy pe | Identifies the wastage type as either sales or spoilage wastage. Sales wastage occurs during processes that make an item saleable (for example, fat is trimmed off at customer request). Spoilage wastage occurs during the products shelf life (for example, 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. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 60 | WastePc t | Average percent of wastage for the item over its shelf life. Used in inflating the retail price for wastage items. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-32 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 61 | DefaultW astePct | Default daily wastage percent for spoilage type wastage items. This value defaults to all item locations and represents the average amount of wastage that occurs on a daily basis. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 62 | Constant DimInd | This field will always have data. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 63 | Contains InnerInd | Indicates that the dimensions of the product are always the same, regardless of the supplier. Valid values are Y and N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 64 | SellableI nd | Indicates if the item may be sold as a unit. If it is Y, the item will have its own unique unit retail. If it is N, the item will not have a unit retail. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-33 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 65 | Orderabl eInd | Indicates if the 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 for example) 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. In-house bakery items are not orderable because the retailer produces them in house. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-34 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 66 | PackTyp e | Indicates if a 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 ease of use within the retail business. 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 contain data 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. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-35 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 67 | OrderAs Type | Indicates if a pack item is receivable at the component level or at the pack level (for a buyer pack only). This field is required if a 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) Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 68 | ItemServ iceLevel | Default shipping option for consumers. Valid values include, but are not limited to: 2DAY - Second Day GRND - Ground OVRNT - Overnight POVRNT - Priority Overnight Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 69 | GiftWrap Ind | This field contains a value of Y if the item is eligible to be gift wrapped. If not explicitly defined, this field defaults to N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-36 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 70 | ShipAlon eInd | This field contains a value of Y if the item must be shipped alone to consumers. If not explicitly defined, this field defaults to N. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 71 | ItemXfor mInd | This field contains a value of Y if the item is associated with an item transformation. The item will either be the sellable item or orderable item in the transformation process. Transformations include a side of beef (orderable transformation item) cut into steaks/ground beef and so on (sellable transformation items). This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 72 | CatchWe ightInd | 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 for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | itm_item | MEASUR E_REQ_F LAG | NUMBER( 1,0) | NA | If Y, then 1. |
July 29, 2026 Appendix B-37 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 73 | CatchWe ightType | This field holds the 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 Data is optional in this field and will only exist for catch weight, simple pack items. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 74 | CatchWe ightOrder Type | This field holds a code that indicates how catch weight items are ordered. Valid values are: F - Fixed weight V - Variable weight Data is optional in this field and will only exist for catch weight items. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 75 | CatchWe ightSale Type | This field holds a code that indicates how catch weight items are sold in store locations. Valid values are: V - variable weight each L - Loose weight Data is optional in this field and will only exist for catch weight items. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 76 | CatchWe ightUOM | UOM for Catchweight Items. Data is optional in this field and will only exist for catch weight items. | Character | 4 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-38 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 77 | DepositIt emType | 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. Valid values include: 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. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 78 | Containe rItem | This field holds the container item number for a contents item. This field is only populated and required if the DepositItemType is E. It will hold an item number that has a DepositItemType of A. Data is optional in this field. | Character | 25 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-39 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 79 | DepositI nPricePe rOUM | 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_TY PE = E. Valid values are: I - Includes deposit amount E - Excludes deposit amount Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 80 | SOHInqu iryAtPack Ind | This field indicates if stock on hand inquiries from downstream systems should be allowed at the pack level for this item. It defaults to N for non-pack items. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 81 | Notional PackInd | 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 track inventory at the component level. It defaults to N for non-pack items. This field will always have data for the ITEMHDRCRE and ITEMHDRMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-40 of B-111
Appendix B RMS Item Header
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 82 | Commen ts | Holds any free-form comments associated with the item. Data is optional in this field. | Character | 2000 | NA | NA | NA | NA | Ignored. |
| NA | NA | NA | NA | NA | itm_item | MERCH_L EVEL_1 | VARCHAR 2(60 CHAR) | NA | Populated by looking up the parent of the merch_level _2 value in loc_org_hier archy. |
| NA | NA | NA | NA | NA | itm_item | ITEM_TYP CODE | VARCHAR 2(30 CHAR) | STANDA RD | NA |
| NA | NA | NA | NA | NA | itm_item | DESCRIP TION | VARCHAR 2(254 CHAR) | NA | Contains synthesized Translation key following the pattern: “+item: [ITEM ID]:descripti on”. Key maps to the com_tranlsat ion record populated from RMS ItemLoc. |
| NA | NA | NA | NA | NA | itm_item | NAME | VARCHAR 2(254 CHAR) | NA | Contains synthesized Translation key following pattern: “+item: [ITEM ID]:descripti on”. Key maps to com_tranlsat ion record populated from RMS ItemLoc. |
July 29, 2026 Appendix B-41 of B-111
Appendix B RMS Item Location
Table B-4 (Cont.) RMS Item Header Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMSM ax Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | NA | NA | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
| NA | NA | NA | NA | NA | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =ITEMHDR MOD. |
| NA | NA | NA | NA | NA | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | CREATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Not set when Type =ITEMHDR MOD. |
| NA | NA | NA | NA | NA | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =FULLHDR. |
| NA | NA | NA | NA | NA | itm_item, itm_item_d imension_ value, itm_item_d imension_t ype | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Not set when Type =FULLHDR. |
RMS Item Location
Table B-5 describes the RMS Item Location mapping.
Table B-5 RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always ITEMLOC. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-42 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Type | Value is always FULLITEMLOC when the program is run in full mode. In delta mode, valid values are: ITEMLOCCRE ITEMLOCMOD ITEMLOCDEL Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 | LocType | This field indicates whether the location is a Store or Warehouse. Valid values are: S - Store W - Warehouse E - External Finisher Data will always be present in this field. | Character | 1 | itm_item_ options | LEVEL_C ODE | VARCHA R2(30 CHAR) | STORE | If not S, entire record is ignored. |
| 3 | Location | This field holds the numeric ID of the store of WH. Data will always be present in this field. | Number | 10 | itm_item_ options | LEVEL_V ALUE | VARCHA R2(30 CHAR) | NA | NA |
| 4 | Item | ID of the item. Data will always be present in this field. | Character | 25 | itm_item_ options | ITEM_ID | VARCHA R2(60 CHAR) | NA | NA |
| 5 | ItemPar ent | ID of the parent of the item. Item parent does not vary by location, but is included in this feed as a denormalized convenience for downstream systems. Data is optional in this field for many items. | Character | 25 | NA | NA | NA | NA | Ignored, obtained from ItemHdr feed. |
July 29, 2026 Appendix B-43 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 6 | ItemGra ndparen t | ID of the grandparent of Item. Item grandparent does not vary by location, but is included in this feed as a denormalized convenience for downstream systems. Data is optional in this field for many items. | Character | 25 | NA | NA | NA | NA | Ignored, obtained from ItemHdr feed. |
| 7 | InitialUni tRetail | Initial Unit Retail of the item in the item’s standard unit of measure. Data is optional in this field for some type of items. Data is only included in this field for the ITEMLOCCRE and FULLITEMLOC records. After initial item creation, unit retail and other pricing information should come from RPM. If this program is run in full mode and produces FULLITEMLOC records, a full extract from RPM of pricing should also be performed to update all price records. | NA | NA | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-44 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 8 | SellingU nitRetail | Data is optional in this field for some type of items. Data is only included in this field for the ITEMLOCCRE and FULLITEMLOC records. After initial item creation, unit retail and other pricing information should come from RPM. If this program is run in full mode and produces FULLITEMLOC records, a full extract from RPM of pricing should also be performed to update all price records. | Number | 20 | itm_item_ prices | PRICE | NUMBE R(17,6) | NA | When non- null, a Regular Price Event record will be created in itm_item_pr ices. |
| 9 | Currenc yCode | Currency Code of retail values. This field should be populated for the ITEMLOCCRE and FULLITEMLOC records that have InitialUnitRetail and SellingUnitRetail values. | NA | NA | NA | NA | NA | NA | Ignored. |
| 10 | SellingU OM | Data is optional in this field for some type of items. Data is only included in this field for the ITEMLOCCRE and FULLITEMLOC records. | Character | 4 | itm_item_ options | UNIT_OF _MEASU RE_COD E | VARCHA R2(30 CHAR) | NA | NA |
| 11 | TaxableI nd | Indicates if the item is taxable at the location. This field will always have data for FULLITEMLOC, ITEMLOCCRE, and ITEMLOCMOD. | Character | 1 | itm_item_ options | TAX_GR OUP_ID | VARCHA R2(60 CHAR) | 0 | If N, then 0, or configured value, (dataloader- beans.xml). |
July 29, 2026 Appendix B-45 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 12 | LocalIte mDesc | Contains the local description of the item. This may be the same as the primary description of the item, a regional description of the item (jimmies versus sprinkles in the US or roll versus bap versus cob versus bun in the UK), or a value in a local language (Overlay dress - true black knit at US stores versus Lagenkleid - Strick, tiefschwarz at stores in Germany). The intent is that this string is appropriate to print this description on signage/receipts at this location. This field will always have data. | Character | 250 | com_tran slations | TRANSL ATION | VARCHA R2(4000 CHAR) | NA | If translated, ItemDescrip tionsEnable d is true (see dataloader- beans.xml), and then com_transl ations record is created using ItemDesc. It is recommend ed that translated ItemDescrip tionsEnable d be set to false when loading Xcenter because non-local descriptions are used in translation records when loading ItemHdr. |
July 29, 2026 Appendix B-46 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 13 | LocalSh orDesc | May contain an abbreviated local description of the item. This may be the same as the primary abbreviated description of the item, an abbreviation of regional description of the item, or an abbreviation in a local language. The intent is that this string is appropriate to print this description on signage/receipts at this location. Data is optional in this field. | Character | 120 | NA | NA | NA | NA | Ignored. |
| 14 | Ti | Number of shipping units (cases) that make up one tier of a pallet of this item for this location. A location may use a local pallet configuration if there are special space or receiving configurations that make typical pallets impractical. Multiply TI by HI to get the total number of cases for a pallet. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-47 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 15 | Hi | Number of tiers that make up a complete pallet (height). A location may use a local pallet configuration if there are special space or receiving configurations that make typical pallets impractical. Multiply TI by HI to get the total number of cases for a pallet. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 16 | StoreOr derMulti ple | Contains the multiple in which the item needs to be shipped from a warehouse to the location. This field will always have data for FULLITEMLOC, ITEMLOCCRE, and ITEMLOCMOD. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 17 | Status | Current status of item at the location. Valid values are: A - Active, item is valid and can be ordered and sold. I - Inactive, item is valid, but cannot be ordered or sold. C - Discontinued, item is valid and sellable, but no longer orderable .D - Delete, item is pending delete and cannot be ordered or sold.This field will always have data for FULLITEMLOC, ITEMLOCCRE, and ITEMLOCMOD. | Character | 1 | itm_item_ options | ITEM_AV AILABILI TY_COD E, STOCK_ STATUS | VARCHA R2(30 CHAR, VARCHA R2(60 CHAR) | NA | If itemLoc:stat us=A or C, the item_availa bility_code is Available. If itemLoc:stat us=I or D, the item_availa bility_code is NA. If itemLoc:stat us=C, the stock_statu s is DISCONTI NUED. Otherwise, stock_statu s is null. |
July 29, 2026 Appendix B-48 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 18 | DailyWa stePct | Average percentage lost from inventory on a daily basis due to natural wastage. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 19 | Measur eOfEac h | Size of an each in terms of the uom_of_price, for example, 12 oz. This information can be used in ticketing and display to consumers. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 20 | Measur eOfPric e | Size to be used on the ticket in terms of the uom_of_price. For example, if the user wants the ticket to have the label print the price per ounce, this value would be 1. If the user wants the price per 100 grams, this value would be 100. Used in ticketing. Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 21 | UomOfP rice | Unit of measure that is used on the ticket for this item. Data is optional in this field. | Character | 4 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-49 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 22 | Primary Variant | This field is used to address sales of PLUs (that is, above transaction level items) when inventory is tracked at a lower level (that is, UPC). This field only contains a value for items one level higher than the transaction level. Valid choices are any transaction level item that is a child of this item. In order to select a transaction level item as the primary variant, the item/ location relationship must exist at the transaction level. When a transaction level item is specified as a primary variant for an item higher than the transaction level, an extra pos_mods record will be written. Both the transaction level item (that is, UPC) and the higher than transaction level item (that is, PLU) will be sent to the POS to allow the store to sell the PLU. The information sent for the PLU will be the same information sent for the transaction level item (that is, UPC). Data is optional in this field. | Character | 25 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-50 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 23 | Primary CostPac k | This field contains an item number that is a simple pack containing the item in the item column for this record. If populated, the cost of the future cost table will be driven from the simple pack and the deals and cost changes for the simple pack. Data is optional in this field. | Character | 25 | NA | NA | NA | NA | Ignored. |
| 24 | Primary Supplier | Numeric identifier of the supplier who will be considered the primary supplier for the specified item/loc. The supplier/origin country combination will determine the value of the unit cost field on item_loc. If the supplier is changed and ELC = N, the unit cost field on item_loc will be updated with the new supplier’s cost. Data is optional in this field. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 25 | Primary OriginC ountry | Contains the identifier of the origin country which will be considered the primary country for the specified item/location. Data is optional in this field. | Character | 3 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-51 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 26 | Receive AsType | This column determines whether the stock on hand for a pack component item or the buyer pack itself will be updated when a buyer pack is received at a warehouse. Valid values are Each or Pack. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 27 | Inbound Handlin gDays | This field indicates the number of inbound handling days for an item at a warehouse type location. Data is optional in this field. | Number | 2 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-52 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 28 | Source Method | This value is used to specify how the ad-hoc PO/TSF creation process should source the item/location request. If the value is Warehouse, the process will attempt to fill the request by creating a transfer from the warehouse in the source_wh field. If this warehouse does not have enough inventory to fill the request, a purchase order will be created for the item/ location’s primary supplier. For warehouses, it is used by Oracle Retail Allocation to determine the valid sources and destinations for warehouse to warehouse allocations. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 29 | Source Wh | This value is used by the ad-hoc PO/ Transfer creation process to determine from which warehouse to fill the stores request. It is also used by the Allocation process to support warehouse to warehouse allocations. A value is required in this field if the sourcing method is Warehouse. Data is optional in this field. | Number | 10 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-53 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 30 | UinType | This column contains the unique identification number (UIN) used to identify the instances of the item at the location. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Used to determine a Serialized Item. If empty, itm_item.se rialized_ite m_flag is set to 0. Otherwise, itm_item.se rialized_ite m_flag is set to 1. |
| 31 | UinLabe l | This column contains the label for the UIN when displayed in SIM. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 32 | Capture TimeInP roc | This column indicates when the UIN should be captured for an item during transaction processing. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 33 | ExtUinIn d | This Yes/No indicator indicates if the UIN is being generated in the external system. This field will always have data for FULLITEMLOC, ITEMLOCCRE, and ITEMLOCMOD. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-54 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 34 | Intention allyRan gedInd | Determines if the location is ranged intentionally by the user for replenishment/ selling (Y) or incidentally ranged (N) by the RMS programs when the item is not ranged to a specific location on the transaction. This field will always have data for FULLITEMLOC, ITEMLOCCRE, and ITEMLOCMOD. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 35 | Costing Location | Numeric identifier of the costing location for the franchise store. This field may contain a store or a warehouse. Data is optional in this field. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 36 | Costing LocType | This field holds the type of costing location in the CostingLocation field. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 37 | Launch Date | Holds the date that the item should first be sold at the location; in the human readable format DD-MON- YYYY. Data is optional in this field. | Character | 12 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-55 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 38 | QtyKey Options | Determines whether the qty key on a POS should be used for this item at the location. Valid values include, but are not limited to: R - Required P - Prohibited O - Optional Data is optional in this field. | Character | 6 | itm_item_ options | PROMPT _FOR_Q UANTITY FLAG, FORCE QUANTIT Y_OF_O NE_FLAG | NUMBE R(1,0) | NA | PROMPT_ FOR_QUA NTITY_FLA G - 1 if R, otherwise 0. FORCE_Q UANTITY_ OF_ONE_F LAG - 1 if P, otherwise 0. |
| 39 | Manual PriceEnt ry | Determines whether the price can/should be entered manually on a POS for this item at the location. Valid values include, but are not limited to: R - Required P - Prohibited O - Optional Data is optional in this field. | Character | 6 | itm_item_ options | PROMPT _FOR_P RICE_FL AG | NUMBE R(1,0) | NA | 1 if R, othewise 0. |
| 40 | Deposit Code | Indicates if a deposit is associated with this item at the location. Deposits are not subtracted from the retail of an item uploaded to RMS, and so on. This kind of processing is the responsibility of the client and should occur before sales are sent to Sales Audit and RMS. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-56 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 41 | FoodSta mpInd | Indicates whether the item is approved for food stamps at the location. This indicator does not impact processing in Sales Audit and RMS. Data is optional in this field. | Character | 1 | itm_item_ options | FOODST AMP_ELI GIBLE_F LAG | NUMBE R(1,0) | NA | 1 if Y, otherwise 0. |
| 42 | WicInd | Indicates whether the item is approved for WIC at the location. This indicator does not impact processing in Sales Audit and RMS. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 43 | Proporti onalTare Pct | Holds the value associated for the packaging in items sold by weight at the location. The proportional tare is the proportion of the total weight of a unit of an item that is packaging (that is, if the tare item is bulk candy, this is the proportional of the total weight of one piece of candy that is the candy wrapper). Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-57 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 44 | FixedTar eValue | Holds the value associated for the packaging in items sold by weight at the location. Fixed tare is the tare of the packaging. This value is fixed, regardless of how much of the item is sold (that is, if the tare item is bulk candy, this is weight of the bag and twist tie). Data is optional in this field. | Number | 12 | NA | NA | NA | NA | Ignored. |
| 45 | FixedTar eUom | Holds the unit of measure value associated with the tare value. Data is optional in this field. | Character | 4 | NA | NA | NA | NA | Ignored. |
| 46 | Reward EligibleI nd | Holds whether the item is legally valid for various types of bonus point/award programs at the location. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 47 | NatlBra ndComp Item | Holds the nationally branded item to which the current item should be compared. Data is optional in this field. | Character | 25 | NA | NA | NA | NA | Ignored. |
| 48 | ReturnP olicy | Holds the return policy for the item at the location. Retailers may configure any number of return policies. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-58 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 49 | StopSal eInd | Indicates that sale of the item should be stopped immediately at the location (that is, in case of recall, and so on). Data is optional in this field. | Character | 1 | itm_item_ options | ITEM_AV AILABILI TY_COD E | VARCHA R2(30 CHAR | NA | If stopSaleInd =Y, item_availa bility_code is RECALL. Otherwise, see the itemLoc:stat us mapping. |
| 50 | ElectMtk Club | Holds the code that represents the marketing clubs to which the item belongs at the location. Retailers may configure any number of marketing clubs. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 51 | ReportC ode | Code to determine which reports the location should run. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 52 | ReqShel fLifeOn Selectio n | Holds the required shelf life for an item on selection in days. This field is not required. Data is optional in this field. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 53 | ReqShel fLifeOn Receipt | Holds the required shelf life for an item on receipt in days. Data is optional in this field. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 54 | IBShelfL ife | Holds the Investment Buy- specific shelf life for the item/location in days. Data is optional in this field. | Number | 4 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-59 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 55 | StoreRe orderabl eInd | Indicates whether the store may reorder the item. This field is required to be either Y - yes or N - no. The field defaults to N. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 56 | RackSiz e | Indicates the rack size that should be used for the item. This field is not required. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 57 | FullPalle tItem | Indicates whether a store must reorder an item in full pallets only. This field is required to be either Y - yes or N - no. The field defaults to N. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 58 | InStore MarketB asket | Holds the in-store market basket code for this item/location combination. Data is optional in this field. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 59 | Storage Location | Holds the current storage location or bin number for the item at the location. Data is optional in this field. | Character | 7 | NA | NA | NA | NA | Ignored. |
| 60 | AltStora geLocati on | Holds the preferred alternate storage location or bin number for the item at the location. Data is optional in this field. | Character | 7 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-60 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 61 | Returna bleInd | This field contains a value of Yes when the item can be returned to the location. Data is optional in this field. | Character | 1 | itm_item_ options | NOT_RE TURNAB LE_FLAG | NUMBE R(1,0) | NA | 1 if N, otherwise 0. |
| 62 | Refunda bleInd | This field contains a value of Yes when the item is refundable at the location. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 63 | BackOr derInd | This field contains a value of Yes when the item can be back-ordered to the location. Data is optional in this field. | Character | 1 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-61 of B-111
Appendix B RMS Item Location
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 64 | Merch5 andiseIn d | Note that the MerchandiseInd does not vary by locations (items are not physical entities in one location and fees in another). The MerchandiseInd is denormalized to the item/location level because it is a common use case for some downstream systems to care only about physical or non-physical items. This field is denormalized to assist those systems in their filtering logic. All items, both merchandise and non-merchandise, are exported from RMS. This field will always have data for all records. | Character | 1 | NA | NA | NA | NA | If N, then NON_PHY SICAL item so record is skipped. |
| 65 | Clearan ceInd | A flag indicating if the item is in clearance price or regular price. “Y” for clearance price and “N” for regular price. | |||||||
| NA | NA | NA | NA | itm_item, itm_item_ options | ORGANIZ ATION_ID | NUMBE R(10,0) | $ {dtv.loca tion.orga nizationI d} | Always uses default value. | |
| NA | NA | NA | NA | itm_item, itm_item_ options | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =ITEMLOC MOD. | |
| NA | NA | NA | NA | itm_item, itm_item_ options | CREATE_ USER_ID | VARCHA R2(30 CHAR) | DATALO ADER | Not set when Type =ITEMLOC MOD. |
July 29, 2026 Appendix B-62 of B-111
Appendix B RMS Merchandise Hierarchy
Table B-5 (Cont.) RMS Item Location Mapping
| Pos | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | NA | itm_item, itm_item_ options | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =FULLITE MLOC. | |
| NA | NA | NA | NA | itm_item, itm_item_ options | UPDATE_ USER_ID | VARCHA R2(30 CHAR) | DATALO ADER | Not set when Type =FULLITE MLOC. |
RMS Merchandise Hierarchy
Table B-6 describes the RMS Merchandise Hierarchy mapping.
Table B-6 RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always MERCHHIERARCHY . | Character | 20 | ITM_MER CH_HEIR ARCHY | NA | NA | NA | No need to store this information. This information is only consumed by the transformer to determine the feed type. |
July 29, 2026 Appendix B-63 of B-111
Appendix B RMS Merchandise Hierarchy
Table B-6 (Cont.) RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary, and be composed of the entity (DIVISION, GROUP, DEPT, CLASS, SUBCLASS) and the type of change (CRE, MOD, DEL). Examples include: DIVISIONCRE DIVISIONMOD DIVISIONDEL GROUPCRE GROUPMOD GROUPDEL DEPTCRE DEPTMOD DEPTDEL CLASSCRE CLASSMOD CLASSDEL SUBCLASSCRE SUBCLASSMOD SUBCLASSDEL **Note:**Deleting a node of the merchandise hierarchy is unusual, and can only be done if no items are associated with the node. | Character | 15 | ITM_MER CH_HEIR ARCHY | NA | NA | NA | No need to store this information. This information is only consumed by the transformer to determine the action type. |
July 29, 2026 Appendix B-64 of B-111
Appendix B RMS Merchandise Hierarchy
Table B-6 (Cont.) RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 2 | Hierarch yLevel | Value is always DIVISION, GROUP, DEPT, CLASS, SUBCLASS. This field cannot be null. This information identifies the level of the merchandise hierarchy that is described by this record. It is not possible to modify a HierarchyLevel on an existing record. | Character | 10 | ITM_MER CH_HEIR ARCHY | level_code | VARCHAR 2(30 CHAR) | NA | level |
| 3 | Hierarch yNodeId | HierarchyNodeId is only unique within a HierarchyLevel (meaning it is possible, for example, that there is both a DIVISION 1 and a GROUP 1 in the full merchandise hierarchy). It is not possible to modify HierarchyNodeId on an existing record. | Number | 10 | ITM_MER CH_HEIR ARCHY | heirarchy_i d | VARCHAR 2(60 CHAR) | NA | heirarchy id+first letter of hierarchy level. |
| 4 | Hierarch yNodeN ame | Name of the organizational hierarchy entity. This field cannot be null. Description data is only sent in the primary integration language of the system. HierarchyNodename can be modified. | Character | 150 | ITM_MER CH_HEIR ARCHY | description | VARCHAR 2(254 CHAR) | NA | node name |
July 29, 2026 Appendix B-65 of B-111
Appendix B RMS Merchandise Hierarchy
Table B-6 (Cont.) RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 5 | ParentLe vel | Level of the organizational hierarchy above the current node. Both ParentLevel and ParentId should be evaluated to correctly traverse the hierarchy. It is not possible to modify ParentLevel on an existing record. | Character | 10 | ITM_MER CH_HEIR ARCHY | NA | NA | NA | This ID is used to validate the parent child relationship. It is not persisted into the database, but plays a key role in the parent child relationship validation of the merchandise hierarchy. |
| 6 | ParentId | ID of the level of the organizational hierarchy above the current node. Both ParentLevel and ParentId should be evaluated to correctly traverse the hierarchy. ParentId can be modified, meaning it is possible to change the division to which a group belongs. | Number | 10 | ITM_MER CH_HEIR ARCHY | parent_id | VARCHAR 2(60 CHAR) | NA | parent heirarchy id |
July 29, 2026 Appendix B-66 of B-111
Appendix B RMS Merchandise Hierarchy
Table B-6 (Cont.) RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 7 | Grandpa rentMerc hDisplayI d | Only populated for SUBCLASS entities. For subclasses, this column holds the department ID used for display purposes in RMS (department is the grandparent of subclass). Note that in RMS, dept, class, and subclass display IDs are combined to form a composite unique key. Every department can have a class 1. Every class in Department 1000 can have a subclass 1. Looking only at the display IDs, all three values are required for uniqueness. | Number | 4 | NA | NA | NA | NA | NA |
| 8 | parentM erchDisp layId | Only populated for CLASS and SUBCLASS entities. For classes, this column holds the department ID used for display purposes in RMS (department is the parent of class). For subclasses, this column holds the class ID used for display purposes in RMS. Note that in RMS, dept, class, and subclass display IDs are combined to form a composite unique key. Every department can have a class 1. Every class in Department 1000 can have a subclass 1. Looking only at the display IDs, all three values are required for uniqueness. | Number | 4 | NA | NA | NA | NA | NA |
July 29, 2026 Appendix B-67 of B-111
Appendix B RMS Organizational Hierarchy
Table B-6 (Cont.) RMS Merchandise Hierarchy Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 9 | merchDi splayId | Only populated for DEPARTMENT, CLASS, and SUBCLASS entities. For departments, this column holds the department display ID. For classes, this column holds the class display ID. For subclasses, this column holds the subclass display ID. Note that in RMS, dept, class, and subclass display IDs are combined to form a composite unique key. Every department can have a class 1. Every class in Department 1000 can have a subclass 1. Looking only at the display IDs, all three values are required for uniqueness. | Number | 4 | NA | NA | NA | NA | NA |
| NA | NA | NA | NA | ITM_MER CH_HEIR ARCHY | CREATE_ DATE | TIMESTA MP(6) | NA | NA | |
| NA | NA | NA | NA | ITM_MER CH_HEIR ARCHY | CREATE_ USER_ID | VARCHAR 2(30 CHAR) | NA | NA | |
| NA | NA | NA | NA | ITM_MER CH_HEIR ARCHY | UPDATE_ DATE | TIMESTA MP(6) | NA | NA | |
| NA | NA | NA | NA | ITM_MER CH_HEIR ARCHY | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | NA | NA |
RMS Organizational Hierarchy
Table B-7 describes the RMS Organizational Hierarchy mapping.
July 29, 2026 Appendix B-68 of B-111
Appendix B RMS Organizational Hierarchy
Table B-7 RMS Organizational Hierarchy Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 Family | Value is always ORGHIERARCHY. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 1 Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary, and be composed of the entity (COMP, CHAIN, AREA, REGION, DISTRICT, STORE, WH) and the type of change (CRE, MOD, DEL). Examples include: COMPCRE - Creation of a Company node. COMPMOD - Modification of a Company node. CHAINCRE - Creation of Chain node. CHAINMOD - Modification of a Chain node. CHAINDEL - Delete of Chain node. AREACRE - Creation of an Area node. AREAMOD - Modification of Area node. AREADEL - Delete of Area node. REGIONCRE - Creation of Region node. REGIONMOD - Modification of Region node. REGIONDEL - Delete of Region node. DISTRICTCRE - Creation of District node. | Character | 15 | NA | NA | NA | NA | Determines action. |
July 29, 2026 Appendix B-69 of B-111
Appendix B RMS Organizational Hierarchy
Table B-7 (Cont.) RMS Organizational Hierarchy Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| Type (Continu ed) | DISTRICTMOD - Modification of District node. DISTRICTDEL - Delete of a District node. STORECRE - Creation of a Store node. STOREMOD - Modification of Store node. STOREDEL - Delete of Store node. WHCRE - Creation of WH node. WHMOD - Modification of WH node. WHDEL - Delete of WH node. **Note:**Deletion of Company node is not allowed. | NA | NA | NA | NA | NA | NA | NA | |
| 2 | Hierarch yLevel | Value is always COMPANY, CHAIN, AREA, REGION, DISTRICT, STORE, or WAREHOUSE. This field cannot be null. This information identifies the level of the organizational hierarchy that is described by this record. It is not possible to modify a HierarchyLevel on an existing record. | Character | 10 | loc_org_hi erarchy | org_code | VARCHAR 2(30 CHAR) | NA | For the root COMPANY node, the column is hard-coded as ”*“. |
July 29, 2026 Appendix B-70 of B-111
Appendix B RMS Organizational Hierarchy
Table B-7 (Cont.) RMS Organizational Hierarchy Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 3 | Hierarch yNodeId | This information identifies the node of the organizational hierarchy that is described by this record. This field cannot be null. HierarchyNodeId is only unique within a HierarchyLevel (meaning it is possible, for example, that there is both a DISTRICT 1 and a REGION 1 in the full organizational hierarchy). It is not possible to modify HierarchyNodeId on an existing record. | Number | 10 | loc_org_hi erarchy | org_code | VARCHAR 2(60 CHAR) | NA | For the root COMPANY node, the column is hard-coded as ”*“. |
| 4 | Hierarch yNodeNa me | Name of the organizational hierarchy entity. This field cannot be null. Description data is only sent in the primary integration language of the system. HierarchyNodename can be modified. | Character | 150 | loc_org_hi erarchy | description | VARCHAR 2(254 CHAR) | NA | NA |
| 5 | ParentLe vel | Level of the organizational hierarchy above the current node. Both ParentLevel and ParentId should be evaluated to correctly traverse the hierarchy. ParentLevel is null for the COMPANY, but will exist for all other hierarchy levels. Warehouses always have the COMPANY node as their ParentLevel. It is not possible to modify ParentLevel on an existing record. | Character | 10 | loc_org_hi erarchy | parent_cod e | VARCHAR 2(30 CHAR) | NA | For the root COMPANY node, the column is hard-coded as null. For the second level CHAIN node, the column is hard-coded to ”*“. |
July 29, 2026 Appendix B-71 of B-111
Appendix B RMS Organizational Hierarchy
Table B-7 (Cont.) RMS Organizational Hierarchy Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 6 ParentId | ID of the level of the organizational hierarchy above the current node. Both ParentLevel and ParentId should be evaluated to correctly traverse the hierarchy. ParentId is null for the COMPANY, but will exist for all other hierarchy levels. Warehouses always have the COMPANY node ID as their ParentId. ParentId can be modified, meaning it is possible to change the REGION ID that a DISTRICT ID belongs to (but a DISTRICT will always belong to a REGION as it is not possible to change the ParentLevel). | Number | 10 | loc_org_hi erarchy | parent_val ue | VARCHAR 2(60 CHAR) | NA | For the root COMPANY node, the column is hard-coded as null. For the second level CHAIN node, the column is hard-coded to ”*“. |
| 7 MgrNam e | Manager of the current node of the hierarchy. MgrName is null for the COMPANY, and is optional for CHAIN, AREA, REGION, DISTRICT, and WAREHOUSE. It will always exist for STORE in Cre and Mod records. MrgName can be modified. | Number | 10 | loc_org_hi erarchy | level_mgr | VARCHAR 2(254 CHAR) | NA | NA |
July 29, 2026 Appendix B-72 of B-111
Appendix B RMS Organizational Hierarchy
Table B-7 (Cont.) RMS Organizational Hierarchy Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 8 Currency Code | Currency of the current node of the hierarchy. CurrencyCode is null for the COMPANY and optional for CHAIN, AREA, REGION, DISTRICT, and WAREHOUSE. It will always exist for STORE in Cre and Mod records. CurrencyCode can be modified for a CHAIN, AREA, REGION, and DISTRICT. It cannot be modified for a STORE or Warehouse. | Character | 3 | NA | NA | NA | NA | Ignored. |
| N A NA | NA | NA | NA | loc_org_hi erarchy | level_order | NUMBER( 10,0) | NA | 0 - COMPANY 10 - CHAIN 20 - AREA30 - REGION 40 - DISTRICT 1000 - STORE 2000 - Warehouse |
| N A NA | NA | NA | NA | loc_org_hi erarchy | sort_order | NUMBER( 10,0) | NA | Always set to 0. |
| N A NA | NA | NA | NA | loc_org_hi erarchy | inactive_fla g | NUMBER( 1,0) | NA | Use default 0. |
| N A NA | NA | NA | NA | loc_org_hi erarchy | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
| N A NA | NA | NA | NA | loc_org_hi erarchy | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type represents UPDATE. |
| N A NA | NA | NA | NA | loc_org_hi erarchy | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type represents CREATE. |
| N A NA | NA | NA | NA | loc_rtl_loc | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Always set. |
July 29, 2026 Appendix B-73 of B-111
Appendix B RMS Related Item Detail
RMS Related Item Detail
Table B-8 describes the RMS Related Item Detail mapping.
Table B-8 RMS Related Item Detail Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 Family | Value is always ITEMS. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 1 Type | Value is always FULLRELITEMDET when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: RELITEMDETCRE RELITEMDETMOD RELITEMDETDEL Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines Action. Relationship Type is looked up from rms_related_ item_head by RelationshipI d, Location, and Organization Id. |
| 2 Relations hipID | Unique identifier for each relationship header. Data will always be present in this field. | Number | 10 | itm_substit ute_items, itm_attach ed_items | EXTERNA L_ID | VARCHAR 2(60 CHAR) | NA | NA |
| 3 RelatedIt em | Item ID of the related item Data will always be present in this field. | Character | 25 | itm_substit ute_items, itm_attach ed_items | ATTACHE D_ITEM_I D, SUBSTITU TE_ITEM_ ID | VARCHAR 2(60 CHAR) | NA | NA |
| 4 Location | For corporate level files, this field holds the string CORPORATE. In location specific files, this field holds the numeric ID of the store of WH. Data will always be present in this field. | Character | 10 | itm_substit ute_items, itm_attach ed_items | LEVEL_VA LUE | VARCHAR 2(60 CHAR) | NA | NA |
July 29, 2026 Appendix B-74 of B-111
Appendix B RMS Related Item Detail
Table B-8 (Cont.) RMS Related Item Detail Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 5 Priority | Priority is only defined if the relationship is of the type SUBS at the related item header level. In the case of multiple related substitute items, this column could be used (optionally) to define relative priority. If there are multiple substitute items, it is possible not to define a priority, in which case all possible substitutions have the same relative priority. Data is optional in this field. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 6 StartDat e | Optional start date that the item should be used in the relationship in DD- MON-YYYY format. If defined, this date indicates the first date the item should be offered as an upsell, substitute, or cross sell. Data is optional in this field. | Character | 11 | itm_substit ute_items, itm_attach ed_items | BEGIN_DA TETIME | TIMESTA MP(6) | NA | NA |
| 7 EndDate | Optional end date that the item should be used in the relationship; in DD- MON-YYYY format. If defined, this date indicates the last date the item should be offered as an upsell, substitute or cross sell. Data is optional in this field. | Character | 11 | itm_substit ute_items, itm_attach ed_items | END_DAT ETIME | TIMESTA MP(6) | NA | NA |
| N A NA | NA | NA | NA | itm_substit ute_items, itm_attach ed_items | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
July 29, 2026 Appendix B-75 of B-111
Appendix B RMS Related Item Header
Table B-8 (Cont.) RMS Related Item Detail Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A NA | NA | NA | NA | itm_substit ute_items, itm_attach ed_items | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =RELITEMD ETMOD. |
| N A NA | NA | NA | NA | itm_substit ute_items, itm_attach ed_items | CREATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Not set when Type =RELITEMD ETMOD. |
| N A NA | NA | NA | NA | itm_substit ute_items, itm_attach ed_items | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =FULLRELIT EMDET. |
| N A NA | NA | NA | NA | itm_substit ute_items, itm_attach ed_items | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Not set when Type =FULLRELIT EMDET. |
| N A NA | NA | NA | NA | itm_attach ed_items | PROMPT_ TO_ADD_ FLAG | NUMBER( 1,0) | TRUE | Configurable in dataloader- beans.xml. |
| N A NA | NA | NA | NA | itm_attach ed_items | PROMPT_ TO_ADD_ MSG_KEY | VARCHAR 2(254 CHAR) | _commo nAttache dItemsPr ompt | Configurable in dataloader- beans.xml. |
RMS Related Item Header
Table B-9 describes the RMS Related Item Header mapping.
Table B-9 RMS Related Item Header Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always ITEMS. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-76 of B-111
Appendix B RMS Related Item Header
Table B-9 (Cont.) RMS Related Item Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 1 Type | Value is always FULLRELITEMHDR when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: RELITEMHEADCRE RELITEMHEADMOD RELITEMHEADDEL Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. MOD will move records between itm_substute _items and item_attache d_items when the modified record represents a relationshipt ype change between CRSL/UPSL and SUBS. |
| 2 Relations hipID | Unique identifier for each relationship header. Data will always be present in this field. | Number | 20 | rms_relate d_item_he ad | RELATION SHIP_ID | NUMBER( 20,0) | NA | Used as externaId in itm_substute _items and item_attache d_items records. |
| 3 Item | Item for which the relationships are defined. Data will always be present in this field. | Character | 25 | rms_relate d_item_he ad | ITEM | VARCHAR 2(25 CHAR) | NA | When SUBS, this is the primaryItem. When CRSL/ UPSL, this is the soldItem. |
| 4 Location | For corporate level files, this field holds the string CORPORATE. In location specific files, this field holds the numeric ID of the store of WH. Data will always be present in this field. | Character | 10 | rms_relate d_item_he ad | LOCATION | VARCHAR 2(10 CHAR) | NA | Used as levelValue in itm_substute _items and item_attache d_items records. |
July 29, 2026 Appendix B-77 of B-111
Appendix B RMS Related Item Header
Table B-9 (Cont.) RMS Related Item Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 5 Relations hipName | Name given to the relationship. Data will always be present in this field for the RELITEMHEADCRE and RELITEMHEADMOD records, but will not be present for RELITEMHEADDEL records. | Character | 255 | rms_relate d_item_he ad | RELATION SHIP_NA ME | VARCHAR 2(255 CHAR) | NA | Ignored. |
| 6 Relations hipType | Describes the type of relationship. Valid values are: CRSL Cross Sell SUBS Substitution UPSL Up Sell Data will always be present in this field for the RELITEMHEADCRE and RELITEMHEADMOD records, but will not be present for RELITEMHEADDEL records. | Character | 6 | rms_relate d_item_he ad | RELATION SHIP_TYP E | VARCHAR 2(6 CHAR) | NA | Determines the .type of Xstore related item. SUBS = Xstore Substitute Items, CRSL/UPSL = Xstore Attached Items. |
July 29, 2026 Appendix B-78 of B-111
Appendix B RMS Related Item Header
Table B-9 (Cont.) RMS Related Item Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 7 Mandato ryInd | This field indicates whether the relationship should be mandatory. For example, an item such as a laptop may have a mandatory cross sell relationship. The related items could be power cords for the US, UK, Mainland Europe, India, and so on. When the laptop is sold, it should be mandatory that one of the related power cords also be selected. Note that Merchandising/Sales Audit do not validate that the mandatory related item is also sold. Generally, only cross sell relationships are mandatory. Substitution and upsell relationships can be defined as mandatory, but in those cases, the definition of mandatory is at the discretion of the client and generally means that substitution or upsell must, as business process, be offered to consumers. Data will always be present in this field for the RELITEMHEADCRE and RELITEMHEADMOD records, but will not be present for RELITEMHEADDEL records. | Character | 1 | rms_relate d_item_he ad | MANDATO RY_IND | VARCHAR 2(1 CHAR) | NA | No logic is based on this data. |
July 29, 2026 Appendix B-79 of B-111
Appendix B RMS Store
Table B-9 (Cont.) RMS Related Item Header Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A NA | NA | NA | NA | rms_relate d_item_he ad | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
| N A NA | NA | NA | NA | rms_relate d_item_he ad | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =ITEMHDR MOD. |
| N A NA | NA | NA | NA | rms_relate d_item_he ad | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type =FULLRELIT EMHDR |
| N A NA | NA | NA | NA | item_item_ options | ATTACHE D_ITEMS_ FLAG | NUMBER( 1,0) | NA | Set to 1 when CRSL or UPSL, otherwise 0 for Item. |
| N A NA | NA | NA | NA | item_item_ options | SUBSTITU TE_AVAIL ABLE_FLA G | NUMBER( 1,0) | NA | Set to 1 when SUBS, otherwise 0 for Item. |
RMS Store
Table B-10 describes the RMS Store mapping.
Table B-10 RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always STORES. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-80 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: STORECRE - Creation of an Area node STOREMOD - Modification of Area node STOREDEL - Delete of Area node Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 | StoreId | Contains the unique ID of the store. Data will always be present in this field. | Number | 10 | loc_rtl_loc, tax_rtl_loc _tax_mapp ing | STORE_N BR, RTL_LOC _ID | NUMBER( 10,0) | NA | NA |
| 3 | StoreNa me | Contains the full name of the store. Data will always be present in this field for creation and modification records. | Character | 150 | loc_rtl_loc | DESCRIP TION | VARCHA R(254) | NA | NA |
| 4 | StoreNa me10 | Contains a shortened, no more than 10 character name, for the store. Data will always be present in this field for creation and modification records. | Character | 10 | loc_rtl_loc | STORE_N AME | VARCHA R(254) | NA | NA |
| 5 | StoreNa meAbbr | Contains an abbreviation for the store name. Data will always be present in this field for creation and modification records. | Character | 3 | NA | NA | NA | NA | Ignored. |
| 6 | StoreNa meSec | Contains an secondary name for this store. Data in this field is optional. | Character | 150 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-81 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 7 | StoreCla ssId | Contains the code letter indicating the class of which the store is a member. Valid values are A, B, C, D, E, and X. Data will always be present in this field for creation and modification records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 8 | StoreCla ssDesc | Contains the description of the store class. Data will always be present in this field for creation and modification records. | Character | 250 | NA | NA | NA | NA | Ignored. |
| 9 | Manager | Contains the name of the store manager. Data will always be present in this field. for creation and modification records. | Character | 120 | loc_rtl_loc | STORE_M ANAGER | VARCHA R(254) | NA | NA |
| 10 | OpenDat e | Contains the date on which the store opened. Data will always be present in this field for creation and modification records. Format is YYYYMMDD. | Date | 8 | NA | NA | NA | NA | Ignored. |
| 11 | CloseDat e | Contains the date on which the store closed. Data in this field is optional. Format is YYYYMMDD. | Date | 8 | NA | NA | NA | NA | Ignored. |
| 12 | AquireD ate | Contains the date on which the store was acquired. Data in this field is optional. Format is YYYYMMDD. | Date | 8 | NA | NA | NA | NA | Ignored. |
| 13 | Remodel Date | Contains the date on which the store was last remodeled. Data in this field is optional. Format is YYYYMMDD. | Date | 8 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-82 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 14 | FaxNum ber | Contains the fax number for the store. Data in this field is optional. | Character | 20 | loc_rtl_loc | TELEPHO NE_2 | VARCHA R(32) | NA | Optional fax number. |
| 15 | PhoneN umber | Contains the phone number for the store. Data in this field is optional. | Character | 20 | loc_rtl_loc | TELEPHO NE_1 | VARCHA R(32) | NA | Optional phone number. |
| 16 | Holds the email address for the location. Data in this field is optional. | Character | 100 | loc_rtl_loc | EMAIL_AD DR | VARCHA R(254) | NA | Optional address. | |
| 17 | TotalSqF eet | Contains the total square footage of the store. Data in this field is optional. | Number | 8 | NA | NA | NA | NA | Ignored. |
| 18 | SellingS qFeet | Contains the total square footage of the stores selling area. Data in this field is optional. | Number | 8 | NA | NA | NA | NA | Ignored. |
| 19 | LinearDi stance | Holds the total merchandisable space of the location. Data in this field is optional. | Number | 8 | NA | NA | NA | NA | Ignored. |
| 20 | VatRegio n | Contains the number of the Value Added Tax region in which this store is contained. Data in this field is optional. | Number | 4 | tax_rtl_loc _tax_mapp ing | taxLocatio nId | VARCHAR 2(60) | NA | NA |
| 21 | VatInclIn d | Indicates whether Value Added Tax will be included in the retail prices for the store. Valid values are Y or N. Data in this field is optional. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 22 | StockHol dingIn | This column indicates whether the store can hold inventory. Data will always be present in this field for creation and modification records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 23 | ChannelI d | Contains the channel with which the store is associated. Data in this field is optional. | Number | 4 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-83 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 24 | Channel Name | Contains the name of the channel. Data in this field is optional. | Character | 120 | NA | NA | NA | NA | Ignored. |
| 25 | StoreFor mat | Contains the number indicating the format of the store. Data in this field is optional. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 26 | StoreFor matNam e | Contains the description of the format of the store (for example, mall, standalone, city express, and so on). Data in this field is optional. | Character | 60 | NA | NA | NA | NA | Ignored. |
| 27 | MallNam e | Contains the name of the mall in which the store is located. Data in this field is optional. | Character | 120 | NA | NA | NA | NA | Ignored. |
| 28 | District | Contains the number of the district in which the store is a member. Data will always be present in this field. for creation and modification records. Further organizational hierarchy information is available in the Organizational Hierarchy Extract. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 29 | Transfer Zone | NA | Number | 4 | NA | NA | NA | NA | Ignored. |
| 30 | DefaultW h | Contains the number of the warehouse that may be used as the default for creating cross-dock masks. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 31 | StopOrd erDays | Contains the number of days before a store closing when the store will stop accepting orders. This column is used when the store_close_date is defined. | Number | 3 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-84 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 32 | StartOrd erDays | Contains the number of days before the store_open_date that the store will begin accepting orders. Data will always be present in this field. for creation and modification records. | Number | 3 | NA | NA | NA | NA | Ignored. |
| 33 | Currency Code | This field contains the currency code under which the store operates. Data will always be present in this field. for creation and modification records. | Character | 3 | loc_rtl_loc | CURREN CY_ID | VARCHA R(3) | NA | ISO Currency Code. |
| 34 | StoreLan gISOCod e | This column identifies the language to be used for the given store. Data will always be present in this field for creation and modification records. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 35 | TranNoG enerate | Contains the level at which unique POS transaction numbers are generated. If the store has one sequence number that is used for all registers, then the value in this column will be S (Store). Otherwise, the store has unique sequence numbers for each register and the value in this column will be R (Register). Data will always be present in this field for creation and modification records. | Character | 6 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-85 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 36 | IntPOSIn d | Indicates whether or not the POS system at the store is integrated. Data will always be present in this field for creation and modification records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 37 | DunsNu mber | This field holds the Dun and Bradstreet (D&B) number to identify the store. A D&B number is a unique identification number for each physical location of a business. A DUNS number may be issued to any business worldwide, and is required by many credit reporting, national government, and trade organizations. Data in this field is optional. | Character | 9 | NA | NA | NA | NA | Ignored. |
| 38 | DunsLoc | Legacy, generally not used. Data in this field is optional. | Character | 4 | NA | NA | NA | NA | Ignored. |
| 39 | SisterSto re | This field holds a store number which is used to relate the current store to the historical data of an existing store. Data in this field is optional. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 40 | TsfEntity Id | Data in this field is optional. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 41 | OrgUnitI d | Column contains the organizational unit ID value. Data in this field is optional. | Number | 15 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-86 of B-111
Appendix B RMS Store
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 42 | AutoRcv | This column indicates whether the client is allowing automatic receipt for the store. Valid values are Y (Yes), N (No), and D (System Default). Default value should be D. Data will always be present in this field for creation and modification records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 43 | Remerch Ind | Identifies stores that are undergoing a significant re- merchandising effort. Defaults to N. Other values may be present if AIP is integrated with RMS. Data will always be present in this field for creation and modification records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| 44 | StoreTyp e | This indicates whether a particular store is a franchise (F) or company store (C). Data will always be present in this field for creation and modification records. | Character | 6 | NA | NA | NA | NA | Ignored. |
| 45 | WFCust omer | Numeric ID of the customer. Data in this field is optional. | Number | 10 | NA | NA | NA | NA | Ignored. |
| 46 | Timezon e | Indicates the time zone of the store. For example, America/ New_York. Data will always be present in this field for creation and modification records. | Character | 64 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-87 of B-111
Appendix B RMS Store Address
Table B-10 (Cont.) RMS Store Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 47 | Custome rOrderLo cInd | This column determines whether the location is a customer order location. If the indicator is Y, the location can be used by OMS for sourcing/ fulfillment or both. Otherwise, it cannot be used. It is used only for the company stores. | Character | 1 | NA | NA | NA | NA | Ignored. |
| NA | NA | NA | NA | NA | loc_rtl_loc | STORE_N BR | VARCHA R(254) | NA | Always RMS StoreId. |
| NA | NA | NA | NA | NA | loc_rtl_loc, tax_rtl_loc _tax_mapp ing | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses the default value. |
| NA | NA | NA | NA | NA | loc_rtl_loc | LOCATION _TYPE | VARCHA R(60) | STORE | Value can be configured in dataloader- beans-xml. If not configured, then null. |
| NA | NA | NA | NA | NA | loc_rtl_loc | use_till_ac countabilit y_flag | NUMBER( 1,0) | FALSE | Value can be configured in dataloader- beans-xml. |
| NA | NA | NA | NA | NA | loc_rtl_loc | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type = STOREMOD |
| NA | NA | NA | NA | NA | loc_rtl_loc | CREATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | . Not set when Type = STOREMOD |
| NA | NA | NA | NA | NA | loc_rtl_loc | UPDATE_ DATE | TIMESTA MP(6) | now() | . Always set. |
| NA | NA | NA | NA | NA | loc_rtl_loc | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | Always set. |
RMS Store Address
Table B-11 describes the Store Address mapping.
July 29, 2026 Appendix B-88 of B-111
Appendix B RMS Store Address
Table B-11 RMS Store Address Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always STORES. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 1 | Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: STOREDTLCRE Creation of store address information. STOREDTLMOD Modification of store address information. STOREDTLDEL Deletion of store address information. Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. FULL, STOREDTL CRE, and STOREDTL MOD are all interpreted as updates to an existing loc_rtl_loc record. STOREDTL DEL results in the setting of all non-PK address mapped fields with an empty string. |
| 2 | StoreId | Contains the unique ID of the store. Data will always be present in this field. | Number | 10 | loc_rtl_loc | RTL_LOC _ID | NUMBER( 10,0) | NA | NA |
| 3 | AddrTyp e | Contains the code used to identify the address type. Data will always be present in this field. | Character | 2 | NA | NA | NA | NA | Must match the configurable AddrType code, otherwise record is ignored. |
| 4 | AddrTyp eDesc | Description of the address type code. Common examples include: 01 - Business, 02 - Postal, 03 - Returns, 04 - Order, 05 - Invoice, 06 - Remittance Optional. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-89 of B-111
Appendix B RMS Store Address
Table B-11 (Cont.) RMS Store Address Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 5 | PrimaryA ddrInd | Indicates whether the address is the primary address for the address type. Valid values are Y and N. Data will always be present in this field. | Character | 1 | NA | NA | NA | NA | If not Y, the entire record is ignored. |
| 6 | Add1 | Contains the first line of the address. Data will always be present in this field for STOREDTLCRE and STOREDTLMOD. | Character | 240 | loc_rtl_loc | ADDRESS 1 | VARCHAR 2(254 CHAR) | NA | NA |
| 7 | Add2 | Contains the second line of the address. Optional. | Character | 240 | loc_rtl_loc | ADDRESS 2 | VARCHAR 2(254 CHAR) | NA | NA |
| 8 | Add3 | Contains the third line of the address. Optional. | Character | 240 | loc_rtl_loc | ADDRESS 3 | VARCHAR 2(254 CHAR) | NA | NA |
| 9 | City | Contains the name of the city that is associated with the address. Data will always be present in this field for STOREDTLCRE and STOREDTLMOD. | Character | 120 | loc_rtl_loc | CITY | VARCHAR 2(30 CHAR) | NA | NA |
| 10 | County | Contains the county name for the location. Optional. | Character | 250 | NA | NA | NA | NA | NA |
| 11 | State | Contains the state abbreviation for the address. Optional. | Character | 3 | loc_rtl_loc | STATE | VARCHAR 2(30 CHAR) | NA | NA |
| 12 | Country | Contains the country where the address exists, using ISO 3166-1 alpha-2. Data will always be present in this field for STOREDTLCRE and STOREDTLMOD. | Character | 3 | loc_rtl_loc | COUNTRY | VARCHAR 2(254 CHAR) | NA | NA |
| 13 | PostCod e | Contains the postal code name for the location. Optional. | Character | 30 | loc_rtl_loc | POSTAL_ CODE | VARCHAR 2(30 CHAR) | NA | NA |
| 14 | Jurisdicti onCode | Contains the tax jurisdiction code for the location. Optional. | Character | 10 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-90 of B-111
Appendix B RMS VAT
Table B-11 (Cont.) RMS Store Address Mapping
| Po s | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 15 | Contact Name | Contains the name of the contact person at this address. Optional. | Character | 120 | NA | NA | NA | NA | Ignored. |
| 16 | ContactP hone | Contains a phone number of the contact person at this address. Optional. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 17 | ContactF ax | Contains a fax number of the contact person at this address. Optional. | Character | 20 | NA | NA | NA | NA | Ignored. |
| 18 | ContactE | Contains an email for the contact person at this address. Optional. | Character | 100 | NA | NA | NA | NA | Ignored. |
| NA | NA | NA | NA | NA | loc_rtl_loc | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
| NA | NA | NA | NA | NA | loc_rtl_loc | UPDATE_ DATE | TIMESTA MP(6) | now() | NA |
| NA | NA | NA | NA | NA | loc_rtl_loc | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | NA |
RMS VAT
Table B-12 describes the RMS VAT mapping.
Table B-12 RMS VAT Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always VAT. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-91 of B-111
Appendix B RMS VAT
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 1 Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: VATCRE - Creation of VAT information. VATMOD - Modification of VAT information. VATDEL - Deletion of VAT information. Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines action. |
| 2 VatRegio n | ID of the VAT region. Stores are assigned to a VAT region (if VAT is used in RMS). This field will always have data. | Number | 4 | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup_rule, tax_tax_rat e_rule | TAX_LOC_ ID, TAX_AUT HORITY_I D | VARCHAR 2(60 CHAR) | NA | Use RMS VAT region ID as the tax authority ID in Xstore. |
| 3 VatRegio nName | This field contains the alphanumeric identification for the VAT code. Valid values include, but are not limited to: S - Standard C - Composite Z - Zero E - Exempt This field will always have data. | Character | 120 | tax_tax_lo c, tax_tax_au thority | NAME, DESCRIP TION | VARCHA R(254) | NA | Use RMS VAT region name as the tax authority name in Xstore. |
| 4 VatCode | This field contains the description of the VAT Code. This field will always have data in the VATCRE and VATMOD records. | Character | 6 | tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | TAX_GRO UP_ID | VARCHA R(60) | NA | NA |
July 29, 2026 Appendix B-92 of B-111
Appendix B RMS VAT
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 5 VatCode Desc | This field contains the description of the VAT Code. This field will always have data in the VATCRE and VATMOD records. | Character | 120 | tax_tax_gr oup, tax_tax_gr oup_rule | NAME, DESCRIP TION | VARCHA R(254) | NA | For the root COMPANY node, the column is hard-coded as null. For the second level CHAIN node, the column is hard-coded to ”*“. |
| 6 ActiveDa te | This field is the date the VAT code is active for the VAT region, in human readable format DD-MON- YYYY. This field will always have data. | Character | 12 | tax_tax_rat e_rule | PERCENT AGE | NUMBER( 8,6) | NA | NA |
| 7 VatRate | VAT rate for the VAT code/VAT region. This field will always have data in the VATCRE and VATMOD records. | Number | 20 | tax_tax_rat e_rule | EFFECTIV E_DATETI ME | TIMESTA MP(6) | NA | NA |
| N A NA | NA | NA | NA | tax_tax_gr oup_rule | TAX_TYP CODE | VARCHA R(30) | VAT | Always uses default value. |
| N A NA | NA | NA | NA | tax_tax_gr oup_rule | TAX_RULE _SEQ_NB R | NUMBER( 10,0) | 1 | Always uses default value. The assumption is that there can only be one tax rule per VAT region/VAT code combination. |
| N A NA | NA | NA | NA | tax_tax_gr oup_rule | TAXED_AT TRANS LEVEL_FL AG | NUMBER( 1,0) | TRUE | A configuration spring loaded by the transformer. The out-of- box default is TRUE. |
July 29, 2026 Appendix B-93 of B-111
Appendix B RMS VAT
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | NA | tax_tax_rat e_rule | EXPR_DA TETIME | TIMESTA MP(6) | NA | This has to be derived by the integration layer. During a CRE/FULL, if there is a subsequent rate rule as sorted by effective date, expire this rate rule by setting its expiration date to be 1 millisecond less than the effective date of the subsequent rate rule; otherwise do not expire this rate rule by setting its expiration date to NULL. During a CRE/FULL, if there is a prior rate rule as sorted by effective date, expire the prior rate rule by setting its expiration date to be 1 millisecond less than this effective date. |
July 29, 2026 Appendix B-94 of B-111
Appendix B RMS VAT
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A NA | NA | NA | NA | NA | EXPR_DA TETIME (Continued ) | NA | NA | During a DEL, if there is a prior rate rule as sorted by effective date, extend the prior rate rule by setting its expiration date to be the expiration date of this rate rule. |
| N A NA | NA | NA | NA | tax_tax_rat e_rule | TAX_RULE _SEQ_NB R | NA | 1 | Always uses the default value. The assumption is that there can only be one tax rule per VAT region/VAT code combination. |
| N A NA | NA | NA | NA | tax_tax_rat e_rule | TAX_RATE _RULE_S EQ | NUMBER( 10,0) | NA | This has to be derived by the integration layer. For a newly created VAT rate, its sequence number is one after the maximum rate rule sequence number in the table. |
| N A NA | NA | NA | NA | tax_tax_au thority | ROUNDIN G_CODE | VARCHA R(30) | HALF_U P | A configuration spring loaded by the transformer. The out-of- box default is HALF_UP. |
July 29, 2026 Appendix B-95 of B-111
Appendix B RMS VAT
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A NA | NA | NA | NA | tax_tax_au thority | ROUNDIN G_DIGITS _QUANTIT Y | NUMBER( 10,0) | 2 | A configuration spring loaded by the transformer. The out-of- box default is 2. |
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | EXTERNA L_SYSTE M | VARCHA R(30) | RMS | Always uses the default value. |
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | ORG_CO DE | VARCHA R(30) | * | Always uses the default value. |
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | ORG_VAL UE | VARCHA R(60) | * | Always uses the default value. |
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | ORGANIZ ATION_ID | NUMBER( 10,0) | $ {dtv.locati on.organi zationId} | Always uses the default value. |
July 29, 2026 Appendix B-96 of B-111
Appendix B RMS VAT Item
Table B-12 (Cont.) RMS VAT Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | CREATE_ DATE | TIMESTA MP(6) | now() | Not set when Type represents UPDATE. |
| N A NA | NA | NA | NA | tax_tax_lo c, tax_tax_au thority, tax_tax_gr oup, tax_tax_gr oup_rule, tax_tax_rat e_rule | UPDATE_ DATE | TIMESTA MP(6) | now() | Not set when Type represents CREATE. |
RMS VAT Item
Table B-13 describes the RMS VAT Item mapping.
Note
Do not import a .dat file containing multiple VATITEM records with the same item ID. More than one record for the same item ID could result in an undesired outcome.
Table B-13 RMS VAT Item Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 0 | Family | Value is always VATITEM. Data will always be present in this field. | Character | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-97 of B-111
Appendix B RMS VAT Item
Table B-13 (Cont.) RMS VAT Item Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 1 Type | Value is always FULL when the program is run in full mode. If the program is run in delta mode, the type will vary based on the type of change (CRE, MOD, DEL). Valid values are: VATITEMCRE- Creation of VAT Item information. VATITEMMOD - Modification of VAT Item information. VATITEMDEL - Deletion of VAT Item information. Data will always be present in this field. | Character | 15 | NA | NA | NA | NA | Determines actions. |
| 2 Item | ID of the item. Data will always be present in this field. | Character | 25 | itm_item_o ptions | item_id | VARCHA R(60 CHAR) | NA | NA |
| 3 VatRegio n | ID of the VAT region. Stores are assigned to a VAT region if VAT is used in RMS. Additional information about VAT Regions is stored in RMS, but is not integrated out of the system. VAT region information may need to the synchronized to downstream systems as a manual process. This field will always have data. | Number | 4 | NA | NA | NA | NA | Ignored. |
| 4 ActiveDa te | Date that the VAT rate becomes active, in DD-MON-YYYY format. This field will always have data in the VATITEMCRE and VATITEMMOD records. | Character | 11 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-98 of B-111
Appendix B RMS VAT Item
Table B-13 (Cont.) RMS VAT Item Mapping
| P os RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 5 VatType | The field describes what the VAT rate applies to: C - Cost values R - Retail values B - Both Cost and Retail values This field will always have data. | Character | 1 | NA | NA | NA | NA | Record ignored when VatType=C. |
| 6 VatCode | This field contains the alphanumeric identification for the VAT code. Valid values include, but are not limited to: S - Standard C - Composite Z - Zero E - Exempt If additional VAT Codes are defined in RMS, the VAT code information may need to the synchronized to downstream systems as a manual process. This field will always have data. | Character | 6 | itm_item_o ptions | tax_group_ id | VARCHA R(60) | NA | Column tax_group_id is set to null if Type is VATITEMDE L. Column tax_group_id is unchanged when VatType is C. Otherwise, column tax_group_id is set to the value of the VatCode. |
| 7 VatRate | VAT rate for the item/VAT region. This field will always have data in the VATITEMCRE and VATITEMMOD records. | Number | 20 | NA | NA | NA | NA | Ignored. |
July 29, 2026 Appendix B-99 of B-111
Appendix B RPM Clearance Price
Table B-13 (Cont.) RMS VAT Item Mapping
| P os | RMS Field Name | RMS Description | RMS Field Type | RMS Max Width | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|---|
| 8 | Reverse VatInd | Indicates if the item is subject to reverse charge VAT at the VAT region. VAT reversal can apply to invoices on some items in some VAT regions. Valid values are Y and N. This field will always have data in the VATITEMCRE and VATITEMMOD records. | Character | 1 | NA | NA | NA | NA | Ignored. |
| N A | NA | NA | NA | NA | itm_item_o ptions | UPDATE_ USER_ID | VARCHAR 2(30 CHAR) | DATALO ADER | NA |
| N A | NA | NA | NA | NA | itm_item_o ptions | UPDATE_ DATE | TIMESTA MP(6) | now() | NA |
RPM Clearance Price
The following tables describe the RPM Clearance Price mapping.
Table B-14 describes the Clearance Price FDETL record mapping. FDETL records are interpreted as Create or Update events.
Table B-14 RPM Clearance Price FDETL Record Mapping
| P os | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 | Record Descriptor | File Detail Marker (1 per clearance create/ modify) | Char(5) | NA | NA | NA | NA | Used to determine unit type. |
| 1 | Line Id | Unique line identification | Number(10 ) | NA | NA | NA | NA | Ignored. |
| 2 | Event Type | CRE = Create, MOD = Modify | Char(3) | NA | NA | NA | NA | Used to determine the action type. |
| 3 | Id | Clearance identifier | Number(15 ) | itm_item_pri ces | EXTERNAL_ ID | VARCHAR2( 60 CHAR) | NA | NA |
| 4 | Item | Item identifier | Char(25) | itm_item_pri ces | ITEM_ID | VARCHAR2( 60 CHAR) | NA | NA |
July 29, 2026 Appendix B-100 of B-111
Appendix B RPM Clearance Price
Table B-14 (Cont.) RPM Clearance Price FDETL Record Mapping
| P os | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 5 | Effective Date | Clearance Effective Date (YYYYMMDDHH24MI SS) | Date | itm_item_pri ces | EFFECTIVE _DATE | TIMESTAMP( 6) | NA | NA |
| 6 | Selling Retail | Selling retail with price change applied | Number(20 ,4) | itm_item_pri ces | PRICE | NUMBER(17, 6) | NA | NA |
| 7 | Selling Retail UOM | Selling retail unit of measure | Char(4) | NA | NA | NA | NA | Ignored |
| 8 | Selling Retail Currency | Selling retail currency | Char(3) | NA | NA | NA | NA | Ignored (assumed to be base Currency). |
| 9 | Reset Clearance ID | Clearance reset identification | Number(15 ) | NA | NA | NA | NA | Used to detect clearance reset. Clearance reset is when this value exactly matches the ID field’s value. |
| N A | NA | NA | NA | itm_item_pri ces | ORGANIZAT ION_ID | NUMBER(10, 0) | $ {dtv.locati on.organi zationId} | Always uses default value. |
| N A | NA | NA | NA | itm_item_pri ces | PROPERTY _CODE | VARCHAR2( 60 CHAR) | NA | CLEARAN CE_PRICE when Clearance event, or REGULAR_ PRICE when Clearance Reset event. |
| N A | NA | NA | NA | itm_item_pri ces | CREATE_DA TE | TIMESTAMP( 6) | now() | Not set when EventType = Mod. |
| N A | NA | NA | NA | itm_item_pri ces | CREATE_U SER_ID | VARCHAR2( 30 CHAR) | DATALOA DER | Not set when EventType = Mod. |
| N A | NA | NA | NA | itm_item_pri ces | UPDATE_DA TE | TIMESTAMP( 6) | now() | Always set. |
July 29, 2026 Appendix B-101 of B-111
Appendix B RPM Regular Price
Table B-14 (Cont.) RPM Clearance Price FDETL Record Mapping
| P os | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| N A | NA | NA | NA | itm_item_pri ces | UPDATE_US ER_ID | VARCHAR2( 30 CHAR) | DATALOA DER | Always set. |
| N A | NA | NA | NA | itm_item_pri ces | EXTERNAL_ SYSTEM | VARCHAR2( 60 CHAR) | RPM- CLRPC | NA |
Table B-15 describes the Clearance Price FDELE record mapping. FDELE records are interpreted as Delete events.
Table B-15 RPM Clearance Price FDELE Record Mapping
| P os | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 | Record Descriptor | File Detail Delete Marker (1per clearance delete) | Char(5) | NA | NA | NA | NA | Used to determine unit type. |
| 1 | Line Id | Unique line identification | Number(1 0) | NA | NA | NA | NA | Ignored. |
| 2 | Id | Clearance identifier | Number(1 5) | itm_item_pri ces | EXTERNAL _ID | VARCHAR2( 60 CHAR) | NA | NA |
| 3 | Item | Item identifier | Char(25) | itm_item_pri ces | ITEM_ID | VARCHAR2( 60 CHAR) | NA | NA |
| NA | NA | NA | itm_item_pri ces | ORGANIZAT ION_ID | NUMBER(10 ,0) | $ {dtv.locati on.organi zationId} | Always uses default value. | |
| NA | NA | NA | itm_item_pri ces | EXTERNAL _SYSTEM | VARCHAR2( 60 CHAR) | RPM- CLRPC | NA |
RPM Regular Price
The following tables describe the RPM Regular Price mapping.
Table B-16 describes the Regular Price FDETL record mapping. FDETL records are interpreted as Create or Update events.
Table B-16 RPM Regular Price FDETL Record Mapping
| Po s | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 | Record Descriptor | File Detail Marker (1 per price change create or modify) | Char(5) | NA | NA | NA | NA | Type of event. |
July 29, 2026 Appendix B-102 of B-111
Appendix B RPM Regular Price
Table B-16 (Cont.) RPM Regular Price FDETL Record Mapping
| Po s | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 1 | Line Id | Unique line identification | Number(1 0) | NA | NA | NA | NA | Ignored. |
| 2 | Event Type | CRE = Create, MOD = Modify | Char(3) | NA | NA | NA | NA | Used by the transformer to determine the type of event. |
| 3 | Id | Price change identifier | Number(1 5) | itm_item_pri ces | EXTERNAL_ ID | VARCHAR2( 60 CHAR) | NA | NA |
| 4 | Item | Item identifier | Char(25) | itm_item_pri ces | ITEM_ID | VARCHAR2( 60 CHAR) | NA | NA |
| 5 | Effective Date | Effective Date of the price change (YYYYMMDDHH24MI SS) | NA | itm_item_pri ces | EFFECTIVE _DATE | TIMESTAMP( 6) | NA | NA |
| 6 | Selling Unit Change Ind | Indicates whether the selling unit retail changed with this price event (0 = no change, 1 = changed). | Number(1) | NA | NA | NA | NA | This field need not be persisted in the Xstore database. This field is used in transformer logic. |
| 7 | Selling Retail | Selling retail with price change applied | Number(2 0,4) | itm_item_pri ces | PRICE | NUMBER(17 ,6) | NA | NA |
| 8 | Selling Retail UOM | Selling retail unit of measure | Char(4) | itm_item | UNIT_OF_M EASURE_C ODE | VARCHAR2( 30 BYTE) | NA | Ignored. |
| 9 | Selling Retail Currency | Selling retail currency | Char(3) | NA | NA | NA | NA | Ignored (assumed to be base Currency). |
| 10 | Multi-Unit Change Ind | Did multi-unit retail change with this price event (0 = no change, 1 = changed) | Number(1) | NA | NA | NA | NA | NA |
| 11 | Multi-Units | NA | Number(1 2,4) | NA | NA | NA | NA | NA |
| 12 | Multi-Unit Retail | Number of multi-units | Number(2 0,4) | NA | NA | NA | NA | NA |
| 13 | Multi-Unit UOM | Multi-Unit Retail unit of measure | Char(4) | NA | NA | NA | NA | NA |
| 14 | Multi-Unit Currency | Multi-Unit Retail Currency | Char(3) | NA | NA | NA | NA | NA |
July 29, 2026 Appendix B-103 of B-111
Appendix B RPM Regular Price
Table B-16 (Cont.) RPM Regular Price FDETL Record Mapping
| Po s | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | NA | itm_item_pri ces | ORGANIZAT ION_ID | NUMBER(10 ,0) | $ {dtv.locati on.organi zationId} | Always uses the default value. |
| NA | NA | NA | NA | itm_item_pri ces | PROPERTY _CODE | VARCHAR2( 60 CHAR) | NA | REGULAR_ PRICE will be the value. |
| NA | NA | NA | NA | itm_item_pri ces | CREATE_D ATE | TIMESTAMP( 6) | now() | Current time stamp. Not set when the event type =MOD. |
| NA | NA | NA | NA | itm_item_pri ces | CREATE_U SER_ID | VARCHAR2( 30 CHAR) | DATALO ADER | This is the user ID stored in the database.N ot set when event type = Mod. |
| NA | NA | NA | NA | itm_item_pri ces | UPDATE_DA TE | TIMESTAMP( 6) | now() | Current time stamp. Field value only set when event type=MOD. |
| NA | NA | NA | NA | itm_item_pri ces | UPDATE_U SER_ID | VARCHAR2( 30 CHAR) | DATALO ADER | DATALOAD ER will be the user ID stored in the database. Set only when the event type=MOD. |
| NA | NA | NA | NA | itm_item_pri ces | EXTERNAL_ SYSTEM | VARCHAR2( 60 CHAR) | RPM- REGPC | NA |
Table B-17 describes the Regular Price FDELE record mapping. FDELE records are interpreted as Delete events.
July 29, 2026 Appendix B-104 of B-111
Appendix B RPM Promotions
Table B-17 RPM Regular Price FDELE Record Mapping
| P os | RPM Field Name | RPM Description | RPM Field Type | Xstore Table | Xstore Column | Xstore Data Type | Xstore Default Value | Xstore Comment |
|---|---|---|---|---|---|---|---|---|
| 0 | Record Descriptor | File Detail Delete Marker (1per price change delete) | Char(5) | NA | NA | NA | NA | Used by the transformer to determine the unit type. |
| 1 | Line Id | Unique line identification | Number(1 0) | NA | NA | NA | NA | Ignored. |
| 2 | Id | Price change identifier | Number(1 5) | itm_item_pri ces | EXTERNAL _ID | VARCHAR2( 60 CHAR) | NA | NA |
| 3 | Item | Item identifier | Char(25) | itm_item_pri ces | ITEM_ID | VARCHAR2( 60 CHAR) | NA | NA |
| N A | NA | NA | NA | itm_item_pri ces | ORGANIZAT ION_ID | NUMBER(10 ,0) | $ {dtv.locati on.organi zationId} | NA |
| N A | NA | NA | NA | itm_item_pri ces | EXTERNAL _SYSTEM | VARCHAR2( 60 CHAR) | RPM- CLRPC | NA |
RPM Promotions
Table B-18 describes the RPM Promotions mapping.
Table B-18 RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| FHEAD | Record Descriptor | Char(5) | FHEAD | File head marker | NA | NA | NA |
| Line ID | Number(10) | 1 | Unique line identifier | NA | NA | NA | |
| File Type | Char(5) | PROMO | Promotions | NA | NA | NA | |
| Export Timestamp | Number(10) | System clock timestamp (YYYYMMDDHHMISS ) | NA | NA | NA | ||
| Format Version | Char(5) | 1.0 | File Format Version | NA | NA | NA | |
| Location | Number(10) | Location identifier | NA | NA | NA | ||
| Location Type | Char(1) | S = Store, W = Warehouse | NA | NA | NA | ||
| TIMBPE | Record Descriptor | Char(5) | TIMPBE | Promotion (transaction head). Defines an action associated with a promotion. | NA | NA | NA |
| Line ID | Number(10) | Unique line identifier | NA | NA | NA |
July 29, 2026 Appendix B-105 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Event Type | Char(3) | CRE = Create, MOD = Modify | NA | NA | NA | ||
| TPDTL | Record Descriptor | Char(5) | TPDTL | Promotion Detail Component. Defines a new component. | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| Promo ID | Number(10) | Promotion identifier | prc_deal | deal_id (partially) | NA | ||
| Promo Comp ID | Number(10) | Promotion Component Id | prc_deal | deal_id (partially) | NA | ||
| Promo Name | Char(160) | Promotion Header Name | NA | NA | Ignored. | ||
| Promo Desc | Char(640) | Promotion Header Description | NA | NA | Ignored. | ||
| Promo Comp Desc | Char(160) | Promotion Component Name | prc_deal | description | NA | ||
| Promo Type | Number(2) | Valid values: 0 = Multi-Buy Promotion 1=- Simple Promotion 2 = Threshold Promotion 3 = Finance Promotion (formerly tied to a value of 6) 4 = Transaction Promotion | NA | NA | Determines structure of resulting deal | ||
| Promo Comp Detail ID | Number(10) | Promotion Component Detail identifier | prc_deal | deal_id (partially) | NA | ||
| Date Start | Date | Start Date of Promotion Component Detail (YYYYMMDDHH24MI SS) | prc_deal | effective_da te | NA | ||
| End Date | Date | End Date of Promotion Component Detail (YYYYMMDDHH24MI SS) | prc_deal | end_date | NA |
July 29, 2026 Appendix B-106 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Apply to Code | Number(1) | Holds the Apply to Code for the promotion detail. Determines if the promotion is applied to regular retail only (no clearances in effect), clearance retail only (only when a clearance is in effect), or both regular and clearance retail. Valid values: 0 = Regular Only 1 = Clearance Only 2 = Regular and Clearance | prc_field_te st | NA | ApplyTo is mapped to an additional field test (PRICE BETWEEN X Y). | ||
| Discount Limit | Number(3) | The number of times that the promotion can be applied to a transaction. | prc_deal | iterationCap | NA | ||
| Apply Order | Number(1) | Application Order of the Promotion | NA | NA | Ignored. | ||
| Threshold ID | Number(6) | Threshold identifier | NA | NA | Ignored. | ||
| Customer Type ID | Number(10) | Customer Type identifier | NA | NA | Ignored. | ||
| Threshold Qualification Type | Number(1) | The qualification type for the threshold. Will only be populated for threshold promotions. Valid values are 0 for item level and 1 for threshold level. | NA | NA | Ignored. | ||
| TPGRP | Record Descriptor | Char(5) | TPGRP | Promotion Detail Group | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| Group ID | Number(10) | Group Number | prc_deal_it em | ordinal | Mapped structurally, not by value. | ||
| TGLIST | Record Descriptor | Char(5) | TGLIST | Promotion Group List. Defines an item list. | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| List ID | Number(10) | List identifier | NA | NA | Ignored. |
July 29, 2026 Appendix B-107 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Reward Application | Number(1) | How this reward is applied to the promotion detail. | NA | NA | Not mapped directly, but rather used to determine whether an action from the underlying TPDSC record should be used. | ||
| Description | Char(120) | Description | NA | NA | Ignored. | ||
| Price Range Min | Number(20,4 ) | Contains price range promotion minimum valid retail value. | prc_deal_fi eld_test | NA | Mapped to an additional field test (PRICE BETWEEN X Y). | ||
| Price Range Max | Number(20,4 ) | Contains price range promotion maximum valid retail value. | prc_deal_fi eld_test | NA | Mapped to an additional field test (PRICE BETWEEN X Y). | ||
| TLITM | Record Descriptor | Char(5) | TLITM | Promotion Group List. RPM defines lists by providing SKUs of eligible items. | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| Item ID | Char(25) | Transaction Item Identifier | prc_deal_fi eld_test | value1 | Mapped as SKU EQUAL field test. | ||
| TPDSC | Record Descriptor | Char(5) | TPDSC | Discount Detail for List. Defines a discount to apply to a preceding list of items. | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. |
July 29, 2026 Appendix B-108 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Change Type | Number(2) | Change Type Valid values: -1 = No Change 0 = Percent Off 1 = Amount Off 2 = Fixed Price | prc_deal_it em | action | Type of action: AMOUNT_O FF > CURRENCY OFF PERCENT OFF > PERCENT_ OFF FIXED_PRIC E > NEW_PRICE | ||
| Change Amount | Number(20,4 ) | Change Amount | prc_deal_it em | action_arg | Discount amount when Change Type is AMOUNT_O FF or FIXED_PRIC E. Negated for AMOUNT_O FF. | ||
| Change Currency | Char(3) | Change Currency | NA | NA | Ignored. | ||
| Change Percent | Number(20,4 ) | Change Percent | prc_deal_it em | action_arg | Discount amount when Change Type is PERCENT_ OFF. Negated. | ||
| Change Selling UOM | Char(4) | Change Selling UOM | NA | NA | Ignored. | ||
| Qual Type | Number(2) | Qualification Type | NA | NA | Affects where the Qual Value goes. |
July 29, 2026 Appendix B-109 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Qual Value | Number(2) | Qualification Value | prc_deal_it em | min_qty / max_qty or min_item_to tal | Target field is picked based on the Qual Type value. PRC_DEAL_ ITEM.max_qt y either gets the same value or receives some big number depending on the deal type. | ||
| Change Duration | Number(20,4 ) | Change Duration | NA | NA | Ignored. | ||
| TPISR | Record Descriptor | Char(5) | TPISR | This record type is ignored for now. | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| Item ID | Char(25) | Transaction Item Identifier | NA | NA | Ignored. | ||
| Selling Retail | Number(20,4 ) | Selling retail of the item | NA | NA | Ignored. | ||
| Selling UOM | Char(4) | Selling UOM of the item | NA | NA | Ignored. | ||
| Effective Date | Date | Effective Date of the selling retail - YYYYMMDDHH24MIS S | NA | NA | Ignored. | ||
| Selling Retail Currency | Char(3) | Selling retail currency | NA | NA | Ignored. | ||
| TPCDT | Record Descriptor | Char(5) | TPCDT | Credit Detail | NA | NA | Ignored. |
| Credit Detail ID | Number(10) | Credit Detail Identifier | NA | NA | Ignored. | ||
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. | ||
| Credit Type | Char(40) | Credit Type | NA | NA | Ignored. | ||
| binNumberFrom | Number(10) | Bin Number From | NA | NA | Ignored. | ||
| binNumberTo | Number(10) | Bin Number To | NA | NA | Ignored. | ||
| Commission Rate | Number(10) | Commission Rate | NA | NA | Ignored. | ||
| Comments | Char(160) | Comments | NA | NA | Ignored. | ||
| TPCIL | Record Descriptor | Char(5) | TPCIL | Cancel Item Loc | NA | NA | Ignored. |
| Line ID | Number(10) | Unique line identifier | NA | NA | Ignored. |
July 29, 2026 Appendix B-110 of B-111
Appendix B RPM Promotions
Table B-18 (Cont.) RPM Promotions Record Mappings
| RPM Record Name | RPM Field Name | RPM Field Type | RPM Default Value | RPM Description | Xstore Table | Xstore Field | Xstore Comment |
|---|---|---|---|---|---|---|---|
| Promo ID | Number(10) | Identifier of the promotion | NA | NA | Ignored. | ||
| Promo Comp ID | Number(10) | Promotion Component Identifier | NA | NA | Ignored. | ||
| Promo Comp Detail ID | Number(10) | Promotion Component Detail identifier | NA | NA | Ignored. | ||
| Item ID | Char(25) | Transaction Item Identifier for item | NA | NA | Ignored. | ||
| Cancellation Date | Date | Cancellation effective date - YYYYMMDDHH24MIS S | NA | NA | Ignored. | ||
| TTAIL | Record Descriptor | Char(5) | TTAIL | Transaction Tail | NA | NA | NA |
| Line ID | Number(10) | Unique line identifier | NA | NA | NA | ||
| FPDEL | Record Descriptor | Char(5) | FPDEL | Delete Promotion | NA | NA | NA |
| Line ID | Number(10) | Unique line identifier | NA | NA | NA | ||
| Promo ID | Number(10) | The ID of the promotion | NA | NA | NA | ||
| Promo Comp ID | Number(10) | Promotion Component Identifier | NA | NA | NA | ||
| Promo Comp Detail ID | Number(10) | Promotion Component Detail identifier | NA | NA | NA | ||
| Group ID | Number(10) | Group Number | NA | NA | NA | ||
| List ID | Number(10) | List identifier | NA | NA | NA | ||
| Item ID | Char(25) | Transaction Item Identifier for item | NA | NA | NA | ||
| FTAIL | Record Descriptor | Char(5) | FTAIL | File tail marker | NA | NA | NA |
| Line ID | Number(10) | Unique line identifier | NA | NA | NA | ||
| Number of lines | Number(10) | Number of lines in the file not including FHEAD and FTAIL | NA | NA | NA |
July 29, 2026 Appendix B-111 of B-111
In this guide
- Guide: Merchandising Cloud Services-Xstore Suite 26.0 Implementation Guide
- Previous: A Appendix: Xstore to Sales Audit Mapping Details
Related chapters
- 5 Integration Considerations — Merchandising Cloud Services-Xstore Suite 26.0 Implementation Guide · shares
ITEM_AVAILABILITY_CODE,STOCK_STATUS - 6 Scheduled Integration — Inbound and Outbound Integration Guide · shares
DIFF_DESC,DIFF_ID,DIFF_TYPE_DESC,EFFECTIVE_DATE