topic Re: Regarding Inbound IDOC processing. in Application Development and Automation Discussions

Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 11:38:30 GMT

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?

Re: Regarding Inbound IDOC processing.

Pawan_Kesari — Mon, 18 May 2009 11:50:21 GMT

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

Re: Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 11:53:23 GMT

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

Re: Regarding Inbound IDOC processing.

Pawan_Kesari — Mon, 18 May 2009 12:00:45 GMT

Note 181729 might help

Re: Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 12:01:25 GMT

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

Re: Regarding Inbound IDOC processing.

soumya_jose3 — Mon, 18 May 2009 12:55:00 GMT

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.

Re: Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 13:09:59 GMT

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

Re: Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 13:25:04 GMT

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 .

Re: Regarding Inbound IDOC processing.

Former Member — Mon, 18 May 2009 14:34:03 GMT

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

Re: Regarding Inbound IDOC processing.

Former Member — Tue, 26 May 2009 07:04:40 GMT

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

Re: Regarding Inbound IDOC processing.

Jay71 — Tue, 26 May 2009 09:38:23 GMT

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