4 Size Profiles

Size Profile refers to the ratio derived out of historical sales figures to give an accurate estimate of the number of items of different sizes or colors that must be allocated to the destination store and applies only to fashion items within Allocation.

One of the sources of this data is the Oracle Retail Size Profile Optimization (SPO) system which resides on RPAS and creates optimal profiles of size distribution both by merchandise category and store. In the Store Size Profile Optimization product, you can now create seasonal store size profiles. These multiple store size profiles created in SPO are assigned Generation ID's (GIDs).

A combination of a merchandise hierarchy and store may have multiple size profiles specific to different seasons. These multiple profiles or GIDs are displayed as an option in the Policy Maintenance window and they can be used while performing a fashion allocation depending on the items being allocated and their expected date of arrival at the stores. A fashion item may have different summer and fall profiles defined and you can select the appropriate profile based on the time period of the year when the item is being allocated.

All fashion, fashion pack, and fashion group allocations need to have size profile information. Size profile information is determined based on the selling ratio of the fashion items and is used to spread the quantity being allocated from Style/Color down to the SKU level. If an item / destination location does not have size profile information, it is excluded while performing the calculations.

Populate Size Profile Information

In order to properly use Allocation Cloud Service for fashion items, customers need to populate the size profile data either through the UI or the database table. Each record should have hierarchy, location, and quantity information and should only contain details relevant to the target hierarchy level. For further information about size profile please see the Allocation Cloud Service and SPO section.

A combination of a merchandise hierarchy and location group can have multiple size profiles set up, which are termed as Generation IDs (GIDs). Size Profile Optimization application in RPAS provides size profile information for different seasons. These seasonal profiles are stored using three different tables in Allocation Cloud Service.

Table 4-1 ALC_GID_HEADER

Column Required Description

ID

Y

This is the primary unique ID generated from the sequence

GID

Y

This is the GID season code, populated from SPO

GID_DESC

Y

The description for the GID

CREATED_BY

Y

Indicates the user who created the record

CREATION_DATE

Y

The timestamp of the record creation date

LAST_UPDATED_BY

Y

Indicates the user who last updated the record

LAST_UPDATE_DATE

Y

The timestamp of the last updated date for the record

LAST_UPDATE_LOGIN

Y

Indicates the session login associated to the user who last updated the row.

Table 4-2 ALC_GID_PROFILE

Column Required Description

GID_ID

Y

This is the foreign key to the primary key of ALC_GID_HEADER

GID_PROFILE_ID

Y

This is the primary unique ID generated from the sequence

CREATED_BY

Y

Indicates the user who created the record

CREATION_DATE

Y

The timestamp of the record creation date

LAST_UPDATE_DATE

Y

The timestamp of the last updated date for the record

LAST_UPDATE_LOGIN

Y

Indicates the session login associated to the user who last updated the row

Table 4-3 Size Profile Table details

Column Required Description

SIZE_PROFILE_ID

Y

This column is auto-generated

LOC

Y

This column stores the location to which the size profile will apply. This column should always be populated

DEPT

N

This column stores the dept to which the size profile will apply. This column should be populated only for dept, class, and subclass level size profiles.

CLASS

N

This column stores the class to which the size profile will apply. This column should be populated only for class, and subclass level size profiles.

SUBCLASS

N

This column stores the subclass to which the size profile will apply. This column should be populated only for subclass level size profiles.

STYLE

N

This column stores the Style Id to which the size profile will apply. This column should be populated only for Style, or Style Diff level size profiles.

SIZE1

N

This column stores the aggregated or non-aggregated Diff_1 information to which the size profile will apply. In the case of Style_Diff level, This column contains the aggregated or non-aggregated diff. In the case of Dept, Class, Subclass or Style Level; This column contains the non-aggregated diff.

SIZE2

N

