Interface Mapping for enhanced Receiver Determ. in Integration Scenario

Hi guys,
Defining Integration scenario is a pleasant way working with XI.
But how to define the step "enhanced receiver determination" via message mapping in a scenario?
has anybody come along to this issue?
Kind regards
Jochen

hi,
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
http://www.****************/Tutorials/XI/RecvDetermination/Enhancement.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Edited by: murali krishna on Sep 1, 2008 5:49 PM
Edited by: murali krishna on Sep 1, 2008 6:03 PM

Similar Messages

Interface Determination under Enhanced Receiver Determination Scenario

Hi,
One of the very basic assumption for Enhanced Receiver Determination is that Receivers are found at run time, and one of the such requirement is that we don't know about Receiver Business System at the time of configuration.
Now for such scenarios, how do we configure "Interface Determination". For Interface Determination one of the input filed is "Receiver Service/Party", in addition to "Sender Service/Party" plus "Sender Interface"
Since we don't know Receivers at config, what value(s) should come in "Receiver Service/Party" in Interface Determination at config time.
Thanking all of you in advance

Hi Rajan,
You have to do the following things:-
First, maintain Database Table in SAP XI. Which contains several keys like Sender, Receiver system and then according to that key combination we perform a JCO call and fetch the values which gives us the correct receiver and interface.
Create a Data Type which will be having Two elements Service And Interface.
Now careate a message type and message interface for this data type. This will be for your receiver.
Then use source payload and perform a message mapping between Sender Payload & this Message Type.
Use UDF and make a JCO call and fetch table entries for service and interface.
Then in Directory perform extended determination and use this mapping into it. The result will be Service & Interface.
Thanqs
Biplab

Enhanced Receiver Determination in Synchronous Scenario

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.

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.

Conditional Receiver Determination Through Integration Scenario

Hi
My question is "Is it possible to generate conditional receiver detrmination through integration scenario?"
If yes then how?
Thanks and Regards
Sami

Hi Biplab,
Yes , there is lots of modification in PI 7.1. and we start using it, you will come to know. In this TechEd at banglore , i did hands on the Mapping and it was really good experience, When i started configuring ID, i came to know some powerful ways, and yes i am really looking forward to working on it. Actually, as you know when we configure everything in ID, it becomes complicated, that is rectified thr and also some additional features. Pretty faster than PI 7 we using. also configuration in some extend is automated, we doen't need to bother to configure some of the steps :).
Also you must know that, it added a concept of ESR for IB. Just have a look on some of the PPT for PI 7.1 and you feel it :).
Aashish

Cannot test the Interface mapping for abapmapping

Dear all,
i am trying to go to the test tab in the interface mapping foe testing a abap mapping.
but it is giving me this error " unable to test . you cannot test the program in the test environment "
is this some authorisation issue

login to ABAP stack of XI and is the transaction SXI_MAPPING_TEST to test ABAP mapping

SOAP receiver starting the integration scenario

Hello experts,
I am searching for a way to start an integration scenario with a SOAP receiver in the same way it is possible with JDBC sender (with a pool interval).
The scenario is: I need to execute a webservice, getting information from it, and send this information to an abap proxy on ECC side.
I thought about creating a ccBPM with a loop (with no end) and a wait step for doing it... although it works, I think it is not the best way for doing it.
Thanks for your suggestions!
regards.
Roberti

