S/4HANA for fashion and vertical business 1909 OP

Supply Assignment
Stay Current, SAP
September, 2019

PUBLIC
Agenda

• Dynamic Supply Prioritization

• Workflow Events Handling in Supply Assignment
• Supply Demand Overview for all Documents
• ITA – Selection of Demand based on Supply

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Dynamic Supply Prioritization
Dynamic Supply Prioritization

Goal: Ability to do supply assignment while sorting the supply based on different types of supply
and considering supply type specific time intervals.
Business Background: Dynamic Supply Prioritization can help to make the best use of
existing and incoming supply. On-hand/ warehouse stock can be kept for short notice demand
while demand which is to be fulfilled later can be assigned to future supply.

How :
• Define dynamic supply prioritization in “Configure Supply Sort Rule” Fiori app
• In supply sort rule the priority for different supply types and time horizons can be specified
• System assigns the supply in accordance with priority defined in supply sort rule
• The assignment timeframe for a supply element defines the number of days the respective
supply element can be considered for assignment with respect to the material availability
date of the requirement

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Example of typical dynamic Supply Prioritization

IBD 5 Explanation:
10 For SO 1 ARun searches
1) 20 days backward for PO – PO 3 found
IBD 1 PO 2 PO 3 PO 4 PO 6
2) 20 days forward for PO – PO 4 found (PO
10 10 10 10 10 10
6 is not eligible because outside the search
5
horizon
3 4
IBD 3) 20 days backward for IBD – no IBD
PO
1 2
4) 10 days forward for IBD – no IBD (forward
SO 1
IBD search is shorter than for PO)
30
IBD
5) Warehouse stock used for complete ARun
PO
Search
For SO 2 the number of days is calculated from
SO 2 horizon the material availability date of that order.
Prio Type Backward Forward 30 Backward search finds IBD 1 and PO 2
1 PO 20 20
2 IBD 20 10
3 Wareh.

SO = Sales Order PO = Purchase Order IBD = Inbound Delivery (Shipping Notification)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Configure Dynamic Supply Sorting Rule

Sequence (priority) of possible

supply types are defined
together with the number of
days (backward and forward)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Configure Supply Sorting Rule

This functionality is now

available as Fiori App

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Specify Supply Sort Rule in BOP Variant

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Workflow Events Handling in Supply
Assignment
Workflow Event Handling in Supply Assignment

Goal: Enablement of workflow for the Insight to Action (ITA) exception handling feature and
un-assignment of orders due to changes in cross application
Business Background: With this new feature exceptions related to un-assignments can
be managed in the framework of standard workflow and therefore makes the daily work of
users easier

How :
• A class based event is raised when a demand gets un-assigned due to cross application
changes. The un-assigned order item would be available in the event
• A class based event is raised when orders are deviated from exception rule in
background mode of ARUN Insight to Action (ITA) tool.
• The event can be attached as a triggering event in a workflow and this can be
configured to perform desired tasks.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Example of Workflow Event Trigger for Un-assignment of Orders

1 2
Sales Order
Sales Order 10th April Purchase
Qty: 100 ARuRun
ARun Order
ARu
ARun
Run 100
5th April
Sales Order
11th April

1. Sales order item is assigned to warehouse stock but during a stock count the quantity is updated
and the item gets partially unassigned
2. Purchase order postponed by a month – due to cross application settings the sales order items get
unassigned

• Workflow event is triggered and action item comes to “My Inbox”

• Further actions can be taken based on workflow configuration – manual assignment via ITA, etc.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Workflow for Supply Assignment – Workflow Event

Attach the events in Workflow

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Workflow Event Trigger for Exception Processing in ARun ITA

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Supply Demand Overview for all
Documents
Supply Demand Overview for all Documents

Goal: Get a complete overview of supply and demand regardless of the object types
Business Background: up to 1809 release only ARun related objects were displayed in
the supply demand overview and thus users would not be able to evaluate the overall
situation. Users need the complete picture.

How :
• The new Supply Demand Overview (SDO) Fiori apps allow the evaluation of all
relevant objects
• As pre-requisite “temporary assignments” have to be calculated by a new Fiori app

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Temporary Assignments
Need for Temporary Assignments because:
• Overall visibility of match between Demand and Supply is required
• Visibility of non ARun relevant documents (such as Stock Transfer Requisitions (STRs), Planned Independent
Requirements (PIRs), Purchasing Contracts, Third Party Order (TPO), etc.) is needed to provide a complete
picture. E.g. if customers order via standard sales orders and TPO.
• On the fly match between Demand and Supply for large data selections would result in long response time due
to huge data volume

Solution to provide the complete overview:

• A new Fiori app (Schedule Temporary Assignments) to create temporary assignments of the demand and
supply. This app will be run as a (regular) background job and the results can be displayed in
• A new Fiori App (Supply Demand Overview – All Documents) to visualize the complete demand and supply
status using the following data sources
− Open Demand
− Open Supply
− Normal Assignments (ARun result)
− Preview Assignments (ARun result)
− Temporary Assignments

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

Supply Demand Overview – Scope/ Concept

