SAP Fashion Management PDF

SAP Fashion Management
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_fms10/helpdata/EN/4B/EA9E52C406215CE10000000A44538D/frameset.htm
Created on July 14, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 68
Table of content
1 SAP Fashion Management
1.1 What's New
1.2 Segmentation (LO-SGT)
1.3 Enhancements to Retail
1.4 Enhancements to Fashion Master Data
1.5 Cross-Application Components
1.5.1 Season
1.5.1.1 Season Workbench
1.5.2 Characteristic Value Conversion
1.5.3 Split Valuation
1.5.4 Value-Added Services
1.5.4.1 Value-Added Service Articles
1.5.4.2 Controlling Value-Added Services With Conditions
1.5.4.3 Value-Added Services in Delivery Documents
1.6 Materials Management
1.6.1 Segmentation: Purchasing Documents
1.6.2 Determination of Seasons in Purchasing Documents
1.6.2.1 Determination of Seasons in Purchase Orders
1.6.2.2 Determination of Seasons in Stock Transport Order
1.6.2.3 Determination of Seasons During Goods Movement
1.6.3 Value-Added Services in Purchasing Documents
1.6.4 Characteristic Value Conversion in Purchasing Documents
1.6.5 Stock Overview for Generic Article
1.6.5.1 Viewing Stock Overview for Generic Article
1.6.5.1.1 Example: Stock Overview of Generic Article
1.6.6 Split Valuation in Purchasing Documents
1.6.7 Stock Transport Order for Articles with Segmentation
1.6.8 Reporting in Purchasing
1.7 Sales and Distribution
1.7.1 Segmentation in Sales Documents
1.7.2 Characteristic Value Conversion in Sales Documents
1.7.3 Determination of Seasons in Sales Documents
1.7.4 Value-Added Services in Sales Documents
1.7.5 Mass Season Processing
1.7.6 Special Business Processes in Sales
1.7.6.1 Consignment Processing
1.7.6.2 Third-Party Order (TPO) Processing
1.7.6.3 Purchase-to-Order (PTO) Procurement
1.8 Production Planning and Control
1.8.1 Planned Independent Requirements (PIRs) with Segmentation
1.8.1.1 Creating Planned Independent Requirements for Articles with Segm
1.8.2 Materials Requirement Planning
1.9 Order Allocation Run
1.9.1 Steps in Order Allocation Run
1.9.1.1 Selection Rules
1.9.1.1.1 Dynamic Open to Delivery Date Adjustment
1.9.1.2 Requirement Filter
1.9.1.3 Requirement Grouping
1.9.1.3.1 General Requirements Grouping
1.9.1.4 Requirements and Stock Sorting
1.9.1.5 Allocation
1.9.1.5.1 Allocation Rule
1.9.1.5.1.1 Delivery Scheduling
1.9.1.5.1.1.1 Example: Delivery Scheduling
1.9.1.5.2 Dynamic Stock Prioritization
1.9.1.5.3 Allocation Against Future Receipts
1.9.1.6 Release Rule
1.9.1.6.1 Release Check for Delivery Groups
1.9.1.6.2 Allocating Value-Added Service (VAS) Articles
1.9.1.6.3 Allocating Bill of Material (BOM) Articles
PUBLIC
Page 2 of 68
1.9.1.6.4 Logic to Determine Release Rule

1.9.1.7 Log Rule
1.9.2 Execution of Order Allocation Run
1.9.3 Background Processing (Batch ARun)
1.9.4 Order Allocation Run Workbench
1.9.4.1 Creating Custom Reports in Order Allocation Run Workbench
1.9.4.2 Configuring Levels in Order Allocation Run Workbench
1.9.5 Using Variants in Online and Batch ARun
1.9.6 Stock Protection in Order Allocation Run
1.9.7 Authorizations in Order Allocation Run
1.9.8 Special Order Types
1.9.8.1 Rush Order
1.9.8.2 Consignment Orders
1.9.8.4 Allocation Against SD Contracts
1.9.9 Cross-Applications in Order Allocation Run
1.9.9.1 Changing Sales Orders
1.9.9.2 Changing Stock Transport Orders
1.9.9.3 Changing Purchase Orders
1.9.9.4 Changes During Goods Receipt
1.9.9.5 Changes During Goods Issue
1.9.9.6 Quantities Reserved by Order Allocation Run in MRP
1.9.9.7 Quantities Reserved by Order Allocation Run in ATP
1.10 Mass Maintenance of Fashion Master Data
1.11 Product Number Creation
1.12 Adjusting Screen Sequences in Fashion Management
PUBLIC
Page 3 of 68
1 SAP Fashion Management

Product Information
Product
Release
1.0
Documentation Published
June 2014
Today customers manage their vertical fashion companies as two different business processes design, develop, buy and sell to wholesale customers and to
customers through their own retail channels using two different SAP systems. Both systems use different data models and concepts and are integrated through
data interfaces.
SAP Fashion Management is an integrated solution to bring the processes for vertical fashion companies into one system. This solution enables them to manage
their business processes across one large data system landscape. It also enables the companies in the fashion industry to use the power of in-memory
computing to analyze large data volumes for a fast and accurate overview of products. This results in greater efficiency, quicker time to market, and better
inventory control.
Implementation Considerations
You can implement this solution as an add-on to SAP ERP for SAP Retail. You must install SAP Enhancement Package 7 for SAP ERP 6.0, Support Package
04 on HANA Database.
To use this solution, you must activate the business function FASHION_01 after installing the add-on.
To activate the business function FASHION_01, you must activate the following business functions:
Other Enhancements for SAP Retail (ISR_RETAILSYSTEM)
Retail (EA-RET)
Material Segmentation Across Logistics (LOG_SEGMENTATION)
Integration
The solution is based on the SAP components Materials Management (MM) , Sales and Distribution (SD) , and Logistics - General (LO) .
Features
SAP Fashion Management aims at harmonizing the following processes:
Master data concepts for articles
Planning and Procurement
Inventory Management
ATP or Re-Scheduling and Allocation Run
The solution provides the following features:
Flexible data processing: The solution supports companies to handle accurate end-to-end flow of material across all relevant procurement applications. It
also enables data processing based on the characteristic values such as style, color, size, and season, and other flexible segmentation characteristics
such as seasons, sales channels, and so on.
Segmentation: The solution allows you to categorize materials or articles based on their physical and logical characteristics. For example, color and size are
physical characteristics of a fashion article, quality and country of origin are logical characteristics of a fashion article. Requirement segment is important in
sales, for example in sales orders and planned independent requirements. Stock segments are used for the logical distribution of the existing physical
stock and the future receipts or procurement proposals, such as purchase requisitions.
Multichannel planning: You can forecast future demand and procure supplies for multiple sales channels. You can also manage the demand of different
channels separately, for example retail, wholesale, e-commerce, or franchise, according to the channel-specific processes. MRP on HANA now supports
materials (articles in Retail) with segmentation. For materials with segmentation, the system executes the MRP processes based on the rules defined in the
segmentation strategy. MRP run happens at the variant level of the generic article. As a result, separate documents (purchase requisitions) are created for
each of the variant belonging to the same generic article to fulfill the open requirements at variant level. And the planner or user must spend lot of time
checking or going through multiple documents for variants belonging to the same generic article. You can enable grouping of purchase requisition
functionality, and during the MRP run the system groups the variants belonging to same generic article into a single document based on the certain criteria.
ATP with segmentation: With advanced methods of requirement segmentation and availability check, you can ensure that high priority channels receive
their planned quantities even if their demand is delayed.
Season management: You can define the production of fashion wear according to the season for which it is manufactured. Summer and winter are few
examples of seasons. In the fashion industry, a season belongs to a season year and have collections associated with it. The collections in turn have
themes associated with them. You can define a validity period for every season. The seasons assigned to the articles are used or determined in both the
sales and the purchasing documents. These seasons can then be transferred to the follow-on documents such as, outbound or inbound delivery and billing
document.
Characteristic value conversion: You can represent the value of few characteristics of a fashion article on different scales for different countries or region.
Apart from defining base characteristic values, the feature allows you to define characteristic values in different country scales. You can maintain
characteristic conversion type controls which can be country or region-specific identifiers. You can define the characteristic conversion IDs for an article,
customer or vendor, and a user parameter.
Value added services (VAS): You can request for special labels, packing according to certain criteria, or other special services for their goods. Depending
on the service requested, additional articles or additional personnel/labour or special skills are required. These services increase the value of the finished
goods, which are being delivered. You can handle these services including the costs through value added services in the fashion industry. You can assign
PUBLIC
Page 4 of 68
the information related to different services using conditions. Later, the services are determined in the application documents (sales order, stock transport
order, purchase order). During the special business processes in sales, such as Third Party Order (TPO) and Purchase-to-Order (PTO), the VAS
information is copied to the purchasing documents from the sales documents and you cannot change the values in the purchasing documents.
Order allocation run: The unique situation in the fashion industry necessitates an optimized assignment of existing stock to open requirements (sales orders
and stock transport orders). For example, the allocation run ensures an assignment of the available stock to the open requirements according to your
business requirements when there is a shortage of stock. The allocation run creates a fixed assignment between the requirement records, physical stock
(batch managed or non-batch managed) and future receipts. You can only manually undo this assignment. The allocation run is a process based on rules.
You can use the settings to sort the stock or requirements, release the allocation to decide when each individual requirement should be processed and the
priority.
Constraints
For information about release restrictions for SAP Fashion Management 1.0, see SAP Note 1983386.
1.1 What's New

1.2 Segmentation (LO-SGT)
Businesses compete today in an increasingly customer-oriented market. Therefore, it becomes necessary to streamline internal processes and logistics around
the needs of each market and its unique requirements through appropriate sourcing, planning, and supply of goods to meet market demands.
Some materials are expected to support large volumes of data. Segmentation can be used to order such materials by logically categorizing them based on certain
criteria or characteristics.
For example, in the fashion industry, you can distinguish a fashion material such as a t-shirt based on the size and the color. This t-shirt in a particular size and
color is called a material variant. You can enter a specific item line for a material variant. Using segmentation, you can also order material variants of different
quality levels, for different customer channels, and from different countries of origin.
In material master, you can segment a material using segmentation structure and segmentation strategy.
Implementation Considerations
These functions are a part of the business function Material Segmentation across Logistics (SD, MM, PP, IM, LE) (LOG_SEGMENTATION).
Integration
Segmentation is integrated in the following applications:
LO Material Master
SD Sales
MM Purchasing
You can assign segments to a material using segmentation structure and segmentation strategy in the material master. You can configure these settings for
segmentation in Customizing for Segmentation under
SAP Implementation Guide
Logistics - General .
PUBLIC
Page 5 of 68
Features
There are two types of segments:
Requirement segments
Stock segments
Requirement segments are important for sales documents such as sales orders, planned independent requirements and dependent requirements.
Example
The incoming requirements such as sales orders are divided based on the requested quality - Quality 1, Quality 2, or Quality 3, and by customer channel Store, Wholesale, or E-Commerce.
Stock segments are used for logical distribution of existing and planned stock. Therefore, stock segments are assigned to both the physical stock and
procurement proposals such as planned orders, production orders, purchase requisitions, and purchase orders.
Example
You can divide your stock based on the same criteria as the requirement, that is, by quality - Quality 1, Quality 2, or Quality 3 and by countries of origin India, China, or Germany.
The segments influence the entire logistics chain. You can assign segments to a material using segmentation structure and segmentation strategy in the material
master.
More Information
Segmentation Structure
Segmentation Strategy
1.3 Enhancements to Retail

1.4 Enhancements to Fashion Master Data
SAP Fashion Management has made changes related to master data in the article master to support features related to maintenance of fashion attributes,
seasons, material conversion ID, and order allocation run (ARun). These changes can be broadly divided into changes made to client data and changes made to
site data.
Features
Client Data
Fashion Attributes
You can maintain fashion attributes for an article at the client level. The system allows you to maintain up to three fashion attributes at any time.
The description of these fashion attributes are maintained in the Customizing for Maintain Descriptions of Fashion Attributes under
Guide
Logistics - General SAP Fashion Management . For example, fabric, style, and color can be your fashion attributes.
SAP Implementation
The values of these fashion attributes can be maintained using the report program Maintain Fashion Attributes .
To access this report, on the SAP Easy Access Retailing (transaction W10M ) menu, choose
Fashion Attributes
Fashion Attributes
Maintain
. You can also use the transaction FSH_MG_ATTRI to execute the report.
Fashion attributes can be used to search articles. The attributes maintained for an article also apply to all the variants of the article.
Seasons
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.
A season type helps in determining the listing period of an article. You maintain the default season type to be assigned to a season in the Customizing for
Maintain Default Season Type under
Logistics - General SAP Fashion Management Seasons .
Season Usage
You can maintain Season Usage as one of the Additional data of the article. Based on this, season information is updated in the corresponding sales and
purchase documents.
Season can be assigned to a generic article. This assignment is inherited by the variants of the article. You can also add or change a season for a variant.
You can use one of the following levels at which an article can use season data:
Do not use Season Year/Season
Season Year/Season
Season Year/Season/Collection
Season Year/Season/Collection/Theme
Season Active in Inventory Management and Batch Management
Season active in inventory management indicates season processing is active in inventory management. It stores season, collection, and theme information in
stock tables, batch master and in material movement documents. It also validates the season information in goods movement.
PUBLIC
Page 6 of 68
You have maintained Season Act. IM as one of the Additional data of the article. By selecting the Season Act. IM checkbox, you also make season active in
inventory management option available for sites.
Material Conversion ID
The material conversion ID controls the characteristic value conversion based on individual articles. In addition to material ID, you can also control characteristic
value conversion using user conversion ID and customer/vendor conversion ID. You maintain Mat.Conv. ID for an article.
For more information, see Characteristic Value Conversion.
Site Data
Season Active in Inventory Management and Batch Management
If Season Active in Inventory Management checkbox is selected for an article, that is, at the site level, then batch management becomes mandatory and the
Batch management checkbox in the General control parameters is automatically selected by the system. This will also result in an automatic check to be
carried out on the article. Batch management maintained for an article is copied to its variants.
Season active in inventory management is available at the site level only if has been maintained at the client level, that is, if you have maintained Season Act.
IM as one of the Additional data of the article.
Note
Season Active in IM can also be maintained for the site master. This will be taken into consideration during listing. If it is maintained at the site master level,
the same is adopted by all the relevant sites. Seaon active in inventory management can be maintained at the site level only if is maintained at the client
level.
If you have maintained season active in IM for a variant of a generic article, the same is copied to all the variants of the article in the distribution center (DC).
Also, season active in IM can be changed for a DC in the change mode only if batch is not created for an article in the DC.
Batch management also results in generation of batch numbers in sales and purchasing documents. If you want to generate unique batch numbers during batch
management, you can do so by selecting the Discrete Batch No. checkbox. This checkbox cannot be used on its own. It can only be used in combination with
the Batch Management checkbox. The choice you make for the article is applied to all its variants.
Order Allocation Run (ARun)
Order allocation run (ARun) does optimized assignment of existing stock to open sales order requirements. When there is a stock shortage, for example, the
allocation run ensures an automatic assignment of the available stock to the open requirements according to your business requirements.
Order Allocation Run can also be maintained at the site master level. In case of generic articles, you can either maintain the distribution profile of the article in a
site or ARun, you cannot maintain both at the same time. ARun should always be not relevant for reference CD, reference and non-reference stores.
You can choose to make a variant of a generic article relevant in the Order ARun field. This setting will also apply to all the other variants of the generic article in
that DC. This setting can be made only for variants of an article in a non-referenced DC.
Note
ARun can be maitained only for variants of non-reference DCs. If you have maintained ARun setting for a variant of a generic article, the same is copied to all
the variants of the article in the non-reference DC.
More Information
Season
Characteristic Value Conversion
Order Allocation Run
1.5 Cross-Application Components

1.5.1 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 years 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. So, to ensure that the production lifecycles are aligned with the demand, we have the concept of seasons as an intrinsic framework of
time, on which the production schedule is based.
Features
This function offers the following options:
Relevance of Articles in Seasons

The relevance of an article to a season determines whether the article is planned for a season. Woolen fabric is an example of a seasonal article which is relevant
only for the winters and hence form a part of the production lifecycle for the winter season. But, there are some articles that experience consistent demand
throughout the year, for example, vests, and hence are produced normally without being categorized as an article that is relevant for a particular season.
Determination of Seasons
PUBLIC
Page 7 of 68
There is no fixed method by which a years schedule is demarcated into a number of seasons. You can determine the relevant seasons depending on the kind of
articles produced, the customers discretion and the demand cycles. There can also be a scenario wherein two seasons overlap. For example, there can be an
event like, football season, which creates the demand for apparel associated with the event. You can define this as different season altogether and have specific
merchandise associated with it. Also, this football season can overlap over one or more existing seasons.
Further Classification
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. The presence of these features help in further classification of the offering for a season apart from providing a concept for each
segment of product offering.
The concept of seasons in SAP Fashion Management is seamlessly integrated with the processes of sales and distribution, and purchasing.
You use the Season Workbench (transaction FSH_SWB) to create relevant seasons with season year and the corresponding collections and themes beneath
them. These four characteristics are arranged in a hierarchy as shown in the graphic below, and are the basis for creation of any season attribute.
Note
There is the dependency of an entity in the hierarchy to the one above it. For example, a collection has to be associated to a season and, likewise, a theme
has to be associated to a collection. Hence, a collection or a theme cannot be defined as a stand-alone entity in the hierarchy mentioned above. Also, a
season cannot be created without a season year.
You create these entities to define time frame as the elementary attribute, which indicates its applicability in a year. You can also see the hierarchy through the
user menu and can define the period at any of the three levels. A sales period or a purchasing period, as shown below, defines the time frame within which that
particular entity (season, collection and theme) is valid in the respective application document.
PUBLIC
Page 8 of 68
Activities
Season Processing
You must perform the following activities during the season processing:
1. Create new Season
You must create new seasons that are used in the season processing by using the Season Workbench (transaction FSH_SWB). A season can have one or
more collections and each collection have one or more themes associated with it.
Note
A season cannot be created without a season year.
You can also create a new season by copying data from an existing season. When you try to copy data from an existing season, you have to specify
the target season and season year. The sales and the purchase periods for the new season (target) are calculated and proposed by the system, by
deriving the difference between the Valid From and Valid To dates of the source season and those of the new season (target). You cannot create a
new season using the copy reference functionality without changing the season and season year for the new season. When you use copy reference, in
some cases, the sales or the purchase periods calculated using both the Valid From and Valid To dates might not be logically correct. For example,
the Order Date To date might be earlier than the Order Date From . In such cases, system uses only the Valid From date to calculate sales or
purchase periods.
2. Assign Season to the Fashion Article Master
You must assign the season indicator created above, to the fashion article master. You can assign several seasons to the article master in Basis Data:
Fashion. Before you assign a season to the article master, you have to ensure that the season types are defined in the Customizing activity Maintain
Default Season Type under
SAP Customizing Implementation Guide Logistics - General SAP Fashion Management Seasons
and a default
season type is selected. The periods associated with the default season type are used during listing of the article master. For example, you can define
creation Season, roll-out Season and fading Season as the season types and select Fading Season as the default season type.
3. Create Periods
You can create periods for a season at different levels for sales (sales organization, country, region, customer group, and customer) and purchasing
(purchase organization, purchase group and vendor). You have to assign order window and delivery window while creating periods. Periods can be
maintained at any one of the following levels:
Season year with season
Season year with season and collection
Season year with season, collection and theme
It is specified in which period incoming orders are taken into account and which period is designated for delivery for the articles associated with a season.
Periods can also be maintained when the sales organization or purchase organization details are blank.
Note
You cannot delete a season that has an article associated with it.
1.5.1.1 Season Workbench

Season workbench is a one stop shop to manage seasons. You use this function to not only define, change, and delete season year, season, collection, and
theme, you also use it to assign articles (single articles, generic articles, and structured articles), and maintain sales and purchasing views for seasons.
PUBLIC
Page 9 of 68
Integration
The season workbench is integrated with the sales and purchasing processes.
Features
Multiple Views
The season workbench offers you the following three different views:
Full screen view
Tree view
Grid view
By default, the full screen view is displayed. The full screen view contains the tree view on the left side of the screen and the grid view on the right side of the
screen. You can then choose to display only the tree view or only the grid view using the appropriate icons. Season maintenance can be carried out using any
one of the views.
Create Season Year, Season, Collection, and Theme
You can create a new season with a season year, and then assign collections and themes to that season. A new season can be create using either the create
option or the copy option. In case of create 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.
Note
When you create a season using the copy functionality, the system not only copies season information maintained at the node level of the source season, it
also copies all the season information maintained in the sub nodes. For example, if you copy a season year, the system will automatically copy all the
season, collection, and theme information maintained for that season year.
Assign Season to Articles
A season can be assigned to articles based on the article number and the article group. You can assign an article to a season at any one the following three
levels:
Season year/Season
Collection
Theme
The article assignment is based on the Season Usage maintained in the article master.
You can only assign generic articles, structured articles, and single articles to a season. Season assignment cannot be made at the variant level.
Delete Season Year, Season, Collection, and Theme
You can delete a season year, season, collection, and theme using the delete button. In the tree view, you can right click the relevant season information, and
select Delete Node with subnodes .
Note
If an article is assigned to a season, you cannot delete that season or any of its subnodes.
Maintain 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.
Activities
To launch the season workbench, on the SAP Easy Access Retailing (transaction W10M) screen choose
Seasons
Season
Workbench
You can directly access the season workbench using the transaction FSH_SWB.
1.5.2 Characteristic Value Conversion

A characteristic of a fashion article can be measured using different standards or scales in different countries or geographical regions. For example, a shoe of the
same size is considered size 9 in the UK while it is considered size 10 in the US. Hence, the shoe has both the sizes marked on it. To facilitate this, a
characteristic conversion mechanism is necessary to ensure that on every fashion article, sizes in all the relevant size standards are correctly marked.
Characteristic value conversion only applies to variant creating characteristics that are attached to the article master.
Prerequisites
Use transaction CT04 to define variant creating characteristic. Maintain 2 as the variant creating characteristic relevance indicator. For more information, see
Maintain Segmentation Relevance for Functions
Use transaction WRFCHVAL to maintain base values for the variant creating characteristics.
PUBLIC
Page 10 of 68
Activities
For successful characteristic conversion to take place, you have to first create a conversion logic. This conversion logic defines when the conversion has to take
place and how the system converts each individual value with a specific conversion type based on certain rules.
1. You define a conversion type in the Customizing activity Define Conversion Types under
SAP Customizing Implementation Guide Logistics
General SAP Fashion Management Characteristic Value Conversion . Once you define the conversion type, you then maintain the conversions
specific to variant values in the same customizing activity.
2. Characteristic value conversion can be carried out based on any one of the following criterion:
Article
Customer/vendor
User defined parameter
Item based conversion. For example, sales orders
Hence, based on your requirement, you have to associate conversion ID to with one or more of the above. You do this in the following manner:
Article
In the article master, you have to maintain the Mat. Conv. ID to associate a conversion ID with an article.
Customer/Vendor
In the customer master, under Sales Area Data , maintain the Customer/Vendor ID using the Fashion specific data pushbutton.
User Parameter
Use transaction SU3. In the Parameters tab, maintain a unique value that represents a conversion indicator.
Item Based Conversion
Characteristic value conversion is available in sales and purchase documents. You use the characteristic value conversion pushbutton to carry out
characteristic value conversion of articles in the sales order.
The Item Overview tab can have more than one item. Multiple variant creating characteristics can be associated with an article. Hence, after
applying characteristic value conversion on such articles, the output for these articles would be the concatenation of the converted characteristic
values and displayed in the description column in the sales documents.
On successful conversion, conversion description column is updated. You can then change the conversion description using the Conversion pushbutton.
The conversion description will be changed to the description maintained for the conversion type. You can also manually change the conversion
descriptions at the variant level.
Note
You can maintain conversion of numerical characters. Conversion of textual characteristics is handled based on the descriptions maintained for the
article in the logon language.
3. You then define the conversion indicators and assign conversion types using the Customizing activity Control Conversion Type Determination under
SAP Customizing Implementation Guide Logistics General Fashion in Retail Conversion .
In this Customizing activity, you can specify whether each conversion ID is a material indicator or a customer/vendor indicator. You then specify the
conversion types that can be used based on the combination of material ID, customer/vendor ID and user indicators.
1.5.3 Split Valuation

