Rbdapp01 is working not correct! Whats wron?

Question

Hello together,
I have some strange problems with rbdapp01 to process inbound IDocs of message type CASHJOURNALDOC_CREATE.
I wrote a report which selects all necessary IDocs from table EDIDC and segments from EDIDD.
Afterwards I call (submit) the report rbdapp01.
I devide the IDocs in packages of 100 per call.
This means building internaly a range of Idoc number and after 100 appends I call the report with parameters and "to return".
So what's happend:
Only some IDocs will be processed (new status 53). Sometimes 10, sometimes 15 and so on. All the other are in status 51 (not booked)
I don't know what is wrong!
If I got afterwards to transaction BD87 and reprocess the IDocs with Status 51 it works! All Idocs will be processed!
What could be my problem?
One think what I not really understand is the parameter pacakge size of the report rbdapp01.
How have I to set this if I don't use parallel processing?
Could it be a problem with my internal building of packages?
Thanks in advance!
Christian

Answer 1

Hello,
Firstly ensure that you are using the latest RFC version and
supplement as there is a known problem with entries getting stuck in
transaction recorded with older releases\supplements.
Review note 438015 for help with this.
Next ensure that you have regular runs of report RSARFCEX scheduled
to reporcess entries in SM58 - this is a standard administrative task
that should be in place.
How are these IDocs being sent? What is the current status of the IDocs
in question.
One common reason for this problem is that you are attempting to
process a high volume of IDocs immediately.
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 (using background work
processes) 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.
Also have a look at the SAP note: 555229.
Regards,
David