Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ALE Issue

Former Member
0 Kudos

Hello

We are transferring master data from one system to another via ALE. On the sending system partner profile, we have it as "immediately transfer" and a similar setting on the receiving system.

We use SAP standard transaction BD16 to send all the cost center master data to the receiving system. When we schedule this as a back ground job, all the processes in the receiving system is used up and the system becomes very slow.

How do you correct this?

Thanks.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

I give you some tips for performance of ALE process.

Outbound side:

1. Control the timing of the outbound process - Go for Collect IDocs option in sender side -

2. Control error hanling - In tRFC, RFC destination should be set to suppress the automatic start of background jobs.

3. Control Parallel Processign - On the selection screen for these programs, you can specify the server group and maximum number of objects for each process.

Inbopund Side:

1.Control teh timing - shedule the program RBDAPP01 when system load is low. usually at night time.

2 . Control the packet size - When scheduling the RBDAPP01 program, you can specify the packet size, which defines the number of IDocs bundled together for processing in the inbound function module. This approach improves the performance by using one LUW (Logical Unit of Work) for several documents. This option is available for a limited set of inbound function modules.

3. Control ParallelProcessing - Batched IDocs can be passed to the posting program in a single-threaded or multithreaded mode. In single-threaded mode, the system passes one IDoc packet and waits for the process to finish before the next IDoc packet is sent. In multithreaded mode, the IDoc packets are passed to the inbound process simultaneously. If there are several IDoc packets, the system keeps dispatching until it runs out of packets or the number of processes is exhausted.

Regards,

Thiyagu

Edited by: Thiyagu on Jul 22, 2009 12:28 PM

2 REPLIES 2

alex_m
Active Contributor
0 Kudos

Pls consider the below points,

Whats your receving system capacity?..

Whats the data volume approx SAP to other system?..

Former Member
0 Kudos

Hi,

I give you some tips for performance of ALE process.

Outbound side:

1. Control the timing of the outbound process - Go for Collect IDocs option in sender side -

2. Control error hanling - In tRFC, RFC destination should be set to suppress the automatic start of background jobs.

3. Control Parallel Processign - On the selection screen for these programs, you can specify the server group and maximum number of objects for each process.

Inbopund Side:

1.Control teh timing - shedule the program RBDAPP01 when system load is low. usually at night time.

2 . Control the packet size - When scheduling the RBDAPP01 program, you can specify the packet size, which defines the number of IDocs bundled together for processing in the inbound function module. This approach improves the performance by using one LUW (Logical Unit of Work) for several documents. This option is available for a limited set of inbound function modules.

3. Control ParallelProcessing - Batched IDocs can be passed to the posting program in a single-threaded or multithreaded mode. In single-threaded mode, the system passes one IDoc packet and waits for the process to finish before the next IDoc packet is sent. In multithreaded mode, the IDoc packets are passed to the inbound process simultaneously. If there are several IDoc packets, the system keeps dispatching until it runs out of packets or the number of processes is exhausted.

Regards,

Thiyagu

Edited by: Thiyagu on Jul 22, 2009 12:28 PM