Ewm 2020 Fsp01 Final

EWM in S/4HANA 2020 – FPS01
Scope
EWM Development, SAP SE
February 2021
PUBLIC
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Areas of Investment in S/4HANA 2020 FPS01
Integration Decentral EWM
Advanced Shipping & Miscellaneous

Receiving
Development Topics in The Area of Integration
Goods receipt from Enhancements to Stock Transfer Enhancements to QM Early updates to LE-
external via MIGO EWM – GTS
integration Kanban with WTs defect integration deliveries
• Synchronous updates of
stock in MM-IM and • Trigger compliance • Further round-ups and • Assign EWM stock • Inform LE outbound
improvements delivery about quantity
embedded EWM in check with EWM • Stock postings in record changes
S/4HANA changes of delivery • Reversal with SN warehouse defect app
• No inbound deliveries dates • Reversal with
• Mix GR for MM-IM and • More frequent consignment stock Follow-up actions
EWM storage locations compliance check calls • Reversal with HU • Scrap to cost-center in
in one posting • GTS to update EWM decentral deployment
deliveries
• Planned to be released
via SAP note at RTC
Development Topics in The Area of Decentral EWM
Immediate batch Create local batch in Mapping of customer Further migration

replication triggered decentral EWM on defined business objects
from ECC / S/4HANA S/4HANA partner roles • For migration from Business
Suite EWM to EWM on
• Down-port to ECC EHP3 S/4HANA
and lower S/4HANA release
planned • Condition records for wave
determination
• SCM routes
• Condition records
• Wave templates (after
FPS01)

Development Topics in The Area of Advanced Shipping & Receiving
New EWM-TM integration without transportation units
General strategy Inbound & Outbound RF Inbound & Outbound

• Reduced redundancy in business • New execution UI for freight orders • New logical RF transactions for loading
objects • Warehouse view of a Freight Order and unloading
• New integration without TUs
• Integration approach for basic EWM and
basic TM

Development Topics in The Area of Miscellaneous
RF screens with Vendor License auditing Extensibility of EWM Mass change of

touch enablement consignment stock enhancements product master packaging
in production • Extensibility of EWM specification
• Standard screen • Add JIT and distribution
navigation as buttons • Report to post equipment into the warehouse product • Customer connection
consignment stock to advanced feature check • Extensibility of EWM topic
• Configuration to position own stock based on
navigation buttons of license auditing warehouse product,
selection criteria storage type data view
• Posting to free stock • Add the additional
warehouse request • Supporting
if consignment stock /SCWM/MAT1
arrives in a dedicated created in JIT into the
transaction
storage type measurement of USMM
framework • Supporting warehouse
monitor node

Integration
Goods Receipt From External Via MIGO
Synchronous Goods Receipts For External Procurement in MIGO
Embedded only!
Previous Current
EWM in S/4HANA EWM in S/4HANA
Purchasing document Purchasing document
Inbound delivery
Goods receipt posting
QRFC
EWM inbound delivery
EWM goods receipt posting
EWM goods receipt posting
Confirm inbound delivery QRFC

Warehouse execution
Goods receipt posting
Warehouse execution

Embedded only!
Motivation:
• Improve integration between ERP and EWM :
• Synchronous updates of stock in MM-IM and embedded EWM in S/4HANA
• No hanging queues between ERP components of S/4HANA and embedded EWM in S/4HANA
• Show error messages from EWM to user posting GR in tx. MIGO
• Less documents (no inbound deliveries needed for GR from external procurement)
• Mix GR for MM-IM and EWM storage locations in one posting
• Mix GR into warehouse stock and to consumption (e.g. cost center)
Deployments:
• Embedded EWM in S/4HANA OP 2020 FPS1
• Embedded EWM in S/4HANA CE 2011
• Not supported in decentralized EWM due to system boundaries

Embedded only!
Scope:
• Support of GR for purchasing documents to an EWM managed storage location
• Standard purchase orders
• Scheduling agreements
• Purchase orders referencing value- or quantity contracts
• Stock transfer orders
• Subcontracting purchase order incl. GI posting of components
• Support of GR with HUs (new tab strip in tx. MIGO)

