cancel
Showing results for 
Search instead for 
Did you mean: 

Enhanced Receiver Determination in Synchronous Scenario

former_member188019
Active Participant
0 Kudos

Hi,

my synch scenario with standard Receiver determination is working fine.

the service interfaces i used are SI_OutSynch_EmpInfo_Request and SI_InbSynch_EmpInfo_Provide.

I am now trying to apply enhanced Receiver determination for the same synch scenario.

For this, in ID, in my Receiver Determination object i selected the radio button Extended, then it is asking for an operation mapping. infact it is asking for an OM with sender Interface=SI_OutSynch_EmpInfo_Request (from my swcv) and Receiver Interface = ReceiverDetermination (from SAP BASIS swcv)..

So I logged into ESR, and created an OM_test_EnhancedRD, with sourceInterface=SI_OutSynch_EmpInfo_Request (from my swcv) and TargetInterface = ReceiverDetermination (from SAP BASIS swcv)

But when i tried to activate the OM_test_EnhancedRD, it is not getting activated, and giving below error:

Interface modi are different. Source interface Operation SI_OutSynch_EmpInfo_Request | http://mycomp.com/myns is synchronous. Target interface Operation ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous

So my queries are:

1. is for synch scenarios, if receiver information is part of the request payload, how can we apply the extended Receiver Determination, so that the Receiver is determined dynamically.

2. or is there any synch version of ReceiverDetermination (from SAP BASIS swcv) available.

thanks in advance.

madhu.

Accepted Solutions (1)

Accepted Solutions (1)

former_member181962
Active Contributor
0 Kudos

Check if this blog shows you some direction:

/people/jin.shin/blog/2007/12/11/sap-netweaver-process-integration-enhanced-receiver-determination-for-synchronous-scenarios

Regards,

Ravi Kanth Talagana

Answers (1)

Answers (1)

former_member200962
Active Contributor
0 Kudos
Interface modi are different. Source interface Operation SI_OutSynch_EmpInfo_Request | http://mycomp.com/myns is 
synchronous. Target interface Operation ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous

the error is quite self-explanatory

The SI from your SWCV is Sync while the one from BASIS is Async.....OM cannot be defined between a Sync and Async SI....both of the message/ service interfaces should have the same mode (either Sync or Async)

Regards,

Abhishek.

former_member188019
Active Participant
0 Kudos

you are right abhishek, the error msg is says "OM cannot be defined between a Sync and Async SI"

in this case, does SAP provide synch version of ReceiverDetermination SI, so that we can use that in OM for enhanced Receiver Determination.

in my case , the receiver name is in one of the field of the request payload message. i need to map this field to Service element of the predefined ReceiverDetermination, so that receiver is dynamically determined at runtime.

thanks,

Madhu.

former_member200962
Active Contributor
0 Kudos

in this case, does SAP provide synch version of ReceiverDetermination SI, so that we can use that in OM for enhanced Receiver Determination.

If you have a look at the blog-reference given by Ravi you will find a way on how to make the ReceiverDetermination Si synchronous or work with the same async SI.....for quick reference below is the way mentioned in the blog:

From the blog:
Option 1:
A quick and easy way to allow for synchronous enhanced receiver determination setup is to circumvent the check that prevents 
a synchronous interface to be matched to an asynchronous interface in an interface mapping. This can be done simply by 
manually entering the name and namespace of the ReceiverDetermination interface object (e.g. 'ReceiverDetermination' 
and 'http://sap.com/xi/XI/System' respectively) for the target/receiver interface in the interface mapping, but leaving the value for 
the Software Component Version empty.

Option 2:
Select Modify and then change the mode to synchronous. Since a synchronous interface requires an input message as well, you 
can reuse the Receivers message type used in the output message - it doesn't really matter as long as some message type is 
used.

Both of the above options are available under the Applying the Workarounds section of the blog

Regards,

Abhishek.