Oracle Retail Knowledge Base

8 Size Profiles

13 min read

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.

All Runs
acions
¥
vi		ew Y
+ BF
bd
xX
FC
MB
V
EZ vetacn
StatusRunName
All Profiles
RunDescription		Loc.NodeMerch.NodeEsc.Attribute
132.@ SetupRUN@ 06/05/25, 11:43:11AMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
128&SetupRUN@ 06/04/25, 5:36:51 PMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
124&SetupRUN@ 06/04/25, 2:01:33PMDistrict-AU - NewSouth Wales‘SubClass-GroundCoffeeNone
115=
Setup		RUN@05/30/25, 8:45:59AMDistrict-AU -NewSouth WalesSubClass-GroundCoffeeNone
114=
Setup		RUN@05/29/25,9:31:54PMDistrict-AU -NewSouth WalesSubClass-Ground CoffeeNone
113.
= @ SetupRUN@05/29/25, 9:31:37PMDistrict-AU -NewSouth WalesSubClass-GroundCoffeeNone
112“SetupRUN @ 05/29/25, 9:02:21 PMDistrict-AU - NewSouthWalesSubClass-Ground CoffeeNone
11 =@ SetupRUN@05/29/25,8:43:22PMDistrict-AU -NewSouth WalesSubClass-GroundCoffeeNone
110=
Setup		RUN@05/29/25, 3:32:42PMDistrict-AU -NewSouth WalesSubClass-GroundCoffeeNone
109SetupRUN@ 05/29/25, 3:31:30PMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
108SetupRUN@ 05/29/25, 3:22:27PMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
107SetupRUN@ 05/29/25, 1:18:52 PMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
106&SetupRUN@ 05/29/25, 10:38:47AMDistrict-AU - NewSouth WalesSubClass-GroundCoffeeNone
105SetupRUN@05/29/25,10:37:13AMDistrict-AU-NewSouth WalesSubClass-GroundCoffeeNone

Information Tab

Use the Information tab, to provide the run name and description in the Run Details section. Use the selectors to select merchandise and location nodes that the size profile should be generated for. The highest/lowest level of selection and the lowest level that multi-select is allowed are controlled by global configurations. These configurations are explained in the Oracle Retail AI Foundation Cloud Services AI Foundation Implementation Guide .

Select the historical season to filter the historical data based on the start/end date of that season as well as limit the items to the ones that are mapped to that season. If item-season mapping is not available for a season, no data will be found for processing and no profiles will be generated. You can also select no season. In that case, the start/end of the historical period will be defaulted to the values indicated by SPO_NO_SEASON_START_DATE/ SPO_NO_SEASON_END_DATE in RSE_CONFIG. If those values are null, then the start/end of the historical period will be defaulted to the min/max weeks in the calendar hierarchy data (RSE_CAL_HIER table). In either case, you can override the start/end of historical period in the third tab of the Create Run screen.

In addition to the historical season, you can also select a run season. This is simply linking the run to the selected season. This is a feature which is used by the RMS Allocation system to link the profiles to the upcoming seasons.

If you want to use a product attribute in the escalation, select an attribute value. In the Parameters tab, you can set the escalation path as desired. Lastly, select the option for warehouse profiles, if desired.

Size Ranges Tab

A size range consists of a set of all available sizes for each style-color. For example, the size range for the style-color of Men’s Pullover Black and Store of Boston Downtown is S, M, L, XL. The size range data is provided by the retailer.

Size range data is required for estimating the size profiles. Once you navigate from the Information tab to any of the other tabs, a process runs at the back end to extract size range data for the selected merchandise/location nodes and to populate relevant tables. This process can take some time to complete, depending on the size of data. You will see a pop-up message in the UI to indicate that the process is in progress. While the process is in progress, the merchandise/location filters will be disabled and cannot be modified. You can see the status of this process in the notifications on the left menu in the screen.

