Professional Documents
Culture Documents
Functional Overwiew Part1 FMS
Functional Overwiew Part1 FMS
Functional Overwiew Part1 FMS
The growth of private label and the margin and marketing benefits of growing own
retail has led to brands supporting multiple sales channels:
Wholesalers and Manufacturers are expanding sales channels into retail, digital and
mobile
Retailers with strong brands are expanding sales channels into wholesale
Retailers realize they need more sophisticated solutions to get the value from long,
global apparel, footwear and fashion supply chains
Systems evolved separately to support each business, so companies often use two
ERP solutions (one AFS, one Retail) and two separate sets of business suite
applications around each ERP.
Remark: not all topics are covered in this presentation (e.g. Assortment
Planning, Retail Promotion, Retail Markdowns)
10
11
12
13
14
15
16
The season check is identically for manually entered seasons and system
determined season.
17
18
Further Notes:
Advanced Shipping Notification (ASN):
When creating ASN with reference to purchase order, season information is copied
from PO
System validates information regarding season, collection, and theme during ASN
processing
19
20
This slide shows a general overview of how conversion type identifier is linked
to article master, vendor master and customer master records so that when a
combination of the article and customer / vendor is used in a process
document, then appropriate value conversion gets applied to the article / variant
description by default.
21
22
Purchase Contracts:
Document and item based conversion of characteristic values is possible in
contracts
23
24
25
26
27
28
29
30
31
32
33
34
Use case stock protection with physical separation: Instead of using real values
for channel (e.g. Wholesale, Retail) you can also use e.g. the value common
for all channels: Common QualityA, Common QualityB.
35
Scope 2
36
37
38
All sales relevant document types have been enhanced to support fashion
specific data:
Inquiries
Quotations
Contracts
Sales Orders
Deliveries
Billing
39
40
41
42
43
44
Plant
Release date
Delivery date
Supplying plant (in stock transport requisition)
Supplier or vendor (in external procurement)
Account assignment category
Purchasing organization
Purchasing group
Requirement segments
Stock segments
Document Type
Document Category (Item category)
Storage Location
45
46
47
48
Retailers often have to centrally distribute merchandise among a large number of recipients (for
example, stores). One example would be fashion merchandise or promotional items. Using
allocation tables, you can plan the distribution of this type of merchandise and then trigger the
necessary goods movements.
An allocation table is a tool for planning merchandise distribution used by a head office to
plan, control, and monitor supplies to sites (stores, distribution centers). It is used, for example,
in initial
distribution of articles, distribution of promotional goods, distribution of stocks, and distribution
of imported goods procured centrally.
You create an allocation table in SAP Retail to split up a specific quantity of merchandise. The
allocation table contains all the important information on the how the merchandise is to be
distributed, such as the articles to be allocated, the source of supply, the recipients, the quantity
each is to receive and the delivery dates.
You also determine the goods movements (for example, direct-store-delivery) at this point. You
can have the system propose the sites. To do this, you enter an allocation rule or a site group.
You can include your own allocation strategy. You can change any default data suggested by
the system.
Allocation strategy
The allocation strategy defines how the system calculates the planned quantities for the
recipients. A strategy can process data from SAP Retail, but also data from SAP BI (for
example, sales history).
Some allocation strategies are included in the scope of delivery, others can be created by you.
You can use an allocation strategy instead of an allocation rule or manual distribution.
You can maintain an allocation strategy in the Customizing settings for the allocation table type.
This strategy is proposed in the allocation table at item level.
49
50
51
52
53
54
55
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 neither displayed nor considered for processing inside the purchase
order.
56
57
58
Depending on the use case there are different Customizing entries to set up the
requirement segment determination:
A) If the site is relevant for segmentation (e.g. DC) and is supplying to site relevant for
segmentation (e.g. DC) the requirement segment is determined based on the stock
segment in one of the following ways:
Priority 1: Based on the segment value you maintain in the Customizing Logistics General
-> Segmentation -> Define Segmentation Strategies
Priority 2: Based on the default segment you maintain in the Customizing Logistics
General -> Segmentation -> Define Segmentation Structures
B) Site relevant for segmentation (e.g. DC) is supplying to site not relevant for
segmentation (e.g. Store). The appropriate requirement segment is determined in one
of the following ways:
Priority 1: Based on the segment value assignment you maintain in the
Customizing Logistics General -> Segmentation -> Define Requirement Segment for
Supplying Plants
Priority 2: Based on the default stock segment you maintain in the Customizing
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
59
60
61
62
63
64
Prerequisite
In IMG: split valuation is activated and configured
In the characteristic for segmentation (e.g. Quality), TA = CT04:
In article master:
Article is segmented
In Accounting Distribution Channel Data:
Valuation Category X is enabled to do new value calculation during batch creations and
updates
(For each segment value both, standard price and moving average price can be used)
65
66
67
68