This column stores the aggregated or non-aggregated Diff_2 information to which the size profile will apply. In the case of Style_Diff level, This column contains the aggregated or non-aggregated diff. In the case of Dept, Class, Subclass or Style Level; This column contains the non-aggregated diff.

SIZE3

N

This column stores the aggregated or non-aggregated Diff_3 information to which the size profile will apply. In the case of Style_Diff level, This column contains the aggregated or non-aggregated diff. In the case of Dept, Class, Subclass or Style Level; This column contains the non-aggregated diff.

SIZE4

N

This column stores the aggregated or non-aggregated Diff_4 information to which the size profile will apply. In the case of Style_Diff level, This column contains the aggregated or non-aggregated diff. In the case of Dept, Class, Subclass or Style Level; This column contains the non-aggregated diff.

SIZE_GROUP1

Y

This column stores the value 'X'

SIZE_GROUP2

N

This column stores the value 'null'.

QTY

Y

This column stores the individual size profile quantity.

CREATED_BY

Y

This column stores the created by user name

CREATION_DATE

Y

This column stores the creation date

LAST_UPDATED_BY

Y

This column stores the last updated by user name

LAST_UPDATE_DATE

Y

This column stores the last updated date

LAST_UPDATE_LOGIN

Y

This column stores the last updated login

OBJECT_VERSION_NUMBER

Y

This column store the object version number

GID_PROFILE_ID

N

This column stores the GID_PROFILE_ID. This column is populated when the size profile is part of a Seasonal or Generation set. This column is null if it is a standard size profile. This column is a Foreign Key on the table ALC_GID_PROFILE

SIZE_PROFILE_LEVEL

Y

This column stores a numerical size profile level. Dept = 1, Class = 2, Subclass = 3, Style = 4, Style_Diff = 5

Create Size Profiles

A size profile can be created through any of the following procedures:

Create a Size Profile

You can create a size profile based on the criteria defined here:

Non-GID based size profile

  • If the current allocation is using a non-GID based profile, you can create, edit, or delete the size profile details.

  • If there is no data present in the database corresponding to the item/location combination, you can add the size profile details through the system UI.

To create a size profile:

  1. From the Tasks menu, select Manage Size Profiles. The Manage Size Profiles window appears.

  2. Search and select the size profile that you want to edit.

  3. Click the edit icon. The size profile is enabled for editing.

    Figure 4-1 Size Profile Window - Search Result Pane

    The size profile search results pane

  4. Enter a ratio in the Ratio column for each of the items.

  5. Click Save to save the size profile.

Copy a Parent

To copy a parent:

  1. From the Tasks menu, select Manage Size Profiles. The Manage Size Profiles window appears.

  2. Search and select the size profile that you want to copy to.

  3. Click Copy Entire Parent. The Copy Entire Parent window appears.

    Figure 4-2 Copy Entire Parent Window

    Copy entire parent window

  4. In the Copy From field, select the parent. The size profile details appear.

    Note:

    The parent to copy from must have the same sizes and diffs as the parent being copied to.

  5. Select the size profile. The Copy button is activated.

  6. Click Copy. The size profile is copied and the Size Profile window appears.

  7. If required, you can edit the ratio in the Ratio column.

  8. Click Save to save the size profile.

Copy a Single Diff

You can copy size profile ratios from single diff of the selected parent to one or more diffs of the current parent.

To copy a single diff:

  1. From the Tasks menu, select Manage Size Profile. The Manage Size Profiles window appears.

  2. Search and select the size profile that you want to copy.

  3. Click Copy Single diff. The Copy Single diff window appears.

  4. In the Copy From field, select the parent. The size profile details appear.

  5. Click the Expand icon to view the aggregated diffs available in the size profile.

  6. Select the diff from which you wish to copy. The Copy button is activated.

    Figure 4-3 Copy Single diff Window - Single diff selected

    The copy single diff window

  7. Click Copy. The single diff is copied and the Manage Size Profile window appears.

  8. If required, you can edit the ratio in the Ratio column.

  9. Click Save to save the size profile.