Run Supply Receive Create Run Temp.

Assignment Orders Supply Assign App

ARun Results Temporary

Open Demand Open Supply
(Normal + Preview) Assignments

Selection Criteria
Plant, Material, Org. Data, etc. Supply Demand
Overview

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

“Temporary Assignments” Details
 Supply Demand Overview – Relevant Objects

Demand ARun ARun Temporary Supply ARun ARun Temporary

(Normal) (Preview) Assignm. (Normal) (Preview) Assignm.
Sales Orders ☑ ☑ ☑ Inventory Stock ☑ ☑ ☑
Fashion Sales Contracts ☑ ☑ ☑
Purchase Orders ☑ ☑ ☑
Stock Transport Orders ☑ ☑ ☑
Shipping Notifications (ASN) ☑ ☑ ☑
Subcontracting PO
☑ ☑ Production Orders
Components ☑ ☑ ☑
Production Order Components ☑ ☑ Purchase Requisitions ☑ ☑
Third Party Order (TPO) ☑ Planned Orders ☑ ☑
Purchase-to-Order (PTO) ☑ Purchasing Contract ☑
Make-to-Order (MTO) ☑
Third Party Order ☑
Stock Transfer Requisitions
☑
(STR) Purchase-to-Order ☑
Planned Independent
☑ Make-to-Order
Requirements (PIR) ☑
Dependent Requirements
Customer Returns ( Return
(Planned Order Components &
☑ Sales Order and Return ☑
Subcontracting PR
Deliveries )
Components)
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19
Temporary Assignments (Features)

Features Details
Material Selection Supply Assignment relevant materials only
Selection Screen Material, Plant*, Product Availability Date*, Document Type, ….
Open Requirement Calculation Open Requirement Quantity = Ordered Quantity - ( Normal Assigned + Preview assigned +
Delivered )
Open Stock Quantity Open Stock Quantity = Total Supply Quantity – ( Normal Assigned + Preview assigned )
Assignment Logic Demand: FIFO based on Material Availability Date.
Supply: FIFO based on Delivery Date.
Refresh Temporary Assignments Temporary Assignments are refreshed in below cases:
1. Next Temporary assignment run for respective Material / Plant
2. Next Normal / Preview assignment run for respective Demand and Supply elements
3. Document is changed (Cross Application): only for particular item of the document
Parallelization Parallel Processing based on Material / Plant combination. Server group, number of work
processes, number of packets based on selection screen entry.
Recommended execution of First Normal Supply Assignment, then Preview Supply Assignment and then Temporary
Temporary Assignments Assignments.
Results are stored in new table Table Fields will be similar to Normal and Preview Table

* Mandatory selection fields

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20
Temporary Assignments (Contd.)

When the app for

temporary
assignments is
executed various
selection options
can be used

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

Temporary Assignments (Contd.)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

Supply Demand Overview (SDO)
Display Examples
SDO “Big Picture”
Here “Total Assigned” means
• ARun (normal & preview)
• Temporary Assignments

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

SDO displaying Overall Figures per Channel (Retail, Wholesale, Ecommerce)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25

SDO drilling down into different Demand Elements…

It is also possible to drill down and see the details, such as quantity information (Ordered, Confirmed, Delivered, etc.),
supply details (Assigned Supply Source) or drill down to individual order item. In case of PIR, you can see the consumption
details. In case of Fashion (Sales) Contracts, you can see the overall reference status.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26
 SDO displaying Sales Order in different stages…

Ordered – Confirmed – Delivered – ARun (normal assigned) – ARun (preview assigned) – Temporary assigned – Open

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 27

ITA – Selection of Demand based on
Supply
ITA – Selection of Demand based on Supply
(Supply that is already assigned to the demand)

Goal: In some business situations it is necessary to identify demand elements which have been
assigned to a known supply.
Business Background: up to 1809 release in ITA demand can be selected based on various
information which is part of sales documents and STOs. After a successful supply assignment it
may also be relevant to identify sales orders or STOs based on the supply they are assigned to.
One example can be the “inbound for outbound” (IFO) process where you might know about an
incoming delivery that was subject for supply assignment and the question is which demand
elements are now assigned to it and might be applicable for the IFO process.

How:
• ITA (transactions ARUNITA) has been enhanced with two new tabs that allow for SO and/or
STO selection by the assigned supply
• Users can use the selection criteria of these new tabs to select existing assignments

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

Selection of Demand based on Supply in ITA – new tabs

New tabs for selection

• Stock Specific SO
• Stock Specific STO

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

Selection of Demand based on Supply in ITA – Example

Sales
Before this enhancement Order 23 Purchase With this enhancement
ARun Order 123
order selection was order selection can be done
Sales
possible with criteria that using the already assigned
Order 28
were stored in the order like supply.
customer data, material Sales E.g. selection with PO 124
data, dates, status, plant Order 25 Purchase
Order 124 will yield sales orders 25 and
etc. ARun
31.
Sales
Order 31

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 31

© 2019 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 or an SAP affiliate company.

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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products,
and/or platforms, directions, and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and
they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.