Thank you guys.
Let me explain the scenario in a better way.
The scenario is:
1 - Automatically execute a partner webservice sync call with constant parameters.
2 - Get the webservice response.
3 - Map the response to get required information.
4 - Send this information to an Abap proxy.
5 - Process the information to proper abap objects.
Note: This scenario needs to be automatically executed every 30 minutes.
The purpose of this scenario is to GET documents (xml) from a partner web service and import the information to ECC, continuously, each 30 minutes. So, no one is supposed to start the process, it should be automatically triggered. The goal is exactly the same we have with JDBC or file sender adapter, where we can set a 30 minutes interval to automatically execute an sql statement in the database or read a file in a path.
JAVAGUY and Stefan Grube, I did it in this way. But, scheduling an Abap job to start the proxy -> webservice -> proxy scenario, the Abap job is the RESPONSIBLE for the scenario. If something wrong occurs with that job schedule, the integration will stop working. I would prefer PI as responsible for the process, so I can have alerts and other execution guarantees.
Abhishek Salvi and Pratik_du, I think that the scenario is clear now, don't it? About the ccBPM, this is another way I implemented the solution. I created a ccBPM with
1 - A receiver that I execute just once
2 - One loop with a condition 1 = 1 (infinite)
2a (Into the loop) - A send step to execute the webservice sync call
2b (Into the loop) - A receiver step to get the webservice response
2c (Into the loop) - A map step to transform the information I need
2d (Into the loop) - A send step to send the information to the Abap proxy
2e (Into the loop) - A wait step to wait 30 minutes until execute the next step of the loop
IIn this case, I will have a ccBPM running continuously and doing the job.
I posted the question because I'm not sure which solution is better, and check if you can see another way to make PI the responsible for starting a scenario with a soap receiver like this.
Thank you again.
Roberti

Multi Mapping for JDBC Receiver JDBC Adapter

Hi All,
I'm trying an IDoc to JDBC (canonical XML) scenario using multi mapping (single IDoc as source and two different JDBC messages in receiver end). But, this is failing in RWB with some parser error. So, am not sure whether multi mapping is allowed for JDBC Canonical XML format. Please clarify.
Thanks,
Hussain.

Hi ,
JDBC Adapter supports multi mapping,so you can implement the same,but what do you mean by Canonical XML format??
Regards,
Raj

Will ECC 4.X is enough for Auto ID RTI and Integrated Scenarios or ECC6.0 ?

Hi Friends,
Will all Auto ID Scenarios work with < ECC 6.0 or we need only ECC 6.0 ? Please clarify
Thanks & Regards
V.Rangarajan

For SAP AII RTI Scenario you dont need SAP ECC at all.
Except for Product tracking and authentication which requires SAP ECC 6.0 all other scenario's in SAP AII is supported by lower versions of SAP back end. R/3 4.6C is the minimum requirement.
Regards,
Vivek

Interface Mapping Not Found in Integration Directory

Hey guys!
I'am getting this error in the test configuration part of the integration directory:
"Interface Mapping: <Not Found> com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping"
I don't see why I should be getting this error since I have properly defined a message and interface mapping for the receiving interface.
BTW, I get this error when I use XSLT mapping. If I point my interface mapping to a normal message mapping, I get no error. Is there anything I am missing?
Regards,
Glenn

The weird thing is that when I test the the configuration in the Integration Directory, it is still looking for my old message mapping (the one i created using xi editor) even though I already replaced the referenced message mapping in the interface mapping to the XSL one.
Yes, I tested the interface mapping with the same data using the XSL mapping and there's no problem.
When I send the message though, I get an error saying "NO_RECEIVER_CASE_ASYNC" I really don't see why it should not recognize the receiver. I tried refreshing the cache but it still looks for my old mapping program...
:P

Enhanced Receiver determination - for Integration Process

Hi,
Just wanted to confirm that if it is possible to have more than one Receivers, with Enhanced Receiver Determination and one of the Receiver happens to be Integration Process. I know with Enhanced Receiver Determinations you can find more than one Receivers at Run time, however the key question is, if in addition to normal Receiver Systems (like SAP R/3 or Web Services etc), if we can also kickoff Integration Process within Enhanced Receiver Determination.
Thanking in advance.

as said by Udo Martens
Assumedly the different receivers are using different Inbound Interfaces (a BP is using an Abstract Interface). Therefore you would need for each different receiver a own Interface Determination referring a own mapping.
refer this wiki http://wiki.sdn.sap.com/wiki/pages/pointstab/viewpageversion.action?pageId=131760630&version=5 to Know how to configure Enhanced receiver determination and Interface determination for each receiver .
In your case one of the receiver will be Integration process

Interface mapping is not visible in receiver determination

Hi,
I could not see interface mapping in my receiver determination in ID.
I can see the message interface and receiver agreement in receiver determination
my scenario is idoc to soap (SAP R3 to webservice)
Thanks
Ruban

hi,
could you plz check as Sheshagiri and Phani have said.
Also wanted to know,are u using the configuration wizard for creating ur business scenario and not finding ur interface mapping?
if so is the case then try creating manually ur reciever determination and add ur interface mapping(if u have already done as said by phani and seshagiri) by inserting it.
let us know how it went.
thanks,
ahmed

