Upload customizing (SBIW)
In every SAP source system, part of the ROIDOCPRMS table controls the data transfer from the source system to
the SCM system. The table contains the following information:
MAXSIZE - Maximum size of a data package in KB
STATFRQU - Number of packets that are transferred before statistical information is sent
MAXLINES - Maximum number of records sent in one data package
MAXPROCS - Maximum number of dialog work processes for each upload request used to send the data to the
To ensure the performance and stability of the upload process, it is important that this table is set up correctly. We
have checked the setup of this table for all source systems connected to the SCM system.
To avoid potential extraction problems, change the entries in table ROIDOCPRMS in the different source
systems as explained in the table below.
If the setting for MAXSIZE is too large, data packets will also be very large. A system timeout may occur for
work process(es) on the SCM server assigned to these packets, or there may be problems with the
memory. If the setting for MAXLINES is too large, the high number of records for each data packet might
lead to dumps in the source system or memory problems on the SCM server. If the values are too small,
several small data packets are created, which increases the upload time. Note that you do not have to
reduce the values if you have enough resources available (memory, work processes) and your parameter
settings have been tested carefully.
To implement these settings you have two choices:
a) Modify all source systems centrally using the Administration Workbench of SCM
Call transaction RSA1, select a source system by using the secondary mouse button and choosing
"Customizing for Extraction". The system navigates directly to the selected source system in transaction
SBIW. Choose General Settings -> Maintain Control Parameters for the Data Transfer.
b) Maintain the settings in the different source systems.
Call transaction SBIW and choose General Settings ->Maintain Control Parameters for the Data Transfer.
Earlywatch Session Report, Palm, Inc., 17.11.2008 28
Note: If table ROIDOCPRMS is empty, the systems use default values during runtime. The defaults are
10,000 for MAXSIZE and 100,000 for MAXLINES. The default for MAXSIZE is small whereas the default
for MAXLINES is reasonable for most systems. In some cases, it may be necessary to set the values for
some of the parameters outside our recommended range.
One example of this is the MAXPROCS parameter (maximum number of dialog work processes for each
upload request). This parameter limits the use of resources during an upload in order to prevent a resource
bottleneck occurring in the system. If you reduce the setting for this parameter, the upload performance
may suffer even though there are enough system resources available.
If you use your SCM as a DataMart, you have to maintain this table in the SCM system as well.
Note: In releases up to and including Service API 3.0C, data packages are transferred independently of
any enhancements to outbound scheduling (QOUT scheduler) that have since been made available.
Settings in the corresponding control transaction SMQS were not relevant. However, in some cases, it was
necessary to explicitly deregister the SCM destination (see SAP Note 673940). With Plug-In-Basis 2005.1
(Service API in Release SAP NetWeaver 2004s), you can (optionally) switch control of the transfer to the
standardized outbound scheduling of the queued RFC.
- Your (connected) SCM system has Release >= SAP NetWeaver 2004s
This means the default setting is changed; however, you can revert to the original setting using the
If you are using standardized outbound scheduling, the number of processes used to transfer data
packages to the BI system has to be maintained for the BI destination in transaction SMQS. In this case,
the global data transfer settings only affect the number of processes that are used to transfer the data
packages from the extraction process to the tRFC for the transfer.
When you transfer data within a SCM system using the standardized outbound scheduling, too many
dialog processes may be occupied. This occurs, for example, in a DataMart scenario when data is
transferred from a DataStore Object to an InfoCube. For further information, see SAP Notes 916706 and 905841.
Important SAP Notes for Source System Upload Settings
To optimize upload performance and to prevent any loading problems for the source systems, check and
implement the following SAP Notes as soon as possible.
SAP Note Number Description
327828 Performance of BW supply systems
385741 Collective runs are not deleted
351936 Problems with different collective runs
source: sap recommendation report.