BEST-PRACTICE-EWM-pdf.pdf

Best-Practi Best-P ractice ce Docu Document ment

SAP EW EWM Solu Soluti tion on Monit Monitori oring ng

Dietmar-Hopp-Allee 16 D-69190 Walldorf  DATE January.2013 SAP PRODUCT(S) SAP Extended Warehouse Management OPERATING SYSTEM(S)  All

PRODUCT PRODU CT VERSI VERSION(S) ON(S)  All DATABASE(S)  All

 ALM PHASE(S) Run SAP SOLUTION MANAGER 7.1 SP Generic

© 2013 SAP AG

SAP SOLUTION MANAGER WORK CENTER(S) Business Process Operations

Best-Practice Document SAP EWM Solution Monitoring

Table Table of Cont ents 1

Management Summary

3

2

Goal of Using This Service

4

2.1 Staff and Skills Requirements

4

2.2 Duration and Timing

5

2.3 Related Best-Practice Documents

5

Best-Practice Document

6

3.1 Preliminary Tasks

6

3.2 Business Process: SAP EW M Inbound Process

6

3.3 Typical Monitoring Requirements and Objects in the EW M Inbound Process

9

3

3.3.1 Inbound Deliveries 3.3.2 Queued Remote Function Call (qRFC)

10

3.3.3 In Inbound Delivery Notification

10

3.3.4 Post Goods Receipt

11

3.3.5 IDoc Interface to External Systems

12

3.3.6 Confirm Warehouse Task via Radio Frequency Device

12

3.4 Typical Monitoring Requirements and Objects in the EW M Inbound Process

13

3.5 Typical Monitoring Requirements and Objects in the EW M Inbound Process

15

3.5.1 Outbound Deliveries

15

3.5.2 Queued Remote Function Call (qRFC)

15

3.5.3 Outbound Delivery Request

16

3.5.4 Outbound Deliv ery Order

16

3.5.5 W ave Release/Create W arehouse Order and Warehouse Task

17

3.5.6 IDoc Interface to External Systems

18

3.5.7 Confirm Warehouse Task via Radio Frequency Drive

18

3.5.8 Post Goods Issue

18

3.6 Typical Monitoring Requirements and Objects – Process Independent

4

9

19

3.6.1 Post Processing Framework (PPF) Actions

19

3.6.2 EW M Housekeeping Jobs

20

Further Inf ormation

22

4.1 Ba B ackground Inf ormation and References

22

4.1.1 Monitoring via SAP Solution Manager

22

4.1.2 Monitoring via Easy Graphics Framework/Measurement Services

23

4.1.3 Monitoring via Warehouse Management Monitor

24

4.1.4 Quick Reference

25

4.1.5 Templates

27

4.2 Index

© 2013 S AP AG

27

page 2/28

Best-Practice Document SAP EWM Solution Monitoring

1

Management Summary

This best-practice document gives orientation for identifying suitable application-oriented and technical monitoring objects. This will help you to set up an overall monitoring concept t o detect upcoming problems in the business process flow of your EWM solution at an early stage. This document focuses on the core EWM inbound and outbound processes, and hi ghlights some important monitoring requirements and possibilities for critical steps and interfaces. This document describes an example inbound and outbound flow on a high l evel, as well as critical steps and general transactions and tools used for monitoring. In general, existing monitoring concepts and procedures need to be extended according to the new business processes, technologies, and interfaces to prepare the support organization for upcoming challenges. The outcome of this best practice will be a documentation of t he following: Transactions, reports, documents and interfaces in the scope of monitoring activities Description of monitoring activity and KPIs Monitoring frequency and alerting Responsibilities and activities (escalation path) 

  

This document is not intended to describe all existing possibilities and variants, but provides a starting point for your project and process-specific setup. It is recommended that you also check other available best-practice documents, which have detailed information regarding the following topics:   

   

RFC Monitoring Job Scheduling Management Background Job monitoring with SAP Solution Manager  ALE Monitoring Manage APO Core Interface General Business Process Management SAP Business Process Management for ERP Logistics

© 2013 SAP AG

page 3/28

Best-Practice Document SAP EWM Solution Monitoring

2

Goal of Using This Service

With the introduction of a new EWM solution, new technologies, processes, and interfaces are rolled out that need to be considered within the overall solution monitoring. Therefore it is highly recommended to identify critical steps in terms of performance and stability as soon as possible within the implementation phase to set up and define the monitoring concept accordingly. The chapters below will highlight some important steps and documents that should be considered within your  monitoring concept. This overview serves as a basis and is not a complete list; therefore, it needs to be adapted and improved according to your needs. In general, monitoring is possible to be done within the EWM system by using the related transactions on a regular basis. Furthermore, it i s possible to set up aut omated monitoring and alerting within SAP Solution Manager for specific key figures.

2.1

Staf f and Sk ill s Requ ir emen ts

To implement this best-practice document, the f ollowing teams and skills are required:  Application Management Team This team creates the Business Process Monitoring concept, and consists of experts from several areas of  your company: Business department  

Solution support organization (for example, Basis support and application support)



Implementation project team

Business Process Operations Team The Business Process Operations team is responsible for applying the resulting procedures derived from implementing this best practice. This team includes the f ollowing groups: Responsibles designated to perform business-process-oriented monitoring and ensure that the process runs smoothly (such as the business process champion for each business process) 



All parties in your Solution Support organization and IT department involved in monitoring focused on the application aspects (Application Support, Development Support, Job Scheduling Management)

SAP Technical Operations Team All parties in your solution support organization and IT department involved in monitoring focused on the system administration side (program scheduling management, Software Monitoring team, and System Administration team, including the system administrator) 

Business Process Champion The business process champion is the person in the business department who is responsible for  successful execution of the business process. He or she coordinates all activities necessary for the business process. Therefore, the business process champion is usually responsible for the escalation paths in case of problems. If the Business Process Operations team needs to escalate an issue, then the business process champion will be involved accordingly. 

More information about roles and responsibilities of these teams can be found in the best-practice document General Business Process Management . This best-practice document is available in the SAP Service Marketplace at the following link: https://service.sap.com/solutionmanagerbp.

© 2013 SAP AG

page 4/28

Best-Practice Document SAP EWM Solution Monitoring

2.2

Duration and Timing

Usually, we recommend that you consider this best practice during the build and implementation phase of an SAP EWM project. The background for this is that critical steps and interfaces are identified up front the scheduled integration and performance tests. Thus it is possible to monitor these steps during the test activities and to apply corrective actions to the planned go live at an early stage.

