| Oracle® Retail Size Profile Optimization Implementation Guide Release 14.1 E55738-01 |
|
 Previous |
 Next |
| Oracle® Retail Size Profile Optimization Implementation Guide Release 14.1 E55738-01 |
|
Previous |
Next |
This chapter describes the set up that must be done before building the SPO domain and the batch script that must be executed to build the domain.
RPAS infrastructure (including the server and relevant client) and SPO must be installed before setting up and configuring SPO.
For information on installing RPAS server and client, see the Oracle Retail Predictive Application Server Installation Guide.
For information on installing SPO, see the Oracle Retail Size Profile Optimization Installation Guide.
Before downloading the installation package to the UNIX server, a central directory structure to support the environment needs to be created. This central directory is referred to as <spo_directory>. Set <spo_directory> to the full path name to SPO home.
|
Note: The$SPO_HOME variable is not used. |
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 RPAS 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 clients:
RPAS Classic Client: A Windows-based client interface for end-users and system administrators of an RPAS domain.
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 SPO installer performs the following functions:
Downloads the configuration and batch scripts into the <spo_directory>/config and <spo_directory>/bin directories.
Downloads a set of sample hierarchy and data files into the <spo_directory>/input directory.
Builds a sample domain at <spo_directory>/domain/SizeOpt.
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.hdr.csv.dat
These common hierarchy files are shared among AP, IP, MFP, and SPO.
|
Note: The common hierarchy files are not available for Item Planning Configured for COE. |
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. |
For more information on utilities, see the Oracle Retail Predictive Application Server Administration Guides.
In addition to the regular RPAS environment variables, including RPAS_HOME, you need to export the following environment variables:
All Platforms:
export RPAS_JAVA_CLASSPATH="$RPAS_HOME/applib/aaijni.jar:$RPAS_ HOME/applib/aaiSizeOpt.jar:$RPAS_HOME/applib/aaiPckOpt.jar:$RPAS_ HOME/applib/acknap.jar:$RPAS_HOME/applib/alloclib.jar:$RPAS_ HOME/applib/prepack.jar/:$RPAS_HOME/applib/commons_io_2.4.jar:$RPAS_ HOME/applib/commons_lang3-3.1.jar:$RPAS_ HOME/applib/commons-math3-3.2.jar:$RPAS_JAVA_CLASSPATH
|
Note: There are additional Java environment variables that must be set for your particular operation system. These variables are the same for all applications on RPAS. For more information on environment variables, see the "Java Environment" section of the Oracle Retail Predictive Application Server (RPAS) Installation Guide. |
Define and reset the value for the following environment variable to increase memory allocation to a Java virtual machine within an RPAS process:
If this environment variable is not defined, it defaults to 256MB. If experiencing memory issues, you can define it to increase memory allocation to a Java virtual machine within an RPAS process. Although you can increase the value up to 1024MB, it is suggested to first set it up to 512MB. export RPAS_JAVA_MAXHEAPSIZE=1024MB.
Before building the domain, the following types of files need to be set up:
This section contains a description of each file and includes an example of each file.
The following hierarchy files are needed:
|
Note: As with all standard RPAS hierarchies, these hierarchies are configurable as long as they adhere to the RPAS requirements on hierarchy structures. |
For a description of each hierarchy structure, see Chapter 7.
File name: clnd.csv.dat
File format: comma-separated values file
Fields: Day, Week, Month, Quarter, Season, Year, Week of 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 |
| Week of Year | Week of the year |
Example:
20060205,2/5/2006,W01_2006,2/11/2006,M01_2006,Feb FY2006,Q1_2006,1st Qrtr FY2006,S1_2006,Sprg FY2006,A2006,FY2006,W01,Week 01 20060206,2/6/2006,W01_2006,2/11/2006,M01_2006,Feb FY2006,Q1_2006,1st Qrtr FY2006,S1_2006,Sprg FY2006,A2006,FY2006,W01,Week 01 20060207,2/7/2006,W01_2006,2/11/2006,M01_2006,Feb FY2006,Q1_2006,1st Qrtr FY2006,S1_2006,Sprg FY2006,A2006,FY2006,W01,Week 01 20060208,2/8/2006,W01_2006,2/11/2006,M01_2006,Feb FY2006,Q1_2006,1st Qrtr FY2006,S1_2006,Sprg FY2006,A2006,FY2006,W01,Week 01 20060209,2/9/2006,W01_2006,2/11/2006,M01_2006,Feb FY2006,Q1_2006,1st Qrtr FY2006,S1_2006,Sprg FY2006,A2006,FY2006,W01,Week 01
File name: prod.csv.dat
File format: comma-separated values file
Fields: SKU, Style/Color, Style, Subclass, Department, Group, Division, Company
The following table describes the fields in this file.
| Field | Description |
|---|---|
| SKU | Unique Stock Keeping Unit identifier |
| Style/Color | Style/Color |
| Style | Style |
| Subclass | Subclass |
| Department | Department |
| Group | Group |
| Division | Division |
| Company | Company |
Example:
100001,Evermore Int Flat Pastel Base Quart,100001,Evermore Int Flat Pastel Base Quart,100001,Evermore Int Flat Pastel Base Quart,7 01,701 Flat Matte,802,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited 100002,AM Finest Int Flat Pastel Base Gal.,100002,AM Finest Int Flat Pastel Base Gal.,100002,AM Finest Int Flat Pastel Base Gal.,7 01,701 Flat Matte,802,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited 100003,P.L. Int Flat Pastel Deep Gallon,100003,P.L. Int Flat Pastel Deep Gallon,100003,P.L. Int Flat Pastel Deep Gallon,701,701 Fl at Matte,802,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited 100004,AM Finest Int Flat Accent Base Quart,100004,AM Finest Int Flat Accent Base Quart,100004,AM Finest Int Flat Accent Base Quar t,701,701 Flat Matte,802,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited 100005,P.L. Int Flat Ultra Sht Gal.,100005,P.L. Int Flat Ultra Sht Gal.,100005,P.L. Int Flat Ultra Sht Gal.,701,701 Flat Matte,802 ,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited 100006,AM Finest Int Ltx Flt Wall Qt.,100006,AM Finest Int Ltx Flt Wall Qt.,100006,AM Finest Int Ltx Flt Wall Qt.,701,701 Flat Mat te,802,802 Interior Paint,801,801 Paint,22,22 Do It Yourself,20,20 Hardlines,1,1 Retailers Limited
File name: loc.csv.dat
File format: comma-separated values file
Fields: Store, District, Region, Area, Channel, Chain, Company
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 |
Example:
1000,1000 Charlotte,401,401 Southeast,400,Southeast,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd 1001,1001 Atlanta,400,400 Southeast,400,Southeast,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd 1003,1003 Boston,201,201 Northeast,200,Northeast,1,North,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd 1009,1009 Albuquerque,300,300 Southwest,300,Southwest,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd 1010,1010 Los Angeles,301,301 Southwest,300,Southwest,2,South,1,Brick & Mortar,1,Chain 1,1,Retailer Ltd
The following are special SPO hierarchy files:
|
Note: The Generation ID Hierarchy File, Escalation Level Hierarchy File, Cluster Hierarchy File, and Pack Hierarchy File are internal hierarchies. These files are generated by SPO through the Prepack plug-in; the user does not have to generate them. |
The Attribute hierarchy captures the various attributes and any hierarchical relationship between attributes, for example, Attribute Code aggregates to Season Code, which aggregates to Yearly Season Code. When generating size profiles, attributes can be used as a criteria for grouping the results. That is, it is possible to generate size profiles on data grouped by attributes. For example, all Spring items can be grouped together for generating a size profile.
File name: attr.csv.dat
File format: comma-separated values file
Fields: Attribute Code, SKU Grouping, Season Code, Yearly Season Code.
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Attribute Code | An arbitrary attribute of an item, possibly arrived at by combining or appending multiple attributes. For example, attribute code can be a combination of color and season code. |
| SKU Grouping | Any arbitrary grouping of SKUs. |
| Season Code | An item attribute that defines the season code for the item. Season code can be year dependent, for example, Spring 2008. It can also be year independent, for example, Spring. |
| Yearly Season Code | An annual season code that can be year dependent, for example, 2008 or year independent, for example, ALL. |
Example:
darkbasic,dark color basic,dark,dark color,basic,basic,all,all darkspring2008,dark color spring 2008,dark,dark color,spring2008,spring 2008,2008,2008 darkfall2008,dark color fall 2008,dark,dark color,fall2008,fall 2008,2008,2008lightbasic,light color basic,light,light color,basic,basic,all, lightspring2008,light color spring 2008,light,light color,spring2008,spring 2008,2008,2008 lightfall2008,light color fall 2008,light,light color,fall2008,fall 2008,2008,2008
The Size hierarchy captures all valid size ranges and corresponding sizes in each size range.
File name: sizh.csv.dat
File format: comma-separated values file
Fields: Sub Size, Sub Size Range, Sub Size Length, Master Size Range, Size, and Size Range.
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Sub Size | Sub Size identifier. |
| Sub Size Range | Unique sub size range identifier. The sub size range is a hierarchical aggregate of sub size. |
| Sub Size Length | This indicates the number of sizes in a size range. For example, the size length of the S-M-L size range is three as it has three sizes. |
| Master Size Range | This aggregates sub size ranges. For example, XS-S-M-L-XL is a master size range of S-M-L, XS-S-M, and S-M-L-XL. |
| Size | Size identifier.
Note: The size is expected to have a unique identifier. For example, an S in an S-M-L size range needs to have a unique identifier from an S in an S-M-L-XL size range. |
| Size Range | Unique size range identifier. The size range is a hierarchical aggregate of size. For example, S-M-L, XS-S-M, and S-M-L-XL are a sub size range of XS-S-M-L-XL. |
Example:
6_MensShoes1,6_sub1,MensShoes_1,Men's Shoes S1,6,6 Sizes,MensShoesMaster,Master Men's Shoes,6_MensShoes,6 Master 7_MensShoes1,7_sub1,MensShoes_1,Men's Shoes S1,6,6 Sizes,MensShoesMaster,Master Men's Shoes,7_MensShoes,7 Master 8_MensShoes1,8_sub1,MensShoes_1,Men's Shoes S1,6,6 Sizes,MensShoesMaster,Master Men's Shoes,8_MensShoes,8 Master 9_MensShoes1,9_sub1,MensShoes_1,Men's Shoes S1,6,6 Sizes,MensShoesMaster,Master Men's Shoes,9_MensShoes,9 Master
This file contains all the valid size ranges. Almost a mirror hierarchy of the size hierarchy, the size range hierarchy contains a subset of the size hierarchy. The mirroring of the size hierarchy is required for SPO.
File name: sizr.csv.dat
File format: comma-separated values file
Fields: Sub Size Range, Sub Size Range Length, Master Size Range
The following table describes the fields in this file.
| Field | Description |
|---|---|
| Sub Size Range | The size range is a hierarchical aggregate of size. For example, S-M-L, XS-S-M, and S-M-L-XL are sub size ranges of XS-S-M-L-XL. |
| Sub Size Range Length | This indicates the number of sizes in a size range. For example, the size length of the S-M-L size range is three as it has three sizes. |
| Master Size Range | This aggregates sub size ranges. For example, XS-S-M-L-XL is a master size range of S-M-L, XS-S-M, and S-M-L-XL. |
Example:
MensShoes,Men's Shoes,11,11 Sizes,MensShoesMaster,Master Men's Shoes MensShoes_1,Men's Shoes_1,6,6 Sizes,MensShoesMaster,Master Men's Shoes WomensShoes,Women's Shoes,11,11 Sizes,WomensShoesMaster,Master Women's Shoes WomensShoes_1,Women's Shoes_1,6,6 Sizes,WomensShoesMaster,Master Women's Shoes
The Generation ID hierarchy is a single dimension hierarchy that contains the Generation ID dimension.
File name: gidh.csv.dat
File format: comma-separated values file
Field: Generation ID
The following table describes the field in this file.
| Field | Description |
|---|---|
| Generation ID | A unique identifier that is used to store and archive results from each SPO run. |
Example:
G1,GID 1 G2,GID 2
The escalation level hierarchy is a single dimension hierarchy that contains the escalation level ID.
File name: elh.csv.dat
File format: comma-separated values file
Field: Escalation level ID
The following table describes the field in this file.
| Field | Description |
|---|---|
| Escalation level ID | A unique identifier for each configured escalation level in the solution. |
Example:
l01,level 01 l02,level 02 l03,level 03 l04,level 04 l05,level 05
The cluster hierarchy is a single dimension hierarchy that contains the store clusters.
File name: clsh.csv.dat
File format: comma-separated values file
Field: Cluster ID
The following table describes the field in this file.
| Field | Description |
|---|---|
| Cluster ID | A unique identifier for each configured store cluster in the solution.
Note: The Junk cluster ID is required. It is used for those hierarchy members who values are all NA in the source data. |
Example:
01,Cluster 01 02,Cluster 02 Junk,Junk Cluster
The pack hierarchy is used for exporting prepack result to AP. Pack hierarchy (PCC) has one dimension PACK (pkct). It stores the number of packs.
File name: pcc.csv.dat
File format: comma-separated values file
Field: Pack ID
The following table describes the field in this file.
| Field | Description |
|---|---|
| Pack ID | A unique identifier for each configured Pre-Pack result in the solution. |
Example:
01,Pack 01 02,Pack 02 03,Pack 03 04,Pack 04 05,Pack 05 06,Pack 06 07,Pack 07 08,Pack 08 09,Pack 09 10,Pack 10 11,Pack 11 12,Pack 12 13,Pack 13 14,Pack 14 15,Pack 15 16,Pack 16 17,Pack 17 18,Pack 18 19,Pack 19 20,Pack 20
The following data files are needed:
In addition, the following special data files are needed for SPO:
File names: posxxlxg.csv.ovr.001, posxxlxg.csv.ovr.002
File format: comma-separated values file
Fields: Week, SKU, Store, UnitsExample:
W05_2007,1000000_10,1134,1.00 W07_2007,1000000_10,1134,3.00 W08_2007,1000000_10,1134,2.00 W09_2007,1000000_10,1134,1.00
This file contains Boolean measures that indicate whether an item is a fashion item or not. This file can be loaded into the domain, or the user can edit the measure in the workbook.
File names: fashionflgXXLXG.csv.ovr
File Format: comma-separated values file
Fields: SKU, fashion flag
Example:
1000000_10,false
1000000_11,false
File names: invxxlxg.csv.ovr.001, invxxlxg.csv.ovr.002, invxxlxg.csv.ovr.003, invxxlxg.csv.ovr.004
File format: comma-separated values file
Fields: Week, SKU, Store, Units
Example:
W05_2007,1000000_10,1134,1.00 W06_2007,1000000_10,1134,1.00 W07_2007,1000000_10,1134,1.00 W08_2007,1000000_10,1134,2.00
This data file contains information on the rank of a size in a size range. Size is the unique size identifier. SPO looks up the size range that the size belongs to and interprets the size rank as the rank of the size within the size range.
The size rank information is used by SPO in evaluating size profiles, as well as for displaying sizes and their ordering in the size profile workbooks.
File name: sizerankxxlxg.csv.ovr
File format: comma-separated values file
Fields: Size, Size Rank
Example:
XS_SML,1 S_SML,2 M_SML,3 L_SML,4
This file relates each SKU to an attribute code.
|
Note: For an implementation that is not using attribute codes for size profile generation, all SKUs can be set to a generic value for the attribute code. |
File name: skuatcdmapxxlxg.csv.ovr
File format: comma-separated values file
Fields: Size, Attribute code
Example:
1000035,darkfall2008 1000036,darkfall2008 1000037,darkfall2008 1000038,darkfall2008
This file relates each SKU to a master size.
File name: skumsizmapxxlxg.csv.ovr
File format: comma-separated values file
Fields: SKU, Master Size
Example:
10004,2_BoysShoes 10010,10_BoysShoes
This file is related to the boolean measure based on skup_str_sizN. You can edit this measure from the Size Range Management workbook or load it manually. It identifies the sub size range that is carried over in a store for a certain style-color.
File name: sbsznmskxxlxg.csv.ovr
This file contains descriptive labels for each configured escalation level. This label is available for display as an attribute measure in all SPO workbooks.
File name: elvlintlbxxlxg.csv.ovr
File format: comma-separated values file
Fields: Escalation level, Label
Example:
l01,class/store/attribute/size l02,class/region/attribte/size l03,class/seasoncode/size
This file indicates to SPO the normalization intersection for each escalation level, that is, the intersection to which all sizes in a size range are aggregated to add to 1. It is the same as the escalation level intersection except that the size dimension is aggregated to the size range.
File name: elvlnrmintxxlxg.csv.ovr
File format: comma-separated values file
Fields: Escalation level, Escalation level normalization intersection
Example:
l01,clssstr_atcdsizn l02,clssrgn_atcdsizn l03,clss_scd_sizn
This file contains the default escalation order associated with each escalation level. This file is optional.
|
Note: If this file is not loaded, the same information can be entered from the SPO Administration workbook. |
File name: elvlorderxxlxg.csv.ovr
File format: comma-separated values file
Fields: Escalation level, Escalation order
Example:
l01,1 l02,2 l03,3 l04,4 l05,5 l06,6
This file indicates the intersection at which size profiles are displayed in the SPO Approval workbook. This is the same as the escalation intersection, except with a size range dimension along the Size Range hierarchy appended to it.
File name: elvlinttpxxlxg.csv.ovr
File format: comma-separated values file
Fields: Escalation level, Display intersection
Example:
l01,clssstr_atcdsizeszr_ l02,clssrgn_atcdsizeszr_ l03,clss_scd_sizeszr_
The measure Fashionflg is a Boolean indicator based on SKU. When a SKU is a fashion item, its value is true. The Fashion item indicator file, fashionflgxxlxg.csv.ovr, is the data feed for the measure.
File format: comma-separated values file
Fields: sku number, fashion indicator
Example:
10000011, true
The following are the prepack-specific hierarchy files:
Based on user inputs, the prepack plug-in generates this file in the configuration step of the domain building process.
File name: cpck.csv.dat
Based on user inputs and the product hierarchy file in the domain, this file is generated in the configuration step of the domain building process.
File name: prp.csv.dat
In order to calculate the cardinal values, you can use the following formulas:
Num of gpid = num of max deliveryID * num of prepack type
The number of PACKID per base level or agg level = Num of gpid * num ofstyle-color
The number of PACKID per complex pack level = Num of gpid * num of complexpack
The total PACK pos num = num of PACKID for base level + num of PackID forcomplex pack level + num of PackID for aggregated levels
Based on user inputs, this file is generated in the configuration step of the domain building process.
File name: pckt.csv.dat
Based on user inputs, this file is generated in the configuration step of the domain building process.
File name: optl.csv.dat
Based on user inputs, this file is generated in the configuration step of the domain building process.
File name: prof.csv.dat
Based on user inputs, this file is generated during the domain building process.
File name: dsrc.csv.dat
Based on user inputs, the Prepack plug-in generates the complex pack hierarchy file in the configuration step of the domain building process.
File name: dlvy.csv.dat
The script used to build or patch the SPO domain is described in this section. The script is located in the <spo_directory>/batch directory.
The Building a Domain section contains detailed information on the following build script:
Script
buildSizeOpt.sh
Usage
buildSizeOpt.sh <options -cdil> <flags -gpt>
Table 3-1 Domain Description
| Argument | Allowed Values | Description |
|---|---|---|
|
option |
c |
Configuration directory Default is |
|
d |
Domain path Default is |
|
|
i |
Input directory Default is |
|
|
l |
Log directory Default is |
|
|
flags |
g |
Set this flag to use debug function libraries |
|
p |
Set this flag to make a patch build |
|
|
t |
Set this flag to make a test build |
Notes
The rules in the common_data group are crucial to the batch process and should never be modified by the retailer.
The script uses the Configuration Tools rpasInstall utility to build a domain. See the Oracle Retail Predictive Application Server Administration Guide 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 <spo_directory>/input directory.
SPO GA build script includes the following steps. If you have customizations for the build script, you will need to include the following mandatory steps in the same order as the GA scripts.
Table 3-2 Parameters Used
| Parameter | Purpose |
|---|---|
|
<config path> |
This is the path for the configuration. |
|
<config name> |
This is the configuration name. For GA, it is SPO. |
|
<input path> |
This specifies the path for the input files. |
|
<typeInstall> |
this specifies the install type. Options are -testinstall, -fullinstall, or -patchinstall. |
|
<domain path> |
This specifies the path of the domain. |
The required steps are as follows:
This is a mandatory step, to generate internal hierarchy and measure data files. These files are dynamically created by plugin and have to be created before calling rpasinstall.
For SPO:
execPluginTask.sh sizeOpt:com.retek.labs.sizeopt.plugin.installer.SizeOptPosGenerator <config path>/ <config name> /<config name>.xml <input path>
The following files will be generated and put into <input path>
For PrepackOpt:
execPluginTask.sh PrepackOpt:com.retek.labs.prepackopt.plugin.installer.PrepackOptPosGenerator <config path>/<config name>/<config name>.xml <input path>
The following files will be generated and put into <input path>
If using -patchinstall mode, copy the above files from <input path> to the "input" folder in SPO domain. This is a mandatory step for patching domain, rpasinstall process does not automatically copy files from <input path> to the "input" folder in domain being patched.
This is a mandatory step.
rpasInstall <typeInstall> -ch <config path> -cn <config name> -in <input path> -log <log file name> -dh <domain path> -updatestyles -p <partition dimension> -rf AaiFunctions -rf AaiJniFunctions -rf ClusterEngine -rf Transform -skipvalidation
For the -fullinstall mode, remove styles from "sizeoptapprove" workbook.
remove_styles.ksh -d <domain path>/<config name> sizeoptapprove
This step is a mandatory step. It is needed to remove the RPAS default style which does not work with the SPO dynamic style.
The follow measures need to be loaded to the SPO domain. (for more information refer to Files Needed to Build the SPO Domain).
Table 3-3 Files required for SPO
| File Description | File Name |
|---|---|
|
SKU to Attribute Code Map Data File |
skuatcdmapxxlxg |
|
SKU to Master Size Map Data File |
skumsizmapxxlxg |
|
Inventory Data File |
invxxlxg |
|
Sales Data File |
posxxlxg |
|
Sub Size Range Assignment Data File |
sbsznmskxxlxg |
|
Size Rank Data File |
sizerankxxlxg |
|
Fashion Item Flag |
fashionflgxxlxg |
Table 3-4 Files required for Prepack
| File Description | File Name |
|---|---|
|
Store Profile |
strprof |
|
Clustered Profile |
clstprof |
|
Planned Receipts |
datasrc1 |
|
Last Year Sales |
datasrc2 |
|
Style-color To Master Size Map |
skup2msiz |
|
Style-color To Master Size Range Map |
skup2msrn |
|
Master Size Rank |
msizerank |
|
Start Date for each style-color/store |
skupstartdt |
|
End Date for each style-color/store |
skupenddt |
To populate Active item alert measure for each escalation level:
alertmgr -d $domainPath -findAlerts -categories "Profile_generation"
The SPO 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 RPAS 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 Classic Client or the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
Data is loaded into SPO using the standard RPAS approach. See the Oracle Retail Predictive Application Server Administration Guide for the Classic Client or 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 the ODI enabled integration for the Fashion Planning Bundle, see Chapter 5. If you are using script integration, see Chapter 6. For information on other batch scripts, see Chapter 8.