For certain articles, it is necessary to individually valuate the various stocks in a particular valuation area. If an article is subject to split valuation, then the article
is managed as several partial stock and each partial stock is valuated separately.
Every transaction that is relevant for valuation, be it a goods receipt, goods issue, invoice receipt or physical inventory, is executed at the level of the partial stock.
When you process one of these transactions, you must always specify which partial stock is involved. This is to ensure that only the partial stock in question is
affected by a change in value, the other partial stocks remain unaffected. Along with the partial stock, the total stock is also updated. The calculation of the value of
the total stock results from the total of the stock values and stock quantities of the partial stock. Using split valuation, separate valuation of partial quantities of a
material can be carried out.
Prerequisites
You define whether an article is subject to split valuation on the accounting view of the article master record. You do so using these two fields:
Valuation category specifies the criterion to be used as the basis for differentiating between the various partial stock.
Valuation type specifies an individual characteristic of a partial stock.
Note
Split valuation types can be maintained for an article at that distribution centerl (DC) level only after the fixing of segmentation is done at the DC level. Each
variant and segmentation value combination can have its own valuation type.
You have to enable split valuation for your plants. You do this in the Customizing for Configure Split Valuation under
Materials Management Valuation and Account Assignment Split valuation.
SAP Customizing Implementation Guide
In the the Article Master, enter X as the Valuation Category under Accounting .
Also, enter V as the Price control and a Moving price .
Note
If the article is a generic article, then valuation type has to be filled for all its variants at their corresponding DCs.
Activities
PUBLIC
Page 11 of 68
1. On the SAP Easy Access Retailing menu (transactionW10M), choose
Master Data
Material Data
Material
Create/Change Valuation Type Level
. Alternatively, you can use the transaction SGT_MAINTAIN_VALT.

2. Enter a Material and a Plant .
3. Execute the report.
If you select Generate Accounting View , the entries will be saved in the Material Valuation (MBEW) and the Segmentation Dependent Valuation data
(SGT_MADKA) database tables. If you do not select Generate Accounting View , then the entries will only be saved in the Segmentation Dependent
Valuation data (SGT_MADKA) mapping table database.
If you select Test Run , then split valuation is only simulated, databases are not updated.
Note
You can maintain new valuation data based on the segmentation values for an article or for the variants of the generic article. If no valuation type is assigned to
a variant and a segment combination, such entries will not be stored in the Segmentation Dependent Valuation data (SGT_MADKA) database.
1.5.4 Value-Added Services

Customers frequently request price labels, packing in a certain manner, or any other special services for their ordered fashion articles. These special services
are added to the fashion articles before they are delivered to the customers. Depending on the kind of service and its complexity, you will need articles, expertise,
and/or more personnel to provide the service. These services increase the value of the fashion articles that you will finally deliver to the customer, and are referred
to as value-added services (VAS).
You can map these specific customer requirements, including the costs involved in servicing the requirements, as value-added services (VAS) in the SAP
Fashion Management system. All the different information related to these different services are assigned using conditions and are determined in the application
documents such as sales order, stock transport order, and purchase order later. This way you always have the information about what services which customer
wants and for which fashion articles, during the complete customer-order process. This information can also be added manually in the above documents in some
exceptional scenarios.
During order processing, all the necessary specific services, related information including prices are present in the documents and they would be transferred to
the follow-on documents like outbound delivery, inbound delivery, etc. This is done to help the warehouse personnel to carry out the special tasks needed before
delivering the goods in a timely manner and with precision. Additional ability to maintain the freely definable information fields during the condition maintenance can
be used to pass the necessary information to an external system such as warehouse management, if needed. During special sales business transactions like
third party order (TPO) and purchase-to-order (PTO) processing, VAS information is sent from the sales documents to the purchasing documents. This information
cannot be changed in the purchasing department. This is to ensure that the external vendors would perform the necessary special services, if needed, before
delivering the goods directly to the customer or store.
Note
VAS articles are not enabled for segmentation and seasons.
Integration
VAS is fully integrated with the sales and purchasing processes.
Features
Value-added service in SAP Fashion Management provides you the flexibility to create any number of service types and subservice types. You can create and
define your own maintenance groups for the context FASHION based on the services frequently requested by your customers. You can create maintenance
groups based on service types such as ticketing/labeling, packing, special service and so on.
Note
A customer orders slacks and skirts and wants to receive them packed separately. Since the skirts are made of a more delicate article, you are asked to
pack no more than ten in one carton. For this, you can define a condition maintenance group and specify in the system a packing as the service type and the
maximum number of skirts per carton. In the application, you assign the service type packing to the relevant articles and also specify the maximum number
of skirts for this packing type.
Activities
1. Create service type and subservice type for VAS in the Customizing for Maintain Service Types and Subservice Types under
SAP Customizing
Implementation Guide Logistics - General SAP Fashion Management Value-Added Services (VAS) , you define the service types and the
subservice types..
2. Create the corresponding conditions for the value-added services
3. If necessary, create the articles that are required for certain value-added services. You do this either because you yourself need the articles on a regular
basis, or the customer provides them to you.
Note
Value-added service articles make use of standard article pricing.
1.5.4.1 Value-Added Service Articles

PUBLIC
Page 12 of 68
A customer not only wants you to generally label, package, or otherwise service their goods, but also has very specific instructions that require special articles to
be delivered with the originally ordered goods.
Example
Your customer may want to have a very special label that you find easier to create to their exact specifications and carry it as a article which you enter in this
customer's orders manually.
Especially when goods are delivered directly to a retail store to be offered for sale there, your customer may provide you all necessary articles for labeling,
packing or other services. You are then requested to prepare the order for sale by using those articles.
In this case it may be important for you to know at any time how much of the customers stock is still available at your site so that you can ask for replenishment
when needed. You can do this when you carry such articles as VAS articles in stock. With the proper settings for the availability check, the system not only
controls the stock of the ordered goods, but also that of the VAS articles.
Prerequisites
You have maintained all the Customizing under
Services (VAS) Controls for VAS Determination
Logistics - General
Value-Added
Activities
Value-added service article should be of the article type Additional . This article type can be configured using Material Types (transaction OMS2). This article
types should have 5 Material type for additionals as the Material type ID .
Note
VAS articles are not enabled for segmentation and seasons.
1.5.4.2 Controlling Value-Added Services With Conditions

If some of your customers require value-added services either on a regular or on an article-specific basis, you can define these as conditions. The system checks
whether conditions are present each time you create a sales or purchase document. If there are, the condition records data is copied automatically into the
document. This avoids having to manually enter the same value-added services every time you create a document.
You can put a time limit on each condition if, for example, your customer requires certain value-added services on a seasonal basis.
Prerequisites
You have made the settings in the following Customizing for
Value-Added Services (VAS) Controls for VAS Determination .
Logistics - General
Maintain Field Catalog

Create Condition Tables
Create Access Sequences
Features
Condition Types and Key Combinations
You use condition types to determine whether your condition records for VAS are valid for articles, sales documents, and purchasing documents. You can also
create your own condition type.
You make these settings in the Customizing for Create Condition Types under
Management Value-Added Services (VAS) Controls for VAS Determination .
Logistics - General
SAP Fashion
You can specify the condition types you need for the determination of VAS conditions and you can assign the previously defined access sequences to the
condition types. You use the condition type to define the properties, field combinations and business importance of condition records.
SAP Fashion Management provides the following condition types:
01MG
02MM
03SD
Access sequences with same names are entered for these condition types.
You use these condition types to determine whether your condition records for VAS are valid for articles, sales documents, and purchasing documents. You can
also create your own condition type.
VAS Conditions
In the VAS condition you specify:
the validity period of the condition
the VAS articles you want to use
the key combination and usage
PUBLIC
Page 13 of 68
the VAS details such as the service type and subservice type, article, requirement relevance, procurement relevance, and VAS increment
In addition to the above, in case of sales documents you can specify the customer, customer group, distribution center, division and sales organization and in
case of purchasing documents, you can specify the purchasing organization, purchasing group, and vendor.
You can also use the Create with reference to create a new condition record by making use of an existing condition record as a reference.
You can not only create new conditions, you can also change existing conditions.
Determination Process in Documents
When you create a document, the system checks whether determination is enabled for the document, if enabled, the system checks if VAS condition exists for all
the combinations based on the validity period. If the conditions are found, and if the necessary customizing is maintained, then VAS condition is copied into the
document.
VAS Data in Document, Overview
The overview of the VAS data in the document (sales and purchasing) shows you the VAS data that exists in the document.
Activities
To define VAS conditions, on SAP Easy Access Retailing Menu (transaction W10M), choose
Value-Added Services (VAS)
You can create a condition records based on the condition types. You have the following options:
VAS Condition Maintenance Specific to Article
VAS Condition Maintenance for Sales Documents
VAS Condition Maintenance for Purchasing Documents
1.5.4.3 Value-Added Services in Delivery Documents

Consumption of value-added services (VAS) in delivery documents is necessary for VAS information (data or item) to flow across logistics cycle like order-to-cash
(O2C) or procure-to-pay (P2P) scenarios so that they can be applied to the articles before they are delivered.
Prerequisites
In the Customizing for Define Delivery Types for Fashion Management under
SAP Implementation Guide Logistics - Execution Shipping
Deliveries , you have selected the VAS Active Flag to enable VAS determination option for delivery documents and assigned the Determination
Procedure to the document type created using VAS condition maintenance.
In the Customizing for Define Item Categories for Deliveries in Fashion Management under
SAP Implementation Guide Logistics - Execution
Shipping Deliveries , you maintain the VAS Determination Mode at the item category level.
In the Customizing for Specify Copy Control for Deliveries under
SAP Implementation Guide Logistics - Execution Shipping Copying Control
you specify what data needs to be copied when a delivery document is created with reference to a sales document. In this Customizing, along with other
data, you maintain a VAS related setting to decide whether VAS data needs to be copied from the sales order or fresh determination of VAS has to take
place in the delivery document. Here, you choose between Do not copy VAS Data and Item and Copy VAS Data and Item, No new Determination .
Note
The item category and copy control customizing are the prerequisites only for outbound deliveries. They do not apply to inbound deliveries.
Features
Manual Entry of Value-Added Services in Delivery Documents
In addition to the option of defining value-added services as conditions, you can enter the VAS data manually in a delivery documents for line items. This is
especially useful for a new customer who requests value-added services. Before you define conditions for such a customer, you probably want to see how
business with this customer develops.
The manual entry of VAS data also makes sense for a customer who only requests value-added services occasionally or for one specific delivery, for customers
who require differing services for each document, or want identical ticketing/labeling, packing or other services only for part of the items in the document.
You can maintain manual entries of VAS in the delivery documents using the VAS button. VAS item generation is not possible through manual entry in delivery
documents.
Inbound Delivery
In case of inbound deliveries, VAS data or items are directly copied from purchase orders.
Outbound Delivery
VAS data or items are either copied to an outbound delivery document based on the settings in the customizing for copy control or fresh VAS determination takes
place in the system based on the VAS conditions maintained.
The following are the possible scenarios:
When VAS data is not copied from preceding sales documents, and if the VAS Active Flag in order type is not maintained, and if the VAS Determination
Mode is not maintained for item categories, then VAS determination will not happen inside the delivery document.
When VAS data is not copied from preceding sales documents, and if the VAS Active Flag in order type is maintained, and if the VAS Determination
Mode is also maintained for item categories, then new VAS determination will happen and the VAS data will be determined in the delivery item. No VAS
item will be generated in the outbound delivery even when Req Relevance is selected in the VAS conditions.
If VAS data or item is copied from preceding sales documents using the copy control customizing, VAS determination does not happen inside the delivery
as copy control customizing has precedence over the order type customizing.
Deletion of VAS Data or Item
If VAS data or item has to be deleted in the dialog mode, you can do so using the VAS pushbutton. If a main item is deleted, then along with the main item, the
PUBLIC
Page 14 of 68
corresponding VAS items are also deleted.
1.6 Materials Management

Materials Management in the SAP Fashion Management system is a comprehensive solution for mapping logistical processes in the fashion industry. MRP ,
Purchasing , Goods Receipt , Inventory Management , and Invoice Verification are tools in Materials Management that support you during the entire
procurement process and in inventory management.
You can procure and manage articles at the level of segmentation during the entire procurement process. Reports and screens have been adjusted and master
data has been enhanced so that you can manage articles with characteristics (such as sizes and colors) and segmentation (such as various qualities and country
of origin).
In addition, the following features are available in the procurement process and inventory management:
Seasonal procurement
Characteristic value conversion
Value added services
1.6.1 Segmentation: Purchasing Documents

Segmentation allows you to logically segment articles based on certain attributes, for example, Quality or Customer segment . When you use articles with
segmentation, you can also process quantities and conditions in purchasing documents for the individual stock segments of the variants.
For more information about processing of purchasing documents in the standard ERP system, see Purchasing (MM-PUR).
Prerequisites
You have done the following:
Created characteristics for segmentation using transaction CT04
Defined the segmentation structure in Customizing for
SGTS
Defined the segmentation strategy in Customizing for
SGTC
Logistics General
Logistics General
Segmentation
Segmentation
Define Segmentation Structures

Define Segmentation Strategies
or using transaction
or using transaction
Created articles and assigned a segmentation strategy in the Basic Data: Fashion tab of the article master (using transaction MM41)
Features
To procure articles with segmentation, the system allows you to maintain data in the purchasing documents for the corresponding stock segment. You can
maintain stock segment for the following articles in the purchasing documents:
Single article
Generic article
You can manually enter the stock segment or the system copies from various sources such as other purchasing documents, or the system determines
during MRP. The stock segment you select for a generic article is copied to all the variants. You can also change the stock segment for one or more
variants. However, the new stock segment must be valid for the generic article. In addition, the segmentation structure for all the variants is the same that is
assigned for the generic article.
Structured article
The stock segment you select for the structured article at the header level is not copied to its components. When you process these articles in the
purchasing documents, the system only considers the stock segment assigned at the header level. If the components have different stock segments, they
are not displayed and considered for processing. The system uses the BAdI BADI_SGT_DET_STRUC_ART, if you have defined the BOM explosion for the
structured article during goods receipt in Customizing for
Logistics General Material Master Retail-Specific Settings
Articles
Structured Material in Logistics Process . The BAdI defines the mapping of segments to the components.
Settings for Structured
The system does not allow you to enter or maintain stock segment for an article when one of the following is true:
Article is not relevant for segmentation
Plant is not relevant for segmentation
Article is relevant for segmentation but segmentation strategy and segmentation structure are not assigned and fixed for the article
Scope in the segmentation strategy is defined as Only Requirement Segments Maintained
More Information
Segmentation (LO-SGT)
1.6.2 Determination of Seasons in Purchasing Documents

You manufacture fashion wear according to the season in which you want to sell it. In purchasing documents, the system determines season at the document level
and displays the details at the item level. In documents such as purchase order and stock transport order, the system determines season based on the season
assignment in the article master and the settings in the following Customizing activities:
Maintain Purchasing Document Types for Fashion Management
Maintain Purchase Order Types per Purchasing Area for Fashion Management
Maintain Stock Transport Order Types per Purchasing Area for Fashion Mgmt
PUBLIC
Page 15 of 68
Whenever you mention the supplying plant, the system considers the sales periods for season determination.
Prerequisites
You must have done the following settings for successful season determination:
You have assigned a season to the article in the article master. For more information, see Season Workbench.
You have set the order dates and the delivery dates so that they are within the date range you have specified in the season master data.
You have maintained the season determination process in the following customizing activities under
Materials Management Purchasing
Order
Maintain Purchasing Document Types for Fashion Management
Maintain Purchase Order Types per Purchasing Area for Fashion Management
Maintain Stock Transport Order Types per Purchasing Area for Fashion Mgmt
Purchase
Features
The system validates the information regarding season, collection, and theme during goods movement. When you create invoice verification with reference to
purchase order, the system copies the season information for the article from the reference purchase order.
In the following documents, the system copies the season information from the reference document, such as purchase order:
Inbound delivery
Invoice verification
In the following documents, the system determines season based on the batches assigned or determined for an article and only if you select Season Act. IM
option in the article master:
Physical inventory
Correction postings
Transfer postings
Batch master
Stock overview
Season Determination in Manually Created Documents

When you enter a generic article and delivery date in purchasing documents such as purchase order, the system automatically determines the relevant season
for the article. However, if there is more than one valid season, you can select a different season. After you select the season, it becomes the proposed season for
all variants in the document having the same combination of season and delivery date.
If you change the season, the collection, or the theme in a document, the system triggers a new season determination. If the new season data is not valid, the
system displays a message and you can choose a different set of valid seasons, collections, and themes.
If you change a delivery date, the system checks for the corresponding season, collection, and theme and automatically determines the best match for the
season.
Season Determination in Follow-on Documents

If you generate an inbound delivery with reference to a purchase order, the system copies the season, the collection, and the theme from purchase order. You
cannot change the season in inbound delivery. However, you can view the list of valid seasons.
Mass Season Processing

For more information about mass season processing, see Mass Season Processing
More Information
Season
1.6.2.1 Determination of Seasons in Purchase Orders

In purchase orders, for articles with season, the system determines season based on the Customizing activity Maintain Purchase Order Types per Purchasing
Area for Fashion Management and the season validity periods for purchasing. The season information is displayed at the item level.
Features
When you create a purchase order for an article with season, the system determines season based on the customizing and the following information:
The system copies the season information from the reference document, such as purchase order, into the following documents:
Order date
Document type
Vendor
Purchase organization
Purchase group
Delivery date
Article
For an article with season, the system displays a message based on the message type you maintain in the customizing, if you do not assign a valid season in
PUBLIC
Page 16 of 68
the purchase order. If the message type is an error, you cannot save the document.
You can manually change the seasons for an article in the purchase order. The new season you choose is validated with the delivery date, the order date, and the
season validity period. If you change the purchase organization, the purchase group, the vendor, the order date, or the delivery date, the system redetermines the
season.
You can assign seasons for articles in the purchase order based on the seasons you maintained in the article master, if the following settings are true:
You have not set up season determination for the document type in Customizing for
Management
The article is relevant for season
Maintain Purchase Order Types per Purchasing Area for Fashion
If the number of seasons you maintained for the article in the article master is greater than one, you can filter seasons based on a certain period (for example, list
the seasons maintained in the last two years) using the user parameter FSH_SESN_YEAR.
Example
Example 1
Customizing for Maintain Purchase Order Types per Purchasing Area for Fashion Management
Purchase Group
8000
Season Processing
003
Message Type
Season Determination
P Check at item level
S Specific Search
Season Periods maintained at the Vendor level

Season Year
Season
2013
Purchase
organization
8000
Purchase Group
8000
Delivery Date From
VEND_5000
01.11.2012
Season
2013
0001
Delivery Date To
28.02.2013
Order Date From
01.01.2012
Collection
SW2
Purchase Group
Theme
001
Vendor
003
Season Year
Purchase
organization
Collection
SW1
Delivery Date From
003
01.11.2012
28.02.2013
Theme
002
Vendor
Order Date To
0001
Delivery Date To
28.02.2013
Order Date From
01.01.2012
Order Date To
28.02.2013
Season information maintained for the article SHIRT_T

Season Year
Season
2013
Collection
SW1
Season Year
001
Season
2013
Theme
0001
Collection
SW2
Theme
002
0002
Purchase order
Vendor
VEND_5000
Article
Purchase Organization
SHIRT_T
8000
Purchase Group
003
Order Creation Date

28.02.2012
Requested Del. Date

01.12.2012
The system determines the following season for the article in the purchase order based on the specific match with Purchase Organization , Purchase Group ,
and Vendor .
Season Year
Season
2013
SW1
Collection
Theme
001
0001
Example 2
Customizing for Maintain Purchase Order Types per Purchasing Area for Fashion Management
8000
Purchase Group
003
Season Processing
Message Type
G Generic Search
Season Periods maintained at the Vendor level

Season Year
2013
Season
SW1
Collection
001
PUBLIC
Theme
0001
Page 17 of 68
Purchase
Purchase Group
Vendor
Delivery Date From
Delivery Date To
Order Date From
Order Date To
organization
8000
003
VEND_5000
Season Year
01.11.2012
Season
2013
Purchase Group
8000
01.01.2012
Collection
SW2
Purchase
organization
28.02.2013
Theme
002
Vendor
Delivery Date From
003
01.11.2012
28.02.2013
0001
Delivery Date To
28.02.2013
Order Date From
01.01.2012
Order Date To
28.02.2013
Season information maintained for the article SHIRT_T

Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
Purchase order
Vendor
VEND_5000
Article
Purchase Organization
SHIRT_T
800
Purchase Group
003
Order Creation Date

28.02.2012
Requested Del. Date

01.12.2012
The system determines the following season for the article in the purchase order based on the generic match with Purchase Organization , Purchase Group ,
and Vendor .
Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
The best match season information (in this example, SW1) is populated in the season fields of the purchase document. However, you can select one of the
seasons from the list.
1.6.2.2 Determination of Seasons in Stock Transport Order

