Location Hierarchy File
File name: loc.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Label | Hierarchy Type | Parent |
|---|---|---|---|
|
STOR |
Location |
Main |
None |
|
DSTR |
District |
Main |
STOR |
|
REGN |
Region |
Main |
DSTR |
|
CHNL |
Area |
Main |
REGN |
|
CHAN |
Chain |
Main |
CHNL |
|
COMP |
Company |
Main |
CHAN |
|
LOCT |
Location Type |
Alternate |
STOR |
|
PHWH |
Physical Warehouse |
Alternate |
STOR |
|
FFLT |
Fulfillment Type |
Alternate |
STOR |
|
CHNG |
Chain Group |
UDA |
CHAN |
|
RGNG |
Region Group |
UDA |
REGN |
|
DSTG |
District Group |
UDA |
DSTR |
|
STRC |
Location Cluster |
Alternate |
STOR |
|
CHNC |
Channel |
Alternate |
STRC |
|
CCTY |
Country |
Alternate |
CHNC |
Note:
The Planning Location Hierarchy is aligned with the Merchandising Organization Hierarchy for RAP integration, so Region aggregates to Area as in the Merchandising Hierarchy. Channel is an attribute in RMFCS and is not part of the Organization Hierarchy. RMFCS integration to RAP will send the Planning Channel and Planning Country and that will be mapped to the Channel (CHNC) and Country (CCTY) dimension. Merch Plans and Merch Targets will be created at the Channel (CHNC) level.
Note:
The STRC (Location Cluster) dimension is not currently used in the MFP GA, but it is added to align with the Assortment Planning GA and also to allow for extensibility of MFP or for the non-template customer to enhance to include Location clustering. During hierarchy load, it can be mapped to load with the same STOR dimensions.
Note:
If the customer has Warehouses holding inventory and receipts data, the Virtual Warehouse locations for each Channel can be loaded as locations with Location type as ‘W’. The batch process allows splitting of Warehouse Inventory to locations to include in the Location Inventory for Location Planning.
Example:
STOR,STOR_LABEL,DSTR,DSTR_LABEL,REGN,REGN_LABEL,CHNL,CHNL_LABEL,CHAN,CHAN_LABEL,COMP,COMP_LABEL,LOCT,LOCT_LABEL,PHWH,PHWH_LABEL,FFLT,FFLT_LABEL,STRC,STRC_LABEL,CHNC,CHNC_LABEL,CCTY,CCTY_LABEL,DSTG,DSTG_LABEL,RGNG,RGNG_LABEL,CHNG,CHNG_LABEL 1000,1000 Charlotte,1070,North Carolina,170,Mid-Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1000,1000 Charlotte,1,Brick & Mortar,1,USA,170,Mid-Atlantic,1,North,1,North America 1001,1001 Atlanta,1023,Georgia,400,South Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,2,Kiosk,WH-1,Warehouse - US,1,Brick & Mortar,1001,1001 Atlanta,1,Brick & Mortar,1,USA,400,South Atlantic,2,South,1,North America 1002,1002 Dallas,1104,Texas,230,Gulf States,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1002,1002 Dallas,1,Brick & Mortar,1,USA,230,Gulf States,2,South,1,North America 1003,1003 Boston,1051,Massachusetts,200,New England,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1003,1003 Boston,1,Brick & Mortar,1,USA,200,New England,1,North,1,North America 1004,1004 New York,1066,New York,200,New England,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1004,1004 New York,1,Brick & Mortar,1,USA,200,New England,1,North,1,North America 1005,1005 Philadelphia,1083,Pennsylvania,170,Mid-Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1005,1005 Philadelphia,1,Brick & Mortar,1,USA,170,Mid-Atlantic,1,North,1,North America
Note:
For non-template customers, it is also recommended to align with the GA Location Hierarchy structure for the dimension names for stor, dstr, regn, chnl, chan, comp, strc, chnc, and ccty so that they can upgrade/implement other GA solutions in a multi-app environment. They can use different labels. The lowest dimension should be stor and it is mandatory. The rest of the dimensions are optional and their equivalents should be named accordingly.