2.3

Relat ed Bes t-Pr ac tic e Doc umen ts

Other important best-practice documents are available in the SAP Service Marketplace, quick link /enterprisesupport SAP Enterprise Support Academy Best Practices. If a document is not yet available in the SAP Enterprise Support Academy, pl ease use the following link: https://service.sap.com/solutionmanagerbp. 

 

These relevant best-practice documents are: General Business Process Management : This document explains the procedures that should be used to 





create a general Business Process Management concept. This includes the definition and documentation of the core business processes, definition of monitoring objects, definition of monitoring activities (including error handling procedures), monitoring tools and monitoring frequencies, the definition of communication and escalation procedures, and the assignment of responsibilities.  ALE Monitoring: This best-practice document helps with the setup of an interface monitoring concept , with a focus on ALE Monitoring for SAP solutions. This document outlines possible ways to optim ally monitor   ALE-based interfaces manually, as well as automatically by using SAP Solution Manager. Both monitoring approaches aim to detect any irregularities or deviations, or to detect error situations at an early stage. RFC Monitoring: This best-practice document helps you set up an Interface Monitoring concept with a



focus on RFC Monitoring for your SAP solution. This document outlines how best to m onitor RFC-based interfaces manually, as well as automatically by using SAP Solution Manager. Both monitoring approaches aim to detect any irregularities or deviations or to detect error situations at an early stage. Job Scheduling Management: This best-practice document provides a detailed description of what SAP recommends as a standardized formal process to support a job request process, including an end user job request form and an approval process. SAP Business Process Management for ERP Logistics: This best-practice document supports the setup of  a Business Process Monitoring concept f or SAP ERP solutions. The concept aims to define proc edures for  business-process-oriented monitoring, error handling, and escalations for ERP core business processes. These procedures ensure a smooth and reliable flow of the core business processes so that business requirements are met. Background Job Monitoring with SAP Solution Manager : This best-practice document will help on the



setup of proper background job monitoring in the framework of Business Process Monitoring in SAP Solution Manager. Manage APO Core Interface: This best-practice document enables you to set up a business process





management and monitoring concept for business processes that are part of SAP Supply Chain Management (SAP SCM) using SAP ERP and SAP Advanced Planning & Optimization (SAP APO) and that use the Core Interface (CIF) for data t ransfer between an SAP APO system and one or several SAP ERP systems.

© 2013 SAP AG

page 5/28

Best-Practice Document SAP EWM Solution Monitoring

3 3.1

Best-Practice Document Preliminary Tasks

Before mapping the topics mentioned in this best-practice document to your SAP EWM solution landscape, you need to ensure that you have a good overall picture of your solution. Therefore, you need to involve the following resources, who will be responsible for the processes in scope: 

 

Business department (business process owner, key user) Solution support organization (for example Basis support and application support) Implementation project team

These experts have a clear understanding of the core business processes and therefore are required for  performing this best practice. The following prerequisites are important for defining and implementing a proper monitoring concept: 

   

Identification of core business processes, systems , interfaces involved, and steps (transactions/reports) performed Clear understanding of performance-critical business process steps and possible time constraints Key performance indicators (KPI) of critical steps Discovery of volume-intensive business process steps and interfaces Evaluation of data volumes and peak times

Identification of business-critical documents that require status monitoring (open/overdue documents)

3.2

B us in es s Pr oc es s: SAP EWM In bo un d Pr oc es s

Purpose:  The inbound process is an essential part of the supply chain and is used to receive products into the warehouse based on, for example, a purchase order, stock transport order, scheduling agreement, or  returns order. Below you will find an example business process description.

© 2013 SAP AG

page 6/28

Best-Practice Document SAP EWM Solution Monitoring

Busines Process Descripti on: The inbound process is an essential part of the supply chain. This process includes the steps after the creation of the purchase order, inbound delivery documents, execution of internal warehouse tasks belonging to the putaway process, and goods receipt posting of the ordered goods. The inbound process normally begins in the SAP ECC system when either an inbound delivery is created for  a purchase order, or an advanced shipping notification (ASN) is received directly from the vendor via EDI interface and converted into an inbound delivery document. During inbound delivery data transfer from the SAP ECC system to the SAP EWM system, an inbound delivery notification (IDN) is generated in the SAP EWM system. Subsequently, a second EWM document is created from the IDN, which is the inbound delivery (ID). This step is performed via the Post Processing Framework (PPF) action /SCDL/IDR_TRANSFER, and is usually triggered directly after the inbound delivery notification is saved.  After creation of the inbound delivery in the SAP EWM system, a first goods receipt posting into the received on dock (ROD) storage location takes place. This means that goods have already been physically delivered and are in the goods receipt area, available to be stored in the warehouse. At this point in the process, the goods are of stock type “Unrestricted-Use in Putaway” and are therefore not yet available for picking. When you activate the inbound delivery in the SAP EWM system (transaction /SCWM/PRDI), the GR posting can be executed either manually or automatically via a PPF action. This first goods receipt posting into the ROD storage location is transmitted back from SAP EWM to the SAP ECC system, through qRFC interface to update Inventory Management stock values in the S AP ECC system.

© 2013 SAP AG

page 7/28

Best-Practice Document SAP EWM Solution Monitoring