• Support of Unified Package Builder (UPB) getting packaging proposal from
• Packaging specification
• Packing instruction
• Package builder
• Support of GR for serialized products

• Support of automatic putaway WT creation (optional)
• Display EWM document number in MIGO and MB51 and navigation to EWM goods movement document and warehouse
task (EWM Monitor)
• Support of cancellations of GR documents in tx. MIGO

Warehouse management data in MIGO
Transaction MIGO – Goods Receipt Processing

Activation via (existing) confirmation control key
Confirmation Control Key e.g. 0006 Confirmation Control Key e.g. 0005
Without Confirmation Category LA Incl. Confirmation Category LA
Allowed for GR into EWM Not allowed for GR into EWM
Managed Storage Location Managed Storage Location
No Confirmation Control Key

Allowed for GR into EWM
Managed Storage Location

Goods receipt bin – how it is determined
GR bin determination uses standard

Staging Area Determination
Inbound
Useful attributes are
• Warehouse Number
• Staging Area and Door Det. Group
• Ship-from (new)
If no bin can be determined, fall back

logic exists using new view
/SCWM/V_T340DSGM (Make Settings
for Synchronous Goods Movements)
GR bin is used as proposal for the GR

posting in tx. MIGO.

packing proposal from Unified Package Builder
Assignment of Package Building Profile

using new view /SCWM/V_T340DSGM
(Make Settings for Synchronous Goods
Movements)
Packaging proposal can either come from

• Packaging Specification
• Packing Instruction
• Package Builder

Automatic warehouse task creation (optional)
• Setting on storage type level ‘Automatic WT Creation at GR’

• Inactive St. Type Auto WT
T906 1 Active
• 1 = Active
T907 2 WPT decides
• 2 = Warehouse Process Type decides
T908 Inactive
• Setting on warehouse process type level ‘Automatic WT Creation at GR’

• Inactive WPT Auto WT
• 1 = Active P117 1 Active
P118 Inactive
• Setting on product level ‘Control Indicator for Process Type Determination’

• No Indicator e.g. WPT with inactive ‘Automatic WT Creation at GR’
• Indicator e.g. WPT with active ‘Automatic WT Creation at GR’

Out of scope / Not supported yet
Out of Scope if using the Not supported yet, planned

new posting with future releases
• Mixed handling unit creation • Quality management inspection
lot creation during synchronous
• HU creation for serialized products goods receipt (planned for future
release)
• One handling unit creation for several
batches of one product • Preallocated stock handling

Enhanced GTS Checks
Enhancements to EWM GTS Integration
Not part of FPS01 but will be available via SAP note
Requirement #1: trigger compliance check with EWM changes of delivery dates
compliance checks in GTS are date dependent. In the LE-GTS integration date changes in the LE outbound delivery triggers the re-
execution of a compliance check. Compliance checks must also be triggered by EWM Outbound Delivery Orders (ODO) in case of
relevant delivery dates are changed.
Requirement #2: more frequent compliance check calls

in the existing outbound process, there could be a time gap between compliance checks. This is the case typically between the
relevant changes on deliveries (which changes trigger compliance checks) and the Outbound Delivery (OD) creation (which triggers
the last check in the process). This gap could be even longer, if there is a Transportation Unit (TU) with several ODOs assigned in
the process. There should be more frequent compliance check calls, ideally triggered by events like picking, packing, loading or
staging.
Requirement #3: GTS to update EWM deliveries

currently in LE-GTS integration there is a functionality, which updates LE about changes in GTS. These updates
can trigger further follow-up functionalities like compliance check calls. This functionality is missing in EWM-GTS
integration.

Round Ups in KANBAN
Stock Transfer Kanban With Warehouse Tasks
Recap
KANBAN Board

Stock Transfer Kanban With Warehouse Tasks
Improvements in FPS01
• Ease of Use
Motivation • Simplify Actions
• Resolve Process Impediments
• Support Automatic Posting of Consignment Stock to Own

Scope • Kanban Reverse of Fully Picked Handling Unit
• Kanban Reverse of Picked Serial Numbers
• Embedded EWM in S/4HANA OP 2020

