SAP Note

1423066 - Optimization of the performance in EWM

Component: SCM-EWM-RF (Radio Frequency Processing), Version: 25, Released On: 25.11.2020

Symptom
You are using Extended Warehouse Management (EWM) and you notice that system performance is inadequate for your requirements with
regard to the following aspects of performance:

Dialog response times are too long

in particular for "small" transactions, such as radio frequency (RF) transactions

In particular for "large" transactions, such as the release of a large wave pick with several thousand items.

High consumption of system resources (CPU and database size)

Reason and Prerequisites

Possible causes of the inadequate performance are

You use CPUs with inadequate single computing unit (SCU) performance (see SAP Note 1501701). According to recommendations of the
SAP Quick Sizer, you should use CPUs with SCU performance class AAA for certain process steps in EWM. At least the application
server used by the relevant system users should have this performance class.

Inadequate maintenance of the database and/or the NetWeaver components

Inadequate execution of the "periodic tasks" to be carried out regularly in the "Solution Operation Guide for SAP EWM 2007 (SAP
EWM 2007)" or in the "Application Operations Guide for SAP EWM 7.0"

Available EWM notes of category "P" (performance) are not implemented in your system

Inadequate use of optimization options provided by the EWM application relating to optimized dialog response times and the
optimization of datasets created by transactions (for example, application log and change documents).
Insufficient speed of one or more components in the infrastructure. In addition to the actual EWM system, components such as the
ITS, network, devices, or the browser used can also result in performance problems. If you discover that the response times on
the mobile device are too long but that only a small part is attributable to the processing in the EWM system, you should first
check the affected component for optimization potential.

Solution
This consulting note focuses on the documentation of all optimization options available in the EWM application. In addition, you
should also ensure that you

Carry out all the "periodic tasks" named in the "Operations Guide"; these tasks are not explained again in this note. You can
find the "Operations Guide" under ttps://service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP EWM ->
Using SAP EWM 7.0

Have implemented all notes of the category "P" that are relevant for your processes. In particular, bear in mind that not only
EWM application component notes are relevant; notes for other application components may also be relevant. The following list
provides an overview:

SCM-EWM*

SCM-BAS-DF

AP-LIM* (for example, Note 1039436 and in particular the activation of the database index D of the table /lime/coll_w2im
is required for EWM)

SCM-BAS-ODM

SCM-BAS-PAK*

SCM-BAS-INT-MD

SCM-BAS-MD-BM, SCM-BAS-MD-CAL, SCM-BAS-MD-LO, SCM-BAS-MD-PR, SCM-BAS-MD-RT, SCM-BAS-MD-SCU, SCM-BAS-MD-ZON

SCM-BAS-MDL

SCM-BAS-RG

SCM-BAS-EHS*
If you use EWM on SAP HANA database, refer to the notes on optimization and analysis of the performance of SAP HANA DB, such as
the SAP Note 1999930 for the analysis of potential bottlenecks in I/O operations. Bottlenecks in I/O operations may lead to
sporadic poor dialog response times. In RF or pick by voice processes especially, the system performance perceived by system
users deteriorates sporadically as a result. The performance of I/O operations in connection with SAP HANA DB save points and
delta merges is particularly important, see SAP Note 1999930.

The following list provides an overview of the optimization options that are available in the EWM application. Detailed documentation
about the various points is available in the KW documentation, the IMG documentation, or in the long text of the relevant note:

Optimization of response times in RF transactions:

Update of the start dates of the loading or unloading process in the outbound delivery order or the inbound delivery: This
update potentially includes a lot of deliveries or delivery items and, as a result, the response time may be greater than
1 second. The number of deliveries involved depends on the navigation in the RF because all deliveries belonging to the
initial element (such as door or transportation unit, for example) are updated respectively. If this execution date is not
required in the persistent data of the deliveries, this update should be deactivated via Customizing using the IMG
 activity that you can find in transaction SPRO under "Extended Warehouse Management -> Cross-Process Settings -> Shipping