In the Size Ranges tab, shown in Figure 8-3, size range data is shown for each style-color and each store. If a certain size is not available in a size range, it will be shown as greyed out. If a size has been specified as an expected Kink Size (which means it is an odd size that may have significantly fewer or more sales than other sizes), it will be shown in blue.

Parameters Tab

The Parameters tab displays the parameters that are used by the size profile generation algorithm. The escalation path is used to cluster data and estimate profiles at different levels (that is, merchandise/location or merchandise/location/attribute) and find the optimal size profiles that best represent the expected demand pattern and is most robust to stock out periods, imbalanced stock across sizes and other factors. When a size profile at a given level of the escalation path does not meet the post-processing criteria, it automatically gets rejected and the size profile associated with a higher level is examined. This process continues until a valid size profile is fond at one of the levels along the escalation path.

The lowest level of the escalation path in a run defines the level of the profiles generated in that run. For example, if the escalation path consists of department-region, departmentlocation, subclass-region, and subclass-location, the size profiles will be generated at subclass-location level, that is one profile for each subclass/location/size range. In addition, for all runs at any level, size profiles will also be generated at the lowest level (style-color/ location).

The parameters of the size profiles estimation algorithm fall into two categories: pre-processing and post-processing.

You can edit the values for these parameters, as shown in Figure 8-5. The default values of the parameters are defined in SPO_DFLT_PARAMETER. You can modify the default values using the Manage System Configuration screen under the Control & Tactical Center. The table below shows the name, description, and default value of the parameters.

PARAMETER_NA PARAMETER_TY UI_PARAMETER_ PARAMETER_VA DESCRIPTION ME PE LABEL LUE SPO_MIN_SEASO SKU/Store Minimum Season 1 Minimum Season N_LEN_SKU_STR Eligibility Length Length SKU-Store for determining SKU-Store Eligibility. SPO_MIN_SALES SKU/Store/Week Minimum Sales 1 Minimum Sales for SKU_STR_WK Eligibility determining SKU/ Store/Week Eligibilit SPO_MIN_INV_SA SKU/Store/Week Minimum Inventory 1 Minimum Inventory LES_SKU_STR_W and Sales and Sales for K determining SKU/ Store/Week Eligibility SPO_PCT_MAX_S SKU/Store/Week Percent Maximum 0.05 Percent Max SKUKU_STR_WK Eligibility Store-Week for determining SKU/ Store/Week Eligibility MIN_SLS_PRNT_S SKU-Parent/Store Minimum Sales 4 Minimum sales TR_WK Eligibility units for determining SKUParent/Store Eligibility. MIN_SKUS_PRNT SKU-Parent/Store Minimum SKUs 2 Minimum SKUs for STR_WK Eligibility determining SKUParent/Store Eligibility MIN_WKS_PRNT SKU-Parent/Store Minimum Weeks 2 STR_WK Eligibility determining SKUParent/Store Eligibility SPO_MIN_SKU_S SKU-Parent/Store/ Minimum SKUs 2 Minimum SKUs for TR_WK Week Eligibility determining SKUParent/Store Eligibility SPO_PCT_SZ_RN SKU-Parent/Store/ Valid Sizes 0.41 Percent Size G_PRNT_STR_WK Week Eligibility Percentage Range for determining SKUParent/Store Eligibility. SPO_SZ_PRO_GE Size Profile Size Profile Optimization The size profile N_METHOD Generation Generation Method generation method (Optimization or Normalized). SPO_SKU_PRNT Postprocessing Valid Sample 2 Post Processing STR_WK Threshold threshold: Min

