0% found this document useful (0 votes)
41 views

4.intro To Delivery Processing From ERP-EWM

Intro to Delivery Processing From ERP-EWM

Uploaded by

Ganesh Kella
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views

4.intro To Delivery Processing From ERP-EWM

Intro to Delivery Processing From ERP-EWM

Uploaded by

Ganesh Kella
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Intro to Delivery

Processing from
ERP - EWM
Supply Chain Execution
SCM 5.0

©SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 1


Service Parts Management – Architecture
Customer Relationship Management Supply Chain Management
SAP CRM 5.0 SAP SCM 5.0
CRM Server: CRM
SAP SCM SAP ICH
Sales, Service, Billing,
Marketing and
Middleware global
RFC*
Interaction Center ATP Service Parts Planning
XI
SAP Internet Pricing Configurator SAP Extended Warehouse Management
SAP Global Trade Service 7.0 SAP Transportation Management System
Compliance Customs
Management Management SAP Event Management
CRM Middleware
RFC* SAP SCM Basis
PlugIn 2005 (PI 600) Master Data Transactional Data

SAP ERP 2005 (ECC 6.0) RFC*


XI
Materials Management Logistics Execution

Quality Management Financials/Controlling

Environment, Health and Safety

SAP NetWeaver 2005


Portal Business Warehouse Exchange Infrastructure Web Application Server
© SAP AG 2005 * tRFC, qRFC or RFC

„ SAP BW internal to SAP SCM 2005 needs to be used for storing historical data.
„ SAP NetWeaver
‹SAP NetWeaver BW (external BW to SAP SCM) is used for analytics and reporting capabilities (Parts
Monitoring and Visibility – Supplier Delivery Performance Rating, Inbound Monitor, Service Fill
Monitor and Service Loss Analysis)
‹SAP NetWeaver Exchange Infrastructure is used for the transfer of all data except master data from and
to SAP ICH
‹SAP SCM gATP is necessary for determining facing and stocking location in BW.
„ Integration CRM – SCM
‹Availability Checks
‹BW extractors of CRM Order to SCM SCM staging BW structures (Capture Demand)
‹??? Distribution of Business Partner information (Customer, Supplier, same business partner
with different roles)????
„ Integration CRM – ERP
‹Transfer of CRM Order to unchecked / checked delivery and change management of those objects

© SAP AG Course number (e.g. RACR1W) 2


„ Integration ERP – SCM
‹Core Interface for Master Data
‹Core Interface for inventory data and transactional data between ERP and SCM
‹XI for inventory data and transactional data between ERP and ICH Implementation scope
„ Implementation scope
‹SAP SCM global Available-to-Promise
y gATP must be implemented for the determination of facing and stocking location at sales order entry
and during re-alignment
y The result of gATP delivers facing and stocking location per order line. The result is stored in the
CRM Sales Order and extracted as part of the historical demand
y If CRM Sales Order is not used, the facing and stocking location have to be determined during data
staging (increased run-time)
‹CRM Order Management
y Certain capabilities of SPP will not be able to be used if CRM Sales Order is not used and the
respective capabilities are not implemented in a customer project
–Determination of facing and stocking location during order entry
–Number of order lines
–Requested delivery date on order line level

© SAP AG Course number (e.g. RACR1W) 3


Communication Between ERP and EWM

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 4


EWM - Inbound Delivery Processing

Inbound delivery notification: Represents the inbound


delivery / ASN from the ERP System. Serves as reference
for quantities.
Inbound delivery: a.k.a. Warehouse request. Serves as the
reference for further processing in EWM.

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 5


Create ASN in ERP – (vl60)

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 6


EWM - Outbound Delivery Processing

„ Outbound delivery:
Represents the same data as ERP
Unchecked Delivery
checked delivery. Serves as quantity
reference for further processing in
EWM
„ Outbound Delivery Order:
Warehouse Request. Is comparable
Outbound Delivery with ERP Delivery. All further picking
Request
is based on Outbound Delivery Order.

Outbound Delivery
„ Outbound Delivery:
Order Represents the physical GI quantities
that are posted in EWM. In export
Outbound Delivery cases this might be created before the
GI posting in EWM. In other cases it
will automatically be created with the
GI posting for the Outbound Delivery
Order in EWM.

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 7


Overview – Outbound Process
WHR
WHR11
WHR1
WHR1
WHR1
A list of warehouse requests is created

These warehouse requests are grouped


Wave 1
into one wave

Based on the wave numerous warehouse tasks will


be created Task
WHR11 Task
WHR1n
WHR1
WHR1 WHR1
WHR1
WHR1 WHR1

All Tasks will pass the “Black Box” warehouse


order creation. WOs are created according to the
WO Creation Rule defined in customizing
Warehouse Order
Creation

The Warehouse Order Creation Rule is determined WO 1 WO 2 WO n


from the Activity Area which influences the routing Task
WHR1 Task
WHR1
WHR1 Task
WHR1
WHR1
WHR1
WHR1
WHR1 WHR1
WHR1 WHR1
WHR1

© SAP AG 2005

„ A list of warehouse requests is created and grouped into a wave. Warehouse Tasks are created and then
bundled into work packages called Warehouse Orders.
„ Routing indicates where the product is delivered – whether to packing, staging, etc.

© SAP AG Course number (e.g. RACR1W) 8


Create an outbound delivery in ERP

© SAP AG 2005

„ Delivery creation in ERP example.

© SAP AG Course number (e.g. RACR1W) 9


Delivery Processing with Additional Functions

• Yard Management
• Status Data
• Information about transportation units

• Transportation Management
• EWM sends a shipment output to transportation management when creating a
warehouse request for an outbound delivery or outbound delivery order

• Serial Numbers
• Serial numbers can be included in the delivery so that you can document
them for the delivery and flag them in goods receipt

• Global Trade Services (GTS)


• Transit Procedure
• Temporary Storage
• Customs Warehousing Procedures
• Compliance Check

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 10


Delivery Processing with Additional Functions - 2

• Country of Origin
• Using Batch Management and Inbound or Outbound deliveries

• EH&S
• In phrase management you can enter texts that have a standard character in
the form of phrases with little effort required for entry and translation

• In the hazardous substance master you can enter all important data relating
to hazardous substances, for example, data that you require for hazardous
substance checks prior to storage

• In the inventory list of hazardous substances for the fire department you can
extract all the important data that the fire department requires in the case of a
fire

• In dangerous goods management you can enter all the important data for
dangerous goods. With this data you can run dangerous goods checks, for
example, or print dangerous goods data on a delivery note

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 11


Delivery Processing with Additional Functions - 3

Post Processing Framework


• Basis technology used in delivery processing for scheduling and processing
actions and messages according to the document
Value-Added Services
• Orders for Value-Added Services can be created manually or generated
automatically by EWM
• With automatic generation, the VAS order is written to the document flow of
the EWM delivery. The status of the VAS order is updated in the delivery.
Changes in the delivery quantity will change accordingly, the status of the
VAS order
Kitting
• Kitting is supported in Outbound deliveries only
• EWM receives a delivery with the corresponding item categories for header
and items of kits. Standard item categories are delivered
• VAS orders can be created for kitting

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 12


Delivery Processing with Additional Functions - 4

Post Processing Framework


• Basis technology used in delivery processing for scheduling and
processing actions and messages according to the document
Route Determination
• Delivery processing calls the Routing-Guide for automatic route
determination . This determines the route and send it back to
delivery processing. You can also manually enter or change a route
in the user interface of the delivery.
• Delivery processing executes route checks and in doing so, it
determines whether the route found in the routing guide or the route
that was manually entered is valid for delivery processing.
• When working with automatic route determination, you can, to a
certain extent, use Extended Warehouse Management (EWM) to
automatically find and check the route and transportation
information in the outbound delivery request, the outbound delivery
order and the outbound delivery

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 13


Copyright 2005 SAP AG. 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 AG. The information
contained herein may be changed without prior notice.
„ Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
„ Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
„ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
„ Oracle is a registered trademark of Oracle Corporation.
„ UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
„ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
„ HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
„ Java is a registered trademark of Sun Microsystems, Inc.
„ JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
„ MaxDB is a trademark of MySQL AB, Sweden.
„ SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

„ The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
„ This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document 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.
„ SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
„ The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

© SAP AG 2005

© SAP AG Course number (e.g. RACR1W) 14

You might also like