Deployments • Embedded EWM in S/4HANA with upcoming CE releases
• Not supported in decentralized EWM due to system boundaries

Improvements in Stock Transfer Kanban with Warehouse Tasks
Reverse Status
Reverse from FULL to EMPTY includes …

• Posting stock back into EWM storage location
• Put stock back into source storage bin
• Re-create warehouse task to replenish Kanban
… automatically in one single step
As of Release 2020 FPS01, this includes:

• Pick HUs
• Serialized Stock (Serial Numbers on Stock Level)
• Stock from auto-posted Consignment → Own

Kanban Correction for Control Cycle
Stock Transfer Kanban with Warehouse Tasks
Kanban status change to EMPTY

triggers Warehouse Task creation
PSA Storage Type allows

automatically posting from
consignment to own stock
Supplying
Warehouse PSA Production Line
Consignment
Stock
Confirmation of Warehouse Task
sets Kanban status to FULL … and posts from
Consignment to own Stock
QM Integration: Defect And Notification
Enhanced Integration to QM Defects And QM Notifications
Integration to QM defects and notifications released with 2020 – embedded EWM
Motivation
• Defective material or damaged stock found
• Notify quality department and document defect
Scope
• Quality defect: Enhanced app Record Warehouse Defect:
• Trigger postings to blocked, unrestricted stock or scrap to cost center
• Support manual and automatic stock selection by providing UI5 based list of
stocks
• Quality notification: new follow-up action ‘scrap charged to supplier’
Deployments
• Embedded EWM in S/4HANA 2020 FPS01

Enhancement of app Record Warehouse Defect
Fiori App Record Warehouse Defect
UI5 based list of stocks for manual

and automatic stock selection

Key take aways
• Defective material or damaged stock found

Motivation
• Notify quality department and document defect
• Enhanced app “Record Warehouse Defect”

• Trigger postings to blocked, unrestricted stock or scrap
Scope to cost center
• Quality notification: new follow-up action “Scrap
charged to Supplier”
Deployments • Embedded EWM in S/4HANA 2020 FPS1

• Decentral deployment planned with a future release

QM Integration: Follow-Up Actions
New follow-up actions in decentral EWM – available in embedded since release 2020
Scope
• New follow-up action
‘scrap to cost center’
• New follow-up action
‘sample consumption’
Deployments
• Decentral EWM on
S/4HANA 2020 FPS01
• Embedded EWM in
S/4HANA 2020 (already
available)
Corresponds to stock posting “To sample usage” of inspection lot

on IM managed storage location
Desktop app Record Usage Decision (transaction QA11) → EWM Inspection

New follow-up action “Scrap to Cost Center”
Corresponds to stock posting “Post To

Scrap” of inspection lot on IM managed
storage location

New follow-up action “Sample Consumption”
Corresponds to stock posting “To

sample usage” of inspection lot on IM
managed storage location

Key take aways
• Decide a quality inspection with scrapping inspected

Motivation stock and charge a cost center
• Record the consumed sample to a cost center
• New follow-up action “Scrap to Cost Center”

Scope • New follow-up action “Sample Consumption”
• Decentral EWM on S/4 2020 FPS1

Deployments
• Embedded EWM in S/4 2020

Early Quantity Updates to LE Deliveries
Early quantity updates to LE Outbound Deliveries
Previous Current
EWM in S/4HANA EWM in S/4HANA
Sales Order Sales Order
Outbound delivery Outbound delivery

QRFC QRFC
EWM Outbound delivery EWM Outbound delivery
Adjust quantity Adjust quantity
Update outbound delivery QRFC

EWM goods issue posting
EWM goods issue posting
Confirm outbound delivery QRFC
Confirm outbound delivery QRFC

Early quantity updates to LE Outbound Deliveries
How to activate early delivery update
Exchange the screens
Transaction SPRO – Display IMG

Advanced Shipping &
Receiving
Advanced Shipping & Receiving
New simplified integration with SAP Transportation Management (TM)
Motivation SAP S/4HANA

