| Oracle® Retail Category Management Implementation Guide Release 14.1 E55388-01 |
|
 Previous |
 Next |
| Oracle® Retail Category Management Implementation Guide Release 14.1 E55388-01 |
|
Previous |
Next |
This chapter describes the setup that must be done before building the Category Management domain and the batch script that must be run to build the domain.
RPAS infrastructure (including the server and fusion client) and Category Management must be installed before setting up and configuring Category Management.
For information on installing RPAS server and fusion client, see the Oracle Retail Predictive Application Server Installation Guide.
Additional dependencies and steps are needed for integration with the Assortment and Space Optimization module of Oracle Retail Advanced Science Engine (ORASE) using Hybrid Storage Architecture (HSA). For more information, see "ORASE Integration Using HSA" in Chapter 5.
Before downloading the installation package to the UNIX server, a central directory structure to support the environment must be created. This central directory is referred to as <CM_HOME>. Set <CM_HOME> to the full path name to RCM home.
The Java-based RPAS installation programs that are included with the installation package are used to install the server-side RPAS components on UNIX operating systems.
The RPAS Installer performs the following functions:
Installs the server.
Installs the Configuration Tools on the server.
On Windows, an InstallShield package is used to install the Configuration Tools.
Defines the DomainDaemon port.
The RPAS server installation package also includes the following RPAS client:
RPAS Fusion Client–A web-based client developed using Oracle Application Development Framework (ADF).
Each RPAS client installation package includes a separate installer to help you install the client. For more information on installing the RPAS clients, refer to the Oracle Retail Predictive Application Server Installation Guide.
The Category Management installer performs the following functions:
Downloads the configuration and batch scripts into the <CM_HOME>/config and <CM_HOME>/bin directories
Downloads a set of sample hierarchy and data files into the <CM_HOME>/input directory
Builds a sample domain at <CM_HOME>/domain/catman
Downloads the packages/scripts needed for ASO integration into the <CM_HOME>/hsa directory
The following hierarchy files contain the superset of all the dimensions along the product, location, and calendar hierarchies:
prod.hdr.csv.dat
loc.hdr.csv.dat
clnd.csv.dat
Each hdr.csv.dat (HDR) hierarchy file contains a header line that lists all the dimensions for which position information is contained in the file. The RPAS build process handles these HDR files so that every application extracts the position information relevant to itself and ignores dimensions not configured in the application.
The filterHier utility is run on the HDR files to convert them into standard hierarchy files that are then passed to loadHier. The build process, which uses rpasInstall, can differentiate between standard and HDR hierarchy files. There is no need for the implementer to make any changes in the domain build process.
If using HDR files, the implementer needs to run filterHier before running loadHier. The filterHier utility converts the HDR files into standard hierarchy files that can be processed by loadHier. Note that there is no need to run filterHier if the standard hierarchy files are already available.
|
Note: The HDR files must reside outside the domain input directory before running filterHier. By default, the filterHier utility puts the newly created filtered hierarchy files into the input folder of the domain. |
See the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client for details on the RPAS utilities.
In addition to the regular RPAS environment variables, including RPAS_HOME, you must export the following environment variables:
All platforms:
export RPAS_JAVA_CLASSPATH="$RPAS_HOME/lib/rpasjni.jar:$RPAS_ HOME/lib/oracleRpasUtils.jar:$RPAS_HOME/applib/aaijni.jar:$RPAS_ HOME/applib/aaiCatMan.jar:$RPAS_HOME/applib/rseCatMan.jar:$RPAS_JAVA_CLASSPATH"
|
Note: Additional Java environment variables must be set for your particular operation system. These variables are the same for all applications on RPAS. See the "Java Environment" section of the Oracle Retail Predictive Application Server Installation Guide for these environment variables. |
Before building the domain, set up the following types of files, which are described below:
Standard RPAS Hierarchy files
Category Management-specific Hierarchy files
Data files
The following hierarchy files are needed:
Calendar hierarchy files
Product hierarchy files
Location hierarchy files
|
Note: As with all standard RPAS hierarchies, these hierarchies are configurable as long as they adhere to the RPAS requirements on hierarchy structures. |
File name: clnd.csv.dat
File format: comma-separated values file
Fields: Day, Week, Month, Quarter, Season, Year
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Day | Day or date in YYYYMMDD format |
| Week | Week number |
| Month | Month number |
| Quarter | Quarter of the year |
| Season | Season of the year |
| Year | Year |
Example:
DAY20130101,2013D1,W48_2012,1/5/2013,M11_2012,"Dec, FY2012",Q4_2012,"4th Qrtr, FY2012",S2_2012,"Fall, FY2012",A2012,FY2012 DAY20130102,2013D2,W48_2012,1/5/2013,M11_2012,"Dec, FY2012",Q4_2012,"4th Qrtr, FY2012",S2_2012,"Fall, FY2012",A2012,FY2012 DAY20130103,2013D3,W48_2012,1/5/2013,M11_2012,"Dec, FY2012",Q4_2012,"4th Qrtr, FY2012",S2_2012,"Fall, FY2012",A2012,FY2012 DAY20130104,2013D4,W48_2012,1/5/2013,M11_2012,"Dec, FY2012",Q4_2012,"4th Qrtr, FY2012",S2_2012,"Fall, FY2012",A2012,FY2012 DAY20130105,2013D5,W48_2012,1/5/2013,M11_2012,"Dec, FY2012",Q4_2012,"4th Qrtr, FY2012",S2_2012,"Fall, FY2012",A2012,FY2012
File name: prod.csv.dat
File format: comma-separated values file
Fields: SKU, Vendor, Style/Color, Style, Sub-Category, Category, Department, Group, Division, Company, Sub-Brand, Brand
The following table describes the fields in this file.
| Field | Description |
|---|---|
| SKU | Unique Stock-keeping Unit Identifier |
| Vendor | Product Vendor. Vendor is an alternate roll-up from SKU. |
| Style/Color | Style/Color |
| Style | Style |
| Sub-category | Sub-category |
| Category | Category |
| Department | Department |
| Group | Group |
| Division | Division |
| Company | Company |
| Sub-brand | Sub-Brand. Sub-Brand and Brand are alternate roll-ups from SKU. |
| Brand | Brand |
Example:
3375772212,3375772212 CTL_BR_NATURAL_RTE_CEREAL_14_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772213,223375772213 CTL_BR_NATURAL_RTE_CEREAL_14_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772214,223375772214 CTL_BR_CRNCH_CRNCH_NTRL_NTRL_CRL_GRANOLA,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772215,223375772215 CTL_BR_NATURAL_RTE_CEREAL_10.5_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772216,223375772216 CTL_BR_NATURAL_RTE_CEREAL_10.5_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL
File name: loc.csv.dat
File format: comma-separated values file
Fields: Store, District, Region, Area, Channel, Chain, Company, Store Cluster, Trading Area, Trading Area Group
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Store | Store |
| District | District |
| Region | Region |
| Area | Area |
| Channel | Channel |
| Chain | Chain |
| Company | Company |
| Store Cluster | Store Cluster. This is a group of stores with similar characteristics. Alternate roll-up from Store. |
| Trading Area | Trading Area. One or more Store Clusters form a Trading Area. |
| Trading Area Group | Trading Area Group |
| Store Group | Store Group. This is a user-defined dimension and is not required to be included in the loc.csv.dat load file. |
Example:
1000,1000 Charlotte,401,401 Southeast,400,Southeast,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd,A,Store Cluster A,1,Trading Area 1,1,All Trading Areas 1001,1001 Atlanta,400,400 Southeast,400,Southeast,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd,A,Store Cluster A,1,Trading Area 1,1,All Trading Areas 1003,1003 Boston,201,201 Northeast,200,Northeast,1,North,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd,A,Store Cluster A,1,Trading Area 1,1,All Trading Areas 1009,1009 Albuquerque,300,300 Southwest,300,Southwest,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd,A,Store Cluster A,1,Trading Area 1,1,All Trading Areas 1010,1010 Los Angeles,301,301 Southwest,300,Southwest,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd,A,Store Cluster A,1,Trading Area 1,1,All Trading Areas
The following are the hierarchy files that are specific to Category Management:
Right-Hand Side Product Hierarchy File
Focus Area Attributes Hierarchy File
Consumer Profile Hierarchy File
Retail Segment Hierarchy File
Retailer Hierarchy File
Consumer Segment Hierarchy File
Linear Number Hierarchy File
Tactic Hierarchy File
Breakpoints Hierarchy File
Product Attributes Hierarchy File
Strategy Hierarchy File
Curve Points Hierarchy File
Planogram Hierarchy File
File name: pror.csv.dat
File format: comma-separated values file
Fields: SKU, Vendor, Style/Color, Style, Sub-Category, Category, Department, Group, Division, Company, Sub-Brand, Brand
The following table describes the fields in this file.
| Field | Description |
|---|---|
| SKU | Unique Stock-keeping Unit Identifier |
| Vendor | Product Vendor. Vendor is an alternate roll-up from SKU. |
| Style/Color | Style/Color |
| Style | Style |
| Sub-Category | Sub-Category |
| Category | Category |
| Department | Department |
| Group | Group |
| Division | Division |
| Company | Company |
| Sub-Brand | Sub-Brand. Sub-Brand and Brand are alternate roll-ups from SKU. |
| Brand | Brand |
Example:
3375772212,3375772212 CTL_BR_NATURAL_RTE_CEREAL_14_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772213,223375772213 CTL_BR_NATURAL_RTE_CEREAL_14_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772214,223375772214 CTL_BR_CRNCH_CRNCH_NTRL_NTRL_CRL_GRANOLA,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772215,223375772215 CTL_BR_NATURAL_RTE_CEREAL_10.5_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL 223375772216,223375772216 CTL_BR_NATURAL_RTE_CEREAL_10.5_OUNCE,11,11 STCO_ Cardboard,1,1 STYLE_Cardboard,SCLS_BOX,BOX,CLSS_CEREAL,CEREAL,901,901 Cold Foods,31,31 Breakfast,30,30 Grocery,1,1 Acme Home,V2,V2 H thru P by Air,SBRD_ PRIVATE_LABEL,PRIVATE_LABEL_Cereal,BRD_PRIVATE_LABEL,PRIVATE_LABEL
File name: faah.csv.dat
File format: comma-separated values file
Field: Focus Area
The following table describes the field in this file.
| Field | Description |
|---|---|
| Focus Area | The focus area name |
Example:
fa1,Attributesfa2,Market Basketfa3,Loyaltyfa4,Performance
File name: cprf.csv.dat
File format: comma-separated values file
Fields: Consumer Profile, Consumer Profile Type
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Consumer profile | This represents the gradations within a particular demographic measure. For example, if the demographic measure is "Household Size", then the profile represents the breakdown within that information, such as, 1, 2, 3-4, 5-6, and 7+. |
| Consumer Profile Type | This is the consumer demographic information, such as Household Income, Head of Household Age, Children's Ages, Life Stage, or Household Size. |
Example:
cprd100,"$0 - $19,999",cprt0,Household Income cprd101,"$20,000 - $29,999",cprt0,Household Income cprd102,"$30,000 - $39,999",cprt0,Household Income cprd103,"$40,000 - $49,999",cprt0,Household Income cprd104,"$50,000 - $69,999",cprt0,Household Income cprd105,"$70,000 - $89,999",cprt0,Household Income cprd106,"$90,000 - $109,999",cprt0,Household Income cprd107,"$110,000 - $149,999",cprt0,Household Income cprd108,"$150,000+",cprt0,Household Income cprd200,18-24,cprt1,Head of Household Age cprd201,25-34,cprt1,Head of Household Age cprd202,35-50,cprt1,Head of Household Age cprd203,51-60,cprt1,Head of Household Age cprd204,61-67,cprt1,Head of Household Age cprd205,68+,cprt1,Head of Household Age
File name: rsgh.csv.dat
File format: comma-separated values file
Field: Retailer Type
The following table describes the field in this file.
| Field | Description |
|---|---|
| Retailer Type | The various broad segments of the retail market. |
Example:
rsgd1,Grocery rsgd2,Convenience/Gas rsgd3,Drug rsgd4,Super-Centers rsgd5,Warehouse Club rsgd6,Dollar Stores rsgd7,Mass Merch Without Supers rsgd8,All Other Channels
File name: reth.csv.dat
File format: comma-separated values file
Field: Retailer
The following table describes the field in this file.
| Field | Description |
|---|---|
| Retailer | A simple listing of competitor names. |
Example:
ret1,Retailer 1 ret2,Retailer 2 ret3,Retailer 3
File name: csh.csv.dat
File format: comma-separated values file
Fields: Consumer Segment Version, Consumer Segment
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Consumer Segment Version | The version (1, 2, 3,..., or Summer, Fall,...) of a given consumer segment. |
| ConsumerSegment | A name that identifies a group of consumers with similar buying patterns, such as "Getting By" or "Empty Nester". |
Example:
s1CDT1,Soccer Mom CDT Version 1,s1,Soccer Mom s1CDT2,Soccer Mom CDT Version 2,s1,Soccer Mom s1CDT3,Soccer Mom CDT Version 3,s1,Soccer Mom s1CDT4,Soccer Mom CDT Version 4,s1,Soccer Mom s1CDT5,Soccer Mom CDT Version 5,s1,Soccer Mom s2cdt1,Natural N Healthy CDT Version 1,s2,Natural N Healthy s2cdt2,Natural N Healthy CDT Version 2,s2,Natural N Healthy s2cdt3,Natural N Healthy CDT Version 3,s2,Natural N Healthy s2cdt4,Natural N Healthy CDT Version 4,s2,Natural N Healthy s2cdt5,Natural N Healthy CDT Version 5,s2,Natural N Healthy
File name: lnmh.csv.dat
File format: comma-separated values file
Field: Linear Number
The following table describes the field in this file.
| Field | Description |
|---|---|
| LinearNumber | 01, 02, 03,... |
Example:
01,01 02,02 03,03 04,04 05,05 06,06 07,07 08,08 09,09 10,10
File name: tcth.csv.dat
File format: comma-separated values file
Field: Tactic
The following table describes the field in this file.
| Field | Description |
|---|---|
| Tactic | The name of an area within Category Management where multiple approaches might be relevant. |
Example:
1,Assortment2,Pricing3,Promotion4,Space5,Inventory
File name: pcth.csv.dat
File format: comma-separated values file
Field: Breakpoint
The following table describes the field in this file.
| Field | Description |
|---|---|
| Breakpoint | A threshold used in calculating information about an assortment, such as fragmentation. |
Example:
bp1,50% bp2,75% bp3,80% bp4,85% bp5,90% bp6,95% bp7,99% bp8,Wif_1 bp9,Wif_2 bp10,Wif_3
File name: attr.csv.dat
File format: comma-separated values file
Fields: Attribute Value, Attribute Name
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Attribute Value | The various values that an attribute might have. For example, the "package type" attribute might take the values "bag", "box", or "convenience". |
| Attribute Name | The name of a product attribute, such as "brand", "family type", "flavor", "grain", "package type", "size", or "temperature". |
Example:
familytype_adult,ADULT,familytype,Family Type familytype_convenience,CONVENIENCE,familytype,Family Type familytype_family,FAMILY,familytype,Family Type familytype_kids,KIDS,familytype,Family Type flavor_almond,ALMOND,flavor,Flavor flavor_apple,APPLE,flavor,Flavor flavor_banana,BANANA,flavor,Flavor flavor_berries,BERRIES,flavor,Flavor flavor_berry,BERRY,flavor,Flavor flavor_caramel,CARAMEL,flavor,Flavor flavor_chocolate,CHOCOLATE,flavor,Flavor flavor_cinnimon,CINNIMON,flavor,Flavor
File name: sgyh.csv.dat
File format: comma-separated values file
Field: Strategy
The following table describes the field in this file.
| Field | Description |
|---|---|
| Strategy | The name of a category strategy. |
Example:
STRTG1,Traffic Building STRTG2,Transaction Building STRTG3,Profit Contribution STRTG4,Cash Generating STRTG5,Excitement Creating STRTG6,Image Enhancing STRTG7,Turf Defending
File name: curv.csv.dat
File format: comma-separated values file
Field: Curve Number
This hierarchy is used in demand transference calculations. The following table describes the field in this file.
| Field | Description |
|---|---|
| Curve Number | Represents the number of SKUs under consideration by various demand transference calculations. |
Example:
001,001 sku 002,002 skus 003,003 skus … 098,098 skus 099,099 skus 100,100 skus
File name: pogh.csv.dat
File format: comma-separated values file
Fields: POG Sub-Category, POG Category, POG Department
The following table describes the fields in this file.
| Field | Description |
|---|---|
| POG Sub-Category | POG Sub-Category |
| POG Category | POG Category |
| POG Department | POG Department |
Example:
1000000,Ground - 10 ft,100000,Coffee,10000,Shelf Stable Beverages 1000001,Ground - 12 ft,100000,Coffee,10000,Shelf Stable Beverages 2000000,Instant - 8 ft,100000,Coffee,10000,Shelf Stable Beverages 2000001,Instant - 10 ft,100000,Coffee,10000,Shelf Stable Beverages 2000002,Instant - 12 ft,100000,Coffee,10000,Shelf Stable Beverages 3000000,Single Serve - 6 ft,100000,Coffee,10000,Shelf Stable Beverages 3000001,Single Serve - 8 ft,100000,Coffee,10000,Shelf Stable Beverages 4000000,Whole - 4 ft,100000,Coffee,10000,Shelf Stable Beverages 4000001,Whole - 8 ft,100000,Coffee,10000,Shelf Stable Beverages
Category Management is a data-intensive application. The data files required are listed in Chapter 9.
The script used to build or patch the Category Management domain is described in this section. The script is located in the <CM_HOME>/bin directory.
This section contains detailed information on the Building a Domain script:
Script
build.ksh
Usage
build.ksh
Notes
The script overwrites an existing domain, so it should never be run on top of an existing domain unintentionally. Updating an existing domain should be done through the <CM_HOME>/bin/patch_cm_keepformats.ksh or <CM_HOME>/bin/patch_cm_deleteformats.ksh scripts.
The script uses the Configuration Tools rpasInstall utility to build a domain. See the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client for details on this utility.
The script also uses the following RPAS utilities: mace and loadmeasure. See the Oracle Retail Predictive Application Server Administration Guide for details on these utilities.
All hierarchy and measure files are placed in the <CM_HOME>/input directory.
The script also processes all pre-prepared consumer decision tree files. This creates multiple dynamic hierarchies that provide the ability to aggregate information as determined by a consumer decision tree. It expects these pre-prepared consumer decision trees to be in <CM_HOME>/input/cdtdata/. Any file in this directory ending with .xml is assumed to be a CDT file and will be processed by the CDT Parser.
The Category Management installation software enables you to install the activity taskflow and online help files for the RPAS Fusion Client. In order to install the activity taskflow files, the RPAS Fusion Client must already be installed. For more information on installing the RPAS Fusion Client, refer to the Oracle Retail Predictive Application Server Installation Guide.
During the RPAS Fusion Client installation, the installer automatically sets up the RPAS domain connection configurations in the ProfileList.xml file. In case you choose to set up the domain connection after the installation or set up an additional domain, you must manually set up the connection. For more information, refer to the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
For greater security, users and user groups are not automatically created when you build or patch a domain. To create users and user groups, you must use the usermgr utility. To learn more about usermgr, see the Operational Utilities chapter of the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
Data is loaded into Category Management using the standard RPAS approach. See the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client for details on formatting the load data files and on the utilities that enable administrators to load data into RPAS. If you are using script integration, see Chapter 5. For information on other batch scripts, see Chapter 7.
