We had a requirement to implement a SYNC ASYNC bridge with SOAP as sender and IDOC as receiver. There are few good options we have.

  1. Using IDOC as SOAP service.But the receiver SAP system in version 6.20 or higher. Please see the blog SOAP for IDOC demystified for more details.
  2. Using NWBPM to handle this.

But what you would do in case the receiver SAP system version is low and also you are not having an NWBPM developer. Then the below solution can work.

Use this method Configuring Sync/Async Bridge on SAP NetWeaver Process Orchestration with a little trick.We will configure the ICOs following that and will create one additional ICO which will pick the file and post the IDOC to SAP system.

In the First ICO we are going to receive the SYNC request and write a File on our File System with the name as the message ID.

Sender Channel of 1st ICO:

Pic.jpg

After that we do the necessary mapping to convert the SOAP structure to IDOC. We can also do the same in 3rd ICO which we are going to develop later.

Receiver File channel of 1st ICO:Please note the configuration carefully.

Pic.jpg

Pic.jpg

Pic.jpg

Pic.jpg

Now we go to the config of  2nd ICO:Please note that we just need a sender channel to use NotifyResponseBean however a channel can not work without an ICO, we need to create this ICO.

Sender Channel of 2nd ICO:

Pic.jpg

Pic.jpg

Pic.jpg

Rest of the ICO is just configured with DUMMY values.

Pic.jpg

Pic.jpg

Pic.jpg

After you finish the above configuration we need another ASYNC ICO which will pick the Files written in the Archive Directory(mentioned in the sender channel of 2nd ICO) and post the IDOCs to SAP system.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply