Application Operations Guide SAP Extende PDF

Application Operations Guide
SAP Extended Warehouse Management Operations Guide

Release 7.0
Target Audience
zf Technical Consultants
zf System Administrators
zf Solution Consultants
zf Business Process Owner
zf Support Specialist
PUBLIC
zYj7F)s[`?tcpWs"dtg80Hl
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated 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.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. in the United States and in other countries.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
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.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.
2/56
PUBLIC
2011-05-24
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
2011-05-24
Emphasized words or expressions

Words or characters that you enter in the system exactly as they appear in the
documentation
Textual cross-references to an internet address
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
Hyperlink to an SAP Note, for example, SAP Note 123456
7Z Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
7Z Cross-references to other documentation or published works
7Z Output on the screen following a user action, for example, messages
7Z Source code or syntax quoted directly from a program
7Z File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
Keys on the keyboard
PUBLIC
3/56
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: http://service.sap.com/
instguides.
The following table provides an overview of the most important document changes.
Version
Date
Description
1.0
1.1
2008-11-21
2011-05-24
First version of the SAP EWM Application Operations Guide

Revisions made to appendix
4/56
PUBLIC
2011-05-24
Table of Contents
Chapter 1
1.1
1.2
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Global Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2
2.1
2.2
Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Scenario/Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3
3.1
3.1.1
3.1.2
3.2
3.3
11
11
11
12
12
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.4
Monitoring of EWM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP EWM Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selection and Processing of Post Processing Framework Actions . . . . . . . . . . .
Detailed Monitoring and Tools for Problem and Performance
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Important Problem Analysis and Monitoring Tools . . . . . . . . . . . . . . .
Interface Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
4.1
4.2
4.3
4.4
4.5
4.6
4.6.1
Management of SAP EWM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration Tools of Software Components . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
17
18
18
20
20
21
2011-05-24
PUBLIC
12
12
14
14
14
14
14
15
16
5/56
4.6.2
4.7
4.8
4.9
Required Manual Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging On and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5
High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 6
6.1
6.2
6.3
6.4
6.5
6.6
Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Development Requests and Development Release Management . . . . . . . . . . .
Template Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality Management and Test Management . . . . . . . . . . . . . . . . . . . . . . . . . .
Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . .
Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 8
8.1
8.2
Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Remote Setup Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter A
A.1
A.1.1
A.1.2
A.1.3
A.1.4
A.1.4.1
A.1.4.2
A.1.4.3
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Categories of System Components for Backup and Restore . . . . . . . . . . . . . . .
Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Semantics of External Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Queues of External Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter B
B.1
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6/56
PUBLIC
22
22
23
23
27
27
28
28
28
28
29
35
35
35
36
37
37
44
47
49
2011-05-24
Getting Started
1.1
Global Definitions
1 Getting Started
CAUTION
This guide does not replace the daily operations handbook that we recommend customers create
for their specific production operations.
Designing, implementing, and running your SAP applications at peak performance 24 hours a day has
never been more vital for your business success than now.
This guide provides a starting point for managing your SAP applications and maintaining and running
them optimally. It contains specific information for various tasks and lists the tools that you can use
to implement them. This guide also provides references to the documentation required for these tasks,
so you need other Guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library.
1.1 Global Definitions

SAP Application:
An SAP application is an SAP software solution that serves a specific business area like ERP, CRM,
PLM, SRM, SCM.
Business Scenario:
From a microeconomic perspective, a business scenario is a cycle, which consists of several different
interconnected logical processes in time. Typically, a business scenario includes several company
departments and involves with other business partners. From a technical point of view, a business
scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly
other third-party systems. A business scenario is a unit that can be implemented separately and reflects
the customers prospective course of business.
Component:
A component is the smallest individual unit considered within the Solution Development Lifecycle;
components are separately produced, delivered, installed and maintained.
1.2 Important SAP Notes

CAUTION
Check regularly to see which SAP Notes are available for the Application Operations Guide.
2011-05-24
PUBLIC
7/56
Getting Started
1.2
Important SAP Notes
Important SAP Notes

SAP Note Number
Title
1173570
1173566
1173386
Installation of SCMBPLUS 700 on NW 7.0 EHP 1

Installation/Upgrade SCM_BASIS 700
Installation/Upgrade from SCMEWM 7.0 to ERP 6.0 EHP4
8/56
Comment
PUBLIC
2011-05-24
Technical System Landscape
2.1
Scenario/Component Matrix
2 Technical System Landscape
2.1 Scenario/Component Matrix

For more information regarding the components necessary for business scenarios and processes, see
the SAP EWM Master Guide on the SAP Service Marketplace at http://service.sap.com/
instguides SAP Business Suite Applications SAP SCM SAP EWM
Using SAP EWM 7.0 .
2.2 Related Documentation

NOTE
This Application Operations Guide only covers SAP EWM. If you run SAP EWM as part of an SAP
SCM Server 7.0 installation, use the SAP SCM 7.0 Operations Guide on SAP Service Marketplace
at http://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP SCM
Server Using SAP SCM Server 7.0 .
The following table lists where you can find more information about the technical system landscape.
Topic
Guide/Tool
Application- and Industry-specific

Components such as SAP Financials
and SAP Retail
System landscape and deployment
scenarios
Sizing
Security
Master Guide
http://service.sap.com/instguides
Master Guide
Quick Sizer Tool

Security Guide
http://service.sap.com/sizing
2011-05-24
Quick Link on SAP Service Marketplace
PUBLIC
http://service.sap.com/security
9/56
This page is left blank for documents

that are printed on both sides.
Monitoring of EWM
3.1
Alert Monitoring with CCMS
3 Monitoring of EWM
Within the management of SAP Technology, monitoring is an essential task. A section has therefore
been devoted solely to this subject.
For more information about the underlying technology, see the Technical Operations Manual for SAP
NetWeaver in SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s)
SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrators Guide Technical Operations
Manual for SAP NetWeaver .
3.1 Alert Monitoring with CCMS

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system
environment. SAP provides you with the infrastructure and recommendations needed to set up your
alert monitoring to recognize critical situations for SAP EWM as quickly as possible.
3.1.1 CCMS Monitoring Installation and Setup

SAP EWM is technically based on SAP Web AS 7.01 (part of SAP enhancement package 1 for SAP
NetWeaver 7.0) and thus reuses monitoring tools from NetWeaver such as the Computing Center
Management System (CCMS). Therefore, we recommend that you set up the Monitoring
Infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver 7.0 (2004s) at http://
service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.0 (2004s) Operations Monitoring .
For general information about alert monitoring, see the Technical Operations Manual for SAP
NetWeaver in the SAP Library under SAP NetWeaver.
To enable the auto-alert mechanism of CCMS, see SAP Note Number 617547.
For more information about monitoring, see also the Technical Operations Manual for SAP
NetWeaver in SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s)
SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrators Guide Technical Operations
Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP)
Monitoring .
2011-05-24
PUBLIC
11/56
Monitoring of EWM
3.2
Selection and Processing of Post Processing Framework Actions
3.1.2 SAP EWM Monitor

SAP EWM allows monitoring of SAP Core Interface (CIF) Master Data Queues and EWM-specific values.
You can start the monitor in the SAP Easy Access screen, by choosing Tools CCMS Control/Monitoring
CCMS Monitor Sets (transaction RZ20).
3.2 Selection and Processing of Post Processing Framework

Actions
To monitor Post Processing Framework (PPF) actions (e.g. the printing of delivery notes) with errors
the transaction SPFP is available in EWM.
The following applications that use Post Processing Framework (PPF) for the generation of actions are
available:
qy+s /SCDL/DELIVERY
qy+s /SCTM/FOM
qy+s /SCWM/SHP_RCV
qy+s /SCWM/WME
qy+s QIE
3.3 Detailed Monitoring and Tools for Problem and

Performance Analysis
SAP EWM is technically based on SAP Web AS 7.01. For information about technical problem analysis
(such as for database, operating system, or workload analysis) see the Technical Operations Manual for
SAP NetWeaver in SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0
(2004s) SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrators Guide . This guide
covers only the differences and additional information specific to SAP EWM.
In addition, SAP EWM uses the Exchange Infrastructure (XI). For more information about the
monitoring of the Exchange Infrastructure, see the Technical Operations Manual for SAP
NetWeaver at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0
Library English SAP NetWeaver Library Administrators Guide SAP NetWeaver Technical Operations Manual
Administration of SAP NetWeaver Systems PI (Process Integration) .
3.3.1 Trace and Log Files

Trace files and log files are essential for analyzing problems.
The standard NetWeaver tools such as transactions ST22 and SM21 can be used to monitor trace and
log files. For more information, see the Technical Operations Manual for SAP NetWeaver at http://
help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) (select language) SAP NetWeaver Library
12/56
PUBLIC
2011-05-24
Monitoring of EWM
3.3
Detailed Monitoring and Tools for Problem and Performance Analysis
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Monitoring .
Additionally, EWM uses the application log (part of SAP NetWeaver) to store application error, warning,
and success messages issued in critical processes (for example the delivery interface between ERP and
EWM) or in UI transactions. For UI transactions, the application log has to be saved explicitly by the
user.
For general information on application logs, see the SAP Help Portal at http://help.sap.com SAP
Netweaver (select language) SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle
Management by Key Capability Application Log (BC-SRV-BAL) .
You can monitor the application logs with transaction SLG1.
Log Object
Detailed Description
/SCWM/DLV_ERP
Delivery Processing: Stores

error messages issued during
the qRFC communication of
deliveries between ERP and
EWM with an expiry time of 7
days.
Log for import of accounting Log has to be saved explicitly in transaction /SCWM/
objects from ERP
ACC_IMP_ERP ( SAP Easy Access: Extended Warehouse
Management Interfaces Administration of Accounting Data )
Log for UI messages
Log has to be saved explicitly in the EWM UI transactions.
Warehouse Logistics
Log has to be activated with transaction /SCWM/ACTLOG
Processing: Log for EWM
( SAP Easy Access: Extended Warehouse Management Settings
operations
Activate Application Log )
Site Logistic Processing: Log for
shipping and receiving
transactions
Labor Management: Log for
Log has to be saved explicitly by the user in transaction /
the sending of performance
SCWM/EPD_TRANSFER ( SAP Easy Access: Extended Warehouse
documents to HR
Management Labor Management Employee Performance Send
Performance Document to HR )
Master Data: Log for the
deletion of supply chain units
Master Data: Log for packaging The log for the determination analysis has to be activated
specifications
in transaction /SCWM/PSLOG. The log for the upload of
packaging specifications has to be saved explicitly by the
user in transaction /SCWM/IPU (SAP Easy Access: SCM
BasisMaster DataPackaging SpecificationInitial Data Transfer of
Packaging Specifications
EH&S Master Data: log for
import of master data
(dangerous goods, hazardous
substances and phrases)
Transportation Management
/SCWM/ACC
/SCMB/PATTERN_UI
/SCWM/WME
/SCWM/SHP_RCV
/SCWM/EPD
/SCMB/MD
/SCWM/PACKSPEC
/SEHS/ALE
/SCTM/TM
2011-05-24
Prerequisites
PUBLIC
13/56
Monitoring of EWM
3.3
Log Object
PPF
Post Processing Framework

Routing Guide
/SCMB/RG
Prerequisites
For descriptions of the recommended tasks to contain data growth, see Periodic Tasks [page 20].
3.3.2 Database Monitors

SAP Extended Warehouse Management uses the standard tools for this function available in the SAP
Web Application Server 7.01 and does not require a component-specific tool see the Technical
Operations Manual for SAP NetWeaver in the SAP Help Portal under SAP NetWeaver.
3.3.3 Operating System Monitors

For more information about the Operating System Collector (OS Collector), see the SAP Help Portal
under BC Computing Center Management System.
3.3.4 Workload Monitors

3.3.5 Other Important Problem Analysis and Monitoring Tools

Web Application Server 7.01 and does not require a component-specific tool. For more information,
see the Technical Operations Manual for SAP NetWeaver in SAP Help Portal at http://help.sap.com
SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 Library English SAP NetWeaver Library
Technical Operations Manual for SAP NetWeaver .
3.3.6 Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.
Web Application Server 7.01 and does not require a component-specific tool. For more information,
14/56
PUBLIC
2011-05-24
Monitoring of EWM
3.3
see the Technical Operations Manual for SAP NetWeaver in SAP Help Portal at http://help.sap.com
SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 Library English SAP NetWeaver Library
Technical Operations Manual for SAP NetWeaver
It is recommended that the following queues be monitored on the ERP side within one month as a
goods movement can only be posted in the current and previous period (e.g. a goods movement sent
to the queue on 15.07. must be posted on 31.08. at the latest):
5@ Delivery queues (beginning with DLVS)
5@ Goods movement queues (beginning with EWMGOODSMVT)
For more information about messages, see External Messages in the appendix.
3.3.7 Data Growth and Data Archiving Monitors

You can archive the following data in EWM:
Application component
Document Category
Delivery Processing
Internal Warehouse Requests (Inbound Delivery)

Internal Warehouse Requests (Outbound Delivery)
Warehouse Requests from External Systems
Warehouse Logistic Processing Warehouse Tasks and Goods Movement Documents
Warehouse Orders
Waves
Telegram Flows
Relevant Resource Data
Value-Added Service Orders (VAS Orders)
QIE Inspection Documents
Physical Inventory Documents
LIME Log Entries (goods movements and confirmed
warehouse tasks). Periodicity analogous to WME_TO
Site Logistic Processing
Door Activities
Vehicle Activities
Transport Unit Activities
Labor Management
Indirect Labor Tasks
Executed Workloads
Employee Performance Documents
Business Partners (Processors) only if created originally in
EWM
Freight Order Processing
Shipments
Freight Documents
2011-05-24
PUBLIC
Archiving Object
DLV_INB
DLV_OUT
DLV_REQ
WME_TO
WME_WO
WME_WAVE
WME_MFS
WME_RSRC
WME_VAS
QIE_INSP
LIME_PI
LIME_NLOG
WME_DOOR
WME_VEH
WME_TU
WME_ILT
WME_EWL
WME_EPD
CA_BUPA
TM_SHP
TM_FRD
15/56
Monitoring of EWM
3.4
Data Consistency
NOTE
Archiving of replicated master data (for example products, locations, supply chain units, business
partners, batch data) is not necessary in EWM. The deletion of the master data is triggered by the
solution (for example ERP, CRM), in which the master data was created originally.
For periodic tasks required to contain data growth (that is, to reorganize temporary data), refer to
Periodic Tasks [page 20].
3.4 Data Consistency

SAP EWM exchanges data with SAP ERP using asynchronous messages. If such a message exchange
fails, you can re-send messages. So cases of data inconsistency do not apply here. For more information
about check tools for checking message exchange errors, see the Other Important Problem Analysis and
Monitoring Tools section in this guide.
16/56
PUBLIC
2011-05-24
Management of SAP EWM
4.1
Starting and Stopping
4 Management of SAP EWM
SAP provides you with an infrastructure to help your technical support consultants and system
administrators effectively manage all SAP components and complete all tasks related to technical
administration and operation.
For more information about the underlying technology, see the Technical Operations Manual in the
SAP Library under SAP NetWeaver.
4.1 Starting and Stopping

EWM is provided as part of SAP SCM or as an add-on to SAP ERP.
{X~ EWM as part of SAP SCM: EWM is started/stopped together with the SCM Server (STARTSAP/
STOPSAP). For more information, see the SCM Application Operations Guide.
{X~ EWM as Add-On to SAP ERP: EWM is started/stopped together with SAP ERP (STARTSAP/
STOPSAP). For more information, see the ERP Solution Operation Guide.
We recommend in both cases that you start the interface components CIF and SAP XI (if used) after
starting EWM and that you stop them before stopping EWM.
For more information about STARTSAP/STOPSAP and SAPMMC, see the Technical Operations Manual for
SAP NetWeaver on SAP Help Portal under SAP NetWeaver SAP NetWeaver 7.0 (2004s) (select language)
SAP NetWeaver Library Administrators Guide Technical Operations Manual for SAP NetWeaver General
Administration Tasks Starting and Stopping AS ABAP and AS Java .
For the list of components required for each scenario please refer to the Scenario/Component Matrix
chapter.
Starting and Stopping CIF
See SCM Application Operations Guide.
4.2 Software Configuration

This chapter explains which components or scenarios used by this application are configurable and
which tools are available for adjusting.
Component Configuration Tools
Component Configuration Tool(s) Detailed Description
SAP SCM Basis not relevant
No technical configuration data
2011-05-24
PUBLIC
17/56
4.3
Administration Tools of Software Components
SAP EWM
not relevant
No technical configuration (all technical configuration that is

required for running SAP EWM is part of SAP NetWeaver)
4.3 Administration Tools of Software Components

SAP EWM and the underlying components are all technically based on SAP NetWeaver(SAP
enhancement package 1 for SAP NetWeaver 7.0). For information about the relevant administration
tools, see the Technical Operations Manual for SAP NetWeaver in SAP Help Portal at http://
help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) (select language) SAP NetWeaver Library
Administrators Guide Technical Operations Manual for SAP NetWeaver .
4.4 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in
case of failure.
The backup and restore strategy for Application consists of two parts:
o Backup and restore coverage for each component (see table below)
o Cross-system data dependencies and handling
The backup and restore strategy for your system landscape should not only consider SAP systems but
should also be embedded in overall business requirements and incorporate your companys entire
process flow.
In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of
a data center through fire. It is most important in this context that you ensure that backup devices are
not lost together with normal data storage (separation of storage locations).
Based on the type of application data contained in a component, we have introduced a categorization
scheme for system components that can be used to analyze the backup requirements of any system
component and to easily determine an appropriate backup method for this component. The following
table contains the appropriate Categories of System Components for Backup & Restore.
Component
Category Application Data Type Backup Method for Application Data
SAP EWM, SAP SCM Basis
XI
Orig./Repl.
Database and log backup; file system backup (full

and/or incremental)
The following table lists the components used by SAP EWM and how to back them up:
Backup
Sequence (if
required)
Component
Data to be backed up Backup Method/Tool
Recommended Backup
Frequency
SAP SCM Basis

(Category XI)
Original application
data (where data is
exchanged with
other systems; based
Application data: SAP

N/A
recommendation: daily;
redo log files periodically
(for ex. hourly) Log/
18/56
Data: Database and

log backup,
application log
backup (such as job
PUBLIC
2011-05-24
4.4
Backup and Restore
Component
Data to be backed up Backup Method/Tool
on Web AS),
application log data,
Software,
configuration data,
log data.
SAP EWM
(Category XI)
Recommended Backup
Frequency
Backup
Sequence (if
required)
logs in file system),

data consistency with
other systems must be
considered Backup
of software,
configuration, log
files
configuration files on file

system level: once a week
full backup, daily
incremental backup
Software: SAP
recommendation: after
installation and before &
after each software
change like patches and
upgrades
Original application Data: Database and
Application data: SAP
N/A
data, data exchange log backup,
recommendation: daily;
with other systems, application log
redo log files periodically
based on SAP Web AS backup (such as job (for ex. hourly) Log/
Software,
logs in file system),
configuration files on file
configuration data, data consistency with system level: once a week
log data
other systems must be full backup, daily
considered Backup incremental backup
of software,
Software: SAP
configuration, log
recommendation: after
files
installation and before &
after each software
change like patches and
upgrades
Classification
SAP EWM is the leading component for application data, for example warehouse tasks and warehouse
data. It also holds replicated data such as business partners or product data. SAP EWM exchanges data
with various components of an SAP Business Suite system landscape.
SAP EWM is based on SAP Web AS. As a component with application data, the backup/restore must
comprise database, and ABAP application server backup/restore. SAP EWM is a pure ABAP-based
component and the technical configuration data is stored in ABAP database tables.
EWM as an Add-On on ERP should always be backed up together with ERP. For the backup and recovery
of the database, the ABAP Application Server and SAP ERP, see the SAP ERP Application Operations
Guide at http://service.sap.com/instguides SAP Business Suite Applications SAP ERP SAP ERP
6.0 Operations .
There are no data dependencies between SAP EWM and other components of SAP SCM.
Backup
The backup of the database and SAP Web AS takes care of application data, configuration settings and
log data. For more information, see the Best Practice documentation for backing up and restoring SAP
Business Suite on SAP Service Marketplace at http://service.sap.com/bp-roadmap.
2011-05-24
PUBLIC
19/56
4.5
Application Copy
Online Backup
The data contained in the database can be backed up online. However, it is not possible to do the same
for the runtime infrastructure. An online backup refers to the system landscape and not the databases
that contain the business-critical application or the infrastructure components.
NOTE
If you perform a backup while the server is running, open files may not be backed up.
Restore
See the Best Practice documentation for backing up and restoring SAP Business Suite on SAP Service
Marketplace at http://service.sap.com/bp-roadmap.
Backup and Recovery of SAP Netweaver Components
For the backup and recovery concept for all other SAP NetWeaver components mentioned in this
guide, such as SAP XI, see the Technical Operations Manual for SAP NetWeaver in SAP Help Portal at
http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 Library
English SAP NetWeaver Library Technical Operations Manual for SAP NetWeaver ..
4.5 Application Copy

For a system copy of the EWM component as part of SCM or as add-on to ERP, the standard procedures
of SAP NetWeaver apply.
For more information, see the Technical Operations Manual for SAP NetWeaver under General
Administration Tasks System Copy .
Heterogeneous system copies are currently supported on request and on a project basis. More details
and forms are available under http://service.sap.com/osdbmigration.
NOTE
A client copy from one system into another system with a different operating system or database
is not an alternative to a complete heterogeneous migration. For example, client copies do not
ensure that all repository changes are taken over into the new system. Therefore, if you want to
change your database or application server platform, a heterogeneous system copy is the only
procedure that ensures full data replication into the new system.
4.6 Periodic Tasks

In addition to the standard jobs mentioned in the Technical Operations Manual for SAP NetWeaver
(in the SAP Library under SAP NetWeaver), you must schedule EWM-specific jobs in your SAP system.
All jobs, unless otherwise specified, should be run at times of minimal system activity, so as not to affect
performance or otherwise disrupt your daily operations. All jobs are restartable. There are no
dependencies between the jobs.
20/56
PUBLIC
2011-05-24
4.6
Periodic Tasks
4.6.1 Scheduled Periodic Tasks

This section describes all automatable tasks required to run periodically to keep the application running
smoothly over time. Such tasks may be required on component level and are therefore relevant in each
scenario that uses the component. You can find the mapping in the section Scenario / Component
Matrix above. Other tasks may be relevant for certain business scenarios only. It is important that you
monitor the successful execution of these tasks on a regular basis.
Standard/Housekeeping Jobs
Program Name/Task
Recommended Frequency
Transaction SARA
Depends on the archiving object

and the DB growth
Weekly/monthly
Transaction SLG2 (report

SBAL_DELETE)
Report RSPPFCLEAN
Report /LIME/COLLECTION_DELETE
Report /LIME/BACKGROUND_
DELETE_EXEC
Report /SCWM/R_REORG_
HU_WO_PRINT
Report /SAPAPO/DELETE_PRODUCTS
Report /SAPAPO/DELETE_LOCATIONS
Report /SCMB/ALEN_ALERT_DELETE
Report /SCWM/R_MS_ RESULT_DELETE
2011-05-24
Archiving of archiving objects

mentioned in section 3.2.7
Deletion of application logs
described in section 3.2.1
Same periodicity as archiving of
Deletion of PPF action data that is
deliveries
not deleted with the deletion or
archiving of the dependent object
Periodicity analogous to archiving Warehouse Logistics Processing:
periods of the confirmed
Deletes the dispatch message log for
warehouse tasks.
goods movements between EWM
and ERP
Weekly/monthly
Inventory: Deletes DB entries for
To delete zero quantities set no
zero stock quantities and on
other parameter.
request index entries without
stock. EWM index tables: /SCWM/
STOCK_IW01, _IW02, _IW03, _IW04
The index table entries are only
deleted if this is allowed in
customizing. For more
information, see the EWM
Implementation Guide (IMG)
under SCM Basis Logistics
Inventory Management Engine Basic
Settings Index Tables and Hierarchy
Determine Index Tables .
Periodicity analogous to archiving Warehouse Logistic Processing:
periods of the warehouse tasks
Deletes EWM-specific PPF action
data
Monthly
Master data: Deletes products with
deletion flag
Yearly
Master data: Deletes locations with
deletion flag
Weekly/monthly
Deletes alerts older than x days
Depends on the usage of
Labor Management (Analytics):
Measurement Services
Deletes Measurement Service
Results (SAP Easy Access screen
Extended Warehouse Management
PUBLIC
21/56
4.7
Logging On and Load Balancing
Program Name/Task
Report /SCTM/DELETE_ROUTE
Monthly
Report /SCTM/DELETE_ZONE
Monthly
Report /SCTM/CLEANUP_PPF
Yearly
Settings Measurement Services

Periodic Processing )
Master data: Deletes routes with
deletion flag
Master data: Deletes transportation
zones with deletion flag
Freight order processing: deletes
the PPF actions without
corresponding business objects
(actions to publish the deletion of
the objects)
Determines and sets prices from
ERP
Transfers extracted data from
qRCF-Queue WMTB (warehouse
task), or WMOB (warehouse order),
or WMBB (storage bin), or WMDB
(delivery item) or WMVB (Value
Added Service) to the BI Delta
Queue.
Posts differences (for example
warehouse task differences) to the
ERP system
Transaction /SCWM/VALUATION_SET
Report /SCWM/R_BW_COLLECTIVE_RUN
Report /SCWM/R_WM_ADJUST
4.6.2 Required Manual Periodic Tasks

This section describes all manual tasks required to run periodically to keep the application running
smoothly over time. A manual task needs a person to execute, in contrast to the scheduled tasks listed
above, which can be automated using a task scheduler program. Such tasks may be required on
component level and are therefore relevant in each scenario that uses the component. Other tasks may
be relevant for certain business scenarios only. It is important that you monitor the successful execution
of these tasks on a regular basis.
Required Manual Periodic Tasks
Task or Transaction
Transaction /SCWM/ Depends on the usage of price

VALUATION_SET
information in the physical inventory
process.
Weekly or monthly
Physical Inventory: get product prices from

ERP (SAP Easy Access screen Extended Warehouse
Management Physical Inventory Periodic
Processing )
4.7 Logging On and Load Balancing

SAP EWM uses standard SAP NetWeaver functions for logon and load balancing.
22/56
PUBLIC
2011-05-24
4.8
User Management
For more information, see the documentation in SAP Library at http://help.sap.com SAP
NetWeaver SAP NetWeaver 7.0 including Enhancement Package 2 SAP NetWeaver by Key Capability Solution
Lifecycle Management by Key Capability SAP High Availability .
For more information, see the Technical Operations Manual for SAP NetWeaver in the SAP Help
Portal under SAP NetWeaver.
4.8 User Management

SAP EWM uses standard SAP NetWeaver functions for user management.
For more information, see the documentation in SAP Help Portal under SAP NetWeaver 7.0 (2004s)
SAP Library SAP NetWeaver Library Administrators Guide SAP NetWeaver Security Guide User
Administration and Authentication .
For an overview of the information necessary for operating SAP NetWeaver Identity Management, see
the Solution Operation Guide on SAP Service Marketplace at http://service.sap.com/instguides
SAP NetWeaver SAP NetWeaver Identity Management SAP NetWeaver Identity Management 7.x: Documentation
Center .
4.9 Printing
SAP EWM uses the standard functionality of SAP NetWeaver for printing.
For more information, see the documentation on SAP Help Portal at http://help.sap.com/NW04
SAP NetWeaver 2004s SAP Library SAP NetWeaver Library Administrators Guide Technical Operations
Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP)
Administration Printing .
2011-05-24
PUBLIC
23/56

High Availability
5 High Availability
SAP EWM uses standard SAP NetWeaver functions for high availability.
For more information about high availability, see BC SAP High Availability NW 2004s, which you can find
on SAP Service Marketplace at http://service.sap.com/ha Media Library Documentation HA
Documentation .
2011-05-24
PUBLIC
25/56

Software Change Management
6.1
Transport and Change Management
6 Software Change Management
Software Change Management standardizes and automates software distribution, maintenance, and
testing procedures for complex software landscapes and multiple software development platforms.
These functions support your project teams, development teams, and application support teams.
The goal of Software Change Management is to establish consistent, solution-wide change management
that allows for specific maintenance procedures, global rollouts (including localizations), and open
integration with third-party products
This section provides additional information about the most important software components for SAP
EWM.
The following topics are covered:
Dj3 Transport and Change Management Enables and secures the distribution of software changes
from the development environment to the quality assurance and production environment.
Dj3 Development Request and Development Release Management Enables customer-specific
maintenance procedures and open integration with third-party products.
Dj3 Template Management Enables and secures the rollout of global templates, including
localizations.
Dj3 Quality Management and Test Management Reduce the time, cost, and risk associated with
software changes.
Dj3 Support Packages and SAP Notes Implementation Provide standardized software distribution
and maintenance procedures.
Dj3 Release and Upgrade Management Reduces the time, cost, and risk associated with upgrades.
6.1 Transport and Change Management

For transport and change management issues, SAP EWM uses the procedures of SAP NetWeaver.
For more information about the Transport and Change System, see SAP Help Portal at http://
help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaver
Library Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Software Logistics (Overview) .
2011-05-24
PUBLIC
27/56
6.2
Development Requests and Development Release Management
6.2 Development Requests and Development Release

Management
SAP EWM uses the standard procedures of SAP NetWeaver. For more information, see the Technical
6.3 Template Management

You can deploy Customizing settings by using Business Configuration Sets (BC sets).
For more information about BC sets, see the BC Set Documentation.
6.4 Quality Management and Test Management

You can use the SAP NetWeaver Development Infrastructure to learn about the various possibilities to
test your software changes.
6.5 Support Packages and Patch Implementation

We recommend that you implement Support Package Stacks (SP Stacks), which are sets of Support
Packages and patches for the respective product version that must be used in the given combination.
The technology for applying Support Packages and patches will not change.
For more information about the availability of SP stacks, see SAP Service Marketplace at http://
service.sap.com/sp-stacks.
Read the corresponding Release and Information Notes (RIN) before you apply any Support Packages
or patches of the selected SP Stack.
The RIN and Support Packages for SAP EWM are available on the SAP Service Marketplace at http://
service.sap.com/patches. Use the search function to find EHP1 FOR SAP EWM 7.0.
Use the Maintenance Optimizer (transaction DSWP) of the SAP Solution Manager to select, download,
and install the required software layers, or software components and required Support Packages. For
more information, see the following:
'N SAP Solution Manager documentation in SAP Help Portal at http://help.sap.com SAP Solution
Manager Change Management Maintenance Optimizer
'N SAP Service Marketplace at http://service.sap.com/solman-mopz
For more information about implementing Support Packages as well as possible side effects, see
http://service.sap.com/patches SAP Support Packages in Detail .
Detailed information about the tools necessary for implementing patches can be found in the Technical
Operations Manual for SAP NetWeaver on the SAP Help Portal at http://help.sap.com
Documentation SAP NetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaver Administrators
28/56
PUBLIC
2011-05-24
6.6
Release and Upgrade Management
Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP (Application
Server for ABAP) Software Logistics Software Maintenance .
6.6 Release and Upgrade Management

SAP EWM is delivered as part of SCM Server or as an Add-On to SAP ERP.
Component Release
Software Component
Release
Tool/Remark
SAP SCM Server

SAP ECC
SCM BASIS
SCMBPLUS
XI CONTENT EWM
BI CONT
QIE
SAP EWM
7.0
6.0, EHP 4
7.0
7.0
7.0
7.0 BI CONT ADDON 7.04
200
7.0
See below 1)
See below 1)
System Status
See below 2)
See below 3)
System Status
System Status
System Status
1.
2.
3.
4.
SAP SCM Server or SAP ECC 6.0

The complete list of components for SAP SCM Server or SAP ECC 6.0 can be found in the SCM
Application Operations Guide and the ERP Solution Operation Guide.
SCMBPLUS
The software component SCMBPLUS may only be used with an SCM Server installation.
Displaying the Support Package Version of XI
For details of how to display the support package version of XI, see the online documentation of
XI in the section SAP Exchange Infrastructure Design and configuration time Software logistics for XI objects
Version Management , which can be found in the Help Portal under http://help.sap.com.
Extended Maintenance
SAP offers extended maintenance for application releases based on SAP NetWeaver 2004 and higher.
If extended maintenance has been purchased for an application release, this extended maintenance
also includes extended maintenance for an add-on release for this application, as long as extended
maintenance is offered for this add-on release. However, extended maintenance is not offered for
all add-on releases.
EXAMPLE
If SAP offers extended maintenance for SAP EWM 7.0, you have installed SAP EWM 7.0 on
SAP ECC 6.0, and you have purchased extended maintenance for SAP ECC 6.0, then extended
maintenance for SAP ECC 6.0 includes extended maintenance for SAP EWM 7.0.
Information on planned maintenance durations is published in the Product Availability Matrix on
SAP Service Marketplace at http://service.sap.com/pam.
2011-05-24
PUBLIC
29/56

Troubleshooting
7 Troubleshooting
SAP EWM has no component-specific troubleshooting tools.
2011-05-24
PUBLIC
31/56

Support Desk Management
8.1
Remote Setup Support
8 Support Desk Management
Support Desk Management enables you to set up an efficient internal support desk for your support
organization that seamlessly integrates your end users, internal support employees, partners, and SAP
Active Global Support specialists with an efficient problem resolution procedure.
For support desk management, you need the methodology, management procedures, and tools
infrastructure to run your internal support organization efficiently.
The following topics are covered:
7 Remote Support
7 References to problem-solving solutions
7 Responsibility for monitoring interfaces
7 Responsibility for analyzing interface problems
7 Responsibility for solving interface problems
7 Typical problems
8.1 Remote Setup Support

For information about Remote Support Setup, see SAP Service Marketplace at http://
service.sap.com/access-support.
8.2 Problem Message Handover

For information about processing of internal support messages and forwarding them to SAP, see SAP
Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 SP15 English
Service Desk . For sending problem messages/tickets to SAP, choose the appropriate component (or
subcomponent) name from the SAP component hierarchy:
SCM EWM Extended Warehouse Management
+ SCM-EWM-ANA Analytics
+ SCM-EWM-ARC Archiving
+ SCM-EWM-AUT Authorization
+ SCM-EWM-CD Cross-Docking
+ SCM-EWM-DLP Delivery Processing
+ SCM-EWM-EH Exception Handling
+ SCM-EWM-GM Goods Movements
2011-05-24
PUBLIC
33/56
Support Desk Management
8.2
Problem Message Handover
+ SCM-EWM-IF Interfaces
+ SCM-EWM-LM Labor Management
+ SCM-EWM-MD Fulfillment Coordination
+ SCM-EWM-MFS Material Flow System
+ SCM-EWM-MON Monitoring
+ SCM-EWM-PI Physical Inventory
+ SCM-EWM-PRN Printing
+ SCM-EWM-QM Quality Management
+ SCM-EWM-RF Radio Frequency Processing
+ SCM-EWM-RG Routing Guide
+ SCM-EWM-SR Shipping and Receiving
+ SCM-EWM-TM Transportation Management
+ SCM-EWM-VAS Value Added Services
+ SCM-EWM-WAV Wave Management
+ SCM-EWM-WC Work Center
+ SCM-EWM-WOP Warehouse Order Processing
For information about safeguarding, see http://service.sap.com/safeguarding.
34/56
PUBLIC
2011-05-24
Appendix
A.1
Appendix
A Appendix
A.1 Appendix
A.1.1 Categories of System Components for Backup and
Restore
Categories of
System
Components
II
III
IV
2011-05-24
Category
Properties
Suggested Methods for Backup and Restore
Only software, dh~ No backup, new installation in case of a recovery

no configuration
or
or application
dh~ Initial software backup after installation and
data
upgrade
dh~ Backup of log files
Only software
dh~ Backup after changes have been applied or
and
dh~ No backup, new installation and configuration in
configuration
case of a recovery
information, no dh~ Backup of log files
application data
Only replicated Data:
application data, dh~ No data backup needed
replication time dh~ Backup of software, configuration, log files
is sufficiently
small for a
recovery
application data, dh~ Application-specific file system backup or
backup
dh~ Multiple instances
recommended dh~ Backup of software, configuration, log files
because
replication time
is too long, data
not managed by
a DBMS
application data, dh~ Database and log backup or
backup
dh~ Multiple instances
recommended dh~ Backup of software, configuration, log files
because
replication time
is too long, data
managed by a
DBMS
PUBLIC
Examples
BDOC modeler
SAP Gateway
Comm. Station
SAP Business
Connector
SAP IPC (2.0C)
SAP IMS/Search
Engine
SAP IPC (2.0B)
Webserver
SAP ITS
SAP IMS/Search
Engine
Webserver
SAP IPC (2.0B)

Catalog Server
35/56
Appendix
A.1
Appendix
Categories of
System
Components
VI
VII
VIII
IX
XI
Category
Properties
Original
application data,
standalone
system, data not
managed by a
DBMS
Original
application data,
standalone
system, data
managed by a
DBMS, not based
on SAP WebAS
Original
application data,
standalone
system, based on
SAP WebAS
Original
application data,
data exchange
with other
systems, data not
managed by a
DBMS
Original
application data,
data exchange
with other
systems, data
managed by a
DBMS, not based
on SAP WebAS
Original
application data,
data exchange
with other
systems, based
on SAP WebAS
Suggested Methods for Backup and Restore
Examples
Data:
,x, Application-specific file system backup
,x, Backup of software, configuration, log files
Webserver
Data:
,x, Database and log backup
Data:
Standalone SAP
,x, Database and log backup, application log backup R/3
(such as job logs in file system)
Data:
,x, Application-specific file system backup, data
consistency with other systems must be
considered
Data:
,x, Database and log backup, data consistency with
other systems must be considered
SAP liveCache
SAP Mobile
Workbench
Data:
,x, Database and log backup, application log backup
(such as job logs in file system), data consistency
with other systems must be considered
SAP R/3
SAP CRM
SAP APO
SAP BW
A.1.2 Related Guides

You can find more information about installation and configuration in the Master Guide.
36/56
PUBLIC
2011-05-24
Appendix
A.1
Appendix
A.1.3 Related Information

The following table contains links to information relating to the Application Operations Guide.
Content
Quick Link on SAP Service Marketplace
Master Guide, Installation Guide and Upgrade Guide

Related SAP Notes
Released Platforms
Network Security
http://service.sap.com/notes
http://service.sap.com/platforms
http://service.sap.com/securityguide
http://service.sap.com/network
Technical Infrastructure
SAP Solution Manager
http://service.sap.com/ti
http://service.sap.com/solutionmanager
A.1.4 External Messages

The following table contains a list of the external messages, including the system, processing, and the
application components involved. For more information about the semantics and the queues involved,
see the following sections:
:V Semantics of External Messages
:V Queues of External Messages
Message
/SCWM/INB_DELIVERY_REPLACE
/SCWM/INB_DLV_SAVEREPLICA
/SCWM/INB_PO
/SCWM/OBDLV_CHNG_QUAN_MUL
/SCWM/OUTB_DLV_CHANGE
/SCWM/OUTB_DLV_SAVEREPLICA
/SPE/INB_DELIVERY_CONFIRM_DEC
/SPE/INB_DELIVERY_REPLACE
/SPE/INB_DELIVERY_SAVEREPLICA
/SPE/INB_DELIVERY_RESPONSE
/SPE/INB_DELIVERY_SPLIT
/SPE/INB_EGR_CREATE_PROD
Sender
Syste Recipient Communication
m
System
Type
ERP
ERP
ERP
ERP
ERP
ERP
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
ERP
ERP
ERP
ERP
ERP
ERP
Function module
Function module
Function module
Function module
Function module
Function module
Function module
Function module
Function module
Function module
Function module
Function module
EWM
EWM
EWM
EWM
ERP
EWM
ERP
ERP
ERP
ERP
EWM
ERP
Function module
Function module
Function module
Function module
Function module
Function module
Monitoring Transaction
SMQ1 (EWM) / SMQ2 (ERP)

/SPE/INB_EGR_CREATE_POSA
/SPE/OUTB_DELIVERY_SAVEREPLICA
BAPI_OUTB_DELIVERY_CONFIRM_DEC
BAPI_OUTB_DELIVERY_REJECT
BAPI_OUTB_DELIVERY_SPLIT_DEC
CIFMAT, CFP1, CFM2/3
BAPI_BATCH_SAVE_REPLICA
2011-05-24
PUBLIC
37/56
Appendix
A.1
Appendix
Message
/SCWM/QFU_BY_EXTERNAL
QIE_RFC_CONF_CANCEL_EXT_INSP
QIE_RFC_CONF_CHANGE_EXT_INSP
QIE_RFC_CONF_EXT_INSP
Sender
m
System
Type
ERP
ERP
ERP
ERP
QIE_RFC_NOTIFY_RES_EXT_INSP
ERP
QIE_RFC_STATUS_INFO_EXT_INSP
ERP
/SPE/INSP_MAINTAIN_MULTIPLE
QPLEXT_RFC_INSP_LOT_CREATE
QPLEXT_RFC_INSP_LOT_CHANGE
QPLEXT_RFC_INSP_LOT_CANCEL
/SPE/GOODSMVT_CREATE
/SPE/PO_CREATE
/SCWM/IDOC_OUTPUT_GOODSMVT_CR
/SCWM/OALE_PACKSPEC_REPLICATE
/SCWM/API_PACKSPEC_REPLICATE
/SCWM/OALE_ELEMGROUP_REPLICATE
/SCWM/API_ELEMGROUP_REPLICATE
/SCWM/OALE_WORKSTEP_REPLICATE
/SCWM/API_WORKSTEP_REPLICATE
/SCWM/OALE_CONDITION_REPLICATE
/SCWM/API_CONDITION_REPLICATE
/SCWM/GTS_CBLOCK_RELEASE
EWM
QIE/
EWM
QIE/
EWM
QIE/
EWM
EWM
EWM
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
GTS
EWM
QIE/
EWM
QIE/
EWM
QIE/
EWM
QIE/
EWM
QIE/
EWM
Function module SMQ1 (EWM) / SMQ2 (ERP)

Function module ERP: SWEQADM, SWETYPV, SWELS,
SMQ1
EWM: SMQ2
SMQ1
EWM: SMQ2
SMQ1
EWM: SMQ2
SMQ1
ERP
ERP
EWM: SMQ2
ERP
Function module
ERP
Function module
ERP
ERP
ERP
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
APO/
EWM
EWM
Function module
Function module
SMQ2 (ERP)
IDOC
Function module
SMQ1
Function module
Function module
SMQ1
Function module
Function module
SMQ1
Function module
Function module
SMQ1
Function module
Function module
SM58 and report /SCWM/

GTS_CBREL_MON
38/56
PUBLIC
2011-05-24
Appendix
A.1
Appendix
Message
Sender
m
System
Type
nonSAP
nonSAP
nonSAP
EWM
EWM
EWM
nonSAP
nonSAP
nonSAP
EWM
EWM
IDOC
EWM
IDOC
EWM
IDOC
non-SAP
non-SAP
non-SAP
EWM
IDOC
EWM
IDOC
EWM
IDOC
/SCWM/MFS_RECEIVE2
nonSAP
EWM
/SCWM/R_PS_DATA_LOAD
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
EWM
BI
APO/
EWM
EWM
/SCWM/WMSUID01
/SCWM/WMTCID01
/SCWM/WMBIID01
/SCWM/WMRRID01
TMSHP1
TMFRD2
/SCWM/WMCAID01
/SCWM/WMPHID01
/SCWM/WMTOID01
/SCWM/MFS_SEND
/SCWM/BAPI_PI_DOCUMENT_COUNT
/SCWM/BAPI_PI_DOCUMENT_POST
/SCWM/BAPI_PI_DOCUMENT_DELETE
/SCWM/R_PI_STOCK_DWNLD
/SCWM/R_PI_FILEUPLD
/SCWM/BAPI_PI_DOCUMENT_CREATE
/SCWM/R_INITIALSTOCKUPLOAD
/SCWM/R_INITIALSTOCKUPLOAD
/SCWM/TLAGPS_UPLOAD
ME_APO_FORWARD_PO_TO_APO
0WM_DLVI
2011-05-24
IDOC
IDOC
IDOC
non-SAP Function module
Warehouse Management Monitor

Node MFS Telegram buffer
Outgoing Telegram
Function module Warehouse Management Monitor
Node MFS Telegram buffer
Incoming Telegram
File
BAPI
EWM
BAPI
EWM
BAPI
EWM
file
EWM
file
EWM
BAPI
EWM
file
EWM
file
EWM
file
ERP
EWM
function module
BI Data Source
PUBLIC
39/56
Appendix
A.1
Appendix
Message
0WM_EWL
0WM_EXCCODE
0WM_MS_RESULT
0WM_PL_DLVI
0WM_VAS
0WM_WO
0WM_WT
0WM_WT_WO
0WM_BIN
0WM_LGNUM_ATTR
0WM_LGNUM_TEXT
0WM_MS_TEXT
//1BEA/CRMB_DL_O_RFCCOLLRUN
/1BEA/CRMB_BD_O_RFCCOLLCANCEL
/1BEA/CRMB_BD_O_RFCPRINT
/SAPSLL/GTS_CSD_PRINTREQUEST
/SPE/AAC_DETERMINATION
Sender
m
System
Type
BI
BI
BI
BI
BI
BI
BI
BI
BI
BI
BI
BI
EWM
EWM
EWM
EWM
EWM
Report /SCWM/
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
CRM
CRM
CRM
CRM
ERP
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
BI Data Source
function module
function module
function module
function module
function module
RACC_IMP_ERP_UI
BAPI_TIMEAVAILSCHEDULE_BUILD
BAPI_WAGECOMPEXT_GETLIST
BAPI_WAGECOMPEXT_CREATE
BAPI_WAGECOMPEXT_DELETE
/SPE/INB_CALL_TRX_VL60
/SPE/WBS_ELEM_CONV_INT_EXT
/SCWM/DLV_DELTA_SELECT
BAPI_BATCH_GET_DETAIL
BAPI_OBJCL_GETCLASSES
/SPE/GET_T156
/SPE/MBEW_GEN_ARRAY_READ
L_MM_MATERIALS_READ_QUANTITY
CONVERSION_EXIT_CORPR_INPUT
BAPI_MATERIAL_AVAILABILITY
/SAPSLL/API_6800_TEWM_SYNCH
/SCWM/GTS_SCRAPPING_RELEASE
/SCWM/GTS_SHP_PROC_RELEASE
/SAPSLL/API_6800_SYNCH_MASS
/SAPSLL/API_LCLIC_EXTNO_GET
40/56
ERP
HR
ERP
HR
EWM
EWM
EWM
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
EWM
GTS
GTS
EWM
EWM
EWM
function module
EWM
function module
ERP HR
ERP HR
ERP
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
GTS
EWM
EWM
GTS
GTS
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
PUBLIC
Report /SCWM/ERP_STOCKCHECK
2011-05-24
Appendix
A.1
Appendix
Message
/SAPSLL/API_SYNCH_PRECIP_SPI
/SAPSLL/EWM_SAKE_ERROR
/SAPSLL/API_6800_SCRP_SYNCH
/SCWM/MATERIAL_RFC_READ
/SCWM/DATE_TO_PERIOD_CONVERT
/SCWM/FIRST_DAY_IN_PERIOD_GET
/SCWM/GET_ACCOUNT_OF_PERIODS
/SCWM/LAST_DAY_IN_PERIOD_GET
/SCWM/T009B_READ_MULTI
/SCMB/MDL_KEYC_BY_VRSIOEX
/SCMB/MDL_LOC_GET
/SCWM/LOCATION_RANGE_GETF4
/SAPAPO/PFCS_VALID_PERKZ_GET
/SAPAPO/PFCS_DEMAND_KYFSEM_GET
BAPI_APOATP_CHECK
/SCMB/MDL_LOCPROD_READ_MULTI
DespatchedDeliveryNotification_Ou
Sender
m
System
Type
GTS
EWM
EWM
APO
APO
APO
APO
APO
APO
APO
EWM
APO
APO
APO
EWM
APO
EWM
EWM
GTS
GTS
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
APO
EWM
non-SAP
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
function module
XI
SXMB_MONI
nonSAP
EWM
EWM
XI+WEBservice
SXMB_MONI
non-SAP XI
SXMB_MONI
EWM
non-SAP XI
SXMB_MONI
EWM
non-SAP XI
SXMB_MONI
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
t
/SCWM/BIF_YRD_VAPP_QR
VehicleAppointmentCreatedNotifica
tion_Out
VehicleAppointmentChangedNotifica
tion_Out
VehicleAppointmentCancelledNotifi
cation_Out
/SCWM/BIF_YRD_VAPP_CHANGE_RC
/SCWM/BIF_YRD_VAPP_CAIN_RC
/SCWM/BIF_YRD_VAPP_CAOUT_RC
/SCWM/BIF_YRD_VAPP_CHIN_RC
/SCWM/BIF_YRD_VAPP_CHOUT_RC
/SCWM/BIF_YRD_VAPP_CONN_RC
/SCWM/BIF_YRD_VAPP_DISC_RC
2011-05-24
PUBLIC
41/56
Appendix
A.1
Appendix
Message
/SCWM/BIF_YRD_VAPP_LOCK_RC
/SCWM/BIF_YRD_VAPP_ULOCK_RC
/SCWM/BIF_YRD_DAPP_QR
/SCWM/BIF_YRD_DAPP_CREATE_RC
/SCWM/BIF_YRD_DAPP_CANCEL_RC
/SCWM/BIF_YRD_DAPP_LOCK_RC
/SCWM/BIF_YRD_DAPP_ULOCK_RC
DockAppointmentChangedNotifica
tion_Out
DockAppointmentCreatedNotifica
tion_Out
DockAppointmentCancelledNotifica
tion_Out
/SCWM/BIF_YRD_TAPP_BLOCK_RC
/SCWM/BIF_YRD_TAPP_QR
/SCWM/BIF_YRD_TAPP_CAIN_RC
/SCWM/BIF_YRD_TAPP_CAOUT_RC
TransportationUnitAppointmentCrea
tedNotification_Out
TransportationUnitAppointmentCan
celledNotification_Out
TransportationUnitAppointmentChan
gedNotification_Out
/SCWM/BIF_YRD_TAPP_CHANGE_RC
/SCWM/BIF_YRD_TAPP_CHIN_RC
/SCWM/BIF_YRD_TAPP_CHOUT_RC
/SCWM/BIF_YRD_TAPP_LOCK_RC
42/56
Sender
m
System
Type
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
PUBLIC
2011-05-24
Appendix
A.1
Appendix
Message
/SCWM/BIF_YRD_TAPP_ULOCK_RC
/SCWM/BIF_YRD_TAPP_UBLOC_RC
TransportationUnitAppointmentLoad
ingAdvancedNotification_Out
/SCWM/RFID_ACTION
/SCWM/RFID_AII_EWM
/AIN/PUB_IDCONV_ENCODE
/AIN/PUB_IDCONV_ENCODE_NUMGEN
/AIN/PUB_IDCONV_DECODE
/AIN/PUB_IDCONV_FORMATS_GET
/AIN/PUB_DEVCOM_SPOOL_PRINT
/AIN/ID_ALT_FORMATS_GET
/AIN/ID_ENCODE_NUMGEN
/AIN/AutoIDLabel_PrintRC
/SCWM/BIF_DLV_ID_QR ID
/SCWM/BIF_DLV_OD_QR
DeliveryInformation_Out
DeliveryInformation_Out
/SCWM/BIF_WH_ID_QR
/SCWM/BIF_WHAREA_ID_QR
/SCWM/BIF_SUBAREA_QR
/SCWM/BIF_STAGAREA_QR
/SCWM/BIF_BIN_QR
/SCWM/BIF_WRKSTAT_QR
/SCWM/BIF_DOOR_QR
/SCWM/BIF_CHCKPNT_QR
/SCWM/BIF_SBWHSEAREA_QR
/SCWM/BIF_SBSUBAREA_QR
2011-05-24
Sender
m
System
Type
nonSAP
nonSAP
nonSAP
All
All
EWM
EWM
EWM
EWM
EWM
EWM
EWM
EWM
nonSAP
nonSAP
EWM
EWM
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
EWM
XI+WEBservice
SXMB_MONI
EWM
XI+WEBservice
SXMB_MONI
EWM
XI
SXMB_MONI
EWM
EWM
All
All
All
All
All
All
All
All
EWM
function module
WEBservice
function module
function module
function module
function module
function module
WEBservice
WEBservice
WEBservice
XI+WEBservice
EWM
XI+WEBservice
non-SAP XI
non-SAP XI
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
PUBLIC
43/56
Appendix
A.1
Appendix
Message
/SCWM/BIF_SBSTAGAREA_QR
/SCWM/BIF_SBBIN_QR
/SCWM/BIF_SBWRKSTAT_QR
/SCWM/BIF_SBDOOR_QR
/SCWM/BIF_SBCHCKPNT_QR
/SCWM/BIF_HU_QR
/SCWM/BIF_INV_QR
RFC_READ_TABLE (query table
Sender
m
System
Type
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
nonSAP
EWM
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
EWM
XI+WEBservice
ERP
function module Report /SCWM/
U_11008)
R_PSA_REPLICATE
(Transaction /SCWM/
PSA_REPLICATE)
/SCWM/ERP_PSA_STOCK_QUERY
/SCWM/OUTB_DLV_CANCELLATION
IDENTITY_MODIFY
IDENTITY_RETRIEVE
ERP
ERP
other
other
EWM
EWM
EWM
EWM
function module
function module
function module
function module
Identity Center Monitoring

Identity Center Monitoring
A.1.4.1 Semantics of External Messages

Message
Semantics
Replacement request
Replicate inbound
delivery
Communicate Purchase
Order changes
Quantity change request
for multiple delivery items
Change outbound
deliveries
Replicate outbound
delivery
Confirms goods receipt for
inbound deliveries
Report changes of
inbound deliveries
/SCWM/INB_PO
44/56
PUBLIC
Application Components
Sender
Recipient
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
2011-05-24
Appendix
A.1
Appendix
Message
Semantics
Replicate inbound
delivery
Response to replacement
request of ERP
Communicate delivery
split
Request Goods Receipt
Notifications
Replicate outbound
delivery (without
predecessor document)
Confirms goods issue for
outbound deliveries, stock
posting changes and
returns deliveries; sends
IBGI message (invoice
before goods issue)
Response to quantity
change request of ERP
Communicate delivery
split
Material Master
Distribution (CIFMAT as
ALE message type for CIF,
CFP1 (periodic transfer of
changes from ERP) or
CFM2/3 (CIF initial
transfer) or ERP Core
Update with BTE for CIF)
Creates new batch with
valuation in ERP
Triggers putaway for an
inspected stock
Confirm cancellation of
inspection
Confirm change
inspection
Confirm creation of
inspection lot
Results of inspection lot
Notify status of inspection
lot
2011-05-24
PUBLIC
Sender
Recipient
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-INB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-EWM-IF-ERP
LO-SPM-OUTB
SCM-APO-INT-MD
SCM-APO-INT-MD
SCM-EWM-MD-BA
LO-SPM-RET
SCM-EWM-QM-RP
QM-IM
CA-QIE
QM-IM
CA-QIE
QM-IM
CA-QIE
QM-IM
CA-QIE
QM-IM
CA-QIE
45/56
Appendix
A.1
Appendix
Message
Semantics
Sends Inspection result of

a return item to ERP for
distribution to CRM
Create inspection lot in
ERP
Change inspection lot in
ERP
Cancel inspection lot in
ERP
This message creates goods
movement documents in
ERP. Only valid for goods
movements without ERP
delivery.
Create a STO in ERP
Goods Movement Create
Replicate packspec header
Receiving replicated
packspec header
Replicate packspec
element group
packspec element group
Replicate packspec
workstep
packspec workstep
Replicate packspec
condition record
packspec condition record
Release customs-blocked
stock. Creates a stock
transfer document from
customs-blocked stock to
normal stock
Move Handling Unit
Confirm warehouse task
Block storage bins
Release wave
Send/Receive shipment to/
from an external planning
system
/SPE/PO_CREATE
/SCWM/WMSUID01
/SCWM/WMTCID01
/SCWM/WMBIID01
/SCWM/WMRRID01
TMSHP1
46/56
PUBLIC
Sender
Recipient
SCM-EWM-QM-RP
LO-SPM-RET
CA-QIE
QM-IM-IL
CA-QIE
QM-IM-IL
CA-QIE
QM-IM-IL
SCM-EWM-IF-ERP
LO-SPM-STO
SCM-EWM-QM
LO-SPM-STO
SCM-EWM-IF-ERP
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SCMB-BAS-PAK-PS
SLL-LEG
SCM-EWM-IF-GTS
SCM-EWM-IF-WCU
SCM-EWM-IF-WCU
SCM-EWM-IF-WCU
SCM-EWM-IF-WCU
SCM-EWM-TM
SCM-EWM-TM
2011-05-24
Appendix
A.1
Appendix
Message
Semantics
TMFRD2
Send/Receive a freight
document to/from an
external planning system
Cancellation /
Cancellation Request of WO
Create and distribute PickHus
Create warehouse task
Send Telegram to PLC
Receive Telegram from
/SCWM/WMCAID01
/SCWM/WMPHID01
/SCWM/WMTOID01
/SCWM/MFS_SEND
/SCWM/MFS_RECEIVE2
Sender
Recipient
SCM-EWM-TM
SCM-EWM-TM
SCM-EWM-IF-WCU
SCM-EWM-IF-WCU
SCM-EWM-IF-WCU
SCM-EWM-MFS
SCM-EWM-MFS
PLC
A.1.4.2 Queues of External Messages

Message
Queue Name
DLVS<logicalsystemERP><ClientERP>
<Number_of_originial_ERP_Delivery>. For example
DLVSQ4LCLNT4000180010219
/SCWM/INB_PO
DLWS<logicalsystemEWM><ClientEWM>. For example

DLWSA3PCLNT0010180010317




2011-05-24
PUBLIC
47/56
Appendix
A.1
Appendix
Message
Queue Name
n/a




CFMAT<matnr>, CFLD<src.logsys><number><counter>
WMCC<batchno><productno>
DLVS<logical_system><delivery_number>
For example DLVSQ4LCLNT4000084001775

QI<logical system><inspection_document_number>
For example QIQ1PCLNT401000000112127





DLWS<logical_system><delivery_number>
For example DLWSQ4LCLNT4000084001775




EWMGOODSMVT or <delivery_queue> (For example ROD-AFS)
/SPE/PO_CREATE
EWMSQPO<purchase order external ID>
For example EWMSQPO4500000028

PSID<PSID>
PSID<PSID>
PSEG<PSEG>
PSEG<PSEG>
PSWS<PSWS>
PSWS<PSWS>
PSID<PSID>
48/56
PUBLIC
2011-05-24
Appendix
A.1
Appendix
Message
Queue Name
PSID<PSID>
/SCWM/WMSUID01
/SCWM/WMTCID01
/SCWM/WMBIID01
/SCWM/WMRRID01
TMSHP1
TMFRD2
/SCWM/WMCAID01
/SCWM/WMPHID01
/SCWM/WMTOID01
/SCWM/MFS_SEND
/SCWM/MFS_RECEIVE2
A.1.4.3 Internal Messages

EWM
Component
Queue Name
Semantics
IDP + ODP
WMD<DOCCAT><DOCCNO>
IDP + ODP
WMDL<DOCCAT><DOCCNO>
SLP
TU_DLV_<GUID>
SLP
WMSTL<TRANSMEANS_ID>
SLP
WMDI-<LOGSYSOWNSRACT_NUM>
SLP
WMSI-<LOGSYSOWNSRACT_NUM>
WLP
EWMWV_<LGNUM><WAVE>
IDP
DLV_PP_LOOP_<LOOP_COUNTER>
WLP
WMTR_<WT_NUMBER>
WLP
WMTP_<WT_NUMBER>
WLP
WMTH<HUIDENT>
WLP
EWMV<LGNUM><VAS_ID>
WLP
WMDP<DOCCAT><DOCNO>
WLP
WMDP<DOCCAT><DOCNO>
Warehouse request confirmation

Warehouse request confirmation
using persistant locks
TU update after change to delivery
Create TU/vehicle via DLV PFF
Invoice Before Goods Issue (Delivery)
Invoice Before Goods Issue (Shipping)
Update of the wave item after delivery
Update of the priority points in
inbound deliveries
Follow-up of HU warehouse task
creation for resources
Follow-up of product warehouse task
creation for process-oriented storage
control
Follow-up of product warehouse task
creation for process-oriented storage
control
Asynchronous update of the VAS
order for a changed delivery item and
for the synchronous update of a
locked VAS order
WT creation for delivery
GR posting via PPF action
2011-05-24
PUBLIC
Monitoring
Transaction
SMQ2
SMQ2
SMQ1
SMQ1
SMQ1
SMQ1
SMQ2
SMQ2
SMQ2
SMQ2
SMQ2
SMQ2
SMQ2
SMQ2
49/56
Appendix
A.1
Appendix
EWM
Component
Queue Name
Semantics
MD
WMBB
Update of the BW relevant data of bins

used when executing program /SCWM/
Monitoring
Transaction
SMQ1
R_BW_COLLECTIVE_RUN
IDP + OOP
WMDB
Update of the BW relevant data of

delivery items used when executing
program /SCWM/
SMQ1
R_BW_COLLECTIVE_RUN
WLP
WMTB

warehouse tasks used when executing
program /SCWM/
SMQ1
R_BW_COLLECTIVE_RUN
WLP
WMOB

warehouse orders used when
executing program /SCWM/
SMQ1
R_BW_COLLECTIVE_RUN
WLP
WMVB

value added services used when
executing program /SCWM/
SMQ1
R_BW_COLLECTIVE_RUN
WLP
WMTM<LGNUM><PLC>
IDP
DLVSREACTIVATE<DOCNO>
WLP
EWMKTS<LGNUM><DOCNO>
TM
<DOCNO>
TM
<DOCNO>
IDP
UL<LGNUM><RSRC>
WLP
WMTU<HUIDENT>
ODP
WMOD<LGNUM><WHO>
SM
WMIP<DOCNO>
50/56
Determine the next warehouse task

for sending to the MFS
Reactivate inbound delivery with
cross Hus in case of locking issue
Creation of VAS for Kit to stock in case
of locking issue of corresponding
deliveries
Update from FOM to FD
Update from FOM to ODO
Update inbound delivery
asynchronously
Unpacking of HU after WT
confirmation
Trigger goods issue for production
supply with outbound delivery
Posting of inventory differences in
case of lost/found HUs
PUBLIC
SMQ2
SMQ2
SMQ2
SMQ1
SMQ1
SMQ1
SMQ2
SMQ2
SMQ2
2011-05-24
Reference
B.1
The Main SAP Documentation Types
B Reference
B.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software.
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.
2pSGu Target group:
2pSG Relevant for all target groups
2pSGu Current version:
2pSG On SAP Help Portal at http://help.sap.com Glossary
2pSG In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes.
2pSGu Target group:
2pSG Consultants
2pSG System administrators
2pSG Project teams for implementations or upgrades
2pSG On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels. A collective security guide is available for SAP NetWeaver. This document contains
general guidelines and suggestions. SAP applications have a security guide of their own.
2pSGu Target group:
2pSG System administrators
2pSG Technology consultants
2pSG Solution consultants
2pSG On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required installable
units for each business or IT scenario. It provides scenario-specific descriptions of preparation,
2011-05-24
PUBLIC
51/56
Reference
B.1
execution, and follow-up of an implementation. It also provides references to other documents, such
as installation guides, the technical infrastructure guide and SAP Notes.
*2o Target group:
*2o Technology consultants
*2o Project teams for implementations
*2o Current version:
*2o On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking into
account the combinations of operating systems and databases. It does not describe any business-related
configuration.
*2o Target group:
*2o On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes, and
implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
*2o Target group:
*2o Solution consultants
*2o In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The
Customizing activities and their documentation are structured from a functional perspective. (In order
to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,
which refers to the relevant Customizing activities in the individual SAP systems, is used.)
*2o Target group:
*2o Solution consultants
*2o Project teams for implementations or upgrades
*2o In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers
52/56
PUBLIC
2011-05-24
Reference
B.1
users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup/restore, master data maintenance, transports, and tests.
\ Target group:
\ s System administrators
\ Current version:
\ s On SAP Service Marketplace at http://service.sap.com/instguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks.
\ Target group:
\ s System administrators
\ s Technology consultants
\ s Solution consultants
\ Current version:
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of
an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.
\ Target group:
\ s Project teams for upgrades
\ Current version:
The upgrade guide describes the technical upgrade of an installable unit, taking into account the
combinations of operating systems and databases. It does not describe any business-related
configuration.
\ Target group:
\ s Project teams for upgrades
\ Current version:
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release. Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG).
\ Target group:
2011-05-24
PUBLIC
53/56
Reference
B.1
t6<1 Consultants
t6<1 Project teams for upgrades
t6<^ Current version:
t6<1 On SAP Service Marketplace at http://service.sap.com/releasenotes
t6<1 In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguides
54/56
PUBLIC
2011-05-24
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 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.

Application Operations Guide SAP Extende PDF

Uploaded by

Document Information

Original Title

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

Application Operations Guide SAP Extende PDF

Uploaded by

Copyright:

Available Formats

Application Operations Guide

SAP Extended Warehouse Management Operations Guide

Copyright 2011 SAP AG. All rights reserved.

Emphasized words or expressions

First version of the SAP EWM Application Operations Guide

Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Management of SAP EWM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Required Manual Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1.1 Global Definitions

1.2 Important SAP Notes

Important SAP Notes

Important SAP Notes

Installation of SCMBPLUS 700 on NW 7.0 EHP 1

Technical System Landscape

2 Technical System Landscape

2.1 Scenario/Component Matrix

2.2 Related Documentation

Application- and Industry-specific

Quick Sizer Tool

Quick Link on SAP Service Marketplace

This page is left blank for documents

Alert Monitoring with CCMS

3.1 Alert Monitoring with CCMS

3.1.1 CCMS Monitoring Installation and Setup

Selection and Processing of Post Processing Framework Actions

3.1.2 SAP EWM Monitor

3.2 Selection and Processing of Post Processing Framework

3.3 Detailed Monitoring and Tools for Problem and

3.3.1 Trace and Log Files

Detailed Monitoring and Tools for Problem and Performance Analysis

Delivery Processing: Stores

Detailed Monitoring and Tools for Problem and Performance Analysis

Post Processing Framework

3.3.2 Database Monitors

3.3.3 Operating System Monitors

3.3.4 Workload Monitors

3.3.5 Other Important Problem Analysis and Monitoring Tools

3.3.6 Interface Monitors

Detailed Monitoring and Tools for Problem and Performance Analysis

3.3.7 Data Growth and Data Archiving Monitors

Internal Warehouse Requests (Inbound Delivery)

3.4 Data Consistency

Management of SAP EWM

Starting and Stopping

4 Management of SAP EWM

4.1 Starting and Stopping

See SCM Application Operations Guide.

4.2 Software Configuration

Management of SAP EWM

Administration Tools of Software Components

No technical configuration (all technical configuration that is

4.3 Administration Tools of Software Components

4.4 Backup and Restore

Category Application Data Type Backup Method for Application Data

SAP EWM, SAP SCM Basis

Database and log backup; file system backup (full

Data to be backed up Backup Method/Tool

SAP SCM Basis

Application data: SAP

Data: Database and

Management of SAP EWM