topic Re: IDOC not processed in Application Development and Automation Discussions

IDOC not processed

Former Member — Wed, 07 Apr 2010 12:54:57 GMT

Hello Experts,

I'm transfering an IDOC from Client 300 to client 100. I have created a new IDOC, partner profiles etc...

In client 300(source), I have made an ABAP program to generate and send the idoc. the IDOC is generated and sent with no problem. if I go to we02 I see the IDOC with status 30 (IDoc in processing) and is kept there.

in client 100 the idoc is not appearing.

the port is defined and is pointing to client 100 Logical System.

can you please give me hints of what the problem is?

is it correct to have the status 30? it is hanging there and not visible in client 100

please help

Regards

Re: IDOC not processed

Former Member — Wed, 07 Apr 2010 13:21:46 GMT

Hi Samir Fares

If you are sending idoc from Client 300 to 100 .....

if idoc is in 30 status in Client 300.... then reprocess idoc using BD87 OR RSEOUT00

then idoc will dispatch from 300 and your will be seeing idoc in client 100 in inbound side if interface is every thing is correct..

i hope above info helps you...

Thanks

Ramesh

Re: IDOC not processed

Former Member — Wed, 07 Apr 2010 13:38:44 GMT

Hello Ramesh,

BD87 worked and the IDOC can now be seen in client 100 (this is a very good step, thanks to you), but again the idoc status is 64 (I have the yellow color "IDoc in proessing")

the new status in client 300 (source) has changed to 3 (colored is now green "Processed successfully")

1- shouldn't the IDOC be processed automatically in client 300? why I have to push manually the partner profile should do the job and the idoc should have reached client 100.

2- the Idoc is received at client 100 (reciever) but the data is not posted which means that the IDOC is not processed. I have already made my Fuction module and mapped it to the IDOC message type and again this shuld work fine.

should I manually process the IDOC at client 100 too? how?

3- what the problem may be preventing automatic processing?

Really thanks

Re: IDOC not processed

Former Member — Wed, 07 Apr 2010 13:39:26 GMT

sorry set as answered by mistake

Re: IDOC not processed

Former Member — Wed, 07 Apr 2010 14:11:45 GMT

Hi Samir Fares

Schedule the Background job RBDAPP01 in Client 100

Thanks

Ramesh

Re: IDOC not processed

DavidLY — Thu, 08 Apr 2010 01:17:08 GMT

Hello,

Regarding status 64 note the following:

The "Process Immediately" \ "Transfer Immediately" option should not be

used for high volume, noncritical transactions because you will

encounter resource problems such as this.

Instead you need to ensure you are using background processing for

your ALE communications.

Configure program RBDAPP01 (inbound) \ RSEOUT00 (outbound) to run very

specifically for the high volume message types on your system.

Schedule regular runs of report RBDAPP01 \ RESOUT00 - can be run for

IDoc Type and\or Partner etc..

You can configure these reports to run every 10 minutes or as often as

required. Then change the processing mode for the IDocs in question

For inbound:

-> go to transaction WE20 -> Select Partner

Select Inbound Message Type and change the processing method from

"Trigger Immediately" to "Trigger by background program".

For Outbound:

-> go to transaction WE20 -> Select Partner

Select Outbound Message Type and change the processing method from

"Transfer IDoc Immedi." to "Collect IDocs"

What will happen then is that these IDocs will be processed via

background runs of report RBDAPP01 \ RSEOUT00

in batch mode leaving dialog work processes free for

users and mission-critical processes. Hence you will not encounter

the resources problems you are currently experiencing.

The only other option would be to try increasing the number of

available dialog work processes.

The number of dialog processes must be greater than or equal to the

total of the number of update and background processes per

application server and must be configured across all operation mode

switches. However when there are a large number of IDocs being processed

this is not a viable option.

Please also have a look at SAP notes:

734576 IDocs retain status 64, but should be processed imm

555229 IDocs hang in status 64 for tRFC with immediate processing

Review the above information, change to background processing as

suggested and ensure that you have regular executions of RBDAPP01 and

you will be fine going forward.

Regards,

David

Re: IDOC not processed

Former Member — Thu, 08 Apr 2010 10:59:48 GMT

Thank you David, you have answered all my questions.

Thanks Ramesh too.