1. Reduce redundancy in business objects and data to reduce hardware
resource costs* (EWM Shipping & Receiving (S&R) objects like TU activity Freight unit
are redundant objects to TM Freight Document and its data)
Freight order
2. TCO reduction through technical simplification (for both customers and
Shipping &
SAP) Receiving
3. Overcome scalability limits of existing EWM S&R → support high volume TM
retail and e-Commerce scenarios
4. Provide an integration approach that also works for basic WM and basic TM
5. Provide an integration approach for S/4HANA Public Cloud
Warehouse Handling
6. Remove restrictions of current S&R in EWM (e.g. support unloading and request unit
loading with a single check-in)
EWM

New data model in SAP TM and new objects consignment and loading / unloading point
Two new objects:
• Consignment: Freight Order (Bordero)

group of deliveries with the
same source and destination
location Stop 1 Stop 2
• Loading / Unloading point is

passed from TM via LE to EWM Consignment Consignment Consignment
Supplier 1 Supplier 2 Supplier 3
• A loading / unloading point is a
group of doors
FU FU FU FU FU FU FU FU FU
• Same master data object for
EWM and non-EWM warehouses
• Several loading points can belong DLV DLV DLV DLV DLV DLV
to one warehouse
• One loading point can belong to Unloading Point 7
Unloading Point 1 Unloading Point 2 ULP 3
an EWM- and a non-EWM
warehouse

Inbound process part 1/2
Process Step Supplier TM ERP EWM
EDI message (optional) Create purchase
Create sales order
Create purchase order order
Create FU
Goods issue process at Create FO,

Pick / pack / load Create delivery Create ID
supplier consignment
Set status “In

Truck arrives Update delivery Update ID
Yard”
Change FO and
consignments Update delivery
Update ID and HUs
(Quantity and HUs
At checkpoint packaging items)
Compare paper
documents with system Set status “Ready Update
for warehouse Update ID becomes the
processing” active document

Inbound process part 2/2
Process Step Supplier TM ERP EWM
Set dock-to-door
Dock at door
for the stop
Update status of
Set status
Unload (HUs) HUs and packaging
“unloaded” for HUs
items
Optional:
Update status of
Check unloaded HUs Change delivery
Fus, consignments,
and update in case of quantity and HUs
packaging items
deviations
Update status,
Post goods receipt Update status delivery quantities, Post goods receipt
HUs
Create/confirm
Putaway
WTs

Outbound process
Transport Load Planning before Transport Load Planning after Ad-hoc Loading after warehouse
start of warehouse execution warehouse execution execution
Outbound Delivery Outbound Delivery Outbound Delivery
Outbound Delivery Outbound Delivery Outbound Delivery

Freight Unit Freight Unit Freight Unit
Order Order
Order
Freight Order Warehouse

Freight Order Warehouse Execution
(Assign FUs) Execution (Pick, (Pick, Pack & Stage)
(Assign FUs)
Pack & Stage)
Warehouse
Execution (Pick,
Pack & Stage)
Freight Order
Loading Loading Loading
(Assign FUs)

Advanced Shipping & Receiving – Scenario 2: Mixed Scenario
Outbound process part 1/2: before ‚ready for shipping’
TM ERP EWM
• Outbound Delivery Order is immediately Create sales order
ready for warehouse processing
Create outbound
• Only quantity changes are comunicated Create FU Create ODO
delivery
early to LE and TM
• Data flow: EWM → TM (+ EWM → LE) Create WTs
Quantity changes
LE delivery update
Confirm WTs
FU quantity update
Pack (optional)
Stage (optional)
Set “Ready for

Update Fus, create
shipping” on ODO
Packing items
Header

Advanced Shipping & Receiving – Scenario 2: Mixed Scenario
Outbound process part 2/2: after ‚ready for shipping’
TM ERP EWM
NO update but
• Shipping readiness status is set to Create FO and assign
selection of ODO with
FUs with packing item
‚ready‘ when the delivery quantity has FO number possible
been picked and there are no more
Set status Check-in for
changes regarding quantity or FO (optional)
handling units.
Dock-to-door
(optional)
• The information is sent immediately to
TM where the transportation planner Update package item /
Load HUs in RF
FUs
can create or adjust the freight order.
Create OD when ODO
Update quantity and
is completely loaded
HU
Set status “Loading (optional)
finished” in ASR UI
Post GI in ASR UI Post GI of ODO and HU