and Receiving -> General Settings -> General Settings for Shipping and Receiving".
Update of deliveries in RF transactions that update multiple delivery items: Warehouse tasks that reference multiple
delivery items can be confirmed in some RF transactions and these delivery items must be updated during this confirmation.
These are normally handling unit (HU) warehouse tasks where multiple HU items reference multiple delivery items. Examples
include unloading, loading, and putting away a HU. Due to the potentially large number of involved delivery items, the
dialog response time may be greater than 1 second. To ensure a guaranteed short dialog response time, a threshold value
for the number of delivery items can be defined starting from when the delivery is updated asynchronously. In this case,
the delivery update does not contribute to the dialog response time. For EWM 5.1, the configuration of the threshold value
is provided by Note 1277950 (and other subsequent notes, see the Related Notes section); as of EWM 7.0 Support Package 03,
the configuration is contained in the SAP application menu under "Extended Warehouse Management -> Settings -> Activate
Asynchronous Delivery Update" (or transaction code /SCWM/DLV_ASYN). Bear in mind the restrictions mentioned in Note
1277950 (and subsequent notes) regarding the processes in which the system actually uses the asynchronous delivery update
in accordance with the settings. Generally, this asynchronous delivery update should only be used in necessary cases
because the price of short response times is increased system load and this has a negative effect on the required system
sizing.
Update of the delivery during RF unloading with an implicit goods receipt: A restriction to the previously mentioned
asynchronous delivery update refers to the confirmation of an unloading warehouse task where the system also carries out
the goods receipt posting automatically because it is the warehouse task that was confirmed first. Using another
configuration also makes it possible to activate the asynchronous delivery update in this case. For EWM 5.1, the
configuration is provided with Note 1151892; as of EWM 7.0, the configuration is included in the IMG under "Extended
Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel Processing and Performance". Here,
the parameter "Act. ESL" can be set per warehouse number.
Check for different routes and date/time of departure: You have the option to run this check during warehouse order
creation and confirmation and, therefore, you may also run it in RF confirmations, such as loading. You can deactivate
these checks in transaction SPRO under the IMG activity "Extended Warehouse Management -> Cross-Process Settings ->
Shipping and Receiving -> General Settings -> General Settings for Shipping and Receiving". This can improve the dialog
response time of RF confirmations.
Transfer of the route from the outbound delivery order to the transportation units activity: If a delivery item that was
not assigned previously is loaded to the transportation unit, the route is transferred from the delivery to the
transportation unit. This transfer may increase the RF load confirmation response time. You can deactivate this transfer
in transaction SPRO under the IMG activity "Extended Warehouse Management -> Cross-Process Settings -> Shipping and
Receiving -> General Settings -> General Settings for Shipping and Receiving". This can improve the dialog response time
of RF confirmations.
If you use HTTP-based or HTTPS-based RF user interfaces (UIs) (via Internet Transaction Server (ITS) or WebConsole), then
take into account the recommendations from Note 1422086 about the adjustments necessary for the Internet Communication
Manager (ICMAN) parameter. Otherwise, response times may increase by up to 750 milliseconds when the ICMAN default
parameter values are used.
If you use products that are subject to batch management requirement, the system always creates a batch subitem in the
delivery document by default, even if only a single batch is involved. Creating a batch subitem leads to increased
response times in the picking confirmation during the synchronous delivery update; during the asynchronous delivery
update, it leads to a negative effect on the system sizing and on the performance of the following "In Process" desktop
transaction (for example, goods issue posting) which must then technically process the duplicate number of delivery items.
The creation of the batch item can be suppressed in many cases; for more detailed information, see Note 1367078. As of EWM
7.0 Support Package 05, the configuration is included in the IMG under "Extended Warehouse Management -> Cross-Process
Settings -> Define General Settings for Parallel Processing and Performance". Here you can set the parameter "No Split"
(Avoid Automatic Batch Split for (Picking) Confirmation) per warehouse number.
Optimizing or deactivating the display of messages that were sent from the monitor (transaction /SCWM/MON) to the
resource: By implementing SAP Note 1417111, the display is optimized in such a way that the display function no longer
runs between each individual (validation) field during the warehouse task confirmation and runs only when you switch to
another screen. This has a positive effect on the response time of the validation of some fields and also has a very
positive influence on the number of database commits, which are greatly reduced. With Note 1420970, a configuration is
offered as of EWM 7.0 with which the message display in the RF dialog can be deactivated as standard per warehouse number.
This optimizes the response times for switching screens in RF transactions. As of EWM 7.0 Support Package 06, this
configuration is contained in the SAP application menu under "Extended Warehouse Management -> Master Data -> Resource
Management -> Deactivate Messages to Resources" (or transaction code /SCWM/RSCMSG_DEACT).
Update of the delivery during the RF-based confirmation of a transportation unit movement to the door in the case of very
large transportation units in relation to the number of assigned delivery items (more than 1,000 items): SAP Note 1314848
enabled the parallel delivery update. As of EWM 7.0 Support Package 03, the configuration is included in the IMG under
"Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel Processing and
Performance". Here, you can set the parameter "Parallel CI / YMove" per warehouse number. In addition, in the IMG under
"Extended Warehouse Management -> Cross-Process settings -> Delivery Processing -> General Settings -> Parallel Processing
in the Delivery", parallel processing of the delivery must be activated for the "TU Check In and Yard Movement: Delivery
Update" application.
Working with storage bins containing a very large volume of unpacked stock: Refer to the information in SAP Note 2091466.
You should avoid using bins with a very large volume of unpacked stock. This applies particularly to the number of quants
in goods receipt zones and goods issue zones.
Deactivate the print function for an RF queue: The system uses the Post Processing Framework (PPF) and condition technique
to determine whether warehouse order and handling units are to be printed. Since this determination may be time-consuming,
you can switch off printing for the following processes: Warehouse task creation for the queue and warehouse task
confirmation for the queue. You can switch off printing at the queue level in the Customizing for Extended Warehouse
Management under "Cross-Process Settings -> Resource Management -> Define Queues".
Pick-warehouse task (WT) confirmation using radio frequency (RF): You can deactivate the calculation of the packed
quantities for delivery updates during the pick-warehouse task confirmation via RF. As a result, the RF performance is
improved because handling unit (HU) data is no longer read so often. You can influence this configuration for each
warehouse number in the IMG under "Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for
Parallel Processing and Performance", as described in SAP Note 1532415.
See also SAP Note 1595305, which enables a measurement of the RF dialog runtimes specifically for different radio
frequency (RF) functions.
Optimization of the response times of "large" desktop transactions and optimization of background processing:
Wave pick creation: In scenarios with high throughput numbers (in relation to the number of delivery items), it is
recommended that you use automatic wave assignment for outbound delivery orders instead of manual wave creation. The Post
Processing Framework (PPF) action definition /SCWM/PRD_OUT_WAVE_NEW of the action profile /SCDL/PRD_OUT of the application
/SCDL/DELIVERY enables this. (See transaction SPPFCADM). The waves that are created automatically can demonstrate high
performance with the monitor (transaction /SCWM/MON). This is especially suitable as the entry point for further
processing steps for the wave (manual postprocessing in relation to delivery assignments as well as wave release and
monitoring degrees of processing). If manual wave assignments are carried out for a large number of delivery items per
wave (using transaction /SCWM/WAVE or by jumping from transaction /SCWM/MON), the response time may be very long (a number
of minutes) when the changed wave is saved. It is recommended that you activate the parallel delivery update in this case.
This is possible in the IMG under "Extended Warehouse Management -> Cross-Process Settings -> Delivery Processing ->
 General Settings -> Parallel Processing in the Delivery". Activate parallel processing for the "Delivery Assignment to
