Partner Ws April 21

7/24/2019 Partner Ws April 21

1/36

SAP Fashion Management 1.5

Online Knowledge Transfer Workshop

April 21, 2015


2/36

SAP Fashion Management

overview & outlook


3/36

2015 SAP AG or an SAP affiliate company. All rights reserved. 3Partner Enablement

Overall SAP Fashion Management scope

and outlook

Master Data

Procurement

(P2P)

Manufacturing*

Sales

(O2C)

Planning

Planned

Order*

Production

Order*

MarkersProduction

Lots*

Valuation/Product

Costing*

OrderInformation

System*

Inventory Management

Purchase

Requisition

Purchase

OrderASN

Invoice

Verification

Seasonal

Procurement

Goods

Receipt

Inventory

Mgmt.

Warehouse

Mgmt

Merchandise

Distribution

Merchandising

MRPSize

Distribution*OAPC

Replenish-

ment / VMI

Retail

AllocationPIR

Article

Master

Seasons &

Collections #

Customer

Master

Vendor

Master

Segment-

ation

ValueAdded

Services #

Size Con-

version*

Site

Master

PricingRetail

Promotions

Retail

MarkdownsIn-Store

MIM

Listing,

Assortment

& Layout

SalesOrder

AllocationRun

Shipping BillingPOSOutbound

ATP, Re-Scheduling

Covered in Release 2.0*

Retail specific f unctionality

Retail & Wholesale functionality

Manufacturing

# limitations apply

Covered in Release 2.0


4/36


SAP Fashion Management process overview

By Retail / Wholesale

Organizational Structures / Master data / VAS / Seasons / Segmentation

Demandplanning

Supplyplanning(MRP)

Procure-ment

Retail

alloca-tion

DCInventory

Invoiceverifica-tion

Orderalloca-tion

Logisticsfulfillment

Billing

Earlycustomer

ordering

Storereplenish-ment

B2Corders

Store

opera-tions

In-season

ordering

Assort-

mentplanning

ATPRescheduling

In-season

ordering

Whole-sales

planning

RetailWholesale


5/36

Key functionalities:

ARun


6/36


SAP Fashion Management Order Allocation Run

Overview

Stock

Warehouse stock

Future stock

Requirements

Wholesale

Retail

E-Commerce

Al location

Optional

Online

Batch

Simulation

Prioritization

rulesManual changes

MRP

relevant


7/36



Overview What can be Allocated

Stock

Warehouse stock

With batch management

Without batch

management

Future stock

Purchase orders

Shipping Notifications

(Production orders

Release 2)

Vendor Customer

Store

DC 1

DC 2

PO SO

STO

STO

Stock

Requirements

Sales documents

Sales orders

Fashion quantity

contracts

Purchase documents

Stock transport

orders


8/36



Allocation Process Overview

Selection Grouping Sorting Allocation Release

Order

EntryATP Order Save Allocation Delivery Invoice

ImmediateAllocation

Allocation

Workbench

Allocation results can be changed with the allocation workbench

Rush sales orders can be allocated immediately

If allocation is activated in the article master site view any sales order or stocktransport order needs to be allocated before a delivery can be created.


9/36



Overview of ARUN Transaction Result Screen

The result screen typically shows:

Selected requirements Confirmed order quantity and

allocated quantity

Allocated stock / PO with

details

Allocation status

SAP Fashion Managementinformation like season and

segmentation

Exception messages

SAP Fashion Management offers three

Al locations Statuses which are determined

during the release check:

F the requested fulfillment rate is met, the

delivery can be created.

H the requested fulfillment rate is met but a

manual release to F is necessary before

deliveries can be created.

R the requested fulfillment rate is not met but

the available quantities are still allocated.

Contracts and future stock is always allocated

in R regardless of the fulfillment rate.


10/36



Process Overview

Rules for stock

selection

Batch stock

Storage locationstock

Stock segments

like unrestricted,

quality inspection,..

Future stock:

purchase orders

and inbound

deliveries

Filter options Season

Credit

Cancel date

violation

Temporary

grouping during

runtime

According tovarious fields used

in sales orders and

stock transport

orders

Sorting of

requirements

According to

various fields used

in sales orders and

stock transport

orders

Sorting of stock

According to fields

used in stock and

purchase orders

Allocation logic

FIFO following

the requirement

sorting

Spread stock

distribution in group

Allocation rule

Dynamic sorting for

future stock

allocation

Release Rule

Percentage driven

checks on allocated

quantities

Different levels in

order (item, item-

groups, header,)

Flexible release

rule determination

Selection Grouping Sorting Allocation Release

Every ARun Type executes a set of rules. This is an overview what these rules areused for:


11/36



Overview Allocation Workbench

Allocate

Release

Block

de-allocate

Display / Change

Release CheckNEW


12/36


System Demo