In stock transport orders, for articles with season, the system determines a season based on the following:
The Customizing activity Maintain Stock Transport Order Types per Purchasing Area for Fashion Mgmt
The season you have assigned to an article
The season validity periods for sales
The system displays the season information at the item level.
Features
When you create a stock transport order for an article with season, the system determines the season based on the customizing and the following information:
Order date
Document type
Receiving plant
Sales organization
Distribution center
Division
Delivery date
If you do not assign a valid season in the stock transport order for an article with season, the system displays a message based on the message type you
maintained in the customizing. If the message type is an error, the system does not save the document.
You can manually change the season for an article in the stock transport order. The system validates the new season you selected with the delivery date, the
order date, and the season validity period for sales. If you change the receiving plant, the order date, or the delivery date, the system redetermines the season.
The system proposes a delivery date in the stock transport order only if you enable the delivery date proposal option in the Customizing for sales documents.
Example
Example 1
Customizing for Maintain Stock Transport Order Types per Purchasing Area for Fashion Mgmt
Sales organization
8000
Distribution Center
003
Division
51
Season Processing
Message Type
S Specific Search
Season Periods maintained at the Customer level
PUBLIC
Page 18 of 68
Season Year
Season
2013
Collection
SW1
Sales
Distribution
organization
Center
5020
Country
Region
Customer
US
Season Year
NY
01
Customer
CUS01
Season
2013
Distribution
Center
Delivery Date
Order Date
From
To
From
01.11.2012
28.02.2013
Region
US
Customer
Group
NY
01.01.2012
Order Date To
28.02.2013
Theme
002
Country
01
Delivery Date
Collection
SW2
5020
0001
Group
01
Sales
organization
Theme
001
0001
Customer
Delivery Date
From
01
01.11.2012
Delivery Date
To
28.02.2013
Order Date
From
01.01.2012
Order Date To
28.02.2013
Season information maintained for the Article SHIRT_T

Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
Stock Transport Order

Customer
Article
CUS01
Sales Organization
SHIRT_T
Distribution Center
5020
Customer
01
Customer Group
CUS01
Division
Order Creation Date
51
28.02.2012
Region
01
Requested Del. Date

01.12.2012
Country
NY
US
Note
The customer CUS01 is a plant.
The following season is determined for the article in the stock transport order based on the specific match with Sales Organization , Country , Region , Customer
Group , and Customer .
Season Year
Season
2013
Collection
SW1
Theme
001
0001
Example 2
Customizing for Maintain Stock Transport Order Types per Purchasing Area for Fashion Mgmt
Sales organization
8000
Distribution Center
Division
003
Season Processing
51
Message Type
G Generic Search
Season Periods maintained at the Customer level

Season Year
Season
2013
Sales
organization
5020
Distribution
Center
01
Country
NY
Customer
Group
01
Season
2013
Distribution
organization
Center
01
Country
Customer
CUS01
Delivery Date
From
01.11.2012
Delivery Date
To
28.02.2013
Customer
Customer
Group
NY
01
Order Date
From
01.01.2012
Order Date To
28.02.2013
Theme
002
Region
US
0001
Collection
SW2
Sales
Theme
001
Region
US
Season Year
5020
Collection
SW1
0001
Delivery Date
Delivery Date
Order Date
From
To
From
01.11.2012
28.02.2013
01.01.2012
Order Date To
28.02.2013
Season information maintained for the Article SHIRT_T

Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
PUBLIC
Page 19 of 68
Stock Transport Order

Customer
Article
CUS01
Sales Organization
SHIRT_T
Customer
5020
Customer Group
CUS01
01
Distribution Center
01
Division
51
Region
NY
Order Creation Date

28.02.2012
Requested Del. Date

01.12.2012
Country
US
Note
The customer CUS01 is a plant.
The following season is determined for the article in the stock transport order based on the Generic search criteria:
Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
The best match season information (in this example, SW1 ) is populated in the season fields of the stock transport order document. However, you can select one
of the seasons from the list.
1.6.2.3 Determination of Seasons During Goods Movement

When you create a goods receipt or a goods issue with a reference (for example, purchase orders), the system copies the season information from the reference
documents. You cannot change the season assignment.
If you activate the season processing option for inventory management (by selecting Season Act IM in the article master) and do not maintain season
information in the reference documents, then goods movement is not possible.
If you do not activate the season processing option for inventory management, then season is not mandatory for goods movement. In addition, if the reference
documents contain season information, then the system does not validate season information.
If you activate season processing for inventory management for the article and the distribution center (DC), and do not maintain season information in the
reference documents, then goods movement is not possible.
If you activate season processing in inventory management for article but DC is not relevant for season, then season is not mandatory for goods movement.
When you create a goods receipt or a goods issue without any reference, you can assign valid seasons to the article based on the seasons you maintained for the
article in the article master.
Example
Article
Season IM Act
Shirt1
Article
DC1
DC2
Shirt2
For the article Shirt1 in DC1 , season is mandatory for goods movement.
For the article Shirt1 in DC2 , season is not mandatory for goods movement.
For the article Shirt2 , season is not mandatory for goods movement.
1.6.3 Value-Added Services in Purchasing Documents

Consumption of value-added services (VAS) in purchasing documents is necessary to perform or add special service or expertise before the original goods are
procured.
Prerequisites
In the Customizing for Maintain Purchasing Document Types for Fashion Management under
SAP Implementation Guide Materials Management
Purchasing Purchase Order , you have selected the VAS Active Flag to enable VAS determination option for purchase documents and assigned the
Determination Procedure to the document type created using VAS condition maintenance.
You make the following VAS setting in vendor master:
1. Execute transaction XK01 or transaction XK02.
Create Vendor: Address screen or Change Vendor: Address screen is displayed
2. Enter the mandatory fields (including purchasing area)
3. Choose Fashion specific data pushbutton
4. Enter the VAS Determination Mode
Note
In the case of purchase documents, check for the VAS determination option is first carried at the document level, followed by a check at the vendor
master level.
PUBLIC
Page 20 of 68
Features
Determination of VAS in Purchase Documents Using Conditions
VAS items can be determined in purchase documents using conditions. VAS data can also be manually entered in purchase documents.
Manual Entry of VAS in Purchase Documents
In addition to the option of defining value-added services as conditions, you can enter the VAS data manually in a purchase document. This is especially useful for
a new customer who requests value-added services. Before you define conditions for such a customer, you probably want to see how business with this customer
develops.
You can maintain manual entries of VAS in the purchase documents using the VAS pushbutton. Alternatively, in the Go To menu, select
Value-Added
Service VAS Details . Based on the VAS determination mode, VAS consumption in the document will be triggered. The VAS Determination Mode has
impact on the VAS determination and VAS item generation during the consumption of VAS in purchase documents.
Redetermination of VAS Data
You can redetermine VAS data if you change the delivery date, item category, or any other key field that is used in determination of VAS condition records.
Overview of the VAS Data in Purchase Documents
For a quick overview of which value-added services exist in the purchase document at the header or the item level, you can call up the overview display. On the
purchase document screen, in the Go To menu, select
Value-Added Service VAS Data in Document
If you wish to check the VAS details overview of multiple purchasing documents, on the SAP Easy Access Retailing menu (transaction W10M), choose
Fashion Management
SAP
VAS Details Overview in Purchasing Documents

VAS Data from BAPIs
VAS details, including Items, can be sent through BAPIs from external systems for purchase order processing.
1.6.4 Characteristic Value Conversion in Purchasing Documents

You can define different characteristics, for example color, size, for a fashion article. Some characteristics of a fashion article can be measured using different
standards, or scaled in different countries or geographical regions. For example, size is one of the characteristics and you can define different values to it. The
same shoe can be size 9 in the United Kingdom and size 10 in the United States. Therefore, the shoe has both sizes marked on it. To facilitate this, a conversion
mechanism is necessary to ensure that for every fashion article, sizes in all the relevant size standards are correctly marked. Characteristic value conversion only
applies to variant creating characteristics that are attached to the article master.
Prerequisites
You have set the user parameter FSH_NO_SIZE_CONV = to carry out the characteristic value conversion process in the purchasing documents.
You have defined a conversion type in Customizing for Define Conversion Types under
Logistics General SAP Fashion Management
Characteristic Value Conversion .
You have defined the conversion indicators and assigned the conversion types in Customizing for Control Conversion Type Determination under
Logistics General SAP Fashion Management Characteristic Value Conversion .
You have assigned the conversion type to the following:
Article in the article master ( Basic data: Fashion tab in the transaction MM01)
Customer in the customer master ( Sales data screen in the transaction XD01)
Vendor in the vendor master ( Purchasing Data screen in the transaction XK01)
Features
The system converts the characteristic values in the purchasing documents based on the conversion defined for the article, the vendor, the customer, or the user
parameter (FSH_SC_USR) setting. The system converts the characteristic value for the selected items in the document or for the entire document.
In the document based conversion type, the system converts the characteristic value for all the items in the document. The system considers the
conversion IDs you define for the customer, the vendor, and the user parameter setting.
In the item based conversion type, the system converts the characteristic value for the selected items in the document only if the user parameter
FSH_SC_NO_AUTO_CONV is set to X ( Item-Based Conversion ).
You must associate a conversion ID with the purchasing document. You use the Characteristic Value Conversion pushbutton to convert the characteristic values
of the articles. The system carries out the characteristic value conversion in the following purchasing documents:
Only item based conversion
Item based and document based conversion
Inbound delivery
Purchase order
Purchase requisition
Contracts
Goods movement
Stock transfer order
Stock overview
Invoice verification
PUBLIC
Page 21 of 68
The Item List tab or the Delivery Schedule tab can have more than one item. The variants of a generic article have a short text representing the variant
characteristic values in a concatenated form. Depending on the item based conversion or the document based conversion, the system converts the characteristic
values of the variants using the determined conversion ID. The conversion also happens in the variant matrix. The conversion is applicable only for the new
variant matrix with the user parameter WMMB_MATRIX_ALV. After successful conversion, the system updates the short text with the conversion description.
Note
After conversion, the system does not display the description for generic articles and single articles. It only displays the description for the variants of an
article. When you save the data after conversion, the system does not save the conversion description in the system database and it is only for display
purpose.
Example
Article description: Tshirt
The following are the short descriptions for the variants of the article Tshirt:
Tshirt, Red, 34
Tshirt, Blue, 38
Tshirt, Green, 40
After successful conversion, the short description for the variants of the article Tshirt appears as follows, based on the conversion type:
Tshirt, Red, XS
Tshirt, Blue, S
Tshirt, Green, M
More Information
Characteristic Value Conversion
1.6.5 Stock Overview for Generic Article

The stock overview displays the stock for a particular article at all organizational levels. It also displays quantities of an article held at different storage locations
and/or sites, and the type of stock concerned.
Prerequisites
To view the generic article and its variants in the stock overview, ensure that you have set the user parameter WGEN_VAR.
Features
To display the stock data for a generic article and its assigned variants, you have the following options in the stock overview:
Site Group
Site
Storage Location
Special Stock
Batch
Segment-Based Batch
Season-Based Batch
If you provide a generic article, you can view the generic article and its variants in the result screen. If you provide one or more variants, you can view the generic
article and the selected variant in the result screen.
Generic Article > Variant > Site > Storage Location
1.6.5.1 Viewing Stock Overview for Generic Article

Procedure
1. Goto transaction RWBE.
2. In the Stock Overview screen, enter the generic article or merchandise category or stock segment.
3. Choose the List Display tab.
4. In the List as section, choose Tree Structure . By selecting this option, you can view the stock in a tree structure. In the Display Levels section, by
default, the Base Site Group , Site , and Storage Location are selected.
5. To view the stock of the generic article at other levels, choose Special Stock , Batch , Segment-Based Batch or Season-Based Batch .
Note
If you do not select the Batch option, the system displays the stock only at the storage location level for the article. If you do not select the Storage Location
option and select only the Batch option, the Storage Location and site details are automatically selected.
PUBLIC
Page 22 of 68
Result
Scenario 1
If the user parameter is set
The system...
And you provide generic article or variant in the Stock Overview screen
Displays the cumulative result

Displays the variants
Note
To view special stock details for the variants, select Special Stock option in the
main screen.
If you enter a generic article in the Article Selection section and select Batch in the Display Levels section, the system displays the nodes in a tree structure
in the following sequence:
Generic Article > All Variants > Site > Storage Location > Batch
Note
This is valid only for articles without segment and season. The focus here is to view the articles maintained in batches and not relevant for seasons or
segment.
If you enter a generic article in the Article Selection section and select Segment-Based Batch in the Display Levels section, the system displays the nodes in
a tree structure in the following sequence:
Generic Article > All Variants > Site > Storage Location > Stock Segment > Batch and Season
Note
This is valid only for articles with segment. You can also view the articles without season in this tree structure.
If you enter a generic article in the Article Selection section and select Season-Based Batch in the Display Levels section, the system displays the nodes in
Generic Article > All Variants > Site > Storage Location > Season > Batch and Stock Segment
Note
This is valid only for articles with season and Season Act. IM is activated in article master. You can also view the articles without segmentation in this
tree structure.
If you provide one or more variants, you can view the selected variants along with the generic article. For the selected variants, you can view the stock at Batch ,
Segment-Based Batch , or Season-Based Batch levels based on the selection.
Scenario 2
If the user parameter is not set
The system
And you provide generic article in the Stock Overview screen
Displays the cumulative result

Does not display the variants
Note
To view special stock details for the variants, select Special Stock option in the
main screen.
And you provide a variant in the Stock Overview screen
Displays stock details for the variant

Does not display the stock details for generic article
If you enter a generic article in the Article Selection section and select Batch in the Display Levels section, the system displays the stock details only for the
generic article.
Note
To view the variants and its stock details, go to variant split screen. For a variant, double-click the quantity to view the stock at batch level. The next screen
displays the tree structure for the selected variant in the following sequence:
Generic Article > Variant > Site > Storage Location > Batch
If you enter a generic article in the Article Selection section and select Segment-Based Batch in the Display Levels section, the system displays the nodes in
Generic Article > Variant > Site > Storage Location > Stock Segment > Batch and Season
If you enter a generic article in the Article Selection section and select Season-Based Batch in the Display Levels section, the system displays the nodes in
PUBLIC
Page 23 of 68

Generic Article > Variant > Site > Storage Location > Season > Batch and Stock Segment
If you enter one or more variants, the system displays the stock at Batch , Segment-Based Batch , or Season-Based Batch levels based on the selection.
1.6.5.1.1 Example: Stock Overview of Generic Article

You have maintained an article SHIRT_T of type generic article as follows:
Site
F051
Storage Location
0001
Stock Segment
LOWRET
Batch Number
Season Year
0000000997
2013
Season
Summer
Collection
C1
Theme
T1
In the tree view, the stock is displayed in the following hierarchy, by default:
If you manage the article in batches, you can view the stock based on the batches as follows:
If you manage the article in batches, you can view the batch based on the segment as follows:
If you manage the article in batches, you can view the stock based on Season-Based Batch as follows:
PUBLIC
Page 24 of 68
Note
For articles with segmentation and Scope is Both Stock and Requirement Segment Maintained , batch management is mandatory. When you select the
Batch option, the Storage Location option is automatically selected. The system also displays the stock segment for the article.
1.6.6 Split Valuation in Purchasing Documents

You can use articles that you enable for split valuation in as many different partial stocks as you want. The system uses the split valuation type to apply a split
valuation to a partial stock. The partial stocks refer to the batches or stock segments of articles with segmentation. The system updates the total stock, in addition
to the partial stock. The value calculation of the total stock results from the total of inventory value and inventory quantity of the individual pieces of partial stock
(moving average price).
Prerequisites
You have assigned and fixed a segmentation strategy for an article in the article master using transaction MM41.
You have enabled split valuation for your plants. You do this in Customizing for Configure Split Valuation under
Materials Management Valuation and
Account Assignment Split Valuation .
You have used the characteristic that is relevant for Material Valuation (VAL) as the segment value. You have defined the relevance while creating the
characteristics using transaction CT04.
Features
You can revaluate using transaction SGT_MSC2. To generate account assignment view, use transaction FSH_MAINTAIN_VALT.
More Information
Split Valuation
1.6.7 Stock Transport Order for Articles with Segmentation

Articles relevant for segmentation can be transferred between distribution centers and stores. However, stores are not relevant for segmentation. In such scenarios,
requirement segment can be determined based on the Customizing for
Logistics General Segmentation Define Requirement Segment for Supplying
Plants .
Features
Distribution center relevant for segmentation is supplying to store. The requirement segment for the store is determined in one of the following ways:
Priority 1: Based on the segment value assignment you maintain in the Customizing for
Logistics General Segmentation Define
Requirement Segment for Supplying Plants .
Priority 2: Based on the default stock segment you maintain in the Customizing for
Logistics General Segmentation Define Segmentation
Structures .
Priority 3: If BLANK is not a valid segment and no segment value is found, the system displays an error message.
Distribution center not relevant for segmentation is supplying to store: The article is posted to the store without any segmentation value.
PUBLIC
Page 25 of 68
1.6.8 Reporting in Purchasing

Reports are used to access information from the database, and to list the results based on the selection criteria.
Features
If you have activated the business function FASHION_01, the following reports also display the season values in the result screen:
Purchase orders
Transaction
Description
ME2L
Purchasing Documents per Vendor
ME2M
Purchasing Documents for Material
ME2K
Purchasing Documents per Account Assignment
ME2J
Purchasing Documents per Projects
ME2C
Purchasing Documents for Material Group
ME2B
Purchasing Documents per Requirement Tracking Number
ME2N
Purchasing Documents per Document Number
ME2W
Purchasing Documents per Supplying Plant
More Information
Reporting in Purchasing
1.7 Sales and Distribution

Sales allows the realization of different business transactions based on sales documents stored in the system. When creating a sales order, you can carry out an
availability check to determine whether the required articles of specific colors or sizes are in stock. This also checks whether the stock is sufficient to fill the order
by the expected delivery date. A confirmed delivery date is determined based on the results of the availability check.
PUBLIC
Page 26 of 68
The material requirements planning (MRP) assigns the requirement quantities to the available stock, or creates procurement proposals. For stock that is not
available the internal or external procurement (purchase requests or planned orders) are created.
In addition, in SAP Fashion Management the following features are available in the sales process:
Segmentation
Season management
Characteristic value conversion
Value added services
Order allocation run
Segmentation allows you to categorize articles based on their physical and logical characteristics without the need for defining a unique material number for
articles of different segment values. You segment the articles within the sales process in the sales documents using the requirement segment. In addition, you can
carry out order allocation run for the sales order requirements (if they are within the cancellation period defined in the item) which allow the distribution of the
customer requirements to the existing stock, based on specific rules. If there exists a shortage of stock, the allocation run provides the best possible distribution of
the existing stock. For articles relevant for order allocation run, you must execute order allocation run before you create the Delivery document and the Invoice
document.
1.7.1 Segmentation in Sales Documents

Segmentation is available in sales and distribution (SD). Segmentation at the item level allows you to you to sell articles with different attributes, for example,
quality of the article and its country of origin. To sell articles with segmentation, you can provide data in sales documents using requirement segments.
For more information about processing sales documents in the standard ERP system, see Sales (SD-SLS).
Prerequisites
You have made the following settings:
Segmentation structure and segmentation strategy are maintained in the Customizing for Segmentation under
General
The article is made segmentation relevant in article master
Fix segmentation has been chosen for the corresponding distribution center (DC)
Logistics -
Features
To sell articles with segmentation, the system allows you to maintain data in sales documents for the corresponding requirement segment. You can manually enter
the requirement segment or the system can copy the value from various sources such as other sales documents.
For sales documents such as sales order, inquiry, quotation and contract, you can carry out the following functions:
Specify requirement segment for single articles, structured articles, generic articles and variants.
Change requirement segment for a single articles, structured articles, generic articles and variants.
Note
For an article with segmentation, if you try to save the document without requirement segment values, the document will be saved as an incomplete sales
document. Also, ATP check will not happen if requirement segment values are not maintained for segmentation relevant articles.
For delivery, you can carry out the following functions based on the type of delivery:
Outbound delivery with reference
Requirement segment will be adopted from the preceding sales document and stock segment will be adopted from the batch.
Outbound delivery without reference
Specify the requirement segment and stock segment will be adopted from the batch. There is incompletion log for this type of deliveries and this will be
triggered like sales order when you save segmentation relevant article without specifying requirement segment values.
For billing, requirement segments and stock segments are adopted from preceding sales documents.
When you specify a requirement segment for a generic article, all the variants of that article are updated with the same requirement segment. You can change the
requirement at the variant level. However, if you change the requirement segment for the generic article, the new requirement segment is adopted by all the variant
except for the variants for which the requirement segment has been modified earlier.
Note
You can maintain blank as the segmentation value to be used in combination with a segmentation strategy. In such cases, articles will have blank as
segmentation value in sales documents.
In case of a structured article, you cannot specify requirement segment in case of statistical items.
The behavior of incompletion log and the sales documents created with reference is the same as that in standard SAP ERP.
Note
In case of structure articles statistical items, no incompletion log is displayed even when no requirement segment is specified for the segmentation relevant
article.
Dynamic Filling of Segmentation Values
Sometimes segmentation values are not maintained in segmentation strategy, but are made available as dynamic values, for example, as constant values or as
result of some field values. These dynamic values are determined as segmentation values in runtime during creation of the sales documents.
PUBLIC
Page 27 of 68
Segmentation in Third-party Order (TPO) and Purchase to Order (PTO)

When segmentation relevant articles are entered in sales orders and the corresponding stock segment for these articles in purchase requisition and subsequent
purchasing document is determined based on the rules maintained under Requirement to Stock Conversion while defining segmentation strategy.
Significance of Segmentation Strategy in Non-ARun Relevant Articles in Delivery Documents
When outbound delivery is created for a segmentation relevant article which has been made non-relevant for ARun, the system determines the stock segment
relevant for requirement segment based on the rules maintained under Requirement/Stock Allocation while defining segmentation strategy. In such cases, only
those batches that belong to the stock segment determined above are valid in delivery documents.
Segmentation Values using BAPI and IDoc
Segmentation values of articles can also be enabled using BAPIs and IDoc.
Segmentation Values in Adobe Forms
Segmentation values are also available in the Output Adobe Forms for sales orders, delivery, and billing documents.
More Information
For information about segmentation of sales documents in material master, see the following topics:
Segmentation in Sales Documents
Creation of a Sales Document with Reference
Incompletion Log
1.7.2 Characteristic Value Conversion in Sales Documents

A characteristic of a fashion article can be measured using different standards or scales in different countries or geographical regions. For example, a shoe of the
same size is considered size 9 in the UK while it is considered size 10 in the US. Hence, the shoe has both the sizes marked on it. To facilitate this, a
characteristic conversion mechanism is necessary to ensure that on every fashion article, sizes in all the relevant size standards are correctly marked.
Characteristic value conversion only applies to variant creating characteristics that are attached to the article master.
Prerequisites
For successful character value conversion to take place, you have to first create conversion logic. This conversion logic defines when the conversion has to take
place and how the system converts each individual value with a specific conversion type based on certain rules.
1. You define a conversion type in the Customizing for Define Conversion Types under
SAP Customizing Implementation Guide Logistics General
SAP Fashion Management Characteristic Value Conversion . Once you define the conversion type, you then maintain the conversions specific to
variant values in the same customizing activity.
2. You then define the conversion indicators and assign conversion types using the Customizing for Control Conversion Type Determination under
SAP
Customizing Implementation Guide Logistics General SAP Fashion Management Characteristic Value Conversion . In this customizing activity,
you can specify whether each conversion ID is a material indicator or a customer/vendor indicator. You then specify the conversion types that can be used
based on the combination of material ID, customer/vendor ID and user indicators.
Activities
Characteristic value conversion can be carried out on sales documents. In the case sales documents, you have to associate a conversion ID with the sales
document. You use the Conversion pushbutton in sales documents to carry out characteristic conversion of articles in the sales documents, including delivery
and billing.
The Item Overview tabs can have more than one item. Multiple variant creating characteristics can be associated with an article. Hence, after applying
characteristic value conversion on such articles, the output for these articles would be the concatenation of the converted characteristic values and displayed in
the description column in the sales documents.
You can change the conversion description as many times as you wish using the Conversion pushbutton. You can also manually change the conversion
descriptions.
Note
Characteristic value conversion in sales documents is available for variants. It is not available for single articles and generic articles.
Description post conversion will not be displayed in case of generic articles and single articles. It will only be displayed for the variants of an article.
When you save the data on successful conversion, the conversion description is not saved in the system database if the new description was provided using
the Conversion pushbutton. However, if the description was changed manually by the user, the updated description will saved in the database.
More Information
For characteristic value conversion in article master, see Characteristic Value Conversion.
1.7.3 Determination of Seasons in Sales Documents