Interface Mapping not supported in the JPA specification?

Are there any plans to add Interface support in the JPA specification? It is not supported by JPA annotations, which seems quite disruptive to proper object oriented design. However, individual implementations of JPA seem to support this:
http://docs.jboss.org/hibernate/stable/core/reference/en/html_single/#inheritance-tableperclass
http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_%28ELUG%29#How_to_Use_the_.40VariableOneToOne_Annotation
There is visible interest in getting this implemented at an Annotation level for Hibernate also but the developers for Hibernate point out that this isn't even in the JPA specifications.
http://opensource.atlassian.com/projects/hibernate/browse/ANN-9
https://forum.hibernate.org/viewtopic.php?f=9&t=941363&sid=4abdbc72cbf04380f4a8e2cadd7dfada&start=15
Is this being talked about/in the works for JPA? Why not include @VariableOneToOne in the spec? It would seem to be quite an essential feature for wide adoption.

Hi,
You can only choose the Interface mapping for the Enhanced recevier determination in the extended tab of Receiver determination. & I dont see the Interface mapping in the select list.
Where do I have to check for the proper outbound message???
Regards

Interface Mapping not listing in the Extended Reciever Determination

Hi,
The Interface Mapping is not shown in my Extended receiver determination. I have created and activated the IM & MM using the MT - Receivers within the SAP Basis.
Regards
Unni

Hi,
You can only choose the Interface mapping for the Enhanced recevier determination in the extended tab of Receiver determination. & I dont see the Interface mapping in the select list.
Where do I have to check for the proper outbound message???
Regards

Interface mapping test successful, throws exception in BPM

Hi.
We are having a problem with an Interface mapping which works when
tested in Integration Builder, but throws an Exception when it is part
of the Transformation in a BPM.
The scenarion is such:
1. The sender calls the outbound interface using a web service.
2. XI uses the input and passes to the Integration Process
3. In the BPM, a LOGON message is built to call the web service as
specified by an external web service . The input and
output messages are just a single string, in which the other XML is
embedded.
4. XI receives a response from the web service call
5. XI Extracts the sessionId from the response and combines it with the
initial input (Step 1) to create the query for the query message in
the web service.
It is in Step 5 where the transformation fails, with an Exception in
the DefaultTrace.trc as
Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Thrown:
MESSAGE ID: com.sap.aii.ibrun.server.mapping.rb_MappingRuntimeException.EXCEPTION_DURING_EXECUTE
com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
I have extracted the data from the initial request (step 1) and the
logon response (step 4) and using these I have tested the Interface
Mapping. There is no problem with this and the tests are successful.
From what I can see, because the Response field in the LOGONResponse
contains more XML tags, XI must be parsing it and assuming the tags are
tags in the message, and not just the string, thus it is complaining
that the XSD types do not match. This extra XML Parsing does not take
place in the Interface Mapping Test.
I have put the response into a User Defined Function which just has one
line "return new String("Hello")" and that fails. However, if this UDF
does not have the Response as the input, it does not complain.
Please advise.
--Reenal

hi
You will have to use specific replacements for you xml tags if it is coming as a paramter
replace '<' with <
replace '>' with >
for eg: I want to pass <TakeIt>200</TakeIt> as value to Element <A>
Mapping won't work if it is passed like
a) <A><TakeIt>200</TakeIt></A> - Wrong
Instead the replace the angle brackets
b) <A><TakeIt>200</TakeIt></A> - Correct
While testing the mapping in IR (a) will work bcoz the test tool will convert it to (b) format. Check the xml source in test tool.
So ensure the web response is like (b)
rgds,
Arun

Intermittent JDBC error in Enhanced Receiver Determination

Hi,
I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
The database is DB2 on i5/os 6.1
Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
But the same message with same values is successfull earlier.
This is not a design problem; the interface is working well 95% of the time.
I found some JDBC error in NWA java logs:
Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
Thrown:
com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
Any idea? Can high volume cause the JDBC Receiver to fail?
Martin

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Interface Mapping for enhanced Receiver Determ. in Integration Scenario

Similar Messages

Maybe you are looking for