Update quantity and
Update FU and Send update to LE
HU, post GI
packaging items
Send update to TM
Dock from door
(optional)
Check-out (optional)

User Interfaces and other areas adopted in EWM
• New Transportation Planning Type „E- Obligatory Planning in

TM for Adv. SR” in inbound and outbound delivery headers
• EWM transactions (RF, GUI and Fiori-transactions) have been

extended according to the new process (e.g. with new filters to select by
freight document, external consignment order etc.)
• Freight order UI of TM will be enhanced by EWM-relevant fields

and actions etc. to fit to the needs of a warehouse clerk
• New logical RF transactions to supporting unloading with

reference to the TM objects
• New view on the freight order that is optimized for users in EWM

Advanced Shipping & Receiving - Inbound
Transportation planning type „E- Obligatory Planning in TM for Adv. SR” in inbound delivery headers
Motivation
• Indicate how a single inbound
delivery is planned
• Be able to distinguish which type
of TM integration is active
• Support customers running
current and new integration in
parallel
Maintain Inbound Delivery (transaction /SCWM/PRDI)

New UI to load / unload freight orders
Motivation
• Support loading and unloading activities
• Based on one freight order
• Based on one warehouse or loading/unloading point
• Support both EWM-managed and IM-managed Warehouses
• Load/unload for a single warehouse
• Shared loading/unloading point
• Support loading and unloading activities with a single warehouse visit
• Support navigation to different documents
• Freight Order/ Consignment/ Freight Unit/ LE Delivery/ EWM Documents

App Load or Unload Freight Orders

Supported actions Item Hierarchy

• Door Assignment
• Ready for Warehouse Processing/Reverse
• Unload/Reverse Unload
• Load/Reverse Load
• Goods Receipt/Reverse Goods Receipt
• Goods Issue/Reverse Goods Issue
• Finish Loading/Reverse Finish Loading
• Finish Unloading/Reverse Finish Unloading
• Arrive at Door
• Departure from Door
• Customizable
• If there is no data for one level, nothing is displayed on the UI

Inbound in new freight order UI
1 Door assignment 2 Ready for warehouse processing
3 Unloading 4 Finish Unloading 5 Post goods receipt

Outbound in new freight order UI
1 Door assignment 2 Loading
3 Loading end 4 Post goods issue

Dock to Door / set warehouse door status
Optional: set arrival and departure from door in the inbound / outbound process
App Load or Unload Freight Orders

Enhancements in the area of inbound delivery processing
• New references in EWM inbound delivery

documents
• New selection option

• in transaction /SCWM/PRDI
• in EWM warehouse management monitor
• in FIORI app
• New transportation status to prevent execution

before RFW
EWM Fiori App Change Inbound Deliveries

Enhancements in the area of RF processing
New logical transactions in

the following areas:
• Unloading with reference to
Consignments / Bill of
Lading
• Changing quantity and
packaging material type
during unloading
• Receiving of Handling
Units if items are not
packaged before unloading
• Loading with reference to
Consignments / Bill of EWM RF UI → Inbound Processes → Unloading EWM RF UI → Inbound Processes → Receiving
of Handling Units
Lading

Additional functions for unloading processes
New HU(s) Change Packaging Material & Quantity

Advanced Shipping & Receiving - Outbound
RF logical transactions for loading
• Enable ASR RF Loading for New Objects

• Bill of Lading
• Consignment Order
• Ensure existing RF Loading Work for

• Delivery
• Door
• HU
• Support Multiple Loading Points
• Allow Simple and Complex Loading

EWM RF UI → Outbound Processes → Loading

New simplified integration with SAP Transportation Management (TM)
Out of scope in 2020 FPS01 release (preliminary list):
• Scenario 1 and 3 not supported

