Start of Content Area

Background documentation Activated Background Processing  Locate the document in its SAP Library structure

To optimize the ALE distribution of the Central User Administration, you can perform the outbound and inbound processing of IDocs in the background (see Background Processing: Concepts and Functions).

Optimizing IDoc Outbound Processing

During the tests, it may be useful to temporarily set Transfer IDOCs immediately. However, if you have a large number of parallel dialog processes for IDocs in the central and child systems for mass processing in transactions SU10, PFCG, and PFUD, use the following settings for outbound processing in transaction WE20:

      Transactional RFC (tRFC)

      Package size 60

Select the package size so that as many as possible, but not more than 4000, segments build a package (total size under 4 MB).

      Collect IDocs

Collect IDocs means that a regular background job to be scheduled for report RSEOUT00 packs the IDocs into tRFC calls with the maximum package sizes. The last package is usually not full, but is sent anyway.


The tRFC status messages are updated by a job for report RBDMOIND. Transaction SCUL also displays the open tRFC calls of the CUA (see also transaction SM58).

You can delete unsent, obsolete tRFC calls with report RSARFC01 (see SAP Note 371068).

Optimizing IDoc Inbound Processing

As every sent IDoc requires at least one work process in the receiving system, performing the inbound processing in the background is advantageous if:

      You send a very large number of IDocs at the same time and want to optimize the performance

      Want to perform the processing serially

      Want to restrict to a particular application server

To do this, proceed as follows:


       1.      In the receiving system, set inbound processing to Processing in background in the partner profiles with transaction WE20.

       2.      Schedule Report RBDAPP01 as a Background Job to process the IDocs (see also SAP Note 399271).

The report passes all inbound IDocs to the application for processing, if they meet the selection criteria, and have the following status:

       Status 64, IDoc is ready for transfer to the application

       Status 66, IDoc is waiting for preceding IDoc (Serialization)

Serial IDoc Inbound Processing in the Background

Schedule the report RBDAPP01 for IDoc inbound processing for normal CUA operation with dialog users as a periodic job with a high repetition frequency (such as every 5 minutes) and the following selection:

      Message types USERCLONE and CCLONE

      Process in parallel: No

The IDoc packages are transferred to the application in sequence. This means that the background job occupies only one work process on the application server.

Parallel IDoc Inbound Processing in the Background

If you want to process a very large amount of user data by mass processing (for example, for the user transfer with transaction SCUG or when comparing the role assignments of organizational management with transaction PFUD), it may be useful to schedule the job with the following selection:

      Message types USERCLONE and CCLONE

      Package size 3

      Process in parallel: Yes

A free dialog work process is occupied for the inbound processing of the application on the application servers of the specified server group for each IDoc package (asynchronous RFC); that is, the packages are processed in parallel. If you have selected a large number of IDoc packages, almost all dialog work processes of the application server are occupied by the IDoc processing (two processes remain free; see SAP Note 84716). The server group should therefore only contain servers that are not used by dialog users.


As the report RBDAPP01 does not display a message in the case of termination, we recommend that you schedule a job step for report RBDAPP01 without parallel mode after a job step for report RBDAPP01 with parallel mode. This means that the IDocs that were not processed by the first job step have a logged termination (dialog message or message in job log).



End of Content Area