Wave" application. This enables the manual assignment or cancellation of the assignment for thousands of delivery items
during a system runtime of just a few minutes.
Wave pick release: High-volume wave picks should be released using transaction /SCWM/MON because this monitor transaction
offers the best response times for very large waves (for example, several thousand items). Furthermore, we recommend that
you activate parallel processing using the IMG activity "Extended Warehouse Management -> Goods Issue Process -> Wave
Management -> General Settings -> Edit Parallel Processing for Waves".
Warehouse order creation: Parallel processing can be used for the assignment of warehouse tasks to warehouse orders and,
with it, warehouse order creation. This is always useful in the case of many warehouse tasks that are assigned to
different activity areas or queues (warehouse tasks for the same queue or for the same activity area are always dealt with
in the same parallel process). Warehouse order creation is also part of the wave release (for example) so that it
represents another parallel process that can potentially minimize the runtime in the wave release. You can set parallel
processing of warehouse order creation in the SAP menu under "Extended Warehouse Management -> Settings -> Warehouse Order
-> Set Up Control Parameters for Warehouse Order Creation" (or transaction code /SCWM/WOLOG ) by setting the "Parallel"
parameter for the warehouse number.
Desktop-based confirmation of large warehouse orders: The configuration options for the asynchronous delivery update above
a certain threshold value based on the number of delivery items (as mentioned above for RF transactions) are also taken
into account by the system during desktop-based warehouse order confirmations. Consequently, this optimizes the response
time when saving the confirmation of large warehouse orders. This affects picking and putaway as well as loading and
unloading from transactions /SCWM/LOAD and /SCWM/UNLOAD.
Synchronization of outbound delivery order with transportation unit: SAP Note 1413479 enables the synchronization of the
data of the outbound delivery order with the data of the transportation unit at the time when loading warehouse task are
confirmed. This early data synchronization (as a background process) leads to a shorter system runtime for a subsequent
goods issue posting for the transportation unit.
Synchronization of the outbound delivery order with the transportation unit in particular on receipt of a transportation
unit via IDoc SHPMNT: SAP Note 1786712 enables the data update of the outbound delivery order to be separated from the
generation of the transportation unit in EWM. It also enables parallel processing of the data update of the outbound
delivery order. Both aspects lead to a shorter time during which the outbound delivery order is locked. Parallel
processing leads to faster mass processing if a lot of outbound delivery orders are assigned to the transportation unit in
terms of planning. As a result, subsequent processes such as picking can take place earlier.
Creation of outbound deliveries and goods issue posting for a transportation unit using transaction /SCWM/TU: When using
very large transportation unit activities related to the number of outbound delivery items contained in them, we recommend
activating parallel processing for the creation of outbound deliveries and the goods issue posting if more than one
outbound delivery order is assigned to the transportation units activity. You should always consider this technical
optimization when the system response times are significantly higher than the durations required from a business point of
view. The typical threshold value from which this parallelization is most often useful is 1,000 delivery items. In EWM
5.1, this parallelization is made possible by Note 1164464 (and its related notes). As of EWM 7.0, the configuration is
included in the IMG (also in higher Support Packages for EWM 5.1). You must carry out the following IMG activities: 1.
Activity: "Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel Processing and
Performance". Here, the parameter "ParGI" can be set per warehouse number. 2. Activity: "Extended Warehouse Management ->
Cross-Process Settings -> Delivery Processing -> General Settings -> Parallel Processing in the Delivery". Here, parallel
processing is activated for the "Outbound Delivery Creation" and "Confirmations for Goods Issue" applications.
In transaction /SCWM/CICO, it is possible to use a dialog step for a transportation unit activity to carry out the
"Arrival at Checkpoint" as well as the planned assignment to a door (with the creation of a warehouse task for the yard
movement of the transportation unit from the checkpoint to the door). For very large transportation units (more than 1,000
assigned delivery items), we recommend using the parallel delivery update to optimize the system response time. Note
1277438 makes this optimization possible. As of EWM 7.0 Support Package 03, the configuration is included in the IMG under
"Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel Processing and
Performance". Here, you can set the "ParCI/YM" parameter per warehouse number. In addition, in the IMG under "Extended
Warehouse Management -> Cross-Process settings -> Delivery Processing -> General Settings -> Parallel Processing in the
Delivery", the parallel processing of the delivery must be activated for the "TU Check In and Yard Movement: Delivery
Update" application.
Update of the delivery during the desktop-based confirmation of a transportation unit movement to the door (transaction
/SCWM/YMOVE) in the case of very large transportation units related to the number of assigned delivery items (more than
1,000 items): SAP Note 1311161 enabled the parallel delivery update. As of EWM 7.0 Support Package 03, the configuration
is included in the IMG under "Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for
Parallel Processing and Performance". Here, you can set the parameter "Parallel CI / YMove" per warehouse number. In
addition, in the IMG under "Extended Warehouse Management -> Cross-Process settings -> Delivery Processing -> General
Settings -> Parallel Processing in the Delivery", parallel processing of the delivery must be activated for the "TU Check
In and Yard Movement: Delivery Update" application.
Creation of unloading warehouse tasks and/or creation of putaway warehouse tasks in transaction /SCWM/UNLOAD or
/SCWM/TODLV: In these transactions, the creation of unloading warehouse tasks and/or putaway warehouse tasks may be
requested for thousands of handling units and/or the inbound delivery items contained in them. Note 1135535 (EWM 5.1
Support Package 05) and Note 1229776 (EWM 5.1 Support Package 08) enable parallel processing. As of EWM 7.0, this is
included in the IMG under "Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel
Processing and Performance". Here, the parameter "Par.Ibd.WT" can be set per warehouse number. You can use parallel
processing for all process steps in which you create putaway warehouse tasks together with unloading HU tasks or create
only putaway warehouse tasks.
Quantity adjustment in the merchandise distribution flow-through (transaction /SCWM/MEDI_AQTY) as of EWM 7.0: With this
transaction, the mass quantity adjustment of outbound delivery orders is possible based on the quantities of the related
inbound deliveries (in the flow-through scenario). The proposed quantity for distribution is calculated and displayed by
the transaction and you can save the proposal as changed or unchanged. Parallel processing is provided to calculate the
proposed quantity and save the changed outbound delivery orders. This can be set in the IMG under "Extended Warehouse
Management -> Cross-Process Settings -> Delivery Processing -> General Settings -> Parallel Processing in the Delivery".
Activate parallel processing for the applications "Merchandise Distribution Adjustment: Quantity Calculation" and
"Merchandise Distribution Adjustment: Delivery Update".
Suppressing the update of wave pick items with the transportation unit number: The assigned transportation unit of a wave
pick item is often not important from a business point of view. Therefore, Note 1439613 can be used to suppress the often
unnecessary update of wave items. As of EWM 7.0 Support Package 06, this configuration is included in the IMG under
"Extended Warehouse Management -> Cross-Process Settings -> Define General Settings for Parallel Processing and
Performance". Here, the parameter "NoWvUpd" can be set per warehouse number.
Deletion of the "Expected Goods Receipt" documents: In EWM, optional "Expected Goods Receipt" documents can be created
based on the plan data of the SAP ERP purchase order. These documents can be deleted periodically and recreated based on
potentially changed purchase order data. To reduce the runtime, these documents can be deleted in parallel processing.
This can be set in the IMG under "Extended Warehouse Management -> Cross-Process Settings -> Delivery Processing ->
General Settings -> Parallel Processing in the Delivery". Activate parallel processing for the "Deleting Expected Goods
Receipts" application.
Generic optimizations that are possible within the EWM system for the optimization of response times and the consumption of
system resources:
 Deactivation of the application log: In normal production operation, you should deactivate all EWM application logs in