• No 100% feature parity to existing EWM Shipping & Receiving
• Planned restrictions (at least for first release):
• No warehouse stock on TU level
• EWM Yard Management besides check-in and docked to door not supported (e.g. no movements in the yard)
• Outbound Delivery Splits
• No X-delivery-HUs
• Transit Warehouse
• Integration of EWM Dock Appointment Scheduling (DAS) into the new concept
• Integration of LBN Dock Appointment Scheduling into the new concept
• Integration of Yard Logistics (FBS product) – planned for Q3/2021
• Integration of local ‘new’ S&R used in EWM with a legacy TMS (not SAP TM) without ‘full TM’

Differences Compared to Current TM-EWM Integration Using TUs
Value proposition of new EWM-TM integration
Scenario / Feature Classic TM-EWM ASR

integration
Using Consignments to bundle and communicate inbound and outbound Not supported Supported
operations
Multi-stop transports Not supported Supported
Complete visibility in a single cockpit Not supported Supported
Decentral deployment Supported Not supported; planned

with a future release
Inbound & outbound in a single truck Not supported Supported
Early updates of quantity changes and HU information to TM Not supported Supported
Common (Un-)Loading from IM and EWM-managed storage locations Not supported Supported
Combining EWM and non EWM warehouse in a single freight order Not supported Supported
Visibility about Container in inbound & outbound Not supported Supported
Visibility about “Unloading / Loading Points” Not supported Supported

Decentral EWM
Immediate Batch Replication
Immediate Replication of Batch Master Data to Decentral EWM on S/4HANA
Available via SAP note 2983820
Requirement #1: Enable immediate distribution of newly created or changed batch from ECC to EWM based on ALE
standard messages. This must be supported for all batch levels available in ECC. Also, batches with or without classification
must be supported. In case of batches using classification, a change to only a Z-characteristic must lead to an immediate
distribution of the batch and classification data, too.
Requirement #2: Do not make use of change pointer. Due to expected high load of change pointer for batches as well as
for classification, this solution must not rely on activation of change pointer for BATMAS nor for CLFMAS on the sending
ECC system. This also implies that change pointer must not be “consumed” by this solution to not interfere with existing
customer scenarios. Despite the drop of change pointers, the distribution should be based on the standard mechanisms and
tools of the ALE framework, meaning for example all monitoring tools for IDOC messages should also be usable for data
transfers of this solution.
Requirement #3: The solution must not have any impact on the existing ECC runtime. The solution will be provided in
an SAP internal BAdI on ECC side. However, the implementation must not increase the overall runtime on ECC side when
changing or creating a batch significantly. This can be achieved by decoupling the EWM logic.
Requirement #4: The trigger of the distribution of batch changes or creation must be independent of
the used UI. This means for example that the distribution should be trigger in any case a change on the
DB happen like from transaction MSC2N as well as when creating a batch during creation on an inbound
delivery on ERP side via VL31N as well as changing a batch from a BAPI like
BAPI_BATCH_SAVE_REPLICA.
Create & Change Batch in
Decentral EWM on S/4HANA
Create Local Batch in Decentral EWM on S/4HANA
Available via SAP note 2987398
Motivation
• Warehouse clerks needs to create/change batch in decentral EWM on S/4HANA for
• Physical inventory: product with batch found that is not in the system
• Batch needed after posting change product to product
• Warehouse clerk wants to change characteristic values of a batch in decentral EWM (e.g. SLED)
Scope
• Batch creation and change by batch master data app (tx MSC1N) in decentral EWM on S/4HANA
• Replication of changes to S/4HANA or ERP backend system; determination in case of multiple systems connected
• Batches on plant level
• Plant specific handling of batches on material level
EWM on S/4HANA stack ERP or S/4HANA Backend
Create / change batch master Batch master
Classification Classification
Batch characteristics Batch characteristics

Create Local Batch in Decentral EWM on S/4HANA
Key take aways
Motivation Need for batch creation or change in SAP EWM
Enable batch creation and change by batch master

Scope data app in decentral EWM on S/4HANA
Decentral EWM on S/4HANA 2020 FPS1

Deployments

New Migration Objects
Business Suit EWM to decentral EWM on
S/4HANA
Migration From Business Suite EWM to EWM on S/4HANA
New migration objects
Objects available with 1909 / 2020 release

