Application Development 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: 

Issue with RBDAPP01

Former Member
0 Kudos

Hello ABAP Experts,

I am having an issue with program RBDAPP01. I want to process Queued Inbound IDocs one by one in the background using background job. I set up partner profile for Inbound Message Type choosing the processing method "Trigger by background program".

For some reason, the Queued Inbound IDocs stay in status 75 IDOC received via qRFC. When I try to process these IDoc in the background using program RBDAPP01 with message type, status 75, packet size 1 and no parallel processing the program does not process any queued IDOC and gives message no data selected.

My requirement is to process queued Idoc one by one in background using SAP program and scheduling a batch job. I do not want to process manually using WEINBQUEUE.

Is the program RBDAPP01 right choice for to process queued IDOC? Does it process only status 64 & 66 and/or 62? Is it capable to process 75?

Please help me to solve this serious issue. Thanks.

Ysv

5 REPLIES 5

Former Member
0 Kudos

Anyone can help me please? I want to run this job only once a night. How do I collect queued IDoc and run the program once in the background to process it?

Any help to resolve this issue will be appreciated.

Thanks

Ysv

0 Kudos

Hi,

in my experience, RBDAPP01 can only treat idocs which are in status 64 (only).

you can see that by reading the documentation of this program (tx SE38, button documentation). or [this online doc|http://www.se80.co.uk/sapreports/r/rbda/rbdapp01.htm].

If you want to retreat idocs in status 75, you should use transaction BD87.

Have a look also in this [web page|http://www.erpgenie.com/saptech/transactions.htm].

regards

Mickael

0 Kudos

Thanks Mickael for the info. My requirement is to process in background one at a time. Unfortunately BD87 will not be permanent solution.

On SAP Help, I read detailed information about background processing of queued IDOCS and also reviewed several documents on SAP related website on the same topic. All indicate to use the program RBDAPP01 for background processing. I am quite sure that I have correct ALE configuration and I scheduled a job Z* for the program RBDAPP01 with the parameter specified in my first email. Only thing I remebered that I kicked off the job after IDocs came in the queue. So I am wondering that caused problem for IDOCS went into 75 status?

Is there anyway the background job is trriggered when queued IDocs reach in queue? Or how frequent and when to run this job if I know when IDOCS will arrive in certain time frame. I am confused about these things.

Any information will be welcome.

Thanks.

Ysv

0 Kudos

Hi,

To process IDocs in status 75, you can use transaction: WEINBQUEUE and specify the queue name.

have also a look on: [Note 817939 - IDoc: IDocs remain in status 75|https://service.sap.com/sap/support/notes/817939]

So I am wondering that caused problem for IDOCS went into 75 status?

yes certainly as status 75 is not the "normal" status when we treate idocs.

Is there anyway the background job is trriggered when queued IDocs reach in queue?

I do not know you have to find a permanent bakcground solution, as for me it's not a normal behaviour.

Normal status is 64, and a job on RBDAPP01.

regards

Mickael

0 Kudos

Hi,

As rightly mentioned by Mickael, RBDAPP01 can process only 64 & 66 and not 75 and you need to use WEINBQUEUE to clear the current inbound queue. And based on what I understood about your requirement, you can try IDoc serialization (not ALE serialization - both are different) by populating the field EDIDC-SERIAL (IDoc control record- Technical information tab) with some unique number (may be Datetime stamp ). And when you schedule RBDAPP01 after that, these idocs will be processed one by one based on the serial number.

You can also refer the below link or search IDoc serialization or EDIDC-SERIAL to get more details.

Regards,

Gokul