BW Process chain locked up after execution with RFC

[Former Member]

Hi,

We have the following task at hand. We kick in BW process chain execution via RFC from our R/3 system using the function described below. What happens is that the process chain does get kicked in the remote BW system, but it quickly locks up. System monitor says that all dialog process have been utilized. So, basically it gets stuck in the beginning of the process chain. Is there anything I can do to prevent this from happening?

Here is the function call:

• This function triggers execution of process chain

• (on the remote BW system)

CALL FUNCTION 'RSPC_API_CHAIN_START' DESTINATION p_rdest

EXPORTING

i_chain = p_pchain

• I_T_VARIABLES =

i_synchronous = 'X'

• I_SIMULATE =

• I_NOPLAN =

IMPORTING

E_LOGID = gv_pchain_logid

EXCEPTIONS

failed = 1

OTHERS = 2

.

Thank you,

AG

[Former Member]

Hi AG,

Can you please check the value of profile parameter:

rdisp/rfc_min_wait_dia_wp in you remote BW system. Is it 1?

If that is the case please increase the value to a more suitable value. This will determine the number of waiting dialog work processes in your system.

It is dynamically switichable. Please try this out and check the results.

Please award points if issue got solved.

Regards.

Ruchit.