Manage Size Profiles

The following actions can be performed when managing Size Profiles:

Search for Size Profiles

Generation IDs are sets of store size profile data created and maintained in Oracle's Size Profile Optimization (SPO) product. SPO to Allocation is required in order to search and select GIDs.

You can search for a size profile in three different combinations.

  • GID only search – Displays all the records that correspond to the selected GID. The records displayed may be at the same merchandise hierarchy level or different ones.

  • GID and Merchandise Hierarchy combined search – Displays records, common to the selected GID and merchandise hierarchy.

  • Merchandise Hierarchy only – Displays records that correspond to the selected merchandise hierarchy. There may be more than one GID record (Summer Profile, Spring Profile, Winter Profile) but there is always only one set of non-GID records at a given level.

To search for a size profile:

  1. From the Tasks menu, select Manage Location Size Profiles. The Manage Location Size Profiles window appears.

  2. In the Generation ID field, select an ID for a GID search or a GID merchandise combined search.

  3. In the Size Profile Level field, select a level.

  4. In the Department field, select the department.

  5. If necessary based on the size profile level you selected in step 3, select the class, subclass, parent, or parent/diff.

  6. In Location Selection Criteria, select the location for which the size profile must apply. You must select at least one location.

  7. In Size Group Selection Criteria, select the size group for the size profile.

  8. Click Search. The list of size profiles matching the criteria is displayed.

Edit Size Profiles

You can edit an existing size profile based on the criteria defined here:

GID based size profile

  • If the current allocation is using a GID based profile, you can only edit or delete the size profile.

  • If there is no data present in the database corresponding to the selected GID, then you must either select a different GID or a non-GID based profile. Data addition is not possible for a GID based size profile.

Non-GID based size profile

  • If the current allocation is using a non-GID based profile, you can create, edit, or delete the size profile details.

  • If there is no data present in the database corresponding to the item/location combination, you can add the size profile details through the system UI.

To edit size profiles:

  1. From the Tasks menu, select Manage Size Profiles. The Manage Size Profiles window appears.

  2. Search and select the size profile that you want to edit.

  3. Click the edit icon. The size profile is enabled for editing.

    Figure 4-4 Size Profile Window - Search Result Pane

    The size profile search results pane

  4. Enter a ratio in the Ratio column for each of the items.

  5. Click Save to save the size profile.

Delete a Size Profile

To delete a size profile:

  1. From the Tasks menu, select Manage Size Profiles. The Manage Size Profiles window appears.

  2. Search and select the size profile that you want to delete.

  3. Click the delete icon.

  4. Click OK to confirm deletion of the size profile.

Warehouse Size Profiles

