Regarding idoc performance

[xinjiang_li]

Hi gurus,

We use idoc technology in our project, and most of them are inbound idocs.

Some of these interfaces need to be processed realtime, while some of them are set sporadically in WE20.

For realtime interface, we are worried about the performance, as you know each time one idoc only processes one piece of data, and most of standard idocs use 'call transaction' method. Do we have any solution or infrastructure to get a better performance?

In your system, how many idocs will be generated one day? How many of them are realtime and how many are processed by job?

In our system, we estimate there will be average 4000 idocs per day and 10000 idocs at peak. Is it ok for R3 4.7 system?

Any help will be appreciated.

[xinjiang_li]

Hi gurus,

We use idoc technology in our project, and most of them are inbound idocs.

Some of these interfaces need to be processed realtime, while some of them are set sporadically in WE20.

For realtime interface, we are worried about the performance, as you know each time one idoc only processes one piece of data, and most of standard idocs use 'call transaction' method. Do we have any solution or infrastructure to get a better performance?

In your system, how many idocs will be generated one day? How many of them are realtime and how many are processed by job?

In our system, we estimate there will be average 4000 idocs per day and 10000 idocs at peak. Is it ok for R3 4.7 system?

Any help will be appreciated.

[Former Member]

Hi,

Create an Idoc outbound program and it collects all materials for the particular day .In that program u collect all materials and dumped into one container.with the help of background job scheduling u run that program. .So,u get a better performance.I think it will be helpful to u.