You can determine seasons in sales documents at the item level depending on the Customizing maintained at the order type level in Maintain Sales Document
Types per Sales Area for Fashion .
PUBLIC
Page 28 of 68
Prerequisites
The following prerequisites are necessary for successful season determination:
You should have assigned the season to the fashion article master. For more information, see
The order dates and the delivery dates of the sales order items should be within the date range maintained in the Period-Sales in season master data.
You have maintained the sales order types in the Customizing activity Maintain Sales Document Types per Sales Area for Fashion .
You have selected the Season Determination checkbox in the Customizing activity Maintain Fashion-Specific Item Categories for Sales Documents .
Features
There is no fixed method by which a years schedule is demarcated into a number of seasons. You can determine the relevant seasons depending on the kind of
articles produced, the customers discretion and the demand cycles. There can also be a scenario wherein two seasons overlap. For example, there can be an
event like, football season, which creates the demand for apparel associated with the event. You can define this as different season altogether and have specific
merchandise associated with it. Also, this football season can overlap over one or more existing seasons.
Example
In the Customizing activity Maintain Sales Document Types per Sales Area for Fashion , you have maintained the following information:
Sales organization
Distribution Center
Division
Season Processing
5020
01
51
G Generic Search
You can also choose the type of message to be displayed if the valid season is not determined during the season determination process.
You have maintained the following information at the customer level in Period-Sales in season master data:
Season Year
Season
Collection
Theme
2013
SW1
001
0001
Sales
organization
Dist. Center
Country
Region
Customer
Group
Customer
Delivery Date
From
Delivery Date
To
Order Date
From
Order Date To
5020
01
US
NY
01
CUS01
01.11.2012
28.02.2013
01.01.2012
28.02.2013
Order Date To
Season Year
Season
Collection
Theme
2013
SW2
002
0002
Sales
Dist. Center
Country
Region
Customer
organization
5020
Customer
Group
01
US
NY
Delivery Date
Delivery Date
Order Date
From
To
From
01.11.2012
28.02.2013
01.01.2012
28.02.2013
Article SHIRT_T has the following season information

Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
Sales Order
Customer
Article
Sales
Distribution
Division
Organization Center
CUS01
SHIRT_T
5020
01
51
Order
Requested
Creation
Date
Del. Date
28.02.2012
01.12.2012
Customer
Customer
Region
Country
NY
US
group
CUS01
01
The following seasons are determined for the article in the sales order based on the generic search criteria:
Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
SW1 is available in the season fields of the Sales order document. SW2 is also available for selection in the document.
Note
If you have selected Error as the message type, and if the season is not determined even for the one sales document item, then the sales document cannot
be saved. The sales document can be saved only on successful re-determination of the season. However, if you have selected Warning or Information as
the message type, then the sales document is saved even when seasons are not determination.
Example
PUBLIC
Page 29 of 68
In the Customizing activity Maintain Sales Document Types per Sales Area for Fashion , you have maintained the following information:
Sales organization
Distribution Center
Division
Season Processing
5020
01
51
S Specific Search
You can also choose the type of message to be displayed if the valid season is not determined during the season determination process.
You have maintained the following information at the customer level in Period-Sales in season master data:
Season Year
Season
Collection
Theme
2013
SW1
001
0001
Sales
organization
Dist. Center
Country
Region
Customer
Group
Customer
Delivery Date
From
Delivery Date
To
Order Date
From
Order Date To
5020
01
US
NY
01
CUS01
01.11.2012
28.02.2013
01.01.2012
28.02.2013
Season Year
Season
Collection
Theme
2013
SW2
002
0002
Sales
organization
Dist. Center
Country
Region
5020
01
US
NY
Customer
Group
Customer
Delivery Date
From
Delivery Date
To
Order Date
From
Order Date To
01.11.2012
28.02.2013
01.01.2012
28.02.2013
Article SHIRT_T has the following season information

Season Year
Season
Collection
Theme
2013
SW1
001
0001
2013
SW2
002
0002
Sales Order
Customer
Article
Sales
Distribution
Organization Center
Division
Order
Creation
Date
Requested
Del. Date
Customer
Customer
group
Region
Country
CUS01
SHIRT_T
5020
51
28.02.2012
01.12.2012
CUS01
01
NY
US
01
The following season is determined for the article in the sales order based on the specific match with Sales Organization , Country , Region , Customer
Group , and Customer :
Season Year
Season
Collection
Theme
2013
SW1
001
0001
SW1 is available in the season fields of the Sales order document.
Note
Season determination will still take place when sales organization details are blank in Periods-Sales in season master data. The periods are still valid for the
sales organization.
Season determination will take place only if an Item has not been rejected.
If the delivery date is changed, then the season will be re-determined at the item level. However, if a sales document has subsequent documents such as
Delivery or Billing, season will not be re-determined even if the delivery dates are changed.
Copying Seasons in Sales documents

Season data determined for a sales document can be copied to another sales document. For example, you can copy season data from a sales contract to a sales
order. You can do this by making use of Copy Season Data in the Customizing activity Maintain Copy Control for Sales Documents .
Note
Once season data of a sales document is copied to another sales document using the above copy control Customizing, you cannot modify the season data of
both the source and the target sales document if the source and target documents are different types of document. For example, if the source document is
Inquiry and the target document is sales order. However, if you the source and the target documents are of the same type, then the season data of the source
document can be modified. For example, if both the source and the target documents are Inquiry, then the season data of the source Inquiry document can be
modified but the season data of the target Inquiry document cannot be modified.
Season Data using BAPI and IDoc

Season data for an article can also be sent from external systems using BAPIs and IDoc.
1.7.4 Value-Added Services in Sales Documents

PUBLIC
Page 30 of 68
Consumption of value-added services (VAS) in sales documents is necessary to perform or add special service or expertise before the original goods are ordered.
Prerequisites
In the Customizing for Maintain Sales Document Types for Fashion Management under
SAP Implementation Guide Sales and Distribution Sales
Sales Documents
Sales Document Header , you have selected the VAS Active Flag to enable VAS determination option for sales documents and
assigned the Determination Procedure to the document type created using VAS condition maintenance.
You make the following VAS setting in customer master:
1. Execute transaction XD01 or transaction XD02.
Create Customer: General Data screen or Change Customer: General Data screen is displayed
2. Enter the mandatory fields (including sales area)
3. Choose Fashion specific data pushbutton
4. Enter the VAS Determination Mode
You can also maintain the VAS Determination Mode at the item category level in the Customizing for Maintain Item Categories for Fashion Management
under
SAP Implementation Guide Sales and Distribution Sales
Sales Documents
Sales Document Item
Note
In the case of sales documents, check for the VAS determination option is first carried at the document type level, followed by the check at the customer
master level and finally at the item category level.
In the Customizing for Maintain Copy Control for Sales Documents under
SAP Implementation Guide Sales and Distribution Sales , you specify
what data needs to be copied when a sales document is created with reference to another sales document. In this Customizing, along with other data, you
maintain a VAS related setting to decide whether VAS data needs to be copied from the source document to the target document or fresh determination of
VAS has to take place in the target document.
Features
Determination of VAS in Sales Documents Using Conditions
VAS items can be determined in sales documents using conditions. VAS data can also be manually entered in sales documents.
Manual Entry of VAS in Sales Documents
In addition to the option of defining value-added services as conditions, you can enter the VAS data manually in a sales document. This is especially useful for a
new customer who requests value-added services. Before you define conditions for such a customer, you probably want to see how business with this customer
develops.
You can maintain manual entries of VAS in the sales documents using the VAS pushbutton. Alternatively, in the Go To menu, select
Value-Added Service
VAS Details . Based on the VAS determination mode, VAS consumption in the document will be triggered. The VAS Determination Mode has impact on the
VAS determination and VAS item generation during the consumption of VAS in sales documents.
Redetermination of VAS data
You can redetermine VAS data if you change the delivery date, item category, or any other key field that is used in determination of VAS condition records.
Overview of the VAS Data in Sales Documents
For a quick overview of which value-added services exist in the sales document at the header or the item level, you can call up the overview display. On the
sales document screen, in the Go To menu, select
Value-Added Service VAS Data in Document
If you wish to check the VAS details overview of multiple sales documents, on the SAP Easy Access Retailing menu (transaction W10M), choose
Fashion Management
SAP
VAS Details Overview in Sales Documents
Purchase-to-document (PTO) procurement and Third-party document (TPO) processing.

Among the VAS data or items determined through the condition records or manually entered in the sales document, VAS data or items relevant for procurement
are only applicable for PTO and TPO processes. Only VAS data or items relevant for procurement can be transferred to subsequent purchasing documents,
such as purchase requisition and purchase order, in these processes. Other VAS data or items are not relevant for these processes as the vendor will supply the
procurement relevant VAS services to the customer.
VAS Data from BAPIs
VAS details, including Items, can be sent through BAPIs from external systems for sales order processing.
1.7.5 Mass Season Processing

Mass season processing refers to the following activities that can be carried out on multiple purchase orders, sales orders, and stock transport orders:
redetermine seasons
manually assign seasons
Even though the above activities can be carried out on multiple documents at a time, you can carry out only one activity at a time, that is, you can either
redetermine seasons or manually assign seasons. You cannot carry out both the activities at the same time.
Note
PUBLIC
Page 31 of 68
You can run this report only for documents that you have already created, irrespective of whether the season has already been determined or not determined
for that document.
Prerequisites
Season redetermination happens based on the season data that you have maintained in article master along with the customizing for season maintenance for your
document type.
For sales documents, you maintain this in the Customizing activity for Maintain Sales Documents per Sales Area for Fashion Management under
SAP
Customizing Implementation Guide Sales and Distribution Sales
Sales Documents
Sales Document Header .
For purchase documents, you maintain this in the Customizing activities for Maintain Purchase Order Types per Purchase Area for Fashion Management
and Maintain Stock Transport Order Types per Purchase Area for Fashion Mgmt under
SAP Customizing Implementation Guide Materials
Management Purchasing Purchase Order .
Activities
To use mass season processing report, on the SAP Easy Access Retailing (transaction W10M) screen choose
Mass Season Processing
Seasons
You can directly access the report using the transaction FSH_SRED.
For information about the features of report, see the attached report document in the system.
1.7.6 Special Business Processes in Sales

In addition to carrying out routine sales order processing in the SAP Sales and Distribution module, you can also implement more specialized business
processes, such as the processing of third-party business transactions, purchase-to-order transactions, and consignment processing. You can use articles with
segmentation while executing specialized business processes if you activate the business function LOG_SEGMENTATION.
1.7.6.1 Consignment Processing

Consignment goods are those goods that are stored at the customer's premises, but which are still the property of your company. The settlement for these goods is
not required until the customer withdraws them from the consignment stock (also known as special stock). If you use articles with segmentation when you create
orders, the system considers the segment values you entered and saves them. For fashion articles, optionally you can execute Order Allocation Run (ARun) .
When you create an article, you select the Order ARun option in the Logistic DC: Fashion tab to specify that the article is relevant for ARun for a particular
plant.
Process
The following diagram illustrates the steps involved in the consignment process:
If the article is not relevant for ARun, the consignment processing takes place as in the standard SAP ERP system. For more information, see Consignment Stock
Processing.
If the article is relevant for ARun, the system executes ARun during consignment processing. During the consignment processing, the system performs the
following:
1. Automatically executes the immediate allocation run in the background during order creation if the following condition is satisfied:
You assigned the ARun rule (for immediate allocation) to the order type in Customizing for Assign Rule to Order Types under
Logistics General
SAP Fashion Management Order Allocation Run (ARun) Cross-Applications
Sales Document Handling .
2. Automatically creates a delivery when you save the order based on the settings you defined in Customizing for Define Sales Document Type under
Sales and Distribution Sales
Sales Documents
If Immediate delivery = A, the system creates a delivery immediately for the order type.
If Immediate delivery is BLANK, the system only executes the allocation run and you must manually create the delivery for the order type.
Note
If you do not assign ARun rule for immediate allocation and Immediate delivery is BLANK, you must execute the online ARun after saving the order. In
PUBLIC
Page 32 of 68
addition, you must manually create the delivery.

1. Consignment Fill-up
When you fill the consignment stock of the customer using the consignment fill-up document and you use the article that is relevant for ARun, allocation
happens before creating the delivery in addition to the standard procedure.
The following diagram illustrates the consignment fill-up process for articles relevant for ARun:
2. Consignment Issue
When you withdraw the consignment stock during the sales process, you document this procedure by creating a consignment issue (order type KE in the
SAP system).
When you post the goods issue, the system deducts the relevant quantity from the customer's special stock and from your own valuated stock.
The ARun type selects the stock elements based on the rule you define in Customizing for Maintain Rules for Stock Selection under
Logistics
General SAP Fashion Management Order Allocation Run (ARun) Online ARun Selection . For this selection rule, enable consignment stock
and in view segments enable MSKU-KULAB. Both are essential if you want to allocate consignment stock.
The following diagram illustrates the consignment issue process for articles relevant for ARun:
3. Consignment Pick-Up
Customers can return unused consignment stock to your company's warehouse using the consignment pick-up document. If the customer returns your
consignment stock, you document this procedure by creating a consignment pick-up (order type KA in the SAP system).
When you post the goods issue, the system removes the customers special stock for the corresponding quantity and posts it to the normal stock of the
receiving plant. Your total valuated stock remains the same since the returned stock was taken from your own inventory even while it was at the customer's
premises.
Logistics
General SAP Fashion Management Order Allocation Run (ARun) Online ARun Selection . For this selection rule, enable consignment stock
and in view segments enable MSKU-KULAB. Both are essential if you want to allocate consignment stock.
The following diagram illustrates the consignment pick-up process for articles relevant for ARun:
4. Consignment Returns
Customers can return goods that were previously sold from the consignment stock using the consignment returns document. If the customer wants to reset a
consignment issue, you document this procedure by creating a consignment returns (order type KR in the SAP system). The system increases the
customer special stock when you post the goods issue. You must create a credit memo to complete the process.
The following diagram illustrates consignment return:
PUBLIC
Page 33 of 68
Delivery and Billing

In all the above consignment processes, for articles not relevant for ARun, the system determines the stock segment relevant for the requirement segment
(specified in sales order) based on the segmentation strategy you define Requirement/Stock Allocation in Customizing for Define Segmentation Strategies under
Logistics General Segmentation . You can choose one of the batches relevant for the determined stock segment. You can issue the goods from the batch
entered and later create a billing document.
For an article that is relevant for allocation run, the system determines the batch and the corresponding stock segment in the delivery based on the results from
the allocation run. You can issue the goods from the batch entered and later create a billing document.
1.7.6.2 Third-Party Order (TPO) Processing

In third-party order processing, your company does not deliver the article requested by the customer. Instead, you transfer the order to an external vendor, who
sends the articles directly to the customer and bills you.
Sometimes, customers take orders for goods that they do not produce in-house or do not have enough capacity to produce the goods on time. In such cases, you
ask another vendor to deliver the goods to your customer on your behalf.
A purchase requisition is created for each order item. The purchase requisition is assigned directly to the customer order item and cannot therefore satisfy other
requirements. You do this using an account assignment for the created stock elements. These processes always refer to the original document item, which means
that a purchase order item (converted from the purchase requisition) is assigned to a sales order item.
For more information about TPO in the standard ERP system, see Third-Party Order Processing.
Note
The system determines the stock segment for the requirement segment you maintain in the sales order based on the segmentation strategy you define in
Customizing for Requirement to Stock Conversion in Define Segmentation Strategies under
Logistics General Segmentation .
Process
Sales Order
While creating an order, you process third-party orders through the selection (or assignment) of corresponding item categories and schedule line categories. You
use TAS as the default item category. The purchase order type you define in the standard settings for the schedule line category determines that a purchase
requisition with account assignment is automatically created. This happens for each item when you create a sales order. In this case, MRP does not consider
TPO as a requirement.
Goods Receipt
In third-party order processing, a statistical goods receipt is necessary for general verification. Since, the stock is not valuated or the inventory is not increased,
you must carry out a goods receipt.
Billing
You can process order-based based billing for TPO.

You can order a product from one or several vendors for one particular customer. In contrast to mass orders for the general market, the product in the purchase-toorder is especially designed for the customer so that it cannot be sold to other customers.
Example
A customer places an order X1 with a company A. The company A does not manufacture these goods internally. So, they will procure these goods from
company B and then supply it to their customer.
A purchase requisition assigned to the sales order item is created for each order item. The purchase requisition cannot therefore satisfy other requirements. These
processes are processed at item level. Hence, a purchase order item is assigned to a sales order item. For more information about purchase-to-order in the
standard SAP ERP system, see Individual Purchase Orders.
Process
Sales Order
When creating an order, you process purchase-to-orders based on the selection (or assignment) of corresponding item category and schedule line category. You
use TAB as the default item category. You can create or change purchase requisitions and their assignments through the sales order. When you make changes
in the sales order, the system automatically updates the purchase requisitions only if the purchase requisitions are not converted to purchase orders.
Allocation Run
In Purchase-To-Order processing, it is not mandatory to carry out an allocation run. You can also define if the PTO sales orders are considered in order allocation
run. To allocate PTO sales order, you select the Order Allocation Required checkbox in Customizing for Maintain Order Allocation Run for Special Sales
Documents under
Logistics General SAP Fashion Management Order Allocation Run Cross-Applications
Shipping . You can create a delivery
only if you have already executed the allocation.

PUBLIC
Page 34 of 68

You can transfer the data from the forecast or Sales & Operations Planning of the standard SAP system to the SAP Fashion Management system and use it for
the production planning while considering the specific characteristics of the fashion articles. The requirements planning processes uses this data to fulfill the
requirements, such as sales orders, with the existing or planned stock.
The main function of material requirements planning is to guarantee article availability, that is, it is used to procure or produce the requirement quantities on time
both for internal purposes and for sales and distribution. This process involves the monitoring of stocks and, in particular, the automatic creation of procurement
proposals for purchasing and production.
MRP on HANA now supports articles with segmentation.
1.8.1 Planned Independent Requirements (PIRs) with

Segmentation
Planned independent requirements are planned and organized in Demand Management . A planned independent requirement contains one planned quantity and
one date or a number of planned independent requirement schedule lines. That is, one planned quantity split over time according to dates.
For generic article with segmentation, you can maintain separate planned independent requirements for a combination of variant of a generic article, requirement
segment, plant, requirement type, version, requirements plan number, and external requirements plan ID.
More Information
For more information about PIRs in the standard ERP system, see Planned Independent Requirements (PIRs).
1.8.1.1 Creating Planned Independent Requirements for Articles

with Segmentation
Prerequisites
You have created characteristics for segmentation using transaction CT04
You have defined segmentation structures in Customizing for Define Segmentation Structures under
Logistics General
You have defined segmentation strategies in Customizing for Define Segmentation Strategies under
Logistics General
You have created articles and assigned a segmentation strategy in the article master (transaction MM41)
Segmentation
Segmentation
You have selected Plnng with assembly (101) in the Planned Independent Requirements: Internal Number Assignm view to maintain the number range
for the requirement plan ID
You can access this view using transaction OMPP or in Customizing for Define Internal Number Assignment per Reqmts Class under
Production
Production Planning
Demand Management
Planned Independent Requirements
Default Values and Presettings
Procedure
To create planned independent requirements for articles with segmentation, proceed as follows:
1. Go to transaction MD61.
2. Enter the generic article with segmentation in the screen for creating planned independent requirements.
3. Enter the plant and choose Enter .
If you have entered the generic article in step 1, the variants of the generic article are displayed in the Items tab.
4. In the Items tab, you can now assign requirement segment for individual variants.
5. In the Table tab, enter the requirement for the variants of the generic article at the requirement segment level.
In the Sched. Lines tab, the system displays the external requirement plan ID and the requirement segment.
Result
A new requirements plan number (PBDNR) is generated internally for the unique combination of variant of a generic article, requirement segment, plant,
requirement type, version, requirements plan number, and external requirement plan ID.
You can use the external requirements plan ID to select the planned independent requirements for articles with segmentation.
More Information
Planned Independent Requirements (PIRs) with Segmentation
1.8.2 Materials Requirement Planning

The main function of material requirements planning is to guarantee material availability. That is, it is used to procure the requirement quantities on time both for
internal purposes and for sales and distribution. This process involves the monitoring of stocks and, in particular, the automatic creation of procurement proposals
for purchasing.
PUBLIC
Page 35 of 68
The material requirements planning procedure has now been enhanced to guarantee the material availability at the segment level. For more information about
standard MRP, see Material Requirements Planning (PP-MRP).
The enhanced process uniquely assigns requirements quantities to available stock using segmentation values and / or creates procurement proposals, such as
purchase requisitions, at segment level for nonexisting stock. The system determines the segments in the proposals based on the segmentation strategy.
Process
For articles with segmentation, the MRP processes are executed based on the following mapping rules defined in Customizing for Define Segmentation
Strategies under
Logistics General Segmentation
Requirement/Stock Allocation
Stock Transfer
Requirement to Stock Conversion
Planned Independent Requirement Consumption
1.9 Order Allocation Run

Order allocation run (ARun) ensures that stock is assigned to orders according to the changing requirements in fashion. The special situation in the fashion
industry requires an optimization of the assignment of existing stock to open requirements. In a stock shortage situation, order allocation run ensures an optimal
assignment of stock to the open requirements and distributes the stock currently available to the respective sales orders or stock transport orders (STO) according
to certain calculation logic at a specific time. If the ordered quantities are larger than the available stock, you can use ARun to achieve the best level of customer
satisfaction under the given circumstances in your business. You can use the order allocation run Workbench to view and correct results of allocation if required.
Order Allocation Run Process Flow
Features
You use ARun to ensure that specific stock is assigned to an order and is not consumed by any other order.
You can choose articles for which you want to carry out an order allocation run before the delivery of the stock. You can make this setting in the Logistics: DC
Fashion tab of the article master using the transactions MM41,42,or 43. You can deactivate this feature if you do not want to carry out an allocation run for an
article at a plant level. The allocation type always determines the allocation run. The allocation type forms a framework and contains all allocation rules and checks
that have been defined for a certain business process.
In the fashion industry, there is a difference of several weeks or months between the date of order creation and delivery date of goods to the customer. During this
time period, the quantity of the ordered material or the available stock can be reduced for various reasons. The ARun tool helps you decide how this insufficient
quantity should be distributed among the existing orders.
More Information
Steps in Order Allocation Run
Order Allocation Run Workbench
1.9.1 Steps in Order Allocation Run