The following options are available for warehouse size profiles:

  • % to Total

    When this option is selected, the system allocates based on the percentage of each size to the total available quantity. This is determined using the following steps -.

    Step 1: Determine the percentage availability of each size to the total available quantity to allocate at the source location. Refer to the following table for this calculation:

    Style-Color Red Navy Shirt Available Quantity % to Total
    SKU SM Red Navy Shirt 250 21
    SKU MD Red Navy Shirt 300 26
    SKU LG Red Navy Shirt 450 38
    SKU XL Red Navy Shirt 175 15

    Step 2: To allocate 200 units to the destination warehouse based on its need value.

    Step 3: Apply the % to Total values obtained in Step 1 against the allocated quantity of 200 units going out to the destination warehouse. The results would be as follows:

    Style-Color Red Navy Shirt 200
    SKU SM Red Navy Shirt 43 200*21
    SKU MD Red Navy Shirt 51 200*26
    SKU LG Red Navy Shirt 77 200*38
    SKU XL Red Navy Shirt 30 200*15

    Size SM = 21% of the total available quantity, 200*21% = 43 units

    Size MD = 26% of the total available quantity, 200*26% = 51 units

    Size LG = 38% of the total available quantity, 200*38% = 77 units

    Size XL = 15% of the total available quantity, 200*15% = 30 units

    Total allocated by size to warehouse = 200 units

    Note:

    The total available quantity refers to the total number of units present in the set of sources selected for an item linked to the specific warehouse within an allocation.

    Consider the following example:

    PO1 for WH1 = 100 units

    PO2 for WH2 = 175 units

    SOH at WH1 = 55 units

    SOH at WH2 = 45 units

    • If both PO1 and SOH are selected as sources for WH1, then the total available quantity for allocations sourced out of WH1 = 100 + 55 = 155 units

    • For WH2, if only SOH is selected as the source, then the total available quantity for allocation sourced out of WH2 = 45 units (ignoring the 175 units present in PO2).

    So, based on the source(s) selected within an allocation for a fashion item, the total available quantity is subject to change.

    Note:

    This method does not apply to What-if allocations which will completely rely on records in the database table ALC_SIZE_PROFILE. An exception is thrown if there are no records in this table just like it works for store locations for this type of an allocation.

    Any holdback quantity specified in the source warehouse is not considered while determining the warehouse availability.

  • WH Sales Curve

    This option is valid only for the Demand Source = History. An error pop-up is encountered if you try to apply this option for other demand sources.

    When applied, this will apply a curve using a weighted average logic from all the data present in the Issues column from the existing RMS owned ITEM_LOC_HIST table for the warehouse locations. For any store locations, the check-boxes linked with the sales type that are checked will act as an additional filter.

    For example, if Regular and Promotional are selected in the Policy window, both these types of sales issues in the ITEM_LOC_HIST table will be considered.

    In case of no records present for the warehouse in the table, the allocation will be moved to the Calculation Error state.

Understanding the Manage Size Profiles Window

The Manage Location Size Profiles window allows you to view, edit, and create size profiles, or size curves, at any merchandise hierarchy level including department, class, subclass, parent, diff. Allocation allows you to load size profiles (curves) from Oracle Retail Curve, a module of Oracle Retail Demand Forecasting.

Figure 4-5 Manage Size Profiles Window

Manage size profiles window

Following are the fields available on the Size Profile window:

  • Generation ID

    Indicates the generation IDs (GIDs) sent from Oracle Retail Size Profile Optimization (SPO). GIDs are seasonal store size profiles.

  • Size Profile Level

    Indicates the merchandise hierarchy level for which the size profile records are retrieved. This list contains the following values:

    • Department

    • Class

    • Subclass

    • Parent

    • Parent/Diff

  • Department

    Indicates the Department ID that the size profile is associated with.

  • Class

    Indicates the Class ID that the size profile is associated with.

  • Subclass

    Indicates the Subclass ID that the size profile is associated with.

  • Parent

    Indicates the Parent ID that the size profile is associated with.

  • Parent/Diff

    Indicates the Parent/Diff ID that the size profile is associated with.

  • Single Store

    Indicates the Store ID used for the size profile search.

  • Single Warehouse

    Indicates the Warehouse ID used for the size profile search.

  • Location Group (Advanced search option)

    Following are the options available:

    • Store Grade Group

      Indicates the Store Grade Group ID the size profile is associated with.

    • Store Grade

      Indicates the Store Grade ID the size profile is associated with.

    • Location List

      Indicates the Location List ID the size profile is associated with.

    • Location Trait

      Indicates the Location Trait ID the size profile is associated with.

  • All Stores (Advanced search option)

    Indicates that the size profile details for the items in the allocation for all the valid stores for which the item range exists is displayed.

  • All Warehouses (Advanced search option)

    Indicates that the size profile details for the items in the allocation for all the valid warehouses for which the item range exists is displayed.

  • Size Group

    Indicates the size group linked to the size profile. Displays a list of non-aggregated size groups for the selected merchandise hierarchy and it is applicable to the levels: Department, Class, and Subclass.