such a way that an application log is generated only in the case of errors. These configuration settings can be made in
the productive system using the following menu transactions: 1) Transaction /SCWM/DLVPPFLOG: Log of PPF actions of the PPF
application /SCDL/DELIVERY (delivery). These actions contain subsequent processing for the delivery (for example, wave
pick assignment). 2) Transaction /SCWM/WOHULOG: Log of the PPF print actions of the PPF application /SCWM/WME (Warehouse
Management Engine). 3) Transaction /SCWM/ACTLOG: Many different log subobjects, such as the warehouse task processing log
(for example). Here, the logs should be configured in such a way that the "No Info." setting is activated. Also, only
important messages (error messages) are to be taken into account when setting the value for the parameter 'Log Active' 4)
Transaction /SCWM/PSLOG: Packspec determination analysis should be activated only in test operation/test systems.
Deactivation of change documents (only necessary in exceptional cases as this only affects system utilization, and does
not affect dialog system response times): In scenarios with high throughput, you can deactivate the change document update
of the delivery by using delivery document type Customizing provided this is permitted from a business point of view. In
addition to the documents from the outbound delivery process and the inbound delivery process, this also affects documents
of the warehouse-internal processes of posting changes and stock transfers.
Deactivation of PPF action definitions that are not used: All PPF action definitions that are not used should be
deactivated using transaction SPPFCADM because otherwise the schedule conditions are evaluated for all active action
definitions and this is unnecessary.
An important example for the deactivation of PPF action definitions is the deactivation of the action definition
/SCWM/SR_SET_TU_SYNC_DLV of the action profile /SCWM/TU of the PPF application /SCWM/SHP_RCV. This contains a schedule
condition that has hard-coded logic in the standard SAP system. The scheduling of this action is generally avoided by the
deactivation in transaction SPPFCADM. This is possible with Note 1397685. Without the deactivation, the action is always
scheduled in the standard SAP system when the assignments of deliveries or handling units for the transportation unit are
changed. For example, this is the case when loading data to a transportation unit without the existence of a plan
assignment beforehand. This can lead to a high number of executions of this PPF action and this also negatively affects
the scaling of the system due to the reserved hardware resources and lock times on the transportation unit objects and
delivery objects. An alternative to the scheduling and executing of this PPF action is the manual "check" of a
transportation unit using transaction /SCWM/TU because this check also implicitly synchronizes the transportation unit.
This synchronization also runs implicitly at the start of important functions such as the goods issue posting of the
transportation unit (for example).
Process definition with minimized EWM system load: The number of documents (for example, the number of warehouse tasks for
the outbound delivery process of a delivery item) should be critically scrutinized in the Business Blueprint phase in
relation to the subsequent system sizing requirements. Complex warehouse processes that consist of many steps require much
more hardware system resources. An analysis using the SAP EWM Quick Sizer is recommended. The SAP EWM Quick Sizer is
contained in the general SAP Quick Sizer (https://service.sap.com/quicksizer) in the SCM area. Take into account the
online help for the EWM Inbound and the EWM Outbound process. It contains Quick Sizer data for EWM sample delivery
processes, among other things.
Process definition with minimized system communication load: EWM allows process definitions that can potentially generate
a very high SAP EWM - SAP ERP system communication load. An example for this are the partial goods receipt postings (on
the partial quantities of an inbound delivery item) that can be sent to the SAP ERP system as partial goods receipt
postings. An advantage of these partial confirmations is the immediate availability of these partial quantities in the
stock of the ERP system. However, a disadvantage is the increased system communication related to the necessary system
sizing, especially on the SAP ERP system. In the IMG, EWM provides the option of using Customizing to influence the
message structure that EWM sends to SAP ERP. This can be set in the IMG under "Extended Warehouse Management -> Interfaces
-> ERP Integration -> General Settings -> Set Control Parameters for ERP Version Control".
Outbound delivery orders should not be used as a rough scheduling agreement because this may result in the accrual of a
large number of late delivery split that increase the response time when you confirm a pick-warehouse task.
You can find best practices for the implementation of high throughput processes for storage sections in SAP Note 1896480.
Generic optimizations (within technology components)
If you use DB2 as a database, then take into account Note 1430621 and implement the optimizations included in it.
Otherwise, the performance problems described in the note may occur in EWM systems with high data throughput due to
waiting updates for the table VBDATA (update task interface data).
Take into account the recommendations mentioned in Note 1422086 for the required adjustments to the Internet Communication
Manager (ICMAN) parameter.
General aspects related to asynchronous and parallel processing: In many different application areas, EWM provides the
option of asynchronous updates (technically possible using qRFC) and parallel processing (technically possible via ABAP
"call function in new task"). A logon/server group, which is entered respectively in Customizing, is technically used for
these asynchronous updates and parallel processing. This can be different to the logon group of the dialog user. By using
these separate server groups, the allocation of system resources between normal dialog user transactions, asynchronous
background processing using qRFC, and specific parallel processing can be optimized (refer to Notes 726148 and 74141 for
the configuration of resource management for transactional RFC (tRFC) and asynchronous RFC (aRFC)). In particular, it is
possible in heterogeneous hardware system architectures to allocate the hardware with the best "single user response time"
to the runtime-critical processes. Take this into account in relation to the logon group of the RF users and in relation
to the server groups for runtime-critical parallel processing.
Material flow system (MFS) integration: This integration contains a special example of background processing in relation
to the possible configuration of the allocation of system resources using server groups. The server groups used for MFS
can be defined using transaction /SCWM/MFS_APPSRV in the productive system.
qRFC processing: This is a specific example of background processing with reference to the possible configuration for the
allocation of system resources using server groups. qRFC is used in the EWM system both for system interfaces (for
example, the distribution of deliveries from the ERP system to the EWM system) and for internal process flows (for
example, process-oriented storage control). The qRFC inbound processing, which causes the workload when you use inbound
queuing, can be assigned to a separate logon group or server group for each queue name. You do this by using the QIN
Scheduler (for example, you can access this by calling transaction SMQ2 and chooseing Goto->QIN Scheduler in the menu). It
is then possible to assign, for example, a specific server group to the processing of delivery receipts from the ERP
system in the EWM system.
Database table ARFCRSTATE: In some EWM systems, the most costly database operation is a selection of DB table ARFCRSTATE
caused by the automatic deletion of NetWeaver at the end of processing of an individual qRFC or tRFC. You can deactivate
this individual processing by setting the parameter abap/arfcrstate_col_delete to the value "X", as described in SAP Note
539917. As a result, deletion is carried out through mass processing in a batch job. You must use program RSTRFCEU to
schedule this job for regular execution (see SAP Note 539917). This measure reduces database utilization in these systems,
which improves EWM system performance.
PPF action processing: This is a specific example of background processing in relation to the possible configuration of
the allocation of system resources using server groups. In the EWM system the standard EWM PPF actions whose processing
time is set to "when saving the document" are processed directly asynchronously without queuing using qRFC. If this
background processing is to be directed to special server groups, you can do this by implementing Note 1599301. If you
implement the BadI implementation described in the note, a qRFC is interconnected that then allows you to assign a server
group to the qRFC processing (if you are working with a constant prefix in the queue name). This may be particularly
relevant for the EWM system performance if large numbers of PPF actions are created at the same time due to mass
transactions. If you do not ues qRFC, these PPF actions are all processed at the same time and they create a peak system
load. An EWM example for this is the simultaneous goods issue of many delivery documents, for example the goods issue of a
transportation unit with many delivery documents.
 Size definition of the size of the enqueue lock table: If the EWM system is operated with a large number of simultaneous
users or transactions are executed that handle a large number of objects, it is often necessary to increase the profile
parameter that defines the maximum size of the lock table or the maximum number of lock entries. Transactions with a lot
of delivery items are particularly relevant here because the lock often occurs on the level of the individual delivery
items (and not on the delivery document header level). An example of this is the wave pick release of a wave with tens of
thousands of items.
Database tables /LIME/NTREE and /LIME/NQUAN: If the above database tables are listed in traces (for example, transaction
ST05) with unusually high response times for "FOR ALL ENTRIES" accesses, you can achieve improvements by deactivating the
profile parameter "rsdb/prefer_join_with_fda". Examine the advantages and disadvantages of such a conversion for all
processes in your system together with your SAP Basis consultant. When you do this, the documentation of the parameter and
SAP Notes 1987132 and 2037385 may be helpful.

Note that some of the above-described optimizations are technically based on an asynchronous execution of EWM internal remote
function calls (RFCs). The EWM system checks specific application functions whether they have queued RFCs (qRFCs) called WMDPDO* or
WMDPDI* that are not executed. This may require extended authorizations for the user roles (transaction PFCG) of the EWM users to
enable them to execute a specific RFC function module. You need to perform this necessary extension of the user roles used in the EWM
production system before you optimize the production system. This authorization extension is not only necessary for the user roles
that generate the asynchronous qRFCs but also for other user roles like those for creating warehouse tasks, for example.
Missing authorizations trigger a program runtime error. Transaction ST22 displays it as error 'RFC_NO_AUTHORITY' in program
'/SCWM/SAPLDLV_ASYNC'.

Examples for role maintenance:

When you maintain the authorization object S_RFC with the parameters
'RFC_TYPE'='FUNC'
'RFC_NAME'='/SCWM/DLV_CONFIRM_QPL'
'ACTVT'='16' (Execution)
you grant the authorization to execute RFCs for a function module that is necessary to check whether not executed qRFCs exist.

Manual Activities

Attributes
Key Value

Other Components SCM-EWM-MFS (Material Flow System)

Other Components SCM-EWM-WC (Work Center)

Other Components SCM-EWM-WOP (Warehouse Order Processing)

Other Components SCM-EWM-GM (Goods Movements)

Other Components SCM-EWM-DLP (Delivery Processing)

Other Components SCM-EWM-WAV (Wave Management)

This document refers to

SAP Note/KBA Title

1999930 FAQ: SAP HANA I/O Analysis

74141 Resource Management for tRFC and aRFC

726148 RFC cascade, all work processes occupied with RFC

552289 FAQ: R/3 lock management

539917 SQL error 601 when accessing "ARFCRSTATE" table

1896480 High Throughput Processes - Best Practices

1852138 Performance of HU Read Functions

1850783 Performance of HU WT creation via /SCWM/TO_CREATE_WHR

1847550 High memory consumption when creating whse task for delivery

1837143 Performance when creating HU WTs for inbound delivery

1828399 Performance when creating and confirming putaway WTs

1802159 Performance of wave selection

1786712 parallelization for TU-PDO synch from SHPMNT Idoc

1785694 Inefficient reading of fixed storage bin tables

1756494 Bad performance for warehouse task creation for PDI

1734099 Long runtimes for wave item update in SMQ2 queue

1683490 Unnecessary selection of locked waves

1675539 Inactive warehouse tasks are not posted in parallel

1646731
1599301 Locking problem in the PPF Action execution

1595305 Measuring runtimes for RF devices in SAP EWM

1570648 Performance when synchronizing transportation units

1532415 PERF: Response time during picking HU via RF is slow

1523579 slow performance at GI after note 1462174

1522240 Frequent call of /LIME/QUERY_CONTENT

1521475 Long runtime for update when warehouse tasks are confirmed

1519925 Performance when reading transportation units

1515680 Long runtime when confirming WT if WR is assigned to TU

1511021 Performance during planned loading to TU

1510229 Database locks on /SCWM/LAGP

1501701 Single Computing Unit Performance and Sizing

1483038 Performance of transaction "Determine and Set Prices"

1478841 Selecting large number of differences leads to termination

1439613 Locks due to wave update

1430621

1422086 RF response times when you use HTTP communication

1420970 No possibility to switch off resource message processing

1417111 RF: Optimize processing of messages sent to resource in RF

1413479 Synchronization of outbound del. order w/transportation unit

1397685 TU & delivery synchronization via PPF action suppressed

1367078 Performance: Batch split during conf. of warehouse tasks

1314848 RF: Performance Yard Movement

1311161 /SCWM/YMOVE: Performance - Arrival of TU at door

1277950 Activating the asynchronous delivery update

1277438 /SCWM/CICO: Performance - "Arrival at Checkpoint"

1229776 Performance when creating putaway warehouse tasks

1164464 Performance of goods issue posting for a TU

1151892 Asynchronous goods receipt posting with external lock

1135535 Performance Unload WT Creation

1039436 Poor performance, dispatcher AP 7.0 LIME in mass test

This document is referenced by

SAP Note/KBA Title

2689405 FAQ: SAP S/4HANA Performance Best Practices - Collective Note

2950948 EWM table group for placement on HANA DB scale-out node

2836451 /SCWM/TO_CONF WO BUffer performance improvement

2769436 Door bin determination with TU causes long runtime in labour mangement

2732149 Performance during synchronization of a TU

2718426 Performance issues during cancelation of wave pick tasks

2674764 long response time when selecting waveitems in the warehousemonitor

2603350 Performance during during navigation to TU subnode

2586915 Performance adjustment when reading it_tree

2601850 Long response time during wave selections with advanced selections

2505952 Performance problem during warehouse order creation

2461263 Recommendations for connecting external subsystems to SAP EWM as a blackbox

2312658 SAP EWM CoInnoMod - Consulting - Identify not used PPF Actions in EWM

2091466 long runtimes during GR, GI or WT confirmation when there are many quants on one bin

1962146 Performance during WT creation with addition to stock

1914127 Performance optimization in EWM MFS

1896480 High Throughput Processes - Best Practices

1599301 Locking problem in the PPF Action execution

1683490 Unnecessary selection of locked waves

1852138 Performance of HU Read Functions

1850783 Performance of HU WT creation via /SCWM/TO_CREATE_WHR

1847550 High memory consumption when creating whse task for delivery

1734099 Long runtimes for wave item update in SMQ2 queue

1837143 Performance when creating HU WTs for inbound delivery

1828399 Performance when creating and confirming putaway WTs

726148 RFC cascade, all work processes occupied with RFC

1802159 Performance of wave selection

1785694 Inefficient reading of fixed storage bin tables

1756494 Bad performance for warehouse task creation for PDI

1422086 RF response times when you use HTTP communication

1478841 Selecting large number of differences leads to termination

1483038 Performance of transaction "Determine and Set Prices"

1570648 Performance when synchronizing transportation units

1501701 Single Computing Unit Performance and Sizing

1675539 Inactive warehouse tasks are not posted in parallel

1519925 Performance when reading transportation units

1511021 Performance during planned loading to TU

1522240 Frequent call of /LIME/QUERY_CONTENT

1521475 Long runtime for update when warehouse tasks are confirmed

1510229 Database locks on /SCWM/LAGP

1523579 slow performance at GI after note 1462174

1420970 No possibility to switch off resource message processing

1515680 Long runtime when confirming WT if WR is assigned to TU

74141 Resource Management for tRFC and aRFC

1439613 Locks due to wave update

1417111 RF: Optimize processing of messages sent to resource in RF

1367078 Performance: Batch split during conf. of warehouse tasks

1397685 TU & delivery synchronization via PPF action suppressed

1277950 Activating the asynchronous delivery update

1314848 RF: Performance Yard Movement

1311161 /SCWM/YMOVE: Performance - Arrival of TU at door

552289 FAQ: R/3 lock management

1135535 Performance Unload WT Creation

1277438 /SCWM/CICO: Performance - "Arrival at Checkpoint"

1164464 Performance of goods issue posting for a TU

1229776 Performance when creating putaway warehouse tasks

1151892 Asynchronous goods receipt posting with external lock

1039436 Poor performance, dispatcher AP 7.0 LIME in mass test