Process IDocs in Background

[Former Member]

Hi,

What is the best possible way to process an IDoc (Message type: ORDERS/ORDCHG) in background in an Interactive report.

Thanks in advance.

Rgds,

AK

[christian_wohlfahrt]

Hi AK!

I would say it is the best way to process IDOCs in background - and if you are in a hurry, use also parallel processing.

Report RBDAPP01 is able to do this all.

Regards,

Christian

[Former Member]

Hi Christian,

The program RBDAPP01 is used to process the Idocs with errors 64 and 66 only.

I want to process the IDoc with status 51. In such a case, I can use RBDMANI2 program.

But I am looking for Function Module or BAPI methods.

Rgds,

AK

Message was edited by: AK

[hymavathi_oruganti]

IDOCS_OUTPUT_IN_QRFC check thi fn module, it may help u!

[Former Member]

in we20 (Partner Profiles) you can set for inbound parameters

- Trigger by background programm or

- Trigger immediately

If you change the setting to "Background" you have to plan the report rbdapp01 as a background job.

Regards

kishan

[hymavathi_oruganti]

u can run RBDMIDOC program, and in bd61, u can activate change pointers and u can schedule the idoc to run in background

[Former Member]

AK, Could you please elaborate a little more?

Do you want to process an iDoc that is already existing? or do you want to trigger creation of a new idoc altogether?

If it is a second option, quick and dirty approach is to insert an entry in NAST table for the specified output type (using RV_MESSAGES_INSERT or RV_MESSAGES_UPDATE FM). This will add an entry to NAST table. And you can either set the Processing time to '1' (SEnd with periodically scheduled job) or '4' (so that an idoc is generated immediately).

[Former Member]

Hi AK

Here's the procedure to post IDocs in ALE inbound processing in background.

• Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.

• The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.

Perform the following steps:

1. Set-up background processing (IDoc/ALE area menu):

IDoc Interface/ALE --> Administration --> Runtime Settings --> Partner Profiles (WE20)

Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.

2. Schedule posting (ALE customizing):

Transaction SALE --> Set-Up System Monitoring --> Posting IDocs in Recipient System --> Schedule

You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring --> Status Monitor (BD87), select the IDocs and then select Process.

You should choose background processing, especially if large data volumes are to be distributed. System performance is better.

Packet Processing can be used to process individual inbound IDocs in the background.

Dont forget to reward, if it helps ;>)

Regards,

Rakesh.

Message was edited by: Rakesh

[Former Member]

Hi All,

The question here is:

I want to Process an Error Idoc in the background in a report program. Whenver the user select a specific IDoc from a Custom Report program, it should be automatically processed. It is an Interactive report.

So, I want to know the best possible way for Processing the Error IDoc in the background.

Thanks to you all for taking time to respond.

Rgds,

AK

[Former Member]

HI AK,

To process Idoc in background use report RBDINPUT.

It will give u error details alog with status.

You can use a trickmethod also in BD87 use -restrict and process and there specify in backround.

Thanks & Regards,

Ankur

[Former Member]

Hi,

RBDINPUT does not give option to re-process IDOCs with status 52.

How do we re-process IDOCs with status 52? Is there any other program to do the same?

TIA,

Regards

Deepthi

[Former Member]

HI AK,

It looks you were able to solve the problem on your own . Can you please post how you resolved the issue . It will be helpful for us to resolve these kind of issues if we ever come up in future .

Regards,

Varun .