1 Minimum Season Length SKU-Store for determining SKU-Store Eligibility.

  - 1 Minimum Sales for determining SKU/ Store/Week Eligibilit

  - 1 Minimum Inventory and Sales for determining SKU/ Store/Week Eligibility

  • 0.05 Percent Max SKUStore-Week for determining SKU/ Store/Week Eligibility

    • 4 Minimum sales units for determining SKUParent/Store Eligibility.

    • 2 Minimum SKUs for determining SKUParent/Store Eligibility

    • 2 Minimum Weeks for determining SKUParent/Store Eligibility

    • 2 Minimum SKUs for determining SKUParent/Store Eligibility

  • Range for determining SKUParent/Store Eligibility.

  • Optimization The size profile generation method (Optimization or Normalized).

    - 2 Post Processing threshold: Min number of SKUparent/store/weeks with at least one valid sale.
PARAMETER_NA
ME		PARAMETER_TY
PE		UI_PARAMETER_
LABEL		PARAMETER_VA
LUE
DESCRIPTION
SPO_TOT_UNIT_S
LS		PostprocessingValid Sales units
Threshold		2 Post Processing
threshold: Min
number of valid
sales units that
each size in the
partition should
have.
SPO_TOT_UNIT_S
LS_PCT_SIZES		PostprocessingValid Sizes
Percentage		0.4 Post Processing
threshold: Min
Percent of sizes.
SPO_SALE_PROF
_CORR_THRESH
OLD		PostprocessingThreshold for
correlation with
Sales Profile		0.9 This parameter
provides the
correlation
threshold between
size profiles and
sales profile.
SZ_PROF_OVER_
CORR_THRESHO
LD		PostprocessingThreshold for size
profiles compared
with historical sales
profile		2 Indicates size
profiles are
compared with
historical sales
profile and if the
ratio between size
profile and sales
profile exceeds this
value for at least
one size, profile is
flagged and is
shown in UI under
over-correction tile
in run output
SPO_KINK_INNER
_RATIO		Kink Size AnalysisKink Inner Ratio1.1 The default value
for kink inner ratio.
SPO_KINK_OUTE
R_RATIO		Kink Size AnalysisKink Outer Ratio1.03 The default value
for kink inner ratio.
SPO_CORR_LOW
_SELL_FLG		Low Seller
Correction		Correct Size
Profiles for Low
Sellers		Y The flag (Yes or
No) to indicate
whether to apply
post processing to
correct size profiles
of low sellers
SPO_LOW_SELL_
AVG		Low Seller
Correction		Average Weekly
Sales of SKU		1 Average weekly
sale units across a
season, below
which deems a
SKU (Size) to be a
low seller.

Size Profiles Tab

The Size Profiles tab displays the generated size profiles for each merchandise/location combination at the run level. You can filter the profiles based on their submitted and alert status using the five tiles at the top of the screen for All Profiles, Submitted, Ready to Submit, Low Sellers, Kink Exceptions, and Over-corrected.

Below the tiles, you can use the collapsible filter section to filter the size profiles based on the merchandise and location hierarchies. You can also use the check-box filters above the table to further filter profiles by status (auto/user, submitted, approved, sent for review) as well as profiles with notes/flag. Lastly, you can filter profiles to show/hide the profiles that had any sales during the historical period.

The size profiles table is multi-row selectable, using the Ctrl and Shift buttons. This table has the following columns:

  • The first column (with no header) shows the status of the profile. Values are user submitted ( ), auto submitted ( ), and approved.

  • The action column has the note and flag icons. Values are some notes have been added ( ), no notes added yet ( ), flagged ( ), not flagged ( ).

You can click on the note icon to view or edit the notes in a pop-up. You can also click the flag icon to flag or un-flag a size profile.

  • The columns that show the merchandise and location hierarchy (for example, Region, District, Location, Department, Class, Subclass, and so on) and another column to show attributes. If an attribute is not selected when setting up the run, this column will have value of None.

  • The escalation path that indicates the level at which the size profile has been generated.