The allocation process begins with the creation of sales orders and stock transport orders (STO) along with the availability check. Only STOs with Sales and
Delivery (SD) delivery as a follow-on document are considered for allocation. The allocation run is executed in normal and simulation modes. You can carry out the
allocation with all functions both online and in the background.
PUBLIC
Page 36 of 68
Process
The following steps are involved in the ARun process:
1. Selection
In this step, you determine the stock that allocation run accesses. The system considers the physical stock (stock at the storage location and batch stock)
and future receipts (purchase orders and shipping notifications) when it allocates the stock. For more information, see Selection Rules.
2. Requirement Filter
In this step, you can verify if the selected orders have the following checks:
Checks for sales orders
Header Credit Check: The system checks credit at the order header level.
Cancel Date: The system checks the order cancel date at the order item level.
Season: The system checks that items within an order have a valid season assigned.
Checks for stock transport orders
Season: The system checks that items within an order have a valid season assigned.
Depending on the result of these checks, the orders can then be excluded from the allocation process. For more information, see Requirement Filter
3. Requirement Grouping
In this step, you define conditions for grouping requirements that fulfill the same criteria during an order allocation run. Grouping the requirements is a
prerequisite when you use spread distribution allocation logic. For more information, Requirement Grouping.
4. Stock and Requirement Sorting
In this step, you define a rule to sort requirements and stock. Depending on your settings, you can override the original sequence of incoming orders for the
allocation process. This sorting rule enables optimal distribution of an insufficient quantity of stock among the existing orders according to specific criteria.
For example, customers with high priority due to their sales volume or their importance in the market are given preference and are supplied with goods first.
For more information, see Requirements and Stock Sorting.
Note
If you do not define any sort rule or the sort rule does not contain a sorting parameter, the requirements and stock are sorted in a random sequence.
5. Allocation
In this step, the system allocates the available stock to the selected orders according to the defined allocation logic. Allocation is possible using the FIFO
(First-In-First-Out) principle or the principle of proportionate distribution based on the requirement quantity (spread logic). Requirement grouping is a
prerequisite when you use spread allocation logic. When you use FIFO logic with the Only Up To Release Quantity checkbox selected and if you have
defined a maximum quota for a schedule line in the release rule, the system allocated only up to that quantity. For more information, see Allocation.
6. Release Rules
In this step, the system checks whether the minimum percentage of quantities that are defined at different levels of release rules are fulfilled. If not, the
allocated quantity can either be reserved for a certain order or the stock is used for the next selected order. For more information, see Release Rule.
Result
In the next step, you can create a delivery for the articles that have passed the release checks and then post the goods issue.
1.9.1.1 Selection Rules

When you start the order allocation run, you must enter the Open-To-Delivery date for sales orders and stock transport orders in the respective requirement tabs
of the allocation run. You can also enter a Open-To-Delivery date for future receipts in the Future Receipts tab of the allocation run. This time window depends
on the date fields you have defined in the allocation type.
For example:
For a sales order, you have selected the Confirmed Delivery Date (EDATU) as the open-to delivery date in the allocation type. When you execute ARun,
only those sales orders that have confirmed delivery dates within the date range of the Open-To Delivery Date (specified on the screen) are considered for
allocation.
For a STO, you have selected the Confirmed Delivery Date (EINDT) as the open-to delivery date in the allocation type. When you execute ARun, only the
STOs that have confirmed delivery dates within the date range of the Open-To Delivery Date (specified on the screen) are considered for allocation.
For future receipts, the Open-to-Delivery date depends on the goods receipts date defined in the allocation type. If you choose Item Delivery Date
(EINDT) and execute ARun, only those receipts that have item delivery dates within the date range of the Open-To Delivery Date (specified on the
screen) are considered for allocation.
For more information about Open-to-Delivery date adjustment and related example, see Dynamic Open to Delivery Date Adjustment.
Prerequisites
You have defined a stock selection rule in Customizing under
Logistics - General SAP Fashion Management
Order Allocation Run (ARun) Online
ARun
Selection
Maintain Rules for Stock Selection . You can then assign the relevant rule in the allocation type to decide which stock can be used to
cover requirements.
Features
Requirement Selection
You can decide which requirements should be selected when you execute order allocation run using the transaction ARUN. Only those articles which are ARunrelevant are considered for allocation. The types of requirements available are:
PUBLIC
Page 37 of 68
Sales orders
The sales orders are created when you enter sales documents in Sales and Distribution (SD). Only those sales orders which fulfill the following criteria are
considered for allocation:
Items with ARun-relevant articles
Schedule lines with a confirmed quantity greater than zero
The delivery-related status at header and item level is complete
Stock transport orders
Only the STOs that have the SD delivery as a follow-on document and which fulfill the following criteria are considered for allocation.
Items with ARun-relevant articles from the supplying plant
Schedule lines with a committed quantity greater than zero
The shipping data is complete
Purchase-to-order
To ensure that the PTO sales orders are allocated, select the Order Allocation Required checkbox in Customizing under
Logistics - General SAP
Fashion Management Order Allocation Run (ARun) Cross-Applications
Shipping Maintain Order Allocation Run for Special Sales Documents .
Stock Selection Rule

The stock selection rule determines how the system selects stock elements during an order allocation run. For each stock selection rule, you must specify which
stock elements that the system uses for requirements during an order allocation run. Stock elements can be of the following types:
Batch stock for articles that are batch managed
Storage location stock for articles that are not batch managed
Customer consignment stock for stock available at the customer site
Purchase-to-order (PTO) stock for a specific sales order
Future receipts that include purchase orders and shipping notifications
For physical stock, you must enter segments for each stock type and activate the corresponding stock segment to be used for allocation.
More Information
Dynamic Open to Delivery Date Adjustment
Execution of Order Allocation Run
1.9.1.1.1 Dynamic Open to Delivery Date Adjustment

The system automatically calculates the Open-to-Delivery (OTD) window for an order allocation run (ARun). All open schedule lines with delivery dates that fall
in this window and that match the selection criteria are automatically included in the allocation run. You can specify exactly how the system determines this date
for an order.
Activities
You can either enter the start and end dates manually in the Open-to-Delivery date range fields for sales orders, stock transport orders (STOs), or future receipts
in the respective requirement and future receipts tabs of the allocation run, or allow the system to calculate them automatically. The Open-to-Delivery date for
sales orders and STOs used for requirements whereas the Open-to-Delivery date for future receipts is used for stock. If you want the system to calculate the
Open-to-Delivery date automatically, you must enter the following details:
Base Date: The default value is the system date, but you can override this value with a past or future date of your choice.
Adjusted delivery from date (this field is a number of days, not a date)
Adjusted delivery to date (this field is a number of days, not a date)
Note
Only valid working days are included when calculating the start and end dates.
You can also use the Open-to-Delivery date range directly on the selection screen when you execute an ARun (this is a one-time event).
Example
You want to execute an order allocation run to include orders due for delivery within a seven day period, starting three days in the past and extending to four
days in the future. Shipping occurs all seven days a week.
Field
Value
Open-to-Delivery
(Blank The system calculates this)
Base Date
(Blank The system calculates this)
Adjust From-Date
-3
Adjust To-Date
-4
If today is October 23, the allocation run includes all sales orders from October 20 to October 27. If October 20 is a holiday in your logistics calendar, the
Adjust From-Date is postponed to October 21. Similarly, if one of the days in the future is a holiday, then the Adjust To-Date is moved to October 28. That
is, whenever a start or end date falls on a nonshipping day, the system moves on to the next valid shipping date.
If you enter the Open-to-Delivery date range, you only need to enter either the start or end date; the system calculates forward or backward to determine the
other end of the delivery window.
PUBLIC
Page 38 of 68
Field
Value
Open-to-Delivery
(Blank The system calculates this field)
Base Date
2013-10-23
Adjust From-Date
-7
Adjust To-Date
(Blank The system calculates this field)
The system calculates 7 days back from 2013-10-23 to determine the start date.
Note
A minus sign indicates that the system subtracts the number of days from the base date. An entry without a sign indicates that the system adds that number
of days to the base date. It is also possible to have minus signs in both of the adjusted delivery date fields. This sign only makes sense if the entry in the
Adjust From-Date is greater than the Adjust To-Date .
More Information
Selection Rules
1.9.1.2 Requirement Filter

You can use the requirement filter rule to exclude sales orders and stock transport orders (STO) that have (previously) been selected for ARun. In this way you
can, for example, prevent orders from credit blocked customers from being assigned stock that you want to use for solvent customers.
Prerequisites
You must define a requirement filter rule in Customizing under
Logistics - General
Online
ARun
Selection Maintain Rules to Filter Requirements . You can define your own rules for requirement filtering to perform checks on the selected records
based on the defined rules for requirement selection.
Features
After you have decided which requirements the order allocation run should access (for example, which sales orders and STOs should be allocated), you can
check these requirements for the following criteria:
Header Credit Check : Performs credit check at order header (applicable to sales orders only).
Cancel Date : Checks the cancellation date at order item level (applicable to sales orders only). You can specify the number of days before the order
cancel date until when the order must be allocated in the Days field.
Season Check : The system checks that all items within an order are assigned a valid season (applicable to sales orders and STOs).
Depending on the outcome of these checks, the orders can then be excluded from the order allocation run. You can define what action the system takes after the
checks are executed by selecting one of the following options:
Information (I): The system displays an information message and the requirements are considered for allocation.
Error (E): The requirements are excluded from the allocation.
Warning (W): The system displays a warning and the requirements are considered for allocation.
X (No Action): The system ignores the field check and all requirements are included for allocation.
You can combine the above-mentioned checks in a checking rule in Customizing. The result of failed checks can be saved in a log file.
More Information
1.9.1.3 Requirement Grouping

You can use the requirement grouping rule to combine all requirements that are selected for an order allocation run (ARun) into individual groups. The formation of
allocation groups is the prerequisite for using allocation logic other than the FIFO logic. You can additionally assign release rules to the individual groups and you
can sort by allocation groups within the requirements sorting. You can form groups using general criteria or form them customer-specifically.
Prerequisites
You have defined a grouping rule in Customizing under
Logistics - General
Online ARun
Grouping
Temporary Grouping
Maintain Rules for Grouping . You should assign fields to each of these rules and the requirements are grouped based on
these rules. For example, you can specify that all requirements are grouped by sold-to party in an allocation run. You can then execute order allocation run for
each allocation group based on the spread distribution logic
PUBLIC
Page 39 of 68
Process
General Requirement Grouping
You can use a grouping rule to determine which standards the system uses to form the individual allocation groups. Each requirement is assigned to one
allocation group. You can form any number of requirement groups. You can assign individual release rules to individual groups. You can define a grouping
rule in Customizing and maintain the rule in the corresponding allocation type. For more information, see General Requirements Grouping.
Customer-Specific Requirements Grouping
You can select individual grouping rules for the requirements of certain customers and enter it in the Customer Master of the respective customer at
Sales Area Data
Extras
Additional Data . Requirement grouping is optional. When you configure ARun, check whether you really msut form
allocation groups because they can affect the system runtime.
You can use the defined grouping rule in the corresponding allocation types in Customizing under
Logistics - General
Online ARun
Grouping
Maintain ARun Types . You can also specify the grouping rule that the system uses in
the Usage field in the corresponding allocation type. You can choose from the following options:
X No Grouping
F Customer-Specific Grouping Strategy: The system uses the grouping rule defined for specific customers.
S Default Grouping Rule Only: The system uses the default value mentioned in ARun type.
More Information
General Requirements Grouping
1.9.1.3.1 General Requirements Grouping

You use a grouping rule to combine all the requirements that are selected for an order allocation run into individual groups. The grouping is controlled by the
grouping rule of the allocation type used. The requirements of all customers are grouped according to the same criteria. You need the general requirements
grouping to carry out an allocation according to the equal distribution rule.
Prerequisites
You have activated the grouping rule entered in the allocation type by setting the appropriate grouping logic to S Default Grouping Rule Only . You can do make
this setting in Customizing under
Logistics - General
Online ARun
Maintain ARun
Types .
You must define and activate the grouping rule in the corresponding allocation type. If you want to execute an end-to-end allocation process, the general
requirement grouping must be activated. The system assigns the existing stock to the requirements of the individual allocation groups. The allocation logic controls
this procedure. If you have not specified a requirement grouping rule for ARun, every order is considered as a single group and allocation is then done based on
FIFO (first-in-first-out) logic. If you form requirement groups, allocation can be carried out using the spread logic.
Features
Grouping Rule and Grouping Criteria
In the grouping rule, you determine which criteria the system uses to group the customer requirements. The grouping criteria correspond to individual fields
of the sales order or STO. The number of groups is determined by the grouping criteria selection. This does not mean, for example, that if you select two
grouping criteria, only two allocation groups will be formed. The number of groups depend on the number of characteristic values of the individual grouping
criteria. For example, if you choose the field Sold-to-party , you create an individual group for each sold-to-party using the selected customer requirements.
You can also determine the allocation groups by using a combination of several grouping criteria. This causes the number of created groups to increase
accordingly. You can only use the group fields that you get through the match code help as grouping criteria. The system assigns the internal group
numbers in a random sequence.
External Group Numbers
If you want to use individual release check rules and allocation logic for individual groups, you must flag the corresponding groups with an external group
number. The external group numbers are a prerequisite for using allocation groups as sort criteria in the requirements sorting.
Individual Group Release Rules
You can use different release rules for individual allocation groups. You still control the allocation run with the used allocation type. If you want to use this
function, you must assign an external group number to the requested allocation group.
External groups can be applied to specific customers (any grouping field) by providing constants.
Example
Grouping Rule
Grouping Field
External Group
Constant
Release Rule
001
KUNNUR
C1
CUSTOMER_1
REL1
001
KUNNUR
C2
CUSTOMER_2
REL2
Of all the requirements selected by ARun, the release rule REL1 is applied to only the requirements that are created by Customer_1 . Similarly, REL2 is
applied to only the requirements created by Customer_2 .
More Information
PUBLIC
Page 40 of 68
Requirement Grouping
1.9.1.4 Requirements and Stock Sorting

You use the requirement sorting rule to sort requirements at order and schedule line levels, and thus override the original sequence in which the orders were
placed. The orders are sorted in a different sequence to meet your requirements. The new sequence forms the basis for allocation.
You can use the stock sorting rule to specify the sort order in which stock is allocated. For example, you can use the stock sorting rule if you want stock in one
storage location to be given a higher priority for allocation than stock in another location.
Prerequisites
You have assigned a sort rule for each allocation type.
Features
The sorting rule contains a field catalog with sort fields. You choose the fields from the field catalog that are important for your business processes and put them in
a sequence. You can then compare the selected fields with constants. For example, you can define that customer X always has the highest priority.
Requirement Sort Rule

You can use the requirement sort rule to decide the sequence in which customers receive the requirement quantity. This rule enables you to use your own criteria
and priorities to restructure the original sequence in which the requirements records are posted in the system. The following requirements types are available:
sales order
stock transport order
You can create a requirement sort rule in Customizing under
Logistics - General
SAP Fashion Management Order Allocation Run (ARun)
Online
ARun
Sorting Maintain Rules to Sort Requirements . The fields used for sorting are specific to a sales order, STO, or both and are derived from the
DocType column in the table.
Stock Sort Rule

You can use the stock sorting rule to specify the sort order in which stock is allocated
You create a stock sort rule in Customizing under
Sorting Maintain Rules to Sort Stock .
Logistics - General
Online ARun
Example
You select the Stock Type (FSH_BSKZ) as a stock sort field, but you want to assign individual priorities to each stock type as follows.
Constants
Priority
Field Text
Purchase Orders
Batch Stock
Shipping Notifications
This kind of sorting would not be possible with a normal ascending or descending sort method. However, by assigning individual priorities to each stock type, you
can adjust the sort order to meet your needs.
More Information
1.9.1.5 Allocation
You use the allocation logic to determine the strategy that the system uses to distribute existing quantities to individual requirements. Allocation can be based on
the FIFO (first-in-first-out) principle or the principle of proportionate distribution (spread logic). When you allocate using FIFO logic, the existing stock is assigned to
the requirements according to the existing sorting. That means, the requirements that have a high priority (due to the requirements sorting) are fully allocated, while
requirements with a lower priority are allocated little or no stock, and therefore cannot be released. When you use spread stock logic for allocation, existing stock
can be proportionally distributed to the individual requirements according to certain rules.
The order allocation run results in assignments that are either released for delivery or reserved for delivery at a later date. These assignments have the following
statuses depending on the result of the release check:
Fix (F): The stock is fixed and the outbound delivery is possible (when a release check is successful)
Fix and Hold (H): The stock is on hold and the outbound delivery cannot be created (though the release check successful)
Reserve (R): The stock is reserved.
On Delivery (D): The order is on track for delivery.
PUBLIC
Page 41 of 68
Prerequisites
To carry out an allocation using spread logic, you must create allocation groups using requirements grouping rules. You can store the allocation logic in the
corresponding release rule for the allocation groups.
Features
Allocation Logic
You can use the allocation logic to specify the strategy for allocating existing stock during an order allocation run. You can choose the allocation logic in
Customizing under
Logistics - General SAP Fashion Management Order Allocation Run (ARun)
Online ARun Allocation Logic
Maintain
Allocation Logic .
You select the relevant radio button to determine whether the allocation takes place according to the FIFO principle or the spread principle. You can also use the
Only Up To Release Quantity option if a requirement cannot be fulfilled completely. If there is not enough stock available, the system allocates up to the release
quantity (specified release percentage at schedule line level). The following example shows the allocation results for different of allocation logic settings:
Results for Different of Allocation Logic Settings
In case 1 (FIFO), the allocation is carried out using the FIFO logic. The requirements of the Group 1 are completely fulfilled. The remaining quantity of 25 is
sufficient to fulfill the first requirement of Group 2 up to the minimum quota.
In case 2 (spread distribution), the allocation is carried out using spread distribution combined with a material shortage logic up to the minimum release quantity.
After the requirements of Group 1 are also completely covered, the remaining quantity is equally distributed among the requirements of Group 2.
In Case 3 (FIFO at Max. Quota), allocation is carried out using FIFO distribution with stock shortage logic up to the confirmed quantity is set in the allocation logic.
Since a maximum quantity of 70% was entered in the release rule, the allocation from the order is carried out up to this value instead of up to the confirmed
quantity.
In Case 4 (Spread Distribution at Max. Quota), allocation is carried out using spread distribution logic and stock shortage logic up to the confirmed quantity is
used. Since spread distribution is used here, the system equally allocates the remaining 55 pieces to the requirements of Group 2 (with the remaining quantity
logic from the start of the current group, therefore an allocation of 28 pieces to Group 3).
Note
The following features are not supported when you used spread distribution logic as the allocation strategy:
Dynamic Stock Sorting: This feature is used to prioritize different stock types so that the one with the highest priority is allocated first.
Delivery Scheduling: This feature is used to ensure timely delivery to your customer.
Field Checks: The field checks that you select when your create an allocation rule are not supported.
You can define these features in Customizing under
Allocation Logic
Maintain Rules for Allocation .
Logistics-General
ARun Details
More Information
Allocation Rule
Dynamic Stock Prioritization
Allocation Against Future Receipts

PUBLIC
Page 42 of 68

You use the allocation rule to control how the system assigns stock to requirements during an order allocation run (ARun).
You have made setting in Customizing under

Logic
Logistics - General
Online ARun
Allocation
Structure
The following fields form the basis of the allocation rule:
Requirement Date for Sales Order
You can specify that the availability date is based on one of the following:
Confirmed Delivery Date (EDATU)
Order Cancellation Date (FSH_CANDATE)
Requested Delivery Date (VDATU)
Note
If you choose Requested Delivery Date (VDATU) as a requirement date, the system considers the header level requested delivery date of a sales order.
Requirement Date for Stock Transport Order (STO)
You can specify that the availability date is based on one of the following:
Item Delivery Date (EINDT)
Committed Date (DAT01)
Goods Receipt Date
This date is the reference date for the future receipt that is to be considered for allocation. You can select Schedule Line Date (EINDT) as a reference date.
Note
These reference dates are used during dynamic stock sorting and only when the Cancel Date field check is used.
Delivery Scheduling
You can select the Delivery Scheduling checkbox to ensure timely delivery to the customer. The system checks those factors that influence the delivery
time, such as picking time, packing time, loading time, and goods receipt processing time. For more information, see Delivery Scheduling.
Field Checks
During the allocation process, the system performs checks on the fields in an order document. You can choose from the following settings:
Batch Number :
Checks that only the stock with the same batch number as entered in the order document is considered for allocation.
Storage Location :
Checks that the stock with the same storage location as entered in the order document is considered for allocation.
Segment :
Checks that only that stock with the stock segment mapped to the requirement segment defined in the order document is considered for allocation.
Based on the mapping rules defined in Customizing for Requirement/Stock Allocation under
Segmentation Define Segmentation Strategies
Segment Strategies , the system decides which stock segment can be fulfilled for a
requirement segment
Sort : Ensures that, in addition to the mapping, valid stock elements with different stock segments are prioritized according to the sort parameter
in the segmentation strategy before being allocated.
Cancel Date : Ensures that allocation occurs only when the stock availability date is before the cancel date in the sales document.
Season: Checks whether the season information of a requirement matches the season information of the stock. If there is a shortage in the stock with
matching season information from an order, it cannot be replaced by other stock with different season information. The season information includes
season, season year, collection, and theme.
Stock Prioritization
You can specify whether the system uses a stock sorting rule (which you must already have defined in Customizing) or dynamic stock prioritization.
Use Stock Sort Rule : Use the stock sort rule to prioritize stock elements for allocation. This stock rule must be defined in Customizing under
Online ARun
Selection
Maintain Rules for Stock
Selection .
Stock Sort Rule : You can select an existing stock rule to define the fields, data values (if any), and priorities used to sequence the stock and future
receipts before the allocation stage.
Dynamic Stock Sorting
You can prioritize different stock types so that the one with the highest priority is allocated first for a defined time period. Dynamic stock sorting is not
applicable when you use spread distribution logic. Dynamic stock prioritization applies to physical stock and future stock.
For information about dynamic stock prioritization, see Dynamic Stock Prioritization.
More Information
Delivery Scheduling
Allocation
1.9.1.5.1.1 Delivery Scheduling

PUBLIC
Page 43 of 68
You can use Delivery Scheduling to ensure timely delivery of goods to the customer. The system checks those factors that influence the delivery time, such as
picking time, packing time, loading time, and goods receipt processing time.
Features
The Delivery Scheduling checkbox is applicable to sales order and stock transport orders (STO). If you do not use Delivery Scheduling , one of the following
dates is used as the requirement date for a sales order.
Confirmed Delivery Date (EDATU)
Requested Delivery Date (VDATU)
Order Cancellation Date (FSH_CANDATE)
Note
If you choose Requested Delivery Date (VDATU) as a requirement date, the system considers the header level requested delivery date of a sales order
For STOs, the following dates are used as the requirement date if Delivery Scheduling is not used.
Item Delivery Date (EINDT)
Committed Date (DAT01)
If you use Delivery Scheduling , the new requirement date is calculated as follows:
New Requirement Date = [Requirement Date] [Number of Approximate Working Days Needed to Schedule a Delivery]
Here, the number of approximate working days are the days between the Confirmed Delivery Date (EDATU) and the Material Availability Date (MBDAT), that is,
Number of Working Days = Confirmed Delivery Date (EDATU) Material Availability Date (MBDAT)
Note
Delivery Scheduling is not applicable when you use spread distribution logic as the allocation strategy.
See the example which explains how requirement dates are calculated if you do not use Delivery Scheduling option.
More Information
Example: Delivery Scheduling
Allocation Rule
1.9.1.5.1.1.1 Example: Delivery Scheduling