• EWM resources
• Settings in the area of slotting
• Settings in the area of ,application log’ and travel distance
• WorkCentre settings
• Production supply settings
• Physical inventory settings
• Material flow system settings
• Settings in the area of shipping and receiving
• Settings in the area of QIE
• packaging specifications (via report)
• Warehouse products
• Storage bins
• Bin sortings
• Fixed bins
• Stock
New migration objects for 2020 release FPS01

• Wave templates and wave condition records
• SCM routes (incl. carrier profile, zones and zones
hierarchy) Migration Cockpit – Migration Objects
• Condition records (warehouse dependent and warehouse
independent condition records for slotting, printing, transit
warehousing,…)
• …

Miscellaneous
RF Screens With Touch Enablement
Overview
Motivation
• Enable standard function keys on touchscreen devices
without hardware function keys
Scope
• Standard function keys as push buttons
• F6: clear field value
• F7: back to previous step
• F8: value input help
• F9: display full message
• Ability to switch push buttons on /off
• Four standard variants of push button arrangements on
screen
• BAdI to implement different push button arrangements

Example: RF picking screen
Motivation
• Better support devices which don’t have
buttons to trigger screen actions
• Show standard navigation keys on scree
Scope
• Provide standard screen navigation as
push buttons; today some function keys
are not visible as a Function key was
supposed to be used
• Offer configuration to position the
navigation push buttons
Use note 2957972 for S/4HANA 2020
RF Picking Screen
Configuration of function key position
• New configuration on
presentation device level to
determine the position of
the standard push buttons
• With this the Function Key

name is automatically
removed; e.g. instead of
F10 Print the button is
called Print Transaction /SCWM/PRDVC – Maintain Presentation Devices

Vendor Consignment Stock in Production
Posting changes for consignment stock in production
Motivation
• Avoid consumption of consignment stock in production
• Automatic posting changes for consignment stock to own Post certain time after GR (by batch job)
stock
Scope
• Report to post consignment stock to own stock based on
selection criteria – new posting method
• Posting to free stock if consignment stock arrives in a
dedicated storage type Post before consumption (controlled on
• New flag on storage type level destination storage type level)
Deployments
• Embedded EWM in S/4HANA 2020 FPS01
• Decentral EWM on S/4HANA 2020 FPS01

New posting method in /SCWM/R_STOCK_TYPE_CHANGE
• New ‘posting method’ in

report for stock type change
• Regularly post from
consignment to own stock
based on selection criteria
• Ad-hoc or via background job
Report /SCWM/R_STOCK_TYPE_CHANGE

New flag on storage type level
• New flag on storage type

level
• Destination storage type
controls posting
EWM IMG > Master Data – Define Storage Type

Mass Change of Packaging Specifications
Customer connection topic, down-port planned till EWM 9.5 and S/4HANA 1809
Motivation Lab Preview

• Enable Mass Change
of packaging
specifications
Scope
• Enhancement of packing
specification transaction
• New button ’Mass change
2nd Version’ triggers mass
change functionality
• Change basic data
• Max 5 levels supported
• Available via SAP note Transaction /SCWM/PACK_SPEC
2979103
Support Extensibility of EWM Warehouse Product
Customer fields for warehouse product data
Motivation
• Support customer extensions
• Enable central S/4HANA
Extensibility framework for EWM
master data
Scope
• Extensibility for customer own
fields for transaction Warehouse monitor node Product Master Data
/SCWM/MAT1 at warehouse and

storage type levels
• Custom fields are also displayed
in the warehouse monitor
Business Benefit: reduced TCI

Support Extensibility of EWM Warehouse Product
Add custom fields in fiori app, edit and display in transaction /SCWM/MAT1
FIORI app Custom Fields and Logic
Transaction /SCWM/MAT1 → Tab warehouse data Transaction /SCWM/MAT1 → Tab storage type data

Enhancements to JIT Supply to Production Processing
JIT supply to production released with S/4HANA 2020
Motivation
• Better overview about
picking progress
• Better and faster root cause
analysis
• Better supporting Customer
enhancements
Scope
• New monitor node
“Warehouse Order” EWM Management Warehouse Monitor (transaction /SCWM/MON)
• New BADIs in wave

planning, field selection etc.