In this business process example, process-oriented storage control with a deconsolidation step will be used.  A handling unit warehouse task (HU WT) will be created for each movement, and one product warehouse task will be created for each packed material. From the EWM inbound delivery (ID) document, handling unit warehouse tasks and still-inactive product warehouse tasks are created either manually or automatically, via PPF action, to start the putaway process. Subsequently, these tasks are printed out and distributed to the resources, who will execute the assigned tasks physically. After that, the delivered goods are moved from the goods receipt area to the deconsolidation area, where first warehouse internal putaway activities take place. In this step, the HU WT determines which HUs and quantities should be moved, where they should be picked from (source location), and where they have to be transported to (destination location, in this case, deconsolidation area). When delivered goods have been physically moved from the goods receipt area to the deconsolidation area, the corresponding HU WT must be confirmed in the SAP EWM system. The confirmation of WTs informs SAP EWM that determined tasks have been physically completely executed. Confirmation can be performed using radio frequency (RF) devices, for example (transaction /SCWM/RFUI). RF devices are connected to t he SAP EWM system via WLAN through ITSmobile technology. If there are any packaging specifications for the unpacked goods that should be put away, the system can call packaging specification determination automatically based on customizing settings. In the same way, labels for the corresponding handling units can be printed out automatically by the system using a PPF action. In the deconsolidation area, delivered handling units are physically unpacked and single products within are sorted and repacked into new HUs (optional) for further putaway into final storage bins in the warehouse.  After repacking of the products, the original handling unit in which products were delivered should be closed in the SAP EWM system. When closing the HU, product warehouse tasks are activated automatically for  single products. These product warehouse tasks are used to perform the putaway into the final storage bin. If there is an external non-SAP subsystem for management of an automated warehouse involved, relevant information from the warehouse tasks created in the SAP EWM system might be required and should be sent to the subsystem. This WT information is transferred to the external system through SAP standard IDoc interface /SCWM/WMTORD. When corresponding tasks are physically completed, the confirmation is transmitted back from the external system to the SAP EWM system through SAP standard IDoc interface /SCWM/WMTOCO, which updates the status of the WT in the SAP EWM system to “Confirmed”.  After goods hav e been m oved to the final storage bin, the product WTs need to be confirmed to inform t he SAP EWM system that tasks are physically completed. Warehouse orders (and corresponding warehouse tasks assigned to them) can be confirmed via the EWM Warehouse Monitor (transaction /SCWM/MON), /SCWM/TO_CONF (Confirm Warehouse Task), or RF device. When the final putaway warehouse task is confirmed in the SAP EWM system, an automatic stock posting from the ROD storage location to the available-for-sale (AFS) stock takes place. This means that products are now available for picking activities in the outbound process. Finally, this posting is also replicated automatically into the SAP ECC system via qRFC interface t o update Inventory Management stock v alues.

© 2013 SAP AG

page 8/28

Best-Practice Document SAP EWM Solution Monitoring

During the ROD to AFS posting change in the SAP EWM system, the PPF message IBDLV_CONFIRM_DEC_CI is sent to the corresponding SAP ECC system by using the qRFC Interface. This is triggered by PPF action /SCWM/MSG_PRD_SEND, which can be found i n the inbound delivery.

3.3

Typical Monitoring Requirements and Objects in the EWM Inbound Process

3.3.1

Inbou nd Deli veri es

Inbound deliveries created in SAP ECC system that are relevant for processing in SAP EWM will be replicated to EWM as an inbound delivery notification (IDN) document. Normally, inbound deliveries are created via an IDoc received from a vendor or m anually in the SAP ECC system. Monitoring Requirements: Monitoring of open inbound deliveries without goods receipt posting where the expected delivery date is exceeded 3.3.1.1

Monito ring via SAP Soluti on Manager 

The delivery object in the SAP ECC system can be monitored using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. The application monitor allows you to monitor the object inbound delivery using predefined throughput and backlog indicators. The following key figures are specifically recommended for monitoring open or overdue inbound deliveries (there is no complete list of available indicators):  

Inbound Deliveries (open) Inbound Deliveries (overdue)

3.3.1.2

Bus iness Monitor ing

The following transaction codes can be used for monitoring of inbound deliveries: VL33N (Display Inbound Delivery) VL06i (Inbound Delivery Monitor) VL60 (Inbound Delivery Processing)   

Via transaction code VL33N, you can check the current status of different activities related to the inbound delivery. It is possible to check either the current overall status or the status of each single item of the delivery. Four different statuses are possible for those activities: Blank: Not relevant  A: Not yet processed B: Partially processed C: Completely processed Transaction code VL06i allows you to identify and display inbound deliveries based on predetermined criteria, such as “Delivery Date”. Transaction code VL60 allows you to identify and check inbound deliveries by “Vendor” and/or “External Delivery Number”.

© 2013 SAP AG

page 9/28

Best-Practice Document SAP EWM Solution Monitoring

3.3.2

Queued Remote Function Call (qRFC)

The qRFC technology is used to exchange transactional data, like deliveries and updates, for deliveries between the SAP ECC system and SAP EWM systems. This interface should be processed without errors. If  errors occur, the problem should be resolved as quickly as possible. Detailed information on qRFCs, such as queue naming conventions and related function modules, can be found in the following chapters of the EWM Application Operations Guide: A.1.4.2 Queues of external messages A.1.4.3 Internal messages You can find this document in the SAP Service Marketplace: http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP EWM -> Using SAP EWM 7.0.  

Monitoring Requirements: Errorless processing of qRFCs, no hanging queues, and no qRFCs in status sysfail 3.3.2.1 Monito ring via SAP Soluti on Manager  The qRFCs in your ECC/EWM solution can be monitored using the qRFC backlog and status monitoring functionality within Business Process Monitoring (BPMon) in SAP Solution Manager. This application monitor  can be set up to monitor backlog and status information of qRFC queues. The following key figures are specifi cally recommended for qRFC monitoring: qRFC Status Monitoring = Key figures relating to the status of queues and how long a queue has had a given status qRFC Backlog Monitoring = Key figures relating to the number of queue entries and their oldest age 



3.3.2.2

Bus iness Monitor ing

The following transaction codes can be used for monitoring of qRFCs: SMQ1 - qRFC Monitor for the outbound queue. This transaction is used to monitor the status of the LUWs in the outbound queue. SMQ2 - qRFC Monitor for the inbound queue. This transaction is used to monitor the status of the logical units of work (LUWs) in the inbound queue. /SCWM/MON (in SAP EWM system only) -> Tools -> Message Queue 





Comprehensive information regarding technical background and monitoring for qRFCs can be found in the best-practice document “RFC Monitoring”. 3.3.3

Inbound Delivery Notification

Inbound deliveries created in the SAP ECC system that are relevant for processing in SAP EWM will be replicated to SAP EWM, leading to the creation of an inbound delivery notification (IDN). This document contains all logistic data for the inbound delivery process and is used to create an inbound delivery. Monitoring Requirements: Inactive IDN documents that might prevent creation of inbound delivery required for inbound process 3.3.3.1

Monito ring via SAP Soluti on Manager 

Currently, it is not possible to monitor inbound delivery notifications vi a SAP Solution Manager.

© 2013 SAP AG

page 10/28

Best-Practice Document SAP EWM Solution Monitoring

3.3.3.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM for monitoring of inbound deliv ery notifications: /SCWM/IDN (Maintain Inbound Delivery Notification) /SCWM/MON (Warehouse Monitor) -> Alert -> Inactive Delivery Documents  

