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.

6

Assortment Period Maintenance Task

The Assortment Period Maintenance task defines the relationship between time (assortment periods) and location groupings (clusters), forming the foundation for assortment planning and item flow.

In this task, planners define assortment periods by assigning weeks, associate cluster versions to those periods, and establish receipt timing parameters. This alignment ensures that assortments are planned and executed consistently across locations and time.

Create the Assortment Maintenance Segment

To create the Assortment Period Maintenance segment:

1. Click Assortment Services in the Task menu.

2. Select the Planning Administration activity.

3. Select the Assortment Period Maintenance task. The Create New Plan dialog opens.

4. Click Create New Plan .

5. Enter a plan label and click OK .

6. In Select Product , choose one or more departments and click Finish .

Step: Assortment Period Maintenance

This step defines assortment periods, assigns cluster versions, and establishes receipt timing parameters. These decisions align clusters (locations) with time (assortment periods), enabling consistent assortment planning and execution. It is recommended that departments planned together share the same assortment periods and flows to ensure merchandising alignment across planning.

Tab and Views in this Step:
  • Assortment Period Maintenance Tab:

    • Define Assortment Periods View

    • Review Assortment Periods by Calendar View

    • Review Clusters by Location View

    • Bell, Trend and Slow Item Curves View

Application Actions

Assign Cluster

Copies the selected cluster version to the assortment period and populates the Cluster Version measure with the assigned version for reference in planning.

Approve

Step: Assortment Period Maintenance

Validates and commits the assortment period configuration to the database, ensuring no unresolved alerts (such as overlapping weeks) exist before saving.

Assortment Period Maintenance Tab

This tab is used to define assortment periods, assign cluster versions, and review planning alignment across time and locations.

Define Assortment Periods View

The Define Assort Periods view is used to create and maintain assortment periods by assigning weeks, defining receipt timing, and associating cluster versions.

The steps to complete this process:

1. Enter a value in Define Label to name the assortment period.

This label will be shown in the Assortment Services wizards when selecting Assortment Periods.

2. Enter a value in Start Date to define the beginning of the period.

The Start Week measure will populate.

3. Enter a value in Duration (Weeks) to define the length of the period.

The End Week measure will populate.

4. Enter a value in Maximum Initial Receipt Lead Time to define the number of weeks available for planning receipts prior to the start of the assortment period.

This setting establishes the allowable window for early receipts as defined by week outside of the Assortment Period definition. Within the Item Flow segment, planners can specify the exact receipt week within this window, while Admin Lead Time (Weeks) determines the timing of receipts within the calculation logic.

5. Select a value in Assign Cluster to assign a cluster version.

6. Review alerts:

  • Cluster Not Assigned

Triggers when one assortment period does not have a cluster assigned.

  • Invalid Definition

Triggers when required fields are missing or invalid (label, start date, positive duration) or when time periods overlap.

7. Execute the Assign Cluster application action to copy the selected cluster version to the assortment period.

8. Execute the Approve application action to validate and commit the assortment period.

Note

Weeks cannot overlap between assortment periods. Overlaps generate alerts that must be resolved before committing data.


In this guide