Monitor Enhancements For JIT Supply to Production Processing
• New EEW includes /SCWM/INCL_EEW_S_JIT_QUERY_H and

/SCWM/INCL_EEW_S_JIT_QUERY_I to support customers using own selection
fields
• New BAdI /SCWM/EX_JIT_CUSTOM_FIELDS allows to change extension fields of

the warehouse request and to display them in the warehouse monitor. The BAdI
also allows to use the query extension fields for warehouse request selection
• New BAdI /SCWM/EX_JIT_CUSTOM_SELECT_MON allows to enhance the

selection screens in warehouse monitor for custom selection

License Auditing Enhancements
Scope
• Add JIT and distribution equipment into the advanced feature check of license auditing
• Add the additional warehouse request created in JIT into the measurement of USMM framework

New or Enhanced BADIs
• Enablement of the existing BAdI /SCWM/EX_WAVE_PLAN for

multiple use
• New BAdI /SCWM/EX_WAVE_PLAN_BACKGROUND to allow

customers enhancing the selection criteria for selection report
/SCWM/R_WAVE_PLAN_BACKGROUND
• New BAdI /SCWM/EX_DLV_TOWHR_BD_CREA_WT can override

decision whether to create new warehouse tasks in bin denial or not
• …

Enhancement of Fiori App ‚Pack Outbound Deliveries‘
New logic for cursor positioning
3 Cursor switches back to
‚Reference Number‘ Fiori app Pack Outbound Deliveries
• With this enhancement you can
quickly start packing for the next
reference number instead of re-
positioning the cursor
• When there are no items for packing

and all ship HUs are closed, the
cursor automatically switches to the
position where you can scan another
reference number
1 No unpacked items 2 No open ship HU(s)
Business Benefit: Improved user experience, increased productivity

Roadmap
SAP Extended Warehouse Management
Official roadmap on roadmaps.sap.com

Thank you.

Ewm 2020 Fsp01 Final

Uploaded by

Document Information

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

Ewm 2020 Fsp01 Final

Uploaded by

Copyright:

Available Formats

EWM in S/4HANA 2020 – FPS01

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

Integration Decentral EWM

Advanced Shipping & Miscellaneous

Immediate batch Create local batch in Mapping of customer Further migration

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

General strategy Inbound & Outbound RF Inbound & Outbound

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

RF screens with Vendor License auditing Extensibility of EWM Mass change of

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

Purchasing document Purchasing document

Confirm inbound delivery QRFC

Goods receipt posting

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

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

• Support of GR with HUs (new tab strip in tx. MIGO)

• Support of GR for serialized products

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

Transaction MIGO – Goods Receipt Processing

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

No Confirmation Control Key

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

GR bin determination uses standard

If no bin can be determined, fall back

GR bin is used as proposal for the GR

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

Assignment of Package Building Profile

Packaging proposal can either come from

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

• Setting on storage type level ‘Automatic WT Creation at GR’

• Setting on warehouse process type level ‘Automatic WT Creation at GR’

• 1 = Active P117 1 Active

• Setting on product level ‘Control Indicator for Process Type Determination’

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

Out of Scope if using the Not supported yet, planned

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

Requirement #2: more frequent compliance check calls

Requirement #3: GTS to update EWM deliveries

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

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

• Support Automatic Posting of Consignment Stock to Own

• Embedded EWM in S/4HANA OP 2020

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

Reverse from FULL to EMPTY includes …

… automatically in one single step

As of Release 2020 FPS01, this includes:

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

Kanban status change to EMPTY

PSA Storage Type allows

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

Fiori App Record Warehouse Defect

UI5 based list of stocks for manual

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

• Defective material or damaged stock found

• Enhanced app “Record Warehouse Defect”

Deployments • Embedded EWM in S/4HANA 2020 FPS1

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

Corresponds to stock posting “To sample usage” of inspection lot

Desktop app Record Usage Decision (transaction QA11) → EWM Inspection

Corresponds to stock posting “Post To

Desktop app Record Usage Decision (transaction QA11) → EWM Inspection

Corresponds to stock posting “To

Desktop app Record Usage Decision (transaction QA11) → EWM Inspection

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33