Using transaction code /SCWM/IDN, active as well as inactive inbound delivery notifications can be displayed. When using the Warehouse Monitor /SCWM/MON, the Inactive Delivery Documents  node can be used to display inactive delivery documents by using the document category “IDR” and header status DVA=4 (activate with errors). 3.3.4

Post Good s Recei pt

The goods receipt posting represents the physical receiving of products in your warehouse. With the goods receipt posting for an inbound delivery, you increase the stock in the warehouse. Using the qRFC interface, the goods receipt posting is replicated to the SAP ECC system, where delivery is updated accordingly and material documents are posted. Monitoring Requirements:  

Replication of goods receipt posting to the SAP ECC system using qRFC Open Delivery documents in SAP ECC without GR posting

3.3.4.1 Monito ring via SAP Soluti on Manager  Inbound delivery items with and without goods receipt can be monitored using available throughput and backlog indicators within the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. For monitoring purposes, the following key figures are recommended: Overdue Inb. Deliv. Items without Goods Receipt (backlog) Inbound Delivery Items with Goods Receipt (throughput)  

3.3.4.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM for monitoring of inbound deliv eries: /SCWM/PRDI (Maintain Inbound Delivery) /SCWM/MON (Warehouse Monitor) -> Inbound -> Documents -> Inbound Delivery /SCWM/EGF (Warehouse Cockpit): graphical display of measurement services   

With transaction /SCWM/PRDI, inbound deliveries can be selected depending on the goods recei pt status. When using the Warehouse Monitor SCWM/MON the Inbound Delivery node (Inbound -> Documents -> Inbound Delivery) can be used to monitor inbound deliveries. You can use the Warehouse Cockpit (/SCWM/EGF) for graphical display of key figures by using tailored measurement services (TMS). You can use the wizard (transaction code /SCWM/TLR_WIZARD) to set up the measurement services and variants used for selection. The following basic measurement services (BMS) available in the standard can be used to set up tailored measurement services for the i nbound delivery (in SAP EWM): Number of Inbound Deliveries Number of Inbound Delivery Items  

© 2013 SAP AG

page 11/28

Best-Practice Document SAP EWM Solution Monitoring

3.3.5

IDoc Interface to External Systems

If an external non-SAP warehouse management system is connected, relevant information from the warehouse tasks created in SAP EWM will be transferred to the external system via IDoc of message type /SCWM/WMTORD. The confirmation of the warehouse task will be transferred to SAP EWM with the IDoc of  message type /SCWM/WMTOCO, which will update the status of the warehouse task in SAP EWM. Further  IDoc message types used for communication with external systems are: /SCWM/WMBBIN Block Storage Bins /SCW M/WMCATO Cancellation/Cancellation Request for Transf er Order   /SCWM/WMPIHU Create and Distribute Pick-HU /SCWM/WMRREF Release reference number   /SCWM/WMSUMO Move Handling Unit Monitoring Requirements: 



Performance and volume of IDoc interface, specifically confirmation of warehouse task using IDoc of  message type SCWM/WMTORD and SCWM/WMTOCO Errorless processing of IDocs

3.3.5.1

Monito ring via SAP Soluti on Manager 

The IDoc interfaces can be monitored using Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. This monitoring functionality allows you to perform error and backlog monitoring for  the monitoring object IDoc. Specifically for IDoc monitoring, the following key figures are available: “Delta” monitor – number of suitable IDocs since the last data collection “Total number” monitor – number of suitable IDocs for the last x days  

3.3.5.2

Bus iness Monitor ing

The following transaction codes can be used in SAP ECC/EWM to monitor IDocs: BD87 (Status Monitor for ALE messages) WE02 (Display IDoc)  

The created and failed IDocs can be monitored via transaction BD87 or WE02. Any inbound IDoc having an Error status (for example 51) inhibits the normal inbound flow. Usually, an IDoc is not posted properly because of some error messages in the application, for example missing or incorrect master data. Comprehensive information regarding technical background and monitoring for IDocs can be found in the best-practice document “ALE Monitoring”.

3.3.6

Confirm Warehouse Task via Radio Frequency Device

Warehouse task confirmation is often performed by warehouse workers using mobile radio frequency (RF) devices connected to the SAP EWM system using ITSmobile. Performance of RF transactions (for example, picking, packing, and putaway) is a critical topic for efficient warehouse operations and user satisfaction.

© 2013 SAP AG

page 12/28

Best-Practice Document SAP EWM Solution Monitoring

Monitoring Requirements: Performance of RF transactions used f or picking, packing, and putaway 3.3.6.1

Monito ring via SAP Soluti on Manager 

Currently, it is not possible to monitor performance of specific RF transactions via SAP Solution Manager. 3.3.6.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM for monitoring of performance of individual timecritical RF steps: ST13 (Analysis and Service Tools) -> PERF_TOOL -> EWM_RF_Analysis  

STAD (SAP Workload: Business Transaction Analysis)

 A tool is available that allows detailed logging of RF response t imes for function modules and transactions that are triggered by the RF device. This tool consists of two parts: Analysis Utility: ST/A-PI (version 01P or higher) needs to be implemented according to SAP Note 69455. Backend runtime measurement: To activate logging on a per-resource level, SAP Note 1690850 needs to be implemented.  

Please refer to SAP Note 1595305 – “Measuring runtimes for RF devices in SAP EWM” for availability and further information and documentation, such as the EWM RF Performance Monitoring Tool - User Guide. The screenshot below shows the output of the RF performance tool for putaway steps performed via Radio Frequency transaction /SCWM/RFUI.

With transaction STAD, you can analyzed the statistical performance records with regard to performance values.

3.4

Typical Monitoring Requirements and Objects in the EWM Inbound Process

Purpose:   The EWM outbound process is an essential part of the supply chain and is used to distribute ordered products from the warehouse or distribution center to the customer or storage locations. Below you will find an example business process description.

© 2013 SAP AG

page 13/28

Best-Practice Document SAP EWM Solution Monitoring

Description: The outbound process is an essential part of the supply chain. This process includes the steps after the creation of the sales order, outbound delivery documents, execution of picking warehouse tasks belonging to the picking process, and goods issue posting of the products. The inbound process normally begins in the SAP ECC system when sales order documents are created via transaction VA01, or from IDocs received from external systems. Outbound deliveries can be created in several ways, for example: - VL01N (create outbound delivery) - VL01NO (create outbound delivery without reference), - VL10B (for stock transport orders) - VL10A (sales order). When an outbound delivery document is created that is relevant for processing in SAP EWM, it will be distributed via qRFC to the SAP EWM system. There are two ways to distribute the outbound delivery from the SAP ECC system to the SAP EWM system: - When you save the outbound delivery document, it will be distributed immediately to SAP EWM. - Distribution via scheduled report VL06O (delivery monitor) Outbound deliveries created i n the SAP ECC system from sales documents that are relevant for processing in SAP EWM will be replicated to SAP EWM, leading to the creation of an outbound delivery request (ODR) document. The outbound delivery request is a document containing all the relevant logistics data required for  processing in SAP EWM.