The following example explains how the delivery scheduling feature is used.
Sales order details
Confirmed Delivery Date
November 15
Material Available Date
October 15
Cancel Date
December 15
Number of Working Days
November 15October 15 = 12 Working Days
If you use Confirmed Delivery Date (EDATU) as the requirement date, the new requirement date is Material Availability Date (MBDAT).
The requirement date is calculated as follows:
New Requirement Date = [Requirement Date] [Number of Working Days Needed to Schedule a Delivery]
For this sales order, the new requirement date is calculated as follows:
New Requirement Date = November 15 [November 15 October 15] = October 15
If you use Cancel Date (FSH_CANDATE) as the requirement date, the new requirement date is calculated as follows:
Requirement Date = Cancel Date [Confirmed Date Material Availability Date]
The system calculates the number of working days between the Confirmed Delivery Date (EDATU) and the Material Availability Date (MBDAT). This
number of days is subtracted from the cancel date to determine a new requirement date. The requirement date for the sales order is calculated as follows:
Requirement Date = December 15 [November 15 October 15] = November 27
If you use Requested Delivery Date (VDATU) as the requirement date, the new requirement date is calculated as follows:
Requirement Date = Requested Delivery Date [Confirmed Date Material Availability Date]
More Information
Delivery Scheduling
Allocation Rule
1.9.1.5.2 Dynamic Stock Prioritization

PUBLIC
Page 44 of 68
You can use dynamic stock prioritization to prioritize different stock types so that the stock with the highest priority is allocated first.
Activities
You can define the settings to prioritize different stock types in Customizing under
(ARun)
Online ARun Allocation
Logistics - General
For allocation against goods receipts, the system checks each stock type, matching the stock from the From days field to the To days field. If the value in the
From field for a stock element is greater than the value in the To field, the system searches for stock in the backward direction, otherwise it searches in the
forward direction, as indicated by the arrows on the Dynamic Stock Validity screen.
Example
You can define an allocation window for a stock element. If the requirement date is within the window (starting on the current day, this stock can be allocated. If you
do not enter a safety window for a stock type (From = 0, To = 0), the system ignores that stock type.
The following sales order has the delivery date November 19.
Priority
Stock Type
From
To
System Reaction
Confirmations
-5 (working days)
5 (working days)
The system searches for the

purchase order from November 14
to November 24 (forward
direction).
Batch Stock
10 (working days)
The system searches for the order

for the physical stock that is
available from November 9 to
November 19.
Confirmations
5 (working days)
-5 (working days)
The system searches for the

purchase order from November 24
to November 14 (backward
direction).
Note
Dynamic stock sorting is not applicable when you use spread distribution logic as the allocation strategy.
More Information
Allocation Rule
1.9.1.5.3 Allocation Against Future Receipts

When you use order allocation run (ARun), you can allocate future receipts to sales orders and stock transport orders. You can reserve stock from a future receipt
to ensure that you will have the stock ready for the orders once the goods are received. In this way, the stock purchased for a specific customer or order is
reserved for that customer or order only, even before the stock is received. Based on stock reservations, the committed deliveries to customers are fulfilled.
ARun allocates stock to the following types of future receipts:
purchase order
shipping notification
Integration
All functions and features in ARun treat future receipts as if they were unrestricted stock, with the exception that the future receipt allocations can only be given the
status Reserved (R) . This status cannot be changed to Fixed (F) .
Features
The system uses the following approach while allocating stock against future receipts:
Based on the Customizing settings, the system uses a best match strategy (dynamic stock prioritization) to match purchase orders or notifications and
requirements. During the allocation process, the system runs a date validity check. This ensures that the incoming stock from purchase orders fall within the
timelines of the assigned sales and stock transport orders.
Example
Customer A has an order for 100 pieces. The purchase order created for this order should have a goods receipt date that is prior to the confirmed
delivery date of the sales or stock transport order. The system performs this check before the allocation process. Future receipts which do not fall within
the timelines of the order are ignored for the current requirement that is being checked; however, they will be considered for other requirements which fit
the date constraints.
The release rule calculates the Reserved (R) status based on unrestricted stock.
PUBLIC
Page 45 of 68
Example
You have an order for 100 pieces with an 80% release rule. If an assignment achieves 80% fulfillment from a purchase order (future receipt) and 20%
from unrestricted stock, all assignments are set to the status Reserved (R) .
Conversely, if you have 80% fulfillment from unrestricted stock and 20% from a purchase order, the assignment using physical stock is set to the
status Fixed (F) because the release percentage is over 80%. However, the second assignment using the purchase order retains the status
Reserved (R) .
More Information
Cross-Applications in Order Allocation Run
1.9.1.6 Release Rule

Since there is often a long period of time between the order entry and the actual allocation, quantities that have been confirmed by the availability check during the
order entry can change. When the confirmed delivery date is reached, there are often fewer goods available than had been confirmed. This material shortage can
be caused by under deliveries or delayed deliveries.
You use release check rules to determine which quantities are acceptable for your customers. You can specify the minimum percentage of quantities that must
be fulfilled at the different release levels so that an order can be released for delivery. In case of stock shortage, you can define the maximum percentage of
quantities for schedule lines only. To specify the maximum percentage of quantities that must be fulfilled at the schedule line release level, you must select the
Up To Release Quantity checkbox when you define the allocation logic. You can do this in Customizing under
Logistics - General
SAP Fashion
Management Order Allocation Run (ARun) Online ARun
Allocation
Define Allocation Logic .
Integration
You can define release rules for:
Specific orders: The system checks all requirements selected by ARun with the same release check rule.
Order allocation run types: The system uses the release rule defined for an allocation type depending on the determination logic parameters in each ARun
type. You can define various rules in Customizing activity Maintain ARun Types under
Logistics - General
Order
Allocation Run
Online ARun .
Specific customers: You can define customer-specific release rules by entering the release strategy in Customizing activity Maintain Release Strategies
under at
Order Allocation Run (ARun) Online ARun Release .
External groups: You can also define a release rule for an external group entered for grouping fields. You can define the determination priority in Customizing
activity Maintain ARun Types . The release rule defined for external groups if always of a higher priority than the release rules defined for the determination
priority.
You can assign different release checks for the following release check levels:
Group of Documents
Document Header
Delivery Group/Grouped Items (Sales Order only)
Generic Articles
Articles (Items)
Schedule Lines
Value Added Services (VAS)
Bill of Materials (BOM)
The system uses a bottom-up strategy, which means that the check starts at the lowest level and then goes to the next higher level.
PUBLIC
Page 46 of 68
Release Check Levels
The system sets the following statuses according to whether the result of a release rule check for a requirement is successful or not:
Result
Status
Description
Release rule is successful
Fixed (F)
Outbound deliveries are possible
Fix and Hold (H)
Outbound deliveries are not possible
Reserve (R)
Reserve the quantities that are allocated to requirements
Blank
Do not allocate any quantity to the requirement
Release rule is not successful
Features
The ARun status Reserved (R) is used for the following scenarios:
When a release check fails and the status is maintained as Reserved (R) .
When you allocate a sales contract, the final status will be maintained as Reserved (R) irrespective of the release check.
When you allocate requirement with future receipt stock, the final status will be maintained as Reserved (R) irrespective of the release check
Calculation Method for Release Rules

You can use one of the following calculation methods to calculate release rule:
Include All Quantities
Exclude Already Failed Quantities
The calculation methods are defined in Customizing for Maintain ARun Types under
Run (ARun) Online ARun .
Logistics - General
Order Allocation
Example
The following example explains how release rules are implemented using the following calculation methods:
Include All Quantities
Exclude Already Failed Quantities
PUBLIC
Page 47 of 68
Example of Release Rule
Case 1: Include All Quantities

For schedule lines 1.2 and 2.2, only 30 pieces of the 50 ordered quantity are available and the release check is not fulfilled with a minimum quota of 70%. As a
result, the schedule lines are 1.2 and 2.2 are assigned the ARun status Reserved (R). The system then checks at the item level whether a minimum quota of
70% can be achieved. The available quantities for Item 1 are 75 (45 + 30) and for Item 2 are 60 (35+30). Here, Item 2 fails to achieve the release percentage of
70% (achieved is 65%), and therefore, the ARun status of Sch. Line 2.1 changes to Reserved (R). The system then checks at the order level whether a minimum
quota of 70% can be reached. At order level, the total quantity is 140 (that is, 70%) and the ARun status of the schedule lines are not changed.
Case 2: Exclude Already Failed Quantities
For schedule lines 1.2 and 2.2, only 30 pieces of the 50 ordered quantity are available and the release check is not fulfilled with a minimum quota of 70%. As a
result, the schedule lines are 1.2 and 2.2 are assigned the ARun status Reserved (R). The system then checks at the item level whether a minimum quota of
70% can be achieved. The available quantity for Item 1 is 45 (45%) and Item 2 is 35 (35%). Item 1 and Item 2 fail to achieve the minimum release percentage of
70%. Now, the system checks at the order level whether a minimum quota of 70% can be reached. At order level, since no quantities are carried forward, the total
quantity is 0.
Note
If a release rule check fails at a certain level, the schedule lines are never assigned the status Fixed (F) or Fix and Hold (H) even though the release rule
passes at the higher release check levels. The status of the schedule lines will be set as Reserve (R) or blank (with no entries), as defined in Customizing
under
Logistics - General SAP Fashion Management Order Allocation Run (ARun) Online ARun -> Release
Maintain Release Rules .
More Information
Release Check for Delivery Groups
Logic to Determine Release Rule
Allocating Bill of Material (BOM) Articles
Allocating Value-Added Service (VAS) Articles
1.9.1.6.1 Release Check for Delivery Groups

Your customers may requite that you include a minimum percentage for some group of items in a sales order in their shipments. You can select these specific
items using delivery groups. You can assign one or more items to a delivery group.
Example
Enter 001 for first set of items and 002 for second set of items. Multiple delivery groups can be entered in a sales order. The items with blank delivery group
are assigned to group 000. If you leave the delivery group empty for items. blank are assigned to group 000. When ARun is calculating the release quantity,
you can specify whether it should consider all groups. NOTE: Delivery groups are always at the item level.
Integration
When order allocation run calculates the release quantity, you can specify whether it should consider all items (the default setting), or only the items assigned to
delivery groups. You make this setting in Customizing for Release Rules under
Logistics - General SAP Fashion Management Order Allocation Run
(ARun) Online ARun) Release Maintain Release Rules .
PUBLIC
Page 48 of 68
Example
There are 6 Items in a sales order. Items 1 and 2 have delivery group 001 and items 5 and 6 have delivery group 002. All other items (3 and 4) are not assigned
a delivery group.
If you have not selected the Ignore Blank Delivery Groups checkbox, delivery group 001 and delivery group 002 are checked and all the other items (item 3
and 4) are checked for release as one delivery group (group 000).
If you have selected the Ignore Blank Delivery Groups checkbox, only delivery groups 001 and 002 are checked for release.
More Information
Release Rule
1.9.1.6.2 Allocating Value-Added Service (VAS) Articles

You can perform allocation for value-added service (VAS) articles that are ARun-relevant.
By selecting the VAS Correlation checkbox, you can adjust the allocated quantities for VAS articles. You can also use a minimum quota for VAS articles. You
can do this in Customizing under
Logistics - General
Online ARun
Release
Maintain
Release Rules .
Features
You can use the correlation for the header articles and the corresponding VAS item articles that are ARun-relevant.
Example
An order A consists of a header article with two VAS items: VAS item 1 (10 pieces) and VAS Item 2 (15 pieces). A customer needs 20 pieces of this header
article. That means that you need 200 of VAS item 1 (20x10) and 300 of VAS item 2 (20x15).
The allocation check takes place for each VAS item for this sales order. Only 190 pieces of VAS item 1 (95% of the required quantity) and only 210 pieces of
VAS item 2 (70% of the required quantity) are available for allocation.
The following correlation that takes place causes the allocated quantities to be adjusted so that 14 header articles can be delivered.
Component
Confirmed Quantity
Allocation Results
Result of Correlation
Header
20
NA
14
VAS Item 1
200
190
140
VAS Item 2
300
210
210
More Information
Value-Added Services
Value-Added Service Articles
1.9.1.6.3 Allocating Bill of Material (BOM) Articles

During order allocation run (ARun), you can determine how customer assortments are taken into account if there is a stock shortage for a component. You can use
the BOM Correlation indicator to determine whether the allocated quantities of other components are also reduced whenever there is a stock shortage of an
individual component of a sales bill of materials (BOM). For example, if there is a stock shortage of a component that belongs to the assortment, you can reduce
the allocated total quantity.
Features
When you use a sales BOM in a sales order, the order allocation run is carried out at the schedule line level for each component. You can also use a minimum
quota for BOM components. Select the BOM Correlation checkbox if you want the components of the sales BOM to be allocated in the specified quantity ratios
defined. You can do this in Customizing under
Online ARun
Release
Maintain Release Rules .
Example
The sales BOM A consists of components 1 (10 pieces) and 2 (15 pieces). A customer needs 20 pieces of this BOM. That means that you need 200 of
component 1 (20x10) and 300 of component 2 (20x15).
The allocation check takes place for each component for this sales order. Only 190 pieces of component 1 (95% of the required quantity) and only 210 pieces of
component 2 (70% of the required quantity) are available for allocation.
When the system applies the following correlation, the allocated quantities are adjusted so that 14 pieces of this BOM can be delivered.
PUBLIC
Page 49 of 68
Component
Confirmed Quantity
Allocation Result
Result of Correlation
Comp.1
200
190
140
Comp. 3
300
210
210
1.9.1.6.4 Logic to Determine Release Rule

You can determine which release rule the system uses for a release check. You can choose the release rule in Customizing under
Fashion Management
Online ARun
Maintain ARun Types .
Logistics - General
SAP
Features
You can use the following options to determine which release rule must be used for an order:
Always Use Default : The release rule defined in the order allocation run (ARun) type is applicable.
S First from Sales Order; 2nd Default : The release rule defined in a sales order is given priority. If the release rule is not found, the system applies the
default release rule defined in the ARun type.
F 1st Determination; 2nd Default : The release rule determined by the release strategy is given priority. If the release rule is not found, the system applies
the default release rule defined in the ARun type.
X 1st from Sales Order; 2nd Determination, 3rd Default : The release rule defined in a sales order is given priority. If not found, the release rule determined
by the release strategy is given second priority. If both release rules are not found, the system applies the default release rule entered in the ARun type.
More Information
Release Rule
1.9.1.7 Log Rule

