Considering Season

Seasons form an important aspect in the product life cycle for the fashion industry.

The production of fashion wear is determined or varies qualitatively according to the season for which it is manufactured.

An example of seasons would be summer, winter and others. The reason for such a demarcation of a year's production schedule on the basis of seasonal requirement is understandable, as the demand of fashion wear is almost always seasonal. For instance, woolen garments are in demand only in winter.

In the fashion industry, a season belongs to a season year and can have collections associated with it. Collections can in turn have themes associated with them. Every season has a validity period.

Customizing is necessary to define the season types and activate the season determination within sales and purchasing documents

The Season workbench is used to create and manage seasons. You use the workbench to not only define, change, and delete season year, season, collection, and theme, but also to maintain sales and purchasing views for seasons and assign materials to the relevant seasons.

The season workbench offers you the following three different views:

• Full screen view
• Tree view
• Grid view

Season maintenance can be carried out using any one of the views.

All processes are controlled by season, collection and theme. Each fashion product can be assigned to one or multiple seasons and the season master data determines the purchasing and sales period of the product. Purchasing and sales documents will always carry the season information and also inventory can be split by season if desired.

The seasons workbench can be accessed via the transaction FSH_SWB.

You can create a new season with a season year, and then assign collections and themes to that season. A new season can be created using either the create option or the copy option. In case of creating new season, you create a season by providing new season information. In case of the copy function, you can copy season information from an existing season.

Assign Season to materials: A season can be assigned to materials based on the material number and the merchandise category. You can assign a material to a season at any one the following three levels:

• Season year/Season
• Collection
• Theme

A material can be assigned to several seasons at the same time.

Maintaining Sales and Purchasing Views: You can assign season year, season, collection, and theme to sales and purchasing views. You can specify the order, delivery, and sales windows for sales, and the order and delivery windows for purchasing.

Within transaction FSH_SWB the purchasing view is maintained

Within transaction FSH_SWB materials can also be assigned to several seasons. The figure shows material assignments.

Within transaction FSH_SWB the purchasing view is displayed.

Within transaction FSH_SWB the Sales view is maintained.

It is possible to configure in customizing a season determination for sales documents, purchase order documents and stock transport orders. The dates (purchasing and sales) from the season workbench are checked and an automatic season determination is possible within the documents. Customizing is available to configure Warning, error or info messages; in the case no season is found.

Mass Season Processing is carried out using transaction FSH_SRED.

You can use this report to carry out mass season processing. Mass season processing refers to the following activities that can be carried out for multiple purchase orders, sales orders, and stock transport orders:

• Re-determine seasons
• Manually assign seasons

Even though these activities can be carried out for multiple documents at a time, you can carry out only one activity at a time. That is, you can either re-determine seasons or manually assign seasons. You cannot carry out both activities at the same time.

You can only run this report for documents that you have already created, irrespective of whether the season has already been determined for that document.