© 2013 SAP AG

page 14/28

Best-Practice Document SAP EWM Solution Monitoring

 An outbound delivery order (ODO) is created automatically from the outbound delivery request via the Post Processing Framework (PPF). Waves are used to group delivery items and to create warehouse orders and tasks for the assigned items. Waves can be created manually using transaction /SCWM/WAVE or automatically by using wave templates. With the release of the wave, warehouse tasks will be created and grouped into warehouse orders according to warehouse order creation rules. Waves can be released in three different ways, for example: - Automatic wave release (a job is scheduled to release waves according to specified criteria) - Manual wave release with transactions /SCWM/WAVE or /SCWM/MON Picking activities are generally performed by warehouse workers using radio frequency (RF) devices or pick by voice, or within external systems connected via IDoc. With the physical goods issue posting in SAP EWM, printing of delivery documents will be triggered and the physical departure of products from the warehouse will take place. The goods issue posting can be done, for example, for deliveries by using transaction /SCWM/PRDO or for transportation units by using transaction /SCWM/TU.

The goods issue posting will be replicated to the SAP ECC system using qRFC. This updates the outbound delivery status and performs the related material postings.

3.5

Typical Monitoring Requirements and Objects in the EWM Inbound Process

3.5.1

Ou tb ou nd Del iv eri es

Creation of outbound deliveries is often performed using transaction VL10 in background/batch with a high number of deliveries per cutoff. In general, multiple cutoff times exist throughout the day to support different order types, such as stock orders or urgent orders to the customer. Monitoring Requirements: Performance of delivery creation depending on document volume and time constraints Open/overdue outbound deliveries  

3.5.1.1

Monito ring via SAP Soluti on Manager 

The delivery object can be monitored using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. The application monitoring part of BPMon allows you to monitor outbound deliveries using predefined throughput and backlog indicators. Specifically for monitoring of open or overdue outbound deliveries, the following key figures are recommended (there is no complete list of available indicators): Outbound Deliveries (open) Outbound Deliveries (overdue)  

3.5.1.2

Bus iness Monitor ing

The following transaction codes can be used to monitor outbound del iveries in the SAP ECC system: VL03N (Display Outbound Delivery) VL06O (Outbound Delivery Monitor)  

3.5.2

Queued Remote Function Call (qRFC)

Please refer to chapter Queued Remote Function Call (qRFC). © 2013 SAP AG

page 15/28

Best-Practice Document SAP EWM Solution Monitoring

3.5.3

Outbound Delivery Request

Outbound deliveries created in the SAP ECC system that are relevant for processing in SAP EWM will be replicated to SAP EWM, leading to the creation ofoutbound delivery request (ODR) documents. This ODR document, in general, contains all logistic data for the outbound delivery process and is used to create an outbound delivery order (ODO). Monitoring Requirements: Inactive ODR documents that might prevent creation of an ODO required for the outbound process 3.5.3.1

Monito ring via Solutio n Manager 

Currently, it is not possible to monitor outbound delivery requests vi a SAP Solution Manager. 3.5.3.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM to monitor outbound deliv ery requests: /SCWM/ODR (Maintain Outbound Delivery Request) /SCWM/MON (Warehouse Monitor) -> Alert -> Inactive Delivery Documents  

You can display active and i nactive outbound delivery notifications by using transaction code /SCWM/ODR. When using the Warehouse Monitor /SCWM/MON, you can use the Inactive Delivery Documents  node to display inactive delivery documents by using the document category “ODR” and header status DVA=4 (activate with errors). 3.5.4

Ou tb ou nd Del iv er y Ord er  

 An outbound delivery order (ODO) is created automatically from the outbound delivery request (ODR) via the Post Processing Framework (PPF). The outbound delivery or der is a document containing all the data required to trigger and monitor the complete outbound delivery process. Monitoring Requirements: Monitoring of overdue outbound delivery order items without goods issue posting or warehouse task created 3.5.4.1

Monito ring via SAP Soluti on Manager 

The EWM object “Outbound Delivery Order” can be monitored using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. The application monitor allows you to monitor the object outbound delivery order using predefined throughput and backlog indicators. The following backlock key figures can be set up for monitoring of outbound delivery order items: Overdue Order Items without Warehouse Task Overdue Order Items without Goods Issue Created Order Items Order Items with Goods Issue    

3.5.4.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM to monitor the out bound delivery order: /SCWM/PRDO (Maintain Outbound Delivery Order) 

© 2013 SAP AG

page 16/28

Best-Practice Document SAP EWM Solution Monitoring

 

/SCWM/MON (Warehouse Monitor) -> Outbound -> Documents -> Outbound Delivery Order  /SCWM/EGF (Warehouse Cockpit) by use of measurement services

Outbound delivery orders can be displayed with transaction code / SCWM/PRDO. When using the Warehouse Monitor SCWM/MON, you can use the Outbound Delivery Order  node (Outbound -> Documents -> Outbound Delivery Order ) to monitor and analyze outbound delivery orders. The Warehouse Cockpit (/SCWM/EGF) can be used for graphical display of key figures using tailored measurement services (TMS). You can use a wizard (transaction /SCWM/TLR_WIZARD) to set up the measurement services and variants used for selection. The following basic measurement services (BMS) available in the standard can be used to set up tailored measurement services for the object outbound delivery order: Number of Outbound Delivery Orders Number of Outbound Delivery Items  

3.5.5

Wave Release/Create Warehouse Order and Warehouse Task

If wave processing is used on the customer side, SAP EWM creates the warehouse tasks and the warehouse orders when releasing the wave. Warehouse tasks are instructions for movement of specific products and quantities from a source to a destination bin. Warehouse orders are used to assemble work packages containing one or more warehouse tasks for an individual warehouse worker. Monitoring Requirements Performance of wave release (warehouse order/task creation), considering time constraints and volume Errorless release of wave Open/overdue warehouse order and task   

3.5.5.1

