Skip to Content
0

Process SOAP outbound messages sequentially

Oct 24, 2017 at 11:39 AM

55

avatar image

Hi Experts,

In our project we have a IDoc to SOAP scenario, but we are facing a problem while sending the messages to the target system.

There are only a limited number of sessions that are available in the target system.

For ex: If we are sending 100 messages to the target system and the number of sessions available on the target system is 50, then 50 messages will go into error and return the SOAP fault.

Could someone please tell,

Is there a way to avoid this?

is there a way to send the messages sequentially rather than parallely?

Regards,

Aayush Aggarwal

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Evgeniy Kolmakov Oct 25, 2017 at 08:11 AM
1

Hi Aayush!

Another option might be to use SOAP loop with EOIO quality of service to send IDocs to receiver system one by one.

Regards, Evgeniy.

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Evgeniy,

I am not sure whether i can use that because the scenario is IDoc to SOAP...

Regards,

Aayush Aggarwal

0

Hi Aayush!

It doesn't depend on adapter type used. You just use intermediate interface and split message flow in two parts (ICOs). And in second ICo you can set quality service to EOIO for sender SOAP adapter.

Regards, Evgeniy.

1
Raghuraman S Oct 24, 2017 at 11:48 AM
0

On what process IDOC is triggered.

Try scheduling a batch job so in way that only 50 Idocs are only generated per JOB.

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Raghuraman,

The IDoc is getting generated through a change pointer.

Could you please tell me the steps for scheduling the background job?

Regards,

Aayush Aggarwal

0

Hello Aayush,

Try the below steps

1.In the partner profile select Collect IDOCs options with pack size as 1.

2.Schedule the Job "RSEOUT00" with variants -number of IDOCS as 50 and run this job based on how the IDOC are getting generated(for example in one hour 50 IDOCS means schedule the job to run for every hour).

This is one approach,You can check with ABAPer as well for any other approach.

And is it like every time if you send 100 IDOCS it is getting failed?How long a single IDOC posting takes place?

If its less you can delay each message processing using UDF else you can try BPM as well.

Also below approach might help which will process the IDOC sequentially instead of parallel processing.

https://blogs.sap.com/2013/02/04/proxy-and-idoc-serializing-techniques-in-pi/

0

Hi Raghuraman,

Thanks for your reply, the link you shared is for Inbound IDocs...

Also, I'll give this report RSEOUT00 to the team.

Regards,
Aayush Aggarwal

0
0
Sanjeev Shekhar Singh Nov 06, 2017 at 05:13 AM
0

If you are on PO, you can batch IDocs up and send them sequentially from BPM.

Share
10 |10000 characters needed characters left characters exceeded