SAP Tips – IDocs – Parallel Processing versus Packet Size

What is best to use for system performance?

It is not a cut and dry answer – both methods are valid and have their strengths and weaknesses. The following will help:

Packet size - The number of IDocs in a queue which are processed before a commit is done. Can be used in serial or parallel processing.

EG: packet size = 3; IDocs are processed in a line [-[IDoc 1][IDoc 2][IDoc 3]-Commit]

Pro’s - Packets greater than 1, process IDocs faster.

Con’s - Packets greater than 1 could get errors if complicated logic is used in the process.

Parallel Processing - The number of sessions used simultaneously to process Idocs.

EG: Parallel processing is used with 3 parallel processes (and an example of pack size 2) ; IDocs are processed 2 in a line  per process:

[-[IDoc 1][IDoc 2]-Commit]

[-[IDoc 1][IDoc 2]-Commit]

[-[IDoc 1][IDoc 2]-Commit]

Pro’s - Parallel processing will process IDocs faster than serial processing.

Con’s - It is difficult to determine if there are errors, as some processes will be successful and some will not.

There is a great tip when using parrallel processing as follows:

In parallel processing, processes containing the IDocs to be processed are started in parallel. If there is a termination (dump/ A message), no message is issued by RBDAPP01. The best way to identify such problems is to run RBDAPP01 without parellel mode after a scheduled RBDAPP01 with parallel mode. Then a termination is logged (dialog message or message in job log).


  1. Griechenland Angebote July 24, 2012 at 2:49 am · Reply

    Erzähl doch bitte nochmal ein wenig ausführlicher.
    Ich würde gerne viel mehr darüber wissen.

  2. click July 27, 2012 at 12:39 pm · Reply

    Just want to say this is great, thank you.

Leave a Reply