Monito ring via Solutio n Manager 

The EWM object “Wave” can be monitored using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. The application monitor allows you to monitor the object wave using predefined backlog indicators. The following backlog key figures can be set up to monitor the status of waves: Overdue Waves Waves Released with Defects  

The following key figures can be set up to monitor warehouse orders/tasks (inbound, outbound, or internal): Overdue Warehouse Orders Confirmed Warehouse Orders Overdue Warehouse Tasks Overdue Replenishment Tasks Created Warehouse Task Items Confirmed Warehouse Task Items Confirmed Warehouse Task Items with Exception       

© 2013 SAP AG

page 17/28

Best-Practice Document SAP EWM Solution Monitoring

3.5.5.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM for status/error monitoring or for performance analysis: /SCWM/MON (Warehouse Monitor) /SCWM/EGF (Warehouse Cockpit) /SCWM/WAVE (Maintain Waves) SLG1 (Application Log) STAD (SAP Workload: Business Transaction Analysis)     

The Warehouse Monitor (/SCWM/MON) is the central tool for monitoring and analyis of waves, warehouse orders, and warehouse tasks using the following nodes: Wave (Outbound -> Documents -> Wave) Warehouse Order (Documents -> Warehouse Order ) Warhouse Task (Documents -> Warehouse Task)   

The Warehouse Cockpit (/SCWM/EGF) can be used f or graphical display of key figures. The following basic measurement services (BMS) available in the standard can be used to set up tailored measurement services for the object’s warehouse order or task: Number of Warehouse Tasks Number of Warehouse Orders  

One of several transactions you can use to monitor open or to-be-released waves is transaction /SCWM/WAVE. The wave obj ect might have one of the following statuses: - Initial - Released for Withdrawal - Released - Locked - Transferred to Subsystem - Released with Defects If application logging is activated using transaction /SCWM/ACTLOG, transaction SLG1 can be used to analyze actions and possible errors that occurred during wave release, warehouse order creation, and warehouse task creation. By using transaction STAD, you can analyze the statistical performance records with regard to performance values. 3.5.6

IDoc Interface to External Systems

Please refer to chapter Queued Remote Function Call (qRFC) in inbound process. 3.5.7

Confirm Warehouse Task via Radio Frequency Drive

Please refer to chapter Confirm Warehouse Task via Radio Frequency Drive in inbound process. 3.5.8

Post Goods Issue

The goods issue posting represents the physical departure of products from your warehouse. With the goods issue posting, you reduce the stock in the warehouse. With the qRFC interface, the goods issue posting is

© 2013 SAP AG

page 18/28

Best-Practice Document SAP EWM Solution Monitoring

replicated to the SAP ECC system, where the delivery is updated accordingly and material documents are posted. Monitoring Requirements: Performance of goods issue posting Replication of goods issue posting to the SAP ECC system using qRFC Open delivery documents in SAP EWM and SAP ECC without goods issue posting   

3.5.8.1

Monito ring via Solutio n Manager 

The EWM object “Outbound Delivery” can be monitored using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. The application monitor allows you to monitor the “Outbound Delivery” object using predefined throughput and backlog indicators. The following throughput and backlock key figures can be set up for the “Outbound Delivery” object: Overdue without Goods Issue Created Outbound Delivery Items  

3.5.8.2

Bus iness Monitor ing

The following transaction codes can be used in SAP EWM for status/error monitoring and for performance analysis: /SCWM/FD (Maintain Outbound Delivery) SLG1 (Application Log) STAD (SAP Workload: Business Transaction Analysis)   

By using transaction /SCWM/FD, you can select and monitor outbound deliveries, for example, depending on the goods issue status. If application logging is activated using transaction /SCWM/ACTLOG for object GI_PARALLEL, application log entries are written during parallel goods issue on a transportation unit (TU). You can use transaction SLG1 to analyze actions and possible errors that occurred during goods issue posting. In addition, the log will contain the TU number and the end time of the various parallel GI steps, such as synchronization, final delivery creation, goods issue, and delivery update (confirmation). See SAP Note 1734933 “Enhancement of  the parallel GI application log”. In general, you can select the application log for outbound delivery orders by using transaction SLG1: Specify the EWM outbound delivery order number or final delivery reference in the search criteria fieldExternal ID.

You can use transaction STAD to analyze the statistical performance records with regard to performance.

3.6

Typical Monitoring Requirements and Objects – Process Independent

3.6.1

Post Processing Framework (PPF) Actions

SAP EWM uses the Post Processing Framework (PPF) to perform specific actions. It is a tool for the generic execution of functions and processes. The condition technique is used to find the appropriate condition records for performing a PPF action.

© 2013 SAP AG

page 19/28

Best-Practice Document SAP EWM Solution Monitoring

SAP EWM uses the PPF, for example, for the f ollowing purposes: - Printing - Communication to other systems, such as SAP E CC system or SAP Global Trade Services system - Asynchronous updates between busine ss objects within SAP EWM Monitoring Requirements: Unprocessed PPF actions Incorrectly processed PPF actions

 

3.6.1.1

Monito ring via Solutio n Manager 

The EWM object “PPF Actions” can be monitored using Business Process Monitoring (BPMon) functionality provided in the SAP Solution Manager. The application monitor allows to monitor the object “PPF Actions” using predefined throughput and backlog indicators. The following throughput and backlock key figures can be set up to monitor “PPF Actions”: Unprocessed PPF Actions Incorrectly Processed PPF Actions Processed PPF Actions Created PPF Actions    

3.6.1.2

Bus iness Monitor ing

The following transaction code can be used in SAP EWM for status/error monitoring: SPPFP (Process Actions) 

PPF actions are generated by applications that use the Post Processing Framework. Successful customizing and configuration using transaction SPPFCADM must be completed before actions can be generated by applications that use the PPF. The actions themselves are generated in the corresponding application. When you are in dialog mode, actions are selected according to the selection criteria and displayed in SAP List Viewer (ALV). From this list, you can select individual actions (or all of them) and process them. In the case of a repeated processing, a copy of the action is created and this copy is processed. 3.6.2

EWM Ho us ek eep in g Jo bs

EWM-specific housekeeping jobs need to be considered for periodic scheduling/execution and handover to the support organization. These periodic tasks must be run periodically to keep the application running smoothly over time. It is necessary to monitor the successful execution of periodic tasks on a regular basis. Some example housekeeping reports and transactions are listed below: 

/SCWM/ERP_STOCKCHECK - Compare the stock data between SAP EWM and the SAP ECC system