13/36


Segmentation


14/36


Segmentation

Elements of Segmentation

Segmentation

Elements

Segmentation Scope:

Defines relevancy of segmentation for both requirementand stock segments or only requirement only

Segmentation Strategy:defines how segments are handled in different situations,

i.e. MRP supply proposal, ARun handling of sales orders,

planned independent requirement consumption

Segmentation Structure:

segments used, i.e. quality, channel, country of origin etc.

Also defines possible values for each segment


15/36


Segmentation

Examples

* The system does not distinguish between physical and logical segmentation

Logical

Segmentation*

Channel/Market

Sub-Channel/Region

Quality

Country of Origin

Customer specific

Physical

Segmentation*

Segmentation


16/36


Segmentation

Overview

Definition of

characteristics

for segmentation

and values

Definition of

segmentation

strategies Assign to article

master

Sales OrdersSales

DocumentsSales Orders

Stock

Transfer

Orders *

Sales OrdersPurchase

OrdersSales OrdersPurchase

RequisitionsSales Orders

Planned

Independent

Requirements

Warehouse Stock

Stock Segmentation Requirement Segmentation

*Stock transfer from segmented location to segmented location STO can carry requirement and stock segment

Stock transfer from segmented location to not segmented location STO can only carry requirement segment


17/36


Sales OrdersSales

DocumentsSales Orders

Stock

Transfer

Orders

Sales OrdersPlanned

Independent

Requirements

Sales OrdersStock

Transfer

Orders

Sales OrdersPurchase

OrdersSales OrdersPurchase

Requisitions

Warehouse Stock

Stock Segmentation

Requirement Segmentation

Segmentationstrategies


18/36


Segmentation

Define Characteristic ( Part 1)

Transaction CT04

Basic data:

The characteristic must be

assigned to characteristic group:

SGT_SAP-C Segmentation

Characteristic

Only characteristic with data type

CHAR are supported

Values:

The possible values are assignedto the characteristic


19/36


Segmentation

Define Characteristic ( Part 2)

Addi tional data:

Relevance for some applications can be

defined for segmentation characteristics.

BOM Component Selection by Segment

ROU Routing Selection by SegmentWM1 Warehouse segmentation data

WM2 Storage type segmentation data

NEW


20/36


Segmentation

Definition of Segmentation Strategies of Structure (2)

Enter allowed segmentation values.If you use stock protection: enter the priority sequence of

segment combinations and activate stock protection.

Specify how the requirement segments use the stock segments

during the material requirements planning run, allocation run and

ATP (if the entry below is not maintained)

Specify how the requirement segments are assigned to the

stock segments during the availability check.

You can define common stock pools.

Define the assignment of stock segments to requirementssegments between two sites (plants).

The assignment in this table is used when the dependent

requirement is generated.

Define the stock segment to be proposed for a specific

requirement when the system creates new proposals

Define the requirement segments of the PIRs and the

requirements segments of customer requirement that consumes

the requirement segments of the PIRs

Displays the consolidated mapping rules the system generateswhen you save the following transactions:

Requirement/stock allocation

Stock transfer

Requirement to stock conversion

Planned independent requirements consumption


21/36


Segmentation

Segment Combinations

Segment ValueA1

A2

B1

B2

C1

C2

Segmentation structure with 2segments:

Country: A, B, C

Quality: 1, 2

Stock

protection-

relevant

All combinations are allowed.

It could also make sense that e.g.

country C can not have a second

quality because it is never sold

there C2 would not be set up inthis case


22/36


Segmentation

Requirement / Stock Allocation

Req Seg. CoNo Stock Seg.A1 1 A1

A2 1 A2

A2 2 A1

B2 1 B1

*1 1 *1

*2 1 *2

*2 2 *1

Quality 1 requirements have

to be covered with first

quality stock. Quality 2requirements (e.g. for outlet)

can be fulfilled with second

quality as well


23/36


Segmentation

Material Segmentation in Manufacturing Processes

SAP Fashion Management will support manufacturing of structured articles in

release 2.0.

The standard functionality of segmentation however has already been further rolled

out to support manufacturing of segmented materials.

The supported functionalities include:

Material bill of material (BOM)

Routing

Planned orders

Production orders

Order progress report

NEW


24/36


Segmentation

Summary of prerequisites

Prerequisites for usage of segmentation within purchasing processes You have activated the business functionMaterial Segmentation Across Logistics

(LOG_SEGMENTATION)

You have created the characteristics for segmentation using transaction CT04

You have defined segmentation structures in Customizing forLogistics

General Segmentation Define Segmentation Structures

You have defined segmentation strategies in Customizing forLogistics GeneralSegmentation Define Segmentation Strategies

You have created articles and assigned a segmentation strategy in the article

master (transaction MM41)


25/36


Stock Protection

Options without segmentation

