Application Development and Automation 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: 
Read only

Regarding Inbound IDOC processing.

Former Member
0 Likes
1,646

Hi,

We are receiving inbound IDOCs from WEBMETHODS system.

While defining the partner profile we have choosed the option Transfer Immediately.

This is working fine when receiving few IDOCs.

But when receiving IDOCs in large number (more that 1000) . The IDOCs are created with Ready to transfer status .

Why this is happening?

10 REPLIES 10
Read only

Pawan_Kesari
Active Contributor
0 Likes
1,163

Does IDoc it remains in status 64 or after some time it goes in status 53?

Read only

0 Likes
1,163

It remains in status 64. ( IDOCS were created on friday . still in the same status.)

Read only

0 Likes
1,163

Note 181729 might help

Read only

0 Likes
1,163

Hi,

you can schedule report RBDAPP01 to execute IDocs in status 64.

Also you may talk to you basis guys. The issue that not all IDocs are processed may be due to not enough work processes available. The system in this case would automatically schedule a job (see SE37) to execute / process the IDoc. If enough processes are available all IDocs should be processed within a short time.

Kai

Read only

soumya_jose3
Active Contributor
0 Likes
1,163

Hi Sruthi,

If you are in ECC 6.0 version, you have to unlock the idoc before the send process is triggered.

I also faced the same problem in ECC 6.0 earlier and it was solved by calling the function module

'DEQUEUE_ALL' before doing commit work for the FM 'MASTER_IDOC_DISTRIBUTE' . In ECC 6.0 the idocs must be unlocked before the send process is triggered.

You can also refer the SAP note 1097730 which desribes a similar issue.

Regards,

Soumya.

Read only

Former Member
0 Likes
1,163

after that run BD87 tcode, this is memory problem....

Read only

Former Member
0 Likes
1,163

We have found that there is a TIMEOUT error while the IDOCs are getting posted.

So we are thinking to increase the rdisp\max_wprun_time .

Read only

Former Member
0 Likes
1,163

Hi,

The problem happens when there is not enough work process to execute so many IDocs. You can try to do parallel processing to make it quick and aviod IDocs getting stuck.

Regards,

Yogesh

Read only

Former Member
0 Likes
1,163

By increasing this profile parameter rdisp\max_wprun_time we are able to solve the problem

Read only

0 Likes
1,163

Hi,

if ur sending at a shot 1000 idocs or more then there is a chance tht even if u you increase run time paramters it will go for time out in future. so collect the idocs so tht the idoc posting/processing time is not there...then schedule the reports for backgrnd processing

Jayaram