SLG2 - Delete expired logs



/LIME/BACKGROUND_DELETE_EXEC - Delete DB entries for zero stock quantities and on request index entries without stock  

 

You can find detailed information on SAP EWM housekeeping jobs in the following chapter of the EWM  Application Operations Guide: © 2013 SAP AG

page 20/28

Best-Practice Document SAP EWM Solution Monitoring

4.6.1 Scheduled Periodic Tasks



You can find this document in the SAP Service Marketplace: http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP EWM -> Using SAP EWM 7.0. 3.6.2.1

Monito ring via Solutio n Manager 

Job monitioring can be set up using the Business Process Monitoring (BPMon) functionality provided in SAP Solution Manager. Monitoring and alerting can be set up to monitor issues that might occur during background job processing, for example:   Cancellation

 

Start/End Delay



Maximum Duration

You can find details on the setup of job monitoring in the best-practice document “Background Job monitoring with SAP Solution Manager”, which is available in the SAP Service Marketplace. 3.6.2.2

Bus iness Monitor ing

The following transaction codes can be used to monitor job logs and cancelled jobs: SM37 (Simple Job Selection) 

© 2013 SAP AG

page 21/28

Best-Practice Document SAP EWM Solution Monitoring

4 4.1

Further Information B ac kgr ou nd In fo rmat io n an d Refer enc es

Chapter 3 discussed typical monitoring objects that are relevant for your SAP EWM implementation. Below, you will find further important background information on monitoring tools, such as SAP Solution Manager, Warehouse Cockpit/Measurement Services, and the Warehouse Monit or. 4.1.1

Monitoring via SAP Solution Manager 

General Information: By using the Business Process Monitoring session within SAP Solution Manager, you can monitor a dedicated business process and raise alerts (via mail or SMS, or directly in SAP Solution Manager) if  necessary. The monitoring functionality has two parts: application monitoring (throughput, backlog) and technical monitoring (background jobs, performance, update terminations). Monitoring has to be set up within SAP Solution Manager according to your requirements.  Application monitoring can be used to support business operations, and helps to identify areas of concern, especially unexpected backlog situations. The application monitor is based on Throughput and Backlog Indicators (TBIs). TBIs are available for various application areas. Each application area provides key figures that help to identify a TBI. By the counter definition for a certain key figure, it is possible to define the selection criteria, the frequency of  the automated data selection in the satellite system (SAP ECC or SAP EWM), and the thresholds values for a red or yellow rating. For further information regarding SAP Solution Manager please refer to http://service.sap.com/solutionmanager  For further information regarding Business Process Monitoring in SAP Solution Manager, refer to http://service.sap.com/BPM -> Media Library -> Customer Information or  http://service.sap.com/BPM -> Media Library -> Technical Information In the links above you will find detailed documentation such as: - Key Figure Overview - Setup Roadmap - Setup Guides The figure below shows an example business process setup in SAP Solution Manager with monitoring actviated for the following steps: - Create Outbound Delivery - Release Waves - Confirm Warehouse Tasks You can find further information on the alerts and thresholds by drilling down to the alert list.

© 2013 SAP AG

page 22/28

Best-Practice Document SAP EWM Solution Monitoring

4.1.2

Monitoring via Easy Graphics Framework/Measurement Services

The Easy Graphics Framework (EGF) can be used in SAP EWM to display important warehouse key figures, for example, for warehouse supervisors in real time, and to refresh these figures automatically. Within SAP EWM, you can access the W arehouse Cockpit by using transaction /SCWM/EGF. For creation and display of own key figures in the Warehouse Cockpit, you can set upmeasurement services, for example, by using transaction /SCWM/TLR_WIZARD (tailored measurement services). In addition to the standard objects delivered by SAP, it is possible to create and display your own objects. The figure below shows an example implementation of the Warehouse Cockpit.

© 2013 SAP AG

page 23/28

Best-Practice Document SAP EWM Solution Monitoring

You can find more information, such as the EGF Implementation Guide, in the SAP Service Marketplace: http://service.sap.com/scm -> SAP SCM in Detail -> Warehousing -> Information on EWM in SAP SCM -> Technical Information. The EGF Implementation Guide describes how to visualize warehouse process data in various chart types with the Easy Graphics Framework. 4.1.3

Monitoring via Warehouse Management Monitor 

The warehouse management monitor is the central tool for a warehouse supervisor to monitor and evaluate the current situation in the warehouse. Using this tool, the supervisor can evaluate and observe all activities, as well as stock and bi n situations.

© 2013 SAP AG

page 24/28

Best-Practice Document SAP EWM Solution Monitoring

You can find more information, such as how to add application content to the warehouse monitor, in the SAP Service Marketplace: http://service.sap.com/scm -> SAP SCM in Detail -> Warehousing -> Information on EWM in SAP SCM -> Technical Information -> Adding Application Content to the Warehouse Monitor . This document contains guidelines regarding the monitor framework, which offers a means to modify the monitor  according to customer needs. 4.1.4

Quick Ref eren ce

The table below provides a quick overview of the monitoring possibilities for different transactions/steps.

Object / Step Inbound Delivery

queued Remote Function Call (qRFC)

Inbound Delivery Notification

P os t G oods Rec eipt

© 2013 SAP AG

Business Monitoring via Transaction - VL33N (Display Inbound Delivery) - VL06i (Inbound Delivery Monitor) - VL60 (Inbound Delivery Processing) - SMQ1 – outbound queue - SMQ2 – inbound queue - /SCWM/MON (Warehouse Monitor) -> Tools -> Message Queue - /SCWM/IDN (Maintain Inbound Delivery Notification) - /SCWM/MON (Warehouse Monitor) ->  Alert -> Inactive Delivery Documents - /SCW M/PRDI ( Mai nt ain Inb ound Delivery) - /SCWM/MON (Warehouse Monitor) -> Inbound -> Documents -> Inbound Delivery - /SCWM/EGF (Warehouse Cockpit) by use of measurement services

Monitoring vi a SAP Solution Manager *

Comment

- Inbound Deliveries (open) - Inbound Deliveries (overdue) - qRFC Status Monitoring - qRFC Backlog Monitoring

Best-practice document “RFC Monitoring”

no key figure available

- Overdue Inb. Deliv. Items without Goods Receipt (backlog) - Inbound Delivery Items with Goods Receipt (throughput)

page 25/28

Best-Practice Document SAP EWM Solution Monitoring