Assume three business channels and each channel hasplanned figures for the next season

Retail 200

Wholesale 300

E-Commerce 100

E-Commerce PO

300Wholesale PO

300Retail PO

200

Retail DC

Wholesale DC

E-Comm. DC

Stock can be purchased individually and received into different DCs, storage

locations or batches.

This ensures tight stock protection per channel

Stock overview can be difficult

Making stock available for another channel requires stock bookings and may

involve some logistics

These shortcomings can be overcome with Fashion Management stock protection


26/36


Stock Protection

In SAP Fashion Management

The idea: protect stock for channels

keep common stock without physical separation.

How it works:

Use segmentation to define the channels

Record demand per channel with planned independent requirements

(PIRs)

Availability check (ATP) and allocation run (ARun) consider the

unconsumed PIRs and confirm / allocate only those quantities which

are allowed per channel (in sales orders and stock transport orders)

Channel Segment (PIR) qty. Prio

Retail R 200 1

Wholesale W 300 2

E-Commerce E 100 3

ATP considers PIRs and thus logically

segments the stock.

ATP could confirm for

retail demand: maximum 600

wholesale demand: maximum 400

e-commerce demand: maximum 100


27/36


Stock Protection

Consumption Examples

Channel Segment (PIR) qty. Prio

Retail R 200 1

Wholesale W 300 2

E-Commerce E 100 3

STO R

500

SO W

200

SO E

50

STO R

500

SO W

200

SO E

50

200 confirmed

0 open

200 W

400 confirmed

100 open

200 R + 100 W + 100 E

0 confirmed

50 open

100 confirmed

100 open

100 E

500 confirmed

0 open

200 R + 300 W

0 confirmed

50 open

SO E

50

SO W

400

STO R

500

350 confirmed

50 open

300 W + 50 E

50 confirmed

0 open

50 E

200 confirmed

300 open

200 R

Note: standard Fashion Management logic is

sorting the segments according to the defined

priority, higher priorities can consume quantities

from lower priority segments.

With help of a BAdI it is possible to restrict each

segment to only consume from the same

segment.

Note: no batch management is required if stock

is only logically segmented. This is called

Scope 2

Example 3

Example 2

Example 1


28/36


System Demo


29/36


VAS


30/36


SAP Fashion Management Value Added Services

General information about VAS

Can be charged to customer

Can be created as information only or

as single articles without

segmentation or seasonality

Determined or added manually in

sales and purchase order

Has its own price

Considered in ATP and ARun

Determined with standard condition

technique

Generic article or structured article

levels are not supported for VAS

items

Special packing

e.g. packing on cust-

omer request or for

damageable articles

Ticketing / labelling

e.g. with size-labels or

retail-price tickets

Special handling

e.g. putting shirts on

hangers

VAS are specific services attached to goods before they are delivered


31/36



Summary

* Created as of type VKHM (existing retail article type) with article type ID 5

Customizing Master DataMaintain service types

Maintain sub-service types

Set up determination logic

Set up customer group Create condition records

Set up charge code Maintain pricesCreate VAS articles*

Enable sales documents: header, item

Enable outbound delivery

Maintain copy control

Enable purchase orders

Set up ARun VAS correlation

Enable customers, vendors

NEW


32/36



Charge Codes

IMG Logistics General SAP Fashion

Management Value Added Services

Define Charge Code

Charge codes link VAS to pricing.

If a customer has to pay for the additional service this can be managed as follows:

Define charge codes in customizing

Assign a charge code in the VAS condition record

Create a price condition type for charge codes or use the default types:

F4AC: To calculate an absolute surcharge or discount F4AB: To calculate a percentage-based surcharge or discount

Include this price condition in the pricing procedure

NEW


33/36



Creating VAS Condition Records

Value Added Services condit ion records can be created in three ways

VAS condition maintenance specific to article is used if the VAS is used for both

sales orders and purchase orders.

Transaction: FSH_VASA. Condition type: 01MG

VAS condition maintenance for sales orders is used if the VAS is only for sales

orders.

Transaction: FSH_VAS_SD. Condition type: 03SD

VAS condition maintenance for purchasing documents is used if the VAS is usedonly for purchase orders.

Transaction: FSH_VAS_MM. Condition type: 02MM


34/36



Viewing VAS in Sales Documents

Using transaction VA02 orVA03choose an item then

Goto Value Added Service

VAS Data in Document

Using transaction

VA02 orVA03 choose

an item then

Goto Value Added

Service VAS Detail


35/36



Manual Creation of VAS in Sales Documents

Using transactionVA01 orVA02

choose an item then

Goto Value Added

Service VAS Detail

VAS services and VAS sub-services have to be created upfront so that they canbe used inside the purchase order. The Manual Indicator is set by the system to

indicate VAS has been entered manually (not determined).


36/36


System Demo