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	Store	Main	None
DSTR	District	Main	STOR
REGN	Region	Main	DSTR
CHNL	Area	Main	REGN
CHAN	Chain	Main	CHNL
COMP	Company	Main	CHAN
SSTR	Space Cluster	Alternate	STOR
STRC	Store Cluster	Alternate	SSTR
STC1	Cluster	Alternate	STRC
CHNC	Channel	Alternate	STC1
CCTY	Country	Alternate	CHNC
LOCT	Location Type	Alternate	STOR
PHWH	Physical Warehouse	Alternate	STOR
FFLT	Fulfillment Type	Alternate	STOR

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,SSTR,SSTR_LABEL,STRC,STRC_LABEL,STC1,STC1_LABEL,CHNC,CHNC_LABEL,CCTY,CCTY_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,1000,1000 Charlotte,1000,1000 Charlotte,1,Brick & Mortar,1,USA
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,1001,1001 Atlanta,1001,1001 Atlanta,1,Brick & Mortar,1,USA
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,1002,1002 Dallas,1002,1002 Dallas,1,Brick & Mortar,1,USA
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,1003,1003 Boston,1003,1003 Boston,1,Brick & Mortar,1,USA
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,1004,1004 New York,1004,1004 New York,1,Brick & Mortar,1,USA

Note:

The Space Cluster (SSTR), Store Cluster (STRC), and Cluster (STC1) dimensions are dynamically set within the workbooks. However, while loading the hierarchy file, those positions should be loaded with the same position ID as stor. The Location clustering solution needs unique identifiers for creating store clusters and will use the unique store identifier loaded at these positions as internal identifiers for creating new clusters within the solution.

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. Store Clusters defined within APCS or interfaced should be below this Channel level.

Note:

If the customer has warehouses holding inventory and receipts data, the Virtual Warehouse locations for each Channel can be loaded as locations with the Location type as ‘W’. The batch process allows splitting of Warehouse Inventory to locations to include in the Location Inventory for Location Planning.

Note:

For the non-template customer, 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.