Object / Step

Business Monitoring via Transaction

Monitoring vi a SAP Solution Manager *

IDoc Interface to external systems

- BD87 (Status Monitor for ALE messages) - WE02 (Display IDoc)

- ‘Delta’ monitor – number of  suitable IDocs since the last data collection - ‘Total number’ monitor – number  of suitable IDocs for the last x days no key figure available

Confirm Warehouse Task via Radio Frequency Device

- ST13 (Analysis and Service T ools) -> PERF_TOOL -> EWM_RF_Analysis - STAD (SAP Workload: Business Transaction Analysis)

Outbound Deliveries

- VL03N (Display Outbound Delivery) - VL06O (Outbound Delivery Monitor)

- Outbound Deliveries (open) - Outbound Deliveries (overdue)

Outbound Delivery Request

- /SCWM/ODR (Maintain O utbound Delivery Request) - /SCWM/MON (Warehouse Monitor) ->  Alert -> Inactive Delivery Documents

no key figure available

Outbound Delivery Order

- /SCWM/PRDO (Maintain Outbound Delivery Order) - /SCWM/MON (Warehouse Monitor) -> Outbound -> Documents -> Outbound Delivery Order  - /SCWM/EGF (Warehouse Cockpit) by use of measurement services

- Overdue Order Items without Warehouse Task - Overdue Order Items without Goods Issue - Created Order Items - Order Items with Goods Issue

Wave Release / Create Warehouse Order and Warehouse Task

- SCWM/MON (Warehouse Monitor) - SCWM/EGF (Warehouse Cockpit) - SCWM/WAVE (Maintain Waves) - SLG1 (Application Log) - STAD (SAP Workload: Business Transaction Analysis)

Post Goods Issue

- SCW M/FD (Maintain Outbound Delivery) - SLG1 (Application Log) - STAD (SAP Workload: Business Transaction Analysis)

- Overdue Waves - Waves released with defects - Overdue Warehouse Orders - Confirmed W arehouse Orders - Overdue Warehouse Tasks - Overdue Replenishment Tasks - Created Warehouse Task Items - Confirmed Warehouse Task Items - Confirmed Warehouse Task Items with Exception - Overdue without Goods Issue - Created Outbound Delivery Items

Post Processing Framework (PPF) Actions

- SPPFP (Process Actions)

- Unprocessed PPF Actions - Incorrectly Processed PPF  Actions - Processed PPF Actions - Created PPF Actions

EW M Hous ek eep in g J obs

- SM 37 (Si mpl e J ob S el ec ti on)

- J ob m on iti ori ng (C anc el lati on, Start-/End delay, Maximum Duration)

Comment Best-practice document “ALE Monitoring”

SAP Note 1595305 –   “Measuring runtimes for  RF devices in SAP EWM”

SAP Note 1734933 “Enhancement of the parallel GI application log”

- Reference: EWM  Application Operations Guide - Best-practice document “Job Scheduling Management”, “Background Job monitoring with SAP Solution Manager”

  * Key figures and monitoring objects availble in the SAP standard; no complete list (for a complete list of  available key figures, refer to the key figure overview in the SAP Service Marketplace (see chapter Monitoring via SAP Solution Manager ).

© 2013 SAP AG

page 26/28

Best-Practice Document SAP EWM Solution Monitoring

4.1.5

Templates

The table structure below can be used as a template for specifying relevant monitoring objects. Monitoring Object

4.2

Tool / Trx for  Monitoring

Frequency

Monitoring  Ac ti vit y

Responsibility

Escalation Path

Index

/LIME/BACKGROUND_DELETE_EXEC ........... 20

STAD .................................................... 13, 18, 19

/SCDL/IDR_TRANSFER ..................................... 7

VA01 ................................................................ 14

/SCWM/ACTLOG.............................................. 19

VL01N .............................................................. 14

/SCWM/EGF..........................................11, 17, 18

VL01NO ........................................................... 14

/SCWM/ERP_STOCKCHECK........................... 20

VL03N .............................................................. 15

/SCWM/FD ....................................................... 19

VL06i .................................................................. 9

/SCWM/IDN...................................................... 11

VL06O ......................................................... 14, 15

/SCWM/MON ................... 8, 10, 11, 15, 16, 17, 18

VL10A .............................................................. 14

/SCWM/MSG_PRD_SEND ................................. 9

VL10B .............................................................. 14

/SCWM/ODR .................................................... 16

VL33N ................................................................ 9

/SCWM/PRDI................................................ 7, 11

VL60 .................................................................. 9

/SCWM/PRDO ............................................ 15, 16

WE02 ............................................................... 12

/SCWM/RFUI ................................................ 8, 13 /SCWM/TLR_WIZARD ...........................11, 17, 23 /SCWM/TO_CONF ............................................. 8 /SCWM/TU ....................................................... 15 /SCWM/WAVE............................................ 15, 18 /SCWM/WMBBIN.............................................. 12 /SCWM/WMCATO ............................................ 12 /SCWM/WMPIHU ............................................. 12 /SCWM/WMRREF ............................................ 12 /SCWM/WMSUMO ........................................... 12 /SCWM/WMTOCO ........................................ 8, 12 /SCWM/WMTORD ........................................ 8, 12 BD87 ................................................................ 12 IBDLV_CONFIRM_DEC_CI ................................ 9 SLG1 .......................................................... 18, 19 SLG2 ................................................................ 20 SM37................................................................ 21 SMQ1 ............................................................... 10 SMQ2 ............................................................... 10 SPPFCADM...................................................... 20 SPPFP ............................................................. 20 ST13................................................................. 13 © 2013 SAP AG

page 27/28

© 2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any f orm 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, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, Syst em i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POW ER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RET AIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United St ates and other countries.  Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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 W 3C ® , World Wide Web Consortium, Massachusetts Institute of Technology.  Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or  registered trademarks of Apple Inc. IOS is a registered trademark of Cisc o Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry A pp World are trademarks or registered trademarks of Research in Motion Limit ed. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Busi nessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective log os are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, Busin essObjects, Crystal Reports, Crystal Decisions, W eb 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. Business Obj ects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and s ervices mentioned herein as well as their respective logos are trademarks or r egistered trademarks of Sybase Inc. Sybase is an SAP c ompany. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Servic es are registered trademarks of Crossgate AG in Germany and other  countries. Crossgate 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 var y. 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 n ot be liable for errors or  omissions with respect to the materials. The only warranties f or 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.

© 2013 SAP AG