topic Re: IDOC : Trigger immidiately in Application Development and Automation Discussions

IDOC : Trigger immidiately

dhinesh_thirugnanam — Mon, 14 Jun 2021 11:48:42 GMT

Hi,

I have scheduled a background job using this program(RBDAPP01) to process IDOC documents sent from Ariba to ECC by setting timeframe as 1minute.

However user wants to reduce the time frame or happen it immediately without going into wait mode(for 1 minute).

Can you please let me know how it can be achieved.

Thanks.

Re: IDOC : Trigger immidiately

Dominik_Tylczynski — Mon, 14 Jun 2021 12:36:50 GMT

Hello dhinesh.thirugnanam

I'd say you should set immediate processing of the IDocs in the partner profile - transaction WE20.

Best regards

Dominik Tylczynski

Re: IDOC : Trigger immidiately

RaymondGiuseppi — Mon, 14 Jun 2021 13:21:25 GMT

Menu: IDoc Interface/ALE Administration Runtime Settings Partner Profiles (WE20) - On the Inbound Parameters detail screen, select the immediate option.

But perform some performance tests (number of processes used, etc.)

Re: IDOC : Trigger immidiately

Sandra_Rossi — Mon, 14 Jun 2021 15:29:36 GMT

It has been asked hundreds of times in the forum how to trigger immediately the processing of IDocs.

Re: IDOC : Trigger immidiately

JackGraus — Wed, 16 Jun 2021 03:55:00 GMT

As said setting the process immediate flag in the partner profile is most simple and logic. Then no batch job is required.

However doing so can have some disadvantages. Like when multiple IDOC's are delivered they will be processed asynchronously and could cause locking issues or timing issues. This is prevented by executing a job for RBDAPP01 like you do now. This will execute IDOC's sequential.

When immediate job execution is required you could trigger the job by a batch job event. The batch job event could be raised by kernel executable. Or by creating a small development to trigger the batch job event by interface.

Re: IDOC : Trigger immidiately

dhinesh_thirugnanam — Wed, 16 Jun 2021 05:29:58 GMT

Hi ,

The "Process immediately" checkbox is already set. As IDOCS were not processing immediately even though the checkbox was selected, I went to set up the background job by setting a time frame for 1minute.

However user now wants the time frame to be reduced to seconds or immediate.

For triggering a event, I am not sure what event needs to be put exactly this should happen when "Order Confirmation" is done from Ariba system to ECC.

Re: IDOC : Trigger immidiately

dhinesh_thirugnanam — Wed, 16 Jun 2021 05:30:14 GMT

Hi ,

However user now wants the time frame to be reduced to seconds or immediate.

For triggering a event, I am not sure what event needs to be put exactly this should happen when "Order Confirmation" is done from Ariba system to ECC.

Re: IDOC : Trigger immidiately

Dominik_Tylczynski — Wed, 16 Jun 2021 07:11:48 GMT

Hello dhinesh.thirugnanam

Your IDocs are actually processed immediately - IDoc status 62 "IDoc passed to application" means that the processing has been triggered. Your problem is that the processing is not finishing with final status of 51 or 53.

Consider the following notes:

2324075 - Inbound Idocs getting stuck in status 62

2617821 - How to analyze inbound IDoc slow processing

Best regards

Dominik Tylczynski

Re: IDOC : Trigger immidiately

Dominik_Tylczynski — Wed, 16 Jun 2021 07:14:15 GMT

raymond.giuseppi sandra.rossi jack.graus2

I guess the problem is not that much with IDocs not triggering immediate processing. If it was, IDocs would stuck in 64 status. However they remain in 62, which means that the IDoc processing is started but for some reason it doesn't end with status update to 51 or 53.