You use the log rule to define where the log files (containing exceptions) for the order allocation run (ARun) are saved in the database. You can also use this
feature to save the success messages that were issued during the execution of online ARun, batch ARun, and ARun Workbench, in the database table.
Prerequisites
You have defined a number range for the log file, in Customizing under
Logistics - General
ARun General Settings
Number Ranges
Define Number Range for Log File .
Features
This function enables you to log allocation/deallocation messages and exceptions that occur during the execution of online ARun, batch ARun, and ARun
Workbench. The log rule also determines which of the following exceptions are included in the log file.
All messages
Only error messages
Only warning messages
Errors and warnings
Activities
1. Define a log file rule in Customizing under
Logistics - General
Online ARun
Log
Maintain Log Rules .
2. Specify which exceptions the system includes in the log file that is produced during the allocation run.
3. Choose whether the logs are saved to a database.
4. Assign your log file rule in ARun type ( Logistics - General
Online ARun
Maintain
ARun Types .
More Information
1.9.2 Execution of Order Allocation Run

You can execute order allocation run (ARun) both in the background and online. For more information about about executing ARun in the background, see
Background Processing (Batch ARUN) Background Processing of ARun.
An allocation type controls every allocation run. All the rules that influence the allocation run are grouped in the allocation type. The individual rules (selection,
requirement check, grouping, sorting, allocation, release check, and log) are individually defined in Customizing for the allocation run and entered in the
PUBLIC
Page 50 of 68
corresponding allocation type. Since you can define any number of allocation types, you can map a wide variety of business processes in the system. For
example, you can create special allocation types with specific settings for certain customers. In this way, you can make sure that those special requests can be
mapped by the system during the order processing.
Whenever you start an order allocation run, you can decide whether to run it in normal mode or simulation mode.
In normal mode, the assignments between the requirement and stock are posted and the order is updated. The stock is then assigned to this order and can be
delivered in the next step.
In simulation mode, processing is similar, but the system does not update orders and the requirements are not assigned to a certain stock. You can use this mode
to simulate and test results.
You can display and edit the results of a saved allocation run using ARun Workbench and log files. You can use log rules to check where the log files (containing
exceptions) for order allocation run (ARun) are saved in the database.
Process
1. Define an allocation type in Customizing under
Logistics - General
SAP Fashion Management Order Allocation Run Online ARun
Maintain
ARun Types .
2. Use the transaction ARUN to execute order allocation run (ARun). Alternatively, on the SAP Easy Access screen for Retailing, choose
SAP Fashion
3.
4.
5.
6.
7.
8.
9.
Management Order Allocation Run Order Allocation Run (Online) .

Choose an allocation type to determine which rules are used for executing the allocation
Enter a description for each allocation run. You can use it as search help during later evaluations for the ARun Workbench or the log files.
Choose the mode you want to run the allocation.
Select the requirements to be used during order allocation run
Select the Selection List checkbox if you want to display the allocation results list of the orders selected for an order allocation run.
Select the Allocation List checkbox if you want to display the allocation results list.
Choose Execute to start order allocation run and save your order allocation run.
More Information
Using Variants in Online and Batch ARun
1.9.3 Background Processing (Batch ARun)

A company must manage a large volume of data in Sales. Due to a great number of incoming orders, automatic processing within the logistical process is
required. It is advantageous to externally carry out certain collective processing in times of low system utilization. During background processing (batch ARun), the
data is processed in the background while you execute other functions on the screen. The background processes are not visible to the user and no dialog boxes
or messages appear on the screen. However, they have the same priority as online processes
For example, the allocation run can be triggered at night. The individual customer requirements of the day are collected and can then be processed together. This
guarantees that an overall examination of the requirement situation is carried out and the allocation is executed according to the selected strategy. The next day,
you can filter certain allocations and, if necessary, they can be automatically changed.
Integration
.
The background processing of order allocation run is carried out similarly to that of the ERP Standard. To plan a background job, the system requires the name of
the program to be executed and a variant that contains the selected program parameters for the requested run. You cannot plan order allocation runs as
background jobs directly. You can create a variant for the program, but the selection conditions for the requirements must always be entered manually. Otherwise,
the system does not know which requirements should be selected.
Prerequisites
The name of the program to be executed (with a related variant that contains the corresponding parameters) is required to implement background processing. You
must also completely define the parameters of the allocation run type.
Features
You can trigger background processing for each mode of the allocation run. You can plan a job using the variants in normal and simulation modes.
Activities
1. Use transaction ARUN_BATCH to execute background processing of an order allocation run.
2. Choose a variant .
3. Choose the mode of allocation for the selected allocation type.
4. Execute the operation.
More Information
PUBLIC
Page 51 of 68
Using Variants in Online and Batch ARun
1.9.4 Order Allocation Run Workbench

The order allocation run workbench is used to view and manage allocations performed by order allocation run (online and background). It displays the stock
allocation details (for example, which quantities are reserved, fixed, on delivery or open) at different levels. In combination with Allocation Against Future Receipts,
the ARun Workbench provides early visibility at the complete order level so that you can spot delivery problems and respond appropriately.
You can display and edit the results of a saved allocation run using ARun Workbench. You can also use log rules to subsequently check where the log files
(containing exceptions) for ARun are saved in the database.
Integration
You can use the ARun Workbench to manually change or reset the results of the allocation run. In this way, the system reacts to a changed stock and
requirements situation at any time after the allocation run. You can change undesired allocation and deallocation results.
Prerequisites
You have activated the business function Fashion_01 for SAP Fashion Management.
You have made the necessary settings in Customizing for ARun under
Logistics - General
Order Allocation Run Workbench Maintain ARun Workbench Type .
Features
You can define an ARun Workbench type for the applications areas Assignments and Requirements. When you select Assignments , the allocated orders
are displayed on the result screen of ARun Workbench. When you select Requirements , both allocated orders and open requirements are displayed in the list of
allocation results.
You can use ARun Workbench to perform the following functions for assignments and requirements application areas:
Allocate (For requirements only): You can specify the quantity that needs to be allocated. The system allocates stock using the FIFO (first in first out) logic.
During the allocation, the system applies the allocation and stock selection rules that have been defined in the Customizing activity Maintain ARun
Workbench Types ( Logistics - General
ARun Workbench
Maintain ARun
Workbench Types .
You can release the allocated orders manually to change the status to F (Fixed).
Deallocate: You can specify the quantity that needs to be deallocated from an already allocated order, and perform deallocation.
Release: You can manually change the status of released orders to the status F (Fixed).
Block: You can block an order by changing the status F (Fixed) to the status H (Fixed and Hold) or R (Reserved).
You can use ARun Workbench to create selection reports for assignments and requirements. You can do this in Customizing under
Logistics - General SAP
Fashion Management Order Allocation Run Order Allocation Run Workbench ARun Workbench Control Generate Selection Reports . See Creating
Custom Reports in Order Allocation Run Workbench for more information about generating selection reports.
Optionally, you can also save the success messages issued during an ARun Workbench session, in the database table. You can do this in Customizing under
Logistics - General SAP Fashion Management Order Allocation Run Order Allocation Run Workbench Maintain ARun Workbench Type .
You can use an ARun Workbench type to control which parameters are used by the system to select the allocations and which data is displayed on the result
screen. This allows you to predefine an ARun Workbench with individual settings for different processes and users, and to adjust them to meet the respective
requirements.
More Information
Creating Custom Reports in Order Allocation Run Workbench
Configuring Levels in Order Allocation Run Workbench
Selection Rules
Allocation Rule
1.9.4.1 Creating Custom Reports in Order Allocation Run

Workbench
You use the report generation tool in order allocation run Workbench to create selection reports for assignments and requirements.
The default report for assignments and requirements ensures adequate selection based on frequently used selection criteria. However, if you need reports with
different or additional selection criteria, you can create these reports with the ARun Workbench report generation tool.
For example, suppose if you want to include the Customer Group 5 in the selection criteria. This field does not appear on the default selection screen. You
therefore have to generate a new selection report for all the fields that you want to see in the selection report. You can then assign this new report to the desired
ARun Workbench type.
Process
1. In Customizing, choose
Workbench Control Generate Selection Reports .
PUBLIC
ARun
Page 52 of 68
2. Choose New Entries .

3. Enter the following data:
Set: This number is an identifier for the set of fields you select. Enter the next available number within your application.
Application: This parameter defines the ARun Workbench area for which the report is used. Select assignments or requirements.
Description: Enter a name for your report.
4. Save your data.
5. At the left side of the screen, choose Tables/Fields .
6. Enter the field catalog (set of fields) to be used for selection screen generation.
Table Name : This is the name of the database table to be accessed. A selection field is only unique when defined together with the table name. You
can choose the list of available tables using the F4 option.
Field Name : Enter the technical field name. You can choose the list of available fields using the F4 option. If you have already entered the table
name, press Enter to view the valid field names.
Sequence : Assign a number to each field, reflecting the order in which it is to appear on the selection screen. If you do not enter a valid value, this
field is not considered during the report generation.
Search Help Name : Leave the field blank if you want the system to find an appropriate one during the screen generation. Otherwise enter a specific
help view.
Note
If you make an entry in the above fields and do not generate a report, the system displays and error message and the report is not generated.
If you do not make an entry in the above fields and generate a report, the report with only the default fields is generated.
7. Optionally, you can simulate your selection screen at this point so that you can see what it would look like. To do this:
1. Return to the header screen.
2. Select your report.
3. Choose Details.
4. Choose Simulation.
8. In the detail screen, choose Generate Report . The system prompts you to enter a report name. Enter a unique name for the new report.
9. To use the new selection report, you must assign it to an ARun Workbench type ( Logistics - General SAP Fashion Management Order Allocation
Run (ARun)
Order Allocation Run Workbench Maintain ARun Workbench Types ).
More Information
Configuring Levels in Order Allocation Run Workbench
1.9.4.2 Configuring Levels in Order Allocation Run Workbench

In Order Allocation Run Workbench, you can configure up to three different drill-down paths. Each path consists of three different levels and each level may
consist of different key fields. The Path Level Identifier field determines paths for the ARun Workbench and the path hierarchy within the ARun Workbench type.
You can attach a unique Path Level Identifier to an ARun Workbench type. You can use this parameter for the application area Requirements only.
You can configure levels for ARun Workbench in Customizing under
ARun Workbench
ARun Workbench Control
Configure Levels
Logistics - General
.
Example
If you do not assign any path level identifier in the ARun Workbench type, the default behavior is as follows:
Level 1: AUFNR
Level 2: AUFNR and POSNR
Level 3: AUFNR, POSNR and ETENR
In the ARun Workbench, when you are at level 1, the system displays one entry for each order.
When you drill down from level 1 to level 2, the system displays one entry for each combination of order number and item number.
On the third drill-down level, the system displays one entry for each combination of order/item/schedule line.
More Information
Creating Custom Reports in Order Allocation Run Workbench
1.9.5 Using Variants in Online and Batch ARun

Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific
selections. To select a certain set of data, you enter an appropriate range of values. If you often run the same program with the same set of selections, you can
save the values in a selection set called a variant.
Note
You can create any number of variants for any program in which selection screens are defined. Variants are assigned exclusively to the program for which
they were created.
PUBLIC
Page 53 of 68
Variants in Order Allocation Run

You can maintain variants in order allocation run using the online ARun transaction ARUN or transaction ARUN_VARIANT. These variants can be used during
online (dialog mode) and batch (background processing) ARun.
On the Variant Attributes tab page, if you select the Only for background processing checkbox, you cannot use these variants during an online ARun.
However, all variants selected for online ARun, can be used during a batch ARun.
For more information about defining variants, see Variant Maintenance in SAP Help Portal .
More Information
Execution of Order Allocation Run
Background Processing (Batch ARun)
1.9.6 Stock Protection in Order Allocation Run

In order allocation run (ARun), you can use the stock protection feature to set aside stock for certain segments that should be given the highest priority for their
orders or planned independent requirements (PIRs). When you execute ARun, the existing stock is set aside based on the priority of these segments. Stock is
allocated to lower priority segments only if sufficient stock remains.
Prerequisites
Select the Stock Protection checkbox in the article master for an article using the transactions MM41, 42,or 43.
Make the following changes to requirement or stock segments and PIRs:
Enter the segment strategies in Customizing under
Logistics - General
Segmentation Define Segmentation Strategies .
Select the Stock Protection checkbox for the relevant segment combination values (relevant for requirement segments) for which you want to use
stock protection. Also, you should enter the priorities for the above segment values. You can do this in Customizing under
Logistics - General
Segmentation Define Segmentation Strategies
Segment Strategies
Segment Combinations .
We recommend 1:1 mapping for requirement and PIR segments in Customizing under
Logistics - General
Segmentation Define Segmentation
Strategies
Segment Strategies
Planned Independent Requirements .
We recommend adding a segment priority field (CH_PRIO) in the requirement sorting rules in Customizing under
Logistics - General
SAP Fashion
Management
Online ARun
Sorting
Example
Consider the segments: Retail , e-commerce , and Wholesale . e-commerce has the priority 1, Retail has the priority 2, and Wholesale has the priority 3.
The system gives orders from the e-commerce segment higher priority and sets the stock aside for these orders. The system allocates stock to lower priority
segments only if sufficient stock remains.
Segment
Priority
Planned Forecast
e-commerce
1000
Retail
1000
Wholesale
1000
The total stock in the common stock pool is 3000.

An order from the e-commerce segment with a requirement of 600 is received.
The stock is allocated for this requirement. The stock available in the common pool is now 2400.
An order from the Retail segment with a requirement of 700 is received.
Before the stock is allocated for this requirement, the system sets aside the stock for unconsumed PIRs at the preceding priority level (1). In this case, stock
for 400 unconsumed PIRs is kept aside. The stock for this requirement of 700 is allocated since sufficient stock is available in the common stock pool. The
stock available in the common stock pool reduces to 1700.
An order from the Wholesale segment with a requirement of 1500 is received.
Before the stock is allocated for this requirement, the system sets aside stock for unconsumed PIRs at preceding priority levels (1 and 2). In this case,
stock for 400 unconsumed PIRs (e-commerce segment) and 300 unconsumed PIRs (Retail segment) is set aside. Although the stock available in the
common stock pool is 1700, 700 is set aside for unconsumed PIRs from higher priority segments. Therefore, for this order, only 1000 will be allocated.
Complete allocation is not possible for this order because the segments with the higher priority are given preference over the lower priority segments.
More Information
Stock Protection in ATP
1.9.7 Authorizations in Order Allocation Run

The system carries out an authorization check at the start of the transaction. You can authorize a user to execute the following operations:
Execute order allocation run (Online or Batch)
Order allocation run Workbench
Message Logging in ARun
PUBLIC
Page 54 of 68
Authorization Objects for Order Allocation Run

The following authorization objects are available:
ARUN_ON
This object controls the settings used to execute order allocation run (ARun) There are authorization checks at different levels. The allocation mode and type
are checked at the first screen and the ARun function code is checked at the results screen.
The following authorization field checks are available for this object:
Online ARun (ONLINEARUN): Allows you to execute online ARun. Set the value to 1 to execute ARun.
Batch ARun or /Background Processing (BATCHARUN): Allows you to execute ARun in background (Batch ARun). Set the value to 1 to execute ARun
in background.
ARun Mode (FSH_ARMD): Allows you to choose the modes (normal or simulation) that the system uses for allocation.
ARun Type (FSH_ARTYP): Allows you to choose the allocation type defined for the respective order allocation run.
ARUN_WB
This object controls the settings used to execute ARun Workbench. There are authorization checks at different levels. The ARun Workbench type is
checked at the first screen, the mode is checked at the selection screen, and the function codes are checked at the results screen.
The following authorization field checks are available for this object:
ARun Workbench Type (MTTYP) Allows you to choose an ARun Workbench type.
ARun Workbench Mode (MTMOD): Allows you to choose one of the following modes:
1 Normal
2 Display
ARUN Workbench Fcode (MTFCO): The following function codes are available:
1BLC Block
1DEA Deallocation
1RAL Allocation
1REL Release
ARUN_LOG
This object determines whether you can display or delete the logged messages in order allocation run (ARun).
The following authorization field checks are available:
LOGDISPLAY: Allows you to display log files (containing exceptions) occurred during the execution of ARun. Set the value as 1 for the authorization to
display log files.
LOGDELETE: Allows you to delete log files (containing exceptions) occurred during the execution of ARun. Set the value to 1 to for the authorization to
delete log files.
More Information
1.9.8 Special Order Types

You need to make certain order allocation run (ARun) settings for the following business transactions:
Rush Orders
Consignment Orders
Purchase-to-Order (PTO) Procurement
Allocation Against SD Contracts
1.9.8.1 Rush Order

For rush orders, you must assign an immediate allocation type to the sales document. The system then tries to allocate a requirement immediately when a sales
document is created or modified. A requirement can only be successfully allocated if there is sufficient stock (for example, physical stock or stock against future
receipts). It is assumed that only those goods are available for sales that actually exist in the warehouse. The stock situation remains clear. You can tell the
customer directly whether the ordered goods are available in the requested quantity. Note that the document must contain all delivery-related data when it is saved.
If it does not, the allocation is cancelled and the requirement cannot be delivered immediately.
You can assign an immediate allocation type to a sales document in Customizing under
Run (ARun)
Cross Applications
Sales Document Handling
Maintain ARun Types for Immediate Allocation .
Order Allocation
More Information
Special Order Types
1.9.8.2 Consignment Orders

During consignment order processing, order allocation run (ARun) is executed only for ARun-relevant articles. When you create an article, select the Order
Allocation Run checkbox in the Logistics: DC Fashion tab of the article master to specify if the article is ARun-relevant for a particular plant.
Process
PUBLIC
Page 55 of 68
If the article is not ARun-relevant, the consignment processing takes place as in standard ERP.
If the article is ARun-relevant, the system executes ARun during consignment processing. During the consignment processing, the system performs the following:
1. Automatically executes the immediate allocation run in the background during order creation if the following condition is satisfied:
You assiged the ARun rule (for immediate allocation) to the order type in Customizing for Assign Rule to Order Types under
Logistics - General
SAP Fashion Management Order Allocation Run (ARun) Cross-Applications
2. Automatically creates a delivery when you save the order based on the settings you defined in Customizing for Define Sales Document Type under
Sales and Distribution Sales
Sales Documents
If Immediate delivery = A, the system creates a delivery immediately for the order type.
If Immediate delivery is BLANK, the system only executes the allocation run and you must manually create the delivery for the order type.
Note
If you do not assign ARun rule for immediate allocation and Immediate delivery is BLANK, you must execute the online ARun after saving the order. In
addition, you must manually create the delivery.
Consignment fill-up
When you fill the consignment stock of the customer using the consignment fill-up document and you use an ARun relevant article, allocation should be triggered
before creating the delivery in addition to the standard procedure.
Consignment issue
When you withdraw the consignment stock during the sales process, you document this procedure by creating a consignment issue (order type KE in the SAP
system).
When you post a goods issue, the system deducts the relevant quantity from the customer's special stock and from your own valuated stock.
Logistics - General
Online ARun Selection . For example, for a selection rule, enable consignment stock and in
view segments enable MSKU-KULAB. Both are essential if you want to allocate consignment stock.
Consignment pick-up
Customers can return unused consignment stock to your companys warehouse using the consignment pick-up document. If the customer returns your
consignment stock, you document this procedure by creating a consignment pick-up (order type KA in the SAP system).
When you post the goods issue, the system removes the customers special stock for the corresponding quantity and posts it to the normal stock of the receiving
plant. Your total valuated stock remains the same since the returned stock was taken from your own inventory even while it was at the customers premises.
Logistics - General
SAP Fashion Management Order Allocation Run (ARun) Online ARun Selection . For example, for a selection rule, enable consignment stock and in
view segments, enable MSKU-KULAB. Both are essential if you want to allocate consignment stock.
Consignment return
Customers can return goods that were previously sold from the consignment stock using the consignment returns document. For this process you do not need an
order allocation run.
More Information
Consignment Processing

You can order a product from one or several vendors for one particular customer. In contrast to mass orders for the general market, the product in the purchase-toorder is especially designed for the customer so that it cannot be sold to other customers.
Process
To ensure that Purchase-to-orders (PTOs) are considered in order allocation run (ARun), select the Include Purchase-To-Order checkbox when you execute the
ARUN transaction.
In Purchase-to-Order processing, the order allocation run accesses the sales order stock during stock selection. For example, you must choose a stock selection
for a PTO that selects the sales order stock MSKA with the stock segment KALAB. The available segments for the stock type MSKA are KAINS and KASPE.
In Purchase-to-Order processing, it is not mandatory to execute an allocation run. To include PTO sales orders in order allocation run, select the Order Allocation
Required checkbox in Customizing for Maintain Order Allocation Run for Special Sales Documents under
Logistics - General
Cross-Applications
Shipping . You can create a delivery only if you have already executed the allocation.
More Information
Purchase-to-Order (PTO) Procurement

PUBLIC
Page 56 of 68

You can reserve Sales and Distribution (SD) contracts using the order allocation run (ARun) function. This allows you to physically reserve stock at the storage
location for your customers in advance. Within the contract validity period, customers can now request partial quantities without running the risk that their contract
might not be currently available.
You can process orders both with and without contracts in order allocation run. You can perform allocation for fashion contracts only.
Prerequisites
To allocate fashion-relevant contracts, select the Requirement Relevant checkbox in Customizing activity Maintain Sales Document Types for Fashion
Management under
Sales and Distribution
Sales
Sales Documents
Features
ARun uses different methods for determining the status of allocations. Fashion relevant contracts can only be assigned the status R (Reserved).
You can allocate available unrestricted stock to SD contracts using online ARun (in dialog mode) or batch ARun (background processing). You can also assign an
immediate allocation type to a SD contract to perform immediate allocation. The system can automatically create allocations for contract requirements by assigning
an ARun type to the appropriate contract document type. If you have entered an ARun type in Customizing for Sales Document Handling (under
Logistics General
Cross-Applications , then contract documents with that order type will automatically
have status R when they are saved, for the amount of unrestricted stock available.
If you have a sales order that references a contract (also called a contract release order), and an ARun type has been defined in Customizing for Sales Document
Handling , the system can automatically assign status F to the assigned quantity, depending on the release rule (define in Customizing under
Logistics General
Cross-Applications
Assign Sales Document Rules to Order Types ). This allows
follow-on deliveries to be created for the sales order. If a sales order references a contract, and the sales order quantity is less than the amount of stock with status
R in the contract, the sales order can be filled in one of the following ways, depending on the setting made in Customizing for Sales Document Handling :
If the sales order quantity is covered by the quantity with status R in the contract and meets the sales order release rule, the system assigns that quantity
the status F (Fixed) in the sales order, and the sales order can be delivered. If it does not meet the release rule, the system assigns the available quantity
the status R and the sales order is processed again in the next ARun until the appropriate quantity is available.
The sales order takes the available quantity with the status R in the contract, and the system assigns the remaining quantity from unrestricted stock to fill
the order requirements
For example: You have a contract for 100 pieces, only 50 with the status R . If you have a sales order for 70 pieces, then one of the following option is
applicable:
The sales order receives a quantity of 50 pieces (since that is all that is available in the contract) with status F , H (Fix and Hold) or R , depending on the
release rule.
The sales order receives a quantity of 50 pieces from the contract, plus 20 from unrestricted stock, so the entire 70 pieces is available for delivery and
receives status F .
It is possible to reduce, reject, or delete quantities in a sales order with reference to a contract. If you select the Restore checkbox for a contract order type in
Customizing for Sales Document Handling (under
Logistics - General
Cross-Applications
, the quantity subtracted from the sales order is returned to the contract.
In addition, if you want to return allocated quantities to the contract, you must select make the following settings. Otherwise, the system returns an error message
stating that deletion/reduction is not possible and the quantity remains reserved.
Select the Automatic deallocation checkbox for a contract order type in Customizing under
Sales and Distribution
Sales
Sales Documents
Sales Document Item Maintain Item Categories for Fashion Management .
Select the Restore checkbox for the contract order type in
Logistics - General
CrossApplications
Assign Rule to Order Types .
You can also specify in Customizing whether over-consumption is allowed or not. For example, if you have a contract for 100 pieces, overconsumption allows you
to create a sales order for 120 pieces with reference to the contract. However, if you later reduce the sales order to 5, then 95 pieces are returned to the contract
(100 5), and the remaining 20 (the over-consumed amount) go into unrestricted stock.
Example
The following examples explain how the system reacts to different contract scenarios:
Process
Condition
Result
Rejecting an item in an allocated contract
Automatic deallocation is active
The contract item is deallocated.
Automatic deallocation is not active
Error message: You cannot change item; item is

already allocated.
Canceling the reason for rejecting a contract item
Reducing an item quantity in an already allocated contract
Deleting an item from an allocated contract
The order type contains an ARun type
Reactivated items can be allocated to status R.
The order type does not contain an ARun type
Contract is saved.
Automatic deallocation of the contract item category is

active
The reduced quantity gets deallocated.
Automatic deallocation of the contract item category is not

active
Automatic deallocation is active
The item is deleted and the following message appears:

Item is de-allocated and deleted.
Automatic deallocation is not active
Error message: You cannot delete item, item is
PUBLIC
already allocated.
Page 57 of 68
already allocated.
Adding a quantity to an existing item in an already
reserved contract
The contract type contains an ARun type
The added quantity is allocated to status R .
The contract type does not contain an ARun type
Contract is saved (No further action is possible).
Creating a sales order with reference to an already

allocated contract
The sales order type contains a release rule
The sales order has status F , H or R . If the Fill-Up

checkbox is selected, the ARun type is maintained and the
quantity of sales order is more than the allocated quantity
of the contract, then the remaining quantity will be
allocated from the unrestricted stock.
Creating a sales order with reference to a non-allocated

contract
The sales order type does not contain a release rule
Status R of the contract is transferred to the sales order. If

the Fill-Up is selected, the ARun type is maintained and
the quantity of sales order is more than the allocated
quantity of the contract, then the remaining quantity will be
allocated from the unrestricted stock.
The sales order type contains an ARun type
The sales order can have status F or R , depending on

whether Customizing allows sales orders to be allocated
from the unrestricted stock.
Rejecting an item with status R or F within a sales order

(Contract release order)
Canceling the reason for rejecting an item in a sales order

(Contract release order)
Reducing the quantity of an item in an allocated sales

order (Contract release order)
The sales order type does not contain an ARun type
Sales order is saved (No further action is possible).
Automatic deallocation is active in the sales item category
The rejected quantity goes back to contract with status R

when the Restore checkbox is selected.
Automatic deallocation is not active in the sales item

category
The sales order type contains an ARun type
The reactivated item receives status F or R , depending

on the release rule
The sales order type does not contain an ARun type
Sales order is saved (No further action is possible).
already allocated.
Automatic deallocation is not active in the item category for Error message You cannot change item; item is
the material ordered in the sales order
already allocated.
Automatic deallocation is active in the item category for the The reduced quantity is returned to the contract with status
material ordered in the sales order, and the Restore setting R . The status of the sales order for the remaining item
for the contract order type is active
( R or F ) is unchanged.
Automatic deallocation is active in the item category for the The reduced quantity is returned to unrestricted stock. The
material ordered in the sales order, but the Restore setting status of the sales order of the remaining quantity (R or F)
for the contract order type is not active
is unchanged.
Deleting an item within an allocated sales order (Contract

release order)
Automatic deallocation is not active in the item category for Error message
the material ordered in the sales order
You cannot delete item, item is already
allocated.
Automatic deallocation is active in the item category for the The quantity of the deleted item is returned to the contract
material ordered in the sales order, and the Restore setting with status R .
for the contract order type is active
Automatic deallocation is active in the item category for the The quantity of the deleted item is returned to unrestricted
material ordered in the sales order, and the Restore setting stock.
for the contract order type is not active
More Information
Special Order Types
1.9.9 Cross-Applications in Order Allocation Run

The cross-application settings include all the order allocation run (ARun) settings pertaining to the different application areas. These settings define how each of
these areas interfaces with ARun. For more information about each application area, see the following sections:
Changing Sales Orders
Changing Stock Transport Orders
Changing Purchase Orders
Changes During Goods Receipt
Changes During Goods Issue
Quantities Reserved by Order Allocation Run in MRP
Quantities Reserved by Order Allocation Run in ATP
1.9.9.1 Changing Sales Orders

You control how the system reacts to changes in the allocated sales order by making settings in Customizing under
Management Order Allocation Run (ARun)
Cross-Applications
Logistics - General
SAP Fashion
Allocation and deallocation processes are the same for all types of stock, including future receipts. Therefore, if the confirmed quantity is decreased, the system
adjusts the corresponding assignments.
When you deallocate a sales order, the system locks the corresponding allocated stock (physical or future stock). If the stock cannot be locked, the system
generates an error message. The sales order can only be processed after the stock is unlocked.
PUBLIC
Page 58 of 68
Process
Deallocation Rule
You can use the deallocation rule to specify exactly how the system reacts when the sales order is modified. You can define a deallocation rule to deallocate or
remove the previously allocated quantities.
A deallocation rule contains the following fields:
Requirement Date of a Sales Order: You can specify a requirement date of a sales order. For example, if you choose Requested Delivery Date (VDATU) as
a requirement date, the system uses the Item level requested delivery date of a sales order.
Goods Receipt Date: This date is the reference date of the future receipt that is to be considered for deallocation. You can select Schedule Line Date
(EINDT) as a reference date.
Physical Stock Reference Dates: The Batch Horizon and Storage Location Horizon fields specify the number of days after which the deallocation can
occur for an order.
When you edit an existing allocated order and if the difference between the old requirement date and the new requirement date is less than the number of
days specified in the reference fields, then the deallocation does not occur. However, if this difference is more than the number of days specified in the
reference fields, system behavior is based on the values specified in the Date Reaction check field.
Future Stock Reference Dates: The From and To fields specify the range of days during which the deallocation should not occur.
When you change an existing allocated order and if the difference between the requirement date of a sales order and the goods receipt date for a purchase
order or confirmation is within the From and To field ranges, then the deallocation does not occur. If this difference does not fall within these field ranges,
then the system behaves based on the values specified in the Date Reaction check field.
Field Checks: The system decides how and when the deallocation process should be triggered based on the following values specified in the field checks:
D Deallocation Without Warnings: Order is deallocated completely without a warning.
W Warnings Before Deallocation: A warning message is displayed and the order is deallocated completely.
E Change Not Permitted: You cannot modify an order and deallocation is not possible.
Sort Rule
In ARun Customizing for sales documents, you can define the sequence in which the assigned stock is deallocated. In this way, you can specify which stock has
to be deallocated first. For example, if you want to sort first by stock type, then by batch number, then by purchase order number, you would make the following
entries:
Sort Field
Priority
FSH_BSKZ
FSH_BSNR
EBELN
Sort Descending
By selecting the Sort Descending indicator, you can reverse the sort order for a given field. For example, if select the Sort Descending indicator for purchase
orders (EBELN), the system deallocates the most recent purchase orders first.
Log Rule
Log Rule
During the deallocation of sales orders, you can use this rule to determine which of the following exceptions should be included in the log.
All messages
Only error messages
Errors and warnings
You can define the log file rule in Customizing under
Logistics - General
Log
Online ARun
The logs are saved in a database table.
Immediate Allocation of Sales Orders

You can also assign various ARun-specific functions to the sales documents. If you assign an immediate allocation type to the sales document, the system tries to
allocate a requirement immediately when a sales document is created or modified. A requirement can only be successfully allocated if there is sufficient stock (for
example, physical stock or stock against future receipts). Note that the document must contain all delivery-related data when it is saved. If it does not, the
allocation is cancelled and the requirement cannot be delivered immediately.
You can assign an immediate allocation type to a sales document in Customizing under
Run (ARun)
Cross Applications
Order Allocation
Assign Rules to Order Types

You can also assign an allocation type, deallocation, stock sorting, and logging rules to the SD document type and the sales area (sales organization, distribution
channel, and division). You can do this in Customizing under
Cross
Applications
Assign Rules to Order Types .
More Information

PUBLIC
Page 59 of 68

You control how the system reacts when an allocated stock transport order (STO) is changed by making settings in Customizing under
Cross-Applications
Stock Transport Order Handling .
Logistics - General
Process
Deallocation Rule
You use the deallocation rule to specify exactly how the system reacts when an STO is modified. You can define a deallocation rule to deallocate or remove the
previously allocated quantities.
A deallocation rule contains the following fields:
Requirement Date of a Sales Order and STO: You can specify a requirement date for a sales order and STO based on the available options.
Goods Receipt Date: This date is the reference date of the future receipt that is to be considered for deallocation. You can select Schedule Line Date
(EINDT) as a reference date.
Physical Stock Reference Dates: The Batch Horizon and Storage Location Horizon fields specify the number of days after which the order can be
deallocated.
When you edit an existing allocated order, and if the difference between the old requirement date and the new requirement date is less than the number of
days specified in the reference fields, then the deallocation does not occur. However, if this difference is more than the number of days specified in the
reference fields, the system behavior is based on the values specified in the Date Reaction field check.
Future Stock Reference Dates: These dates specify the range of days for the validity of the stock type.
When you change an existing allocated order and if difference between the requirement date of a STO and the goods receipt date for a purchase order or
confirmation is within the From and To field ranges, then the deallocation does not occur. If this difference does not fall within these field ranges, then the
system behaves based on the values specified in the Date Reaction field check.
Field Checks: The system decides how and when the deallocation process is triggered based on the following values specified in the field check:
Sort Rule
Requirement Sorting Rule
In Customizing for STO Handling , you can define a sort rule that the system uses to sort requirement elements during deallocation. You can use this sort
rule to specify the order in which requirements (sales orders and stock transport orders) are deallocated.
You can do this in Customizing under
Cross-Applications
Stock
Transport Order Handling
Define Requirement Sorting Rules .
Stock Sorting Rule
In Customizing for STO Handling , you can define a sort rule that the system uses to sort stock elements during deallocation. You can use the deallocation
sort rule to specify the order in which stock types (physical stock, purchase orders, shipping notifications, and confirmations) are deallocated.
You can do this in Customizing under
Cross-Applications
Stock
Transport Order Handling
Define Stock Sorting Rules .
Log Rule
During the deallocation of STOs, you can use this rule to determine which of the following exceptions are included in the log.
All messages
Only error messages
Errors and warnings
The logs are saved in a database table. You can define the log file rule in Customizing under
Allocation Run (ARun)
Online ARun
Log
Logistics - General
Order
Immediate Allocation of STO

You can define an immediate allocation type for an STO in Customizing under
(ARun)
Cross-Applications
Stock Transport Order Handling
You can assign an immediate allocation type to an STO in Customizing under

(ARun)
Cross-Applications
Stock Transport Order Handling Define Allocation for Stock Transport Orders .
When you assign an immediate allocation type to an STO, the system tries to allocate a requirement immediately whenever the STO is created or modified. A
requirement can only be successfully allocated if there is sufficient stock (for example, physical stock or stock against future receipts). Note that the document
must contain all shipping-related data when it is saved. If it does not, the allocation is cancelled and the requirement cannot be delivered immediately.
For immediate allocation of STOs, you must activate the Automatic Delivery Creation option. If you want to create a delivery immediately after creation of the stock
transport order, set the Auto Delv. option. You can do this in Customizing under
Material Management
Purchasing
Purchase Order Set Up Stock
Transport Order .
You can assign an allocation type for a stock transport order based on the purchasing document type and the supplying (issuing) plant in Customizing under
Cross-Applications
Define
Allocation for Stock Transport Orders .
Assign Stock Transport Order Rules to Plants

You can assign deallocation, requirement sorting, stock sorting, and logging rules to each plant. If the STOs are consumed as stock, use the requirement sorting
PUBLIC
Page 60 of 68
rule. If the stock transport orders are considered as requirements, then use the stock sorting rule. You can assign these rules in Customizing under
Logistics General SAP Fashion Management Order Allocation Run (ARun)
Cross-Applications
Assign Stock Transport
Order Rules to Plants .
More Information
1.9.9.3 Changing Purchase Orders

You control how the system reacts to changes when an allocated purchase order is changed by making settings in Customizing under
Cross-Applications
Purchase Order Handling .
Logistics- General
When you deallocate a purchase order, all allocated sales orders and stock transport orders are locked. If an order cannot be locked, the system generates an
error message. The purchase order can only be processed when the locked order is unlocked.
Process
Deallocation Rule
In order allocation run Customizing for Purchase Order Handling , you can define deallocation rules to be used when purchase orders are changed. You can
define a deallocation rule to deallocate or remove the previously allocated quantities
Requirement Date of a sales order and stock transport order: You can specify a requirement date for a sales order and STO based on the available options.
For example, if you choose Requested Delivery Date (VDATU) as a requirement date, the system considers the Item level requested delivery date of a
sales order.
Future Stock Reference Dates: The From and To fields specify the range of days during which the deallocation should not occur.
When you change an existing allocated order and if the difference between the requirement date of a sales order or STO and the goods receipt date for a
purchase order or confirmation is within the From and To field ranges, then the deallocation does not occur. If this difference does not fall within these field
ranges, then the system behaves based on the values specified in the Date Reaction field check.
Field Checks: The system decides how and when the deallocation process should be triggered based on the following values specified in the field check:
For confirmations, the Restore checkbox determines whether assignments for a shipping notification are returned to the purchase order or deallocated.
Log Rule
The log rule determines the log file rule to be used for actions taken by the system during purchase order handling. You can define the log file rule in Customizing
under
Logistics - General
Online ARun
Log
You can use the log rule to determine which of the following exceptions should be considered in the log.
All messages
Only error messages
Errors and warnings
Sort Rule
In ARun Customizing for purchase order handling, you can define how the system sorts requirements when it performs deallocation. You can use this sort rule to
specify the order in which requirements are deallocated.
Assign Purchase Order Rules to Plants

You can also assign a deallocation rule, requirement sorting rule, and logging rule to a plant. You can do this in Customizing under
Logistics - General
Fashion Management
Cross Applications
Purchase Order Handling
Assign Purchase Order Rules to Plants .
SAP
More Information
1.9.9.4 Changes During Goods Receipt

You control how the system reacts to changes during goods receipt processing by making settings in Customizing under
Logistics - General
Management SAP Fashion Management
Order Allocation Run (ARun) Cross-Applications
Goods Receipt Handling .
SAP Fashion
During goods receipt processing, one of the following scenarios may occur:
Complete delivery
Partial delivery
Partial delivery with delivery complete indicator (DCI)
Late delivery (for example, past the cancellation date)
PUBLIC
Page 61 of 68
Complete delivery, but goods are different from the originally ordered (for example, change of segment)
Process
Deallocation Rule
In order allocation run Customizing for Goods Receipt Handling , you can define deallocation rules to be used during goods receipts. You can define a deallocation
rule to deallocate or remove the previously allocated quantities by entering values in the following fields:
Requirement Date of a sales order and STO: You can specify a requirement date for a sales order and STO based on the available options.
Physical Stock Reference Dates: The Batch Horizon and Storage Location Horizon fields specify the number of days after which the deallocation can
occur for an order.
When you edit an existing allocated order and if the difference between the requirement date and the posting date is less than the number of days specified
in the reference fields, then the deallocation does not occur. However, if this difference is more than the number of days specified in the reference fields,
system behavior is based on values specified in the Date Reaction field check.
Field Checks: The system decides how and when the deallocation process should be triggered based on the following values specified in the field check:

In Customizing for Goods Receipt Handling , you can define how the system sorts requirements during deallocation. You can use the sort rule to specify the order
in which requirements are deallocated. For example, the requirements with the latest open-to-deliver date is deallocated first.
Log Rule
The log rule determines the log file rule to be used for actions taken by the system during Goods Receipt Handling . You can define the log file rule in Customizing
under
Logistics - General
Online ARun
Log
You can use the log rule to determine which of the following exceptions should be included in the log.
All messages
Only error messages
Errors and warnings
Assign Goods Receipt Rules to Plants

You can assign a deallocation rule, requirement sorting rule, and logging rule to a plant. You can do this in Customizing under
Logistics - General
SAP
Fashion Management SAP Fashion Management
Order Allocation Run (ARun) Cross-Applications
Goods Receipt Handling
Assign Goods Receipt
Rules to Plants .
More Information
1.9.9.5 Changes During Goods Issue

You control how the system reacts to changes during goods issue posting by making settings in Customizing under
Management
Cross-Applications
Goods Issue Handling .
Logistics - General
SAP Fashion
Prerequisites
You have assigned a deallocation rule to the relevant plant in Customizing under
Logistics - General
Order Allocation
Run Cross-Applications
Goods Issue Handling
Assign Goods Issue Rules to Plants .
You have activated automatic deallocation for the goods issue at movement type level in Customizing under
Logistics - General
SAP Fashion
Management Order Allocation Run
Cross-Applications
Goods Issue Handling Activate Deallocation Per Movement Type .
Process
Deallocation Rule
In order allocation run Customizing for Goods Issue Handling , you can define deallocation rules to be used during goods issue. These rules determine whether the
deallocation is permitted or not when the original quantity of an order is modified. You can choose one of the following actions for the Quantity field check:
D Deallocation Without Warnings: Order is deallocated completely without any warnings.
PUBLIC
Page 62 of 68
In ARun Customizing for Goods Issue Handling , you can define how the system sorts requirements during deallocation. You can use this sort rule to specify the
order in which requirements are deallocated. For example, the requirement with the latest open-to-deliver date is deallocated first.
Log Rule
The log rule determines the log file rule to be used for actions taken by the system during Goods Issue Handling . You can define the log file rule in Customizing
under
Logistics - General
Online ARun
Log
You can use the log rule to determine which of the following exceptions are included in the log.
All messages
Only error messages
Errors and warnings
Assign Goods Issue Rules to Plants

You can assign a deallocation rule, requirement sorting rule, and logging rule to a plant. You can do this in Customizing under
Logistics - General
Fashion Management
Order Allocation Run Cross-Applications
Goods Issue Handling -> Assign Goods Issue Rules to Plants
SAP
Activate Deallocation Per Movement Type

You can activate the deallocation function for each individual movement type. In this case, the system automatically deallocates stock during goods issue when
you assign the goods issue deallocation rules to a plant.
More Information
1.9.9.6 Quantities Reserved by Order Allocation Run in MRP

The results from order allocation run (ARun) impact the net-requirement calculation during MRP run. Hence, MRP considers the quantities reserved by order
allocation run for requirements and stock or receipts.
Prerequisites
You have created an article that is relevant for order allocation run
You have executed the order allocation run
Features
During the planning run, the system checks for the stock or future receipts that are already allocated to the requirements during the order allocation run. Since the
available stock or future receipts and requirements are already allocated, the system cannot consume them during the MRP run. Therefore, the system proposes
a new procurement proposal for the requirements.
Example
Assume the following:
Oct 9, 2013: Batch stock of 50 pieces
Oct 16, 2013: Purchase order for 50 pieces
Nov. 3, 2013: Sales order (4711) for 100 pieces
1. Order allocation run allocates the available batch stock and the purchase order to sales order #4712.
MRP result
PUBLIC
Page 63 of 68
2. During the MRP run, the system proposes a new proposal, for example purchase requisition, for sales order #4711 dated Nov. 3, 2013.
Quantities reserved by Order Allocation Run is considered during MRP
Note
For an article that is not relevant for order allocation run or if the order allocation run is not executed, MRP always procures at the latest date, and may even fail
to fulfill the requirements in certain cases.
1.9.9.7 Quantities Reserved by Order Allocation Run in ATP

The results from the order allocation run (ARun) impact the availability of stock during the availability check. Hence, the availability check considers the quantities
that are already reserved by the order allocation run for requirements and stock/receipts.
Prerequisites
You have created an article that is relevant for order allocation run
You have executed the order allocation run for the article
Features
During the availability check, the system checks for the stock or future receipts that are already allocated to the requirements during the order allocation run. Since
the available stock or future receipts and requirements are already allocated, the system does not consider them as available quantity during the availability
check. Therefore, availability check can promise only the remaining stock for any future requirements.
Example
Assume the following:
Oct. 9, 2013: Batch stock of 100 pieces
Oct. 16, 2013: Purchase order for 100 pieces
1. Order allocation run allocates the available batch stock to sales order #4712.
PUBLIC
Page 64 of 68
Result from Order Allocation Run
2. During the availability check for a new requirement (sales order #4711 requires 150 pieces), as the batch stock is already allocated to a requirement, the
system only proposes the remaining quantity of stock or future receipts and requirement as the ATP quantity. That is, the availability check promises the
purchase order of quantity 100 pieces and the remaining 50 pieces will be delivered later.
Results from Availability Check
1.10 Mass Maintenance of Fashion Master Data

Maintaining master data can be time-consuming if you have to make each change individually. It is quicker to make one change and have the system
automatically update all the affected records automatically. The mass maintenance tool enables you to change a large group of master data records at once.
You can select the mass maintenance tool within a number of master data transactions. All these mass maintenance tools are based on the same basic
framework and user interface.
Features
You can mass maintain data related to the following segmentation related enhancements made to article master:
segmentation structure
segmentation strategy
fix segmentation
consumption priority
stock protection indicator
discreet batch management
PUBLIC
Page 65 of 68
weights and volumes

sales status
You can mass maintain data related to the following SAP Fashion Management enhancements made to article master:
season
season usage
fashion attributes
order allocation run (ARun)
Mass changes made at the generic article level will also be applied to all the variants of the generic article.
For segmentation fields, once segmentation value has been fixed at the variant level for an article, changes made to the data through mass maintenance will not
be applied.
1.11 Product Number Creation

SAP Global Trade Services (GTS) helps companies better manage global trade operations, ensure ongoing trade compliance, and optimize the cross-border
supply chain.
Fashion articles involve global trade operation. Fashion articles manufactured in a particular country may be sold in various other countries and geographical
location. To ensure such fashion articles comply with trade and goods movement agreements between countries, the fashion articles are expected to have product
numbers in complaint format. Once the product numbers are generated, you can use the pricing data maintained in SAP Fashion Management in the SAP GTS
system.
Procedure
1. To create reference product numbers and save them to the fashion database, on the SAP Easy Access Retailing (transaction W10M) menu , choose
GTS Integration
Generate Product Number for GTS Transfer
. Alternatively, you use the transaction FSH_PROD to
create reference product numbers and save them to the fashion database.
Note
For articles that are not segmentation relevant, the product number is same as the article number.
For articles that are segmentation relevant, the product number is a combination of the article number and segmentation data.
2. Use transaction /SAPSLL/MATMAS_DIRR3 to generate product numbers in the SAP GTS system. This also transfers the master data, such as weights
and volumes, unit of measure, and product description maintained in SAP Fashion Management to the SAP GTS system.
3. Use transaction /SAPSLL/PRCMAT_DIRR3 to transfer pricing data from the SAP Fashion Management system to the SAP GTS system.
Note
You can attach the tariff codes in the SAP GTS system after step 2 or step 3 and carry out GTS-relevant activities.
Result
Product numbers are generated using the SAP GTS system.
1.12 Adjusting Screen Sequences in Fashion Management

Procedure
Define Structure of Data Screens for Each Screen Sequence
In the Customizing, choose
Logistics - General Material Master
Sequence . Then proceed with the following steps:
Configuring the Material Master
Define Structure of Data Screens for Each Screen
1. Select the screen sequence used by the customer (for example, Z5 ). Do not change any of the screen sequences delivered by SAP (for example, 23 ,
33 ). If necessary, you can copy a screen sequence delivered by SAP into the customer namespace.
2. Double-click Data Screens .
3. Use the pushbutton New Entries to insert a new data screen, with the following information:
Field
Entry
SSq
Z5 (example)
Scrn
56 (if not yet used, else next free number)
Screen description
Basic Data: Fashion (example)
SCon
4004
Maint. status
EDLVBK
GUI status
DATE00
TT
Ret.maint.status
02
PUBLIC
Page 66 of 68
Alt. screen descrip.
4.
5.
6.
7.
Basic Data: Fashion (example)
Use Back (F3) to return to the display of the data screens.

Select the newly inserted data screen.
Select the node Subscreens with a double click.
In the field Scr. of an unused line, replace subscreen 0001 with 2010; in the field Program , replace program SAPLMGD2 with
SAPLFSH_ARTICLE_MASTER.
8. In the field Scr. of another unused line, replace subscreen 0001 with 2000; in the field Program , replace program SAPLMGD2 with
SAPLFSH_ARTICLE_MASTER_FASH.
10. Save your changes.
Define Structure of Data Screens for Each Screen Sequence
Sequence . Then proceed with the following steps:
Define Structure of Data Screens for Each Screen
1. Select the screen sequence used by the customer (for example, Z5 ). Do not change any of the screen sequences delivered by SAP (for example, 23 ,
33 ). If necessary, you can copy a screen sequence delivered by SAP into the customer namespace.
2. Double-click Data Screens .
3. Use the pushbutton New Entries to insert a new data screen, with the following information:
Field
4.
5.
6.
7.
Entry
SSq
Z5 (example)
Scrn
56 (if not yet used, else next free number)
Screen description
Logistics: DC Fashion (example)
SCon
4004
Maint. status
EDLPVBQSAG
GUI status
DATE00
TT
Ret.maint.status
Alt. screen descrip.
Logistics: DC Fashion (example)
Use Back (F3) to return to the display of the data screens.

Select the newly inserted data screen.
Select the node Subscreens with a double click.
In the field Scr. of an unused line, replace subscreen 0001 with 3000; in the field Program , replace program SAPLMGD2 with
SAPLFSH_ARTICLE_SEASON_ASSIGN.
Assign Secondary Screens
following steps:
Logistics - General
Material Master
Assign Secondary Screens
. Then proceed with the
1. Select the screen sequence defined earlier (for example, Z5 ), and choose the pushbutton Details .
2. In the line with the new data screen (for example, 24 ) for Weights and Volumes (example), choose Create Pushbutton FCode , whereby an automatically
assigned FCode, for example, PB03 , should be shown.
3. In the line with the new data screen (for example, 24 ) for Weights and Volumes (example), choose the pushbutton Add to Additional Screens , whereby
a number automatically assigned to the additional screen, for example, 12 , should appear in the column Additional .
5. In the line with the new data screen (for example, 25 ) for Sales-Segmentation (example), choose Create Pushbutton FCode , whereby an automatically
assigned FCode, for example, PB04 , should be shown.
6. In the line with the new data screen (for example, 25 ) for Sales-Segmentation (example), choose the pushbutton Add to Additional Screens , whereby a
number automatically assigned to the additional screen, for example, 13 , should appear in the column Additional .
8. In the line with the new data screen (for example, 26 ) for Segmentation-Sales status (example), enter the FCode PB66.
Note
As function code PB66 is assigned to Segmentation-Sales Status (example) button. Hence, the function code PB66 has to be manually assigned.
Maintain Order of Main and Additional Screens
Logistics - General
Material Master
PUBLIC
Maintain Order of Main and Additional Screens
Page 67 of 68
Then proceed with the following steps:

1. Select the screen sequence defined earlier (for example, Z5 ), and choose the pushbutton Details .
2. In the screen area Order of Main Screens , you can move the new data screen (for example, 21 ) for retail between the tab page for sales and the tab
page for purchasing. You do this by reducing the position number (for example, from 100 to 10 ) and choosing the pushbutton Sort Main Screens .
3. In the screen area Order of Addnl Screens , you can move the new data screen (for example, 24 ) for the textile composition between the tab page for the
short texts and the tab page for the units of measure. You do this by reducing the position number (for example, from 120 to 15 ) and choosing the
pushbutton Sort Addnl Screens .
Check that the changed screen sequence (for example, Z5 ) is assigned to your user, and that it is applied in correspondence with all influencing
factors (Customizing activity Assign Screen Sequences to User/Article Type/Transaction/Industry Sector ) when article maintenance is called.
Call article maintenance (transaction MM43/MM42) to check that, in the view Basic Data , via the pushbutton Additional Data , a new tab page is
available that contains the subscreen for retail with segmentation data.
Assign Screen Sequences to User/Material Type/Transaction/Industry Sector
Type/Transaction/Industry Sector . Then proceed with the following steps:
Assign Screen Sequences to User/Material
1. Use the pushbutton New Entries to assign a new screen sequence to one or more new combinations of transactions, users, material types, and/or industry
sectors. You can use the screen sequence defined in the previous procedure (for example, Z5 ) as the SSq .
Activate New Pushbuttons
1. Execute transaction SM30.
2. Enter V_T133D as the Table/View and choose Edit .
3. Choose New Entries and enter the information in the following table:
SSq
Scrn
Code
SScrn
Z5 (example)
21 (example)
FSEG
21 (example)
Z5 (example)
21 (example)
SEAU
21 (example)
Z5 (example)
21 (example)
SEGR
21 (example)
Z5 (example)
23 (example)
FSBM
23 (example)
Z5 (example)
23 (example)
FSDB
23 (example)
Z5 (example)
23 (example)
FSGT
23 (example)
Z5 (example)
23 (example)
FSAR
23 (example)
Z5 (example)
23 (example)
FSEA
23 (example)

Activate New Pushbuttons
1. Execute transaction SM30.
2. Enter V_T133E as the Table/View and choose Edit .
3. Choose New Entries and enter the information in the following table:
SSq
Code
Spec
Z5 (example)
FSEG
select
Z5 (example)
SEAU
select
Z5 (example)
SEGR
select
Z5 (example)
FSBM
select
Z5 (example)
FSDB
select
Z5 (example)
FSGT
select
Z5 (example)
FSAR
select
Z5 (example)
FSEA
select
Note
The field selection group 141 (transaction OMSR) is delivered by SAP for Segmentation related functionality.
The field selection group 207 (transaction OMSR) is delivered by SAP for SAP Fashion Management.
PUBLIC
Page 68 of 68

SAP Fashion Management PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Fashion Management PDF

Uploaded by

Copyright:

Available Formats

SAP Fashion Management

PDF download from SAP Help Portal:

1.9.1.6.4 Logic to Determine Release Rule

1 SAP Fashion Management