The size profiles column that shows the following values:

  • System: the size profile generated by the system (using the estimation algorithm). This profile will be identical to the “escalated level size profile” unless the merchandise/location at the run level has fewer sizes than the merchandise/location at the escalation level. In that case the escalation level profile will be normalized based on the sizes available for the merchandise/location at the run level such that the system generated profile sums to 1.

  • User: the values edited by the user. If the user has not edited the values or has not seeded system values to populate user values, this row will be empty.

  • Approved: the approved values, if the size profile was approved. If the size profile has not been approved, this row will be empty.

  • Sales Profile: shows the profile of the observed sales (without correcting for the lost sales and any other post-processing) at the profile level.

  • Escalated level sales profile: shows the profile of the observed sales (without correcting for the lost sales and any other post-processing) at the escalation level.

  • Escalated level size profile: shows the estimated profile at the escalation level.

The following actions can be done in the Size Profiles table:

  • Seed the user values with the System size profile by selecting one, or multiple, rows and clicking on the Seed System SP button at the top of the table.

  • Edit a profile in the edit pop-up by selecting a single row and clicking on the Edit icon at the top of the table. If a size profile is submitted, edit is not allowed. To edit, the user must first un-submit the profile. The edit pop-up is shown in Figure 8-7. The edited values must sum

a a

The filters section is similar to the filters in the Run Output screen. You can use it to filter the size profiles based on product and location hierarchies. Using the profile level filter, you can view either the profiles at lowest level (style-color/location) or the profiles at higher levels. You can also use the check-box filters above the table to further filter profiles by ready for approval status, as well as having notes or flags. Lastly, you can filter profiles to show/hide the profiles that had any sales during the historical period, are low sellers, have kink exception, or have over-correction alert.

Assigned Tasks Table

The assigned tasks table is multi-row selectable using the Ctrl and Shift buttons. This table has the following columns:

  • The first column (with no header) shows the status of the profile: Values are user submitted ( ) and auto submitted ( ).

  • The action column has a note icon and a flag icon. Values are some notes have been added (

  • You can click on the Note icon to view or edit the notes in a pop-up. You can also click the Flag icon to flag or un-flag a size profile.

  • Columns that show three levels of hierarchy for the merchandise and location of the profile. For example, if the profile is at style-color/location level, the three location hierarchy columns will show the region, district and location. The three merchandise hierarchy columns will show the subclass, style and style-color. Note that the submitted profiles can belong to different runs with different levels. Therefore, the profiles in submitted table are not necessarily at the same level.

  • Attribute column to show the attribute that was selected when creating the run. If attribute was not selected when setting up the run, this column will have value of None.

  • The escalation path which indicates the level at which the size profile has been generated.

Size profiles chart that shows the following values:

  • System: the size profile generated by the system (using estimation algorithm)

  • User: the values edited by the user. Initially this row shows the values edited by the sender user (if any edits has been made).

  • Submitted: the values that were submitted by the sender user.

  • Sales Profile: shows the profile of the observed sales (without correcting for the lost sales and any other post-processing).

The following actions can be performed in this screen:

  • Seed the user values with System size profile, by selecting one or multiple rows and clicking on the Seed System SP button at the top of the table.

  • View and edit the notes on each profile, using the Note icon in the Action column that opens a pop-up.

  • Flag or un-flag a profile by clicking on the Flag icon in the Action column.

  • Edit a profile in the edit pop-up, by selecting a single row and clicking on the Edit icon at the top of the table.

  • Approve the profiles by selecting one or multiple profiles and using the Approve button above the table. To approve all profiles that match the selected filters, use the Approve All button. The approved profiles will be exported out once the nightly or ad-hoc export process runs.

  • SPO_STYLE_DUP_DIFF_GRP_VW: provides the style-colors having more than one size range. This is considered invalid data and will require review of data in the source system.

In this guide

  • 10 Size Profiles — AI Foundation Implementation Guide · shares RSE_CAL_HIER, SPO_DFLT_PARAMETER, SPO_NO_SEASON_END_DATE, SPO_NO_SEASON_START_DATE

Graph View

Backlinks