RFC Look ups

Hi all,
I need to get a value for a field from the target system according to the soucre field.
For Ex : material number 0001 is from source system and i need to find the corresponding material number from the target SAP system.
Please let me know how it can acheived.
Thanks
Faheem

1. Create a RFC in R/3 system that has ur desired functioanlity.
2. Create RFC look up in the UDF.
3. Map the UDF as follows
Source- field-> UDF(RFC Look up)---> Target Field
Refer this for more info
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72

Similar Messages

Look-Ups

Hi All,
1.Can you tell me what exactly the look-ups are?
2.Please tell me about the RFC and JDBC look-ups.
3.Also please tell me how many data types do I need to create for For JDBC <---> RFC sync ?
4.From my point of view I should create 2 data types ,2 message types for JDBC Request and JDBC Response while I can skip creating data types for Receiving RFC side.Is it?
Thanks in advance.

Hi Swetha,
1.Can you tell me about when are RFC,JDBC,CSV look-ups are used?
Look ups can be useful in any where, especially when we like to map the value that is reseided in some other application system and that value tend to change or get updated very frequently in that system .So as to get the recently updated values we prefer this .if it doesnot happen we cn directly go for hardcoding either by using Fixed values or value mapping.If the value is queried from R/3 we use RFC look ups.If the value is to be retived from Database we go for JDBC.
2.I think look ups are nothing but the User Defined Functions.Is it?Please tell me in detail.
Look ups need not not only Java functions we can do that in BPMs remember Filr to RFC to FIle using BPM scenario there we get values from RFC response too in Bpm .But this is again a performance issue with out using UDF.But its very easy to perform the lookups using UDF.Even SAP has provided good JavaAPI to perform lookups according to requirement.In most of the cases we use lookups for querying single values.But in PI7.1 there has been added advantage in the form of Graphical lookups to avoid java code and maintin reusability.The link was mentioned by experts already.
3.Please give me any scenerio about the implementation of RFC,JDBC,CSV look-ups .
I am giving example which i came across while working with EDI documents in SEEBURGER environment.There was a field value "TE" in some segment, while mapping to target i should get the Defintion forTE wich was maintained in some other data base and map to the target side, for that purpose we had to use JDBC look up and ping the data base to retrive the required value as the result of Lookup. So when i applied look up i got the value "TELEPHONE" for the code TE.The same way for FX the lookup result was FASCIMILE.Not only this for PLANTCODES and some other business related data we might need to use Lookups...Hope you understood my point.
Thanks,
Ram.

Hi experts- RFC look up in IDoc to File Senario

Hi,
I have req with Idoc to file (delivery Idoc).
But i need to get user name of sender(r/3) into file which is not available in idoc type.
I think we can do through RFC lookup functonality.
Can u tell me exact procedure and code for this?

Hi,
Check some links on Look ups.
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
Look ups.
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
/people/francesco.bersani/blog/2007/03/05/data-lookup-optimized
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
Use this crazy piece for any RFC Mapping Lookups!
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
SAP XI Lookup API
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
Lookups in XI made simpler
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
Lookup - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
DB lookup - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0
Lookup's in XI made simpler - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
How to check JDBC SQL Query Syntax and verify the query results inside a User Defined Function of the Lookup API -
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
/people/prasad.illapani/blog/2006/10/25/how-to-check-jdbc-sql-query-syntax-and-verify-the-query-results-inside-a-user-defined-function-of-the-lookup-api
Lookups - /people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
Lookups - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/content.htm
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
Lookups with XSLT - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72
/people/sravya.talanki2/blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
How we have to create the lookups?
Check this weblogs with some screenshots on how to achieve this:
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
/people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
Regards,
Phani
Rewar points if Helpful

Help regarding Look ups

Hi All,
Right now i am using look ups for RFC Receiver Adapter.
i have code something like this in Mapping for Look ups
//Determine a channel, as created in the Configuration
channel = LookupService.getChannel("DB-SYSTEM-NAME","DB-CHANNEL-NAME");
Now my problem is here in this code i am hard coding "DB-SYSTEM-NAME" and "DB-CHANNEL-NAME". I dont want this hard coding, as when i will transport this code to Quality or Production system, at that time name is going to get changed. If suppose DB-SYSTEM-NAME is SAPXIDEV then in QA it will be like SAPXIQA and in Production it will be something like SAPXIPRD like that.
I want to know that is there any way to get SID of XI system in this code? as in place of DB-SYSTEM-NAME i am giving SID (business system name) for XI Dev server, which i need to change when i will transport it to QA or PRD.
Please reply me as soon as possible. Please let me know if any other things need to be clearified.
Regards,
HS

Hi,
Search on SDN for Value Mapping Using Graphical Mapping.
The basic idea of using Graphical Mapping is like using a properties file in Java. You will have a Key-Value pair . The Key is always the same across the environments which you hardcode and the Value will change.
So KEY will be BusinessSystem and the value will change across environments and so on.
Regards
Bhavesh

What is Mapping Look ups?

Can any one explain me what is mapping look ups in graphical mapping?

Hi,
There are three types of look ups u can do
RFC look up
SOAP look up
JDBC look up
What is Lookup and why we need:
Within an XI mapping it is a common requirement to be able to perform data lookups on-the-fly. In particular, there may be a need to look up some data that is maintained in an R/3 application.
In the error handling topic we have seen the different validations which need to be performed on file. This can be done through Lookup.
Some use cases:
Look up material number from table MARA.
Look up cost center budget.
Look up employee information.
Look up unit-of-measure (UOM) information from table t006a.
Lookup for raising an alert.
The purpose of the lookup may be:
To perform application-level validation of the data, before sending it to the backend.
To populate fields of the XML document with some additional data found in the backend application.
This is a form of value transformation.
The "value mappings" offered by XI are not adequate in this case, since the data would have to be manually entered in the Integration Directory.
There are two ways in which we can do lookup:
Call lookup method from GUI mapping.
Call lookup method from XSLT mapping.
Lookup method from GUI mapping can be called using any of the following ways.
RFC lookup using JCO (without communication channel)
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
RFC lookup with communication channel.
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
Lookup using JDBC adapter.
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
CSV file lookup.
/people/sundararamaprasad.subbaraman/blog/2005/12/09/making-csv-file-lookup-possible-in-sap-xi
Lookups with XSLT - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffbbf72
/people/sravya.talanki2/blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
DB lookup - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
You can refer to these links.
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer Absolute stealer.
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
For Java APIs and also here you can map that how many types of lookups are possible in XI.
http://help.sap.com/javadocs/NW04/current/pi/com/sap/aii/mapping/lookup/package-summary.html
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

LOOK UPS situation

Hi,
          i studied all the links regarding LOOK UPS which are provided in the SDN .. but still i did't clear with this information..   when exactly we will go for lookups.. i means in which situation we will go for lookups..( i studyed that lookups will interrupt the mapping and interact with the database and access the data from the database in the mapping time..)   but in what scenario we need to get the data from database...give me a simple example..
       can any body give me a brief idea abt LOOK UPs..
thanks
babu

Within an XI mapping it is a common requirement to be able to perform data lookups on-the-fly. In particular, there may be a need to look up some data that is maintained in an R/3 application.
In the error handling topic we have seen the different validations which need to be performed on file. This can be done through Lookup.
Some use cases:
Look up material number from table MARA.
Look up cost center budget.
Look up employee information.
Look up unit-of-measure (UOM) information from table t006a.
Lookup for raising an alert.
The purpose of the lookup may be:
To perform application-level validation of the data, before sending it to the backend.
To populate fields of the XML document with some additional data found in the backend application.
This is a form of value transformation.
The "value mappings" offered by XI are not adequate in this case, since the data would have to be manually entered in the Integration Directory.
There are two ways in which we can do lookup:
Call lookup method from GUI mapping.
Call lookup method from XSLT mapping.
Lookup method from GUI mapping can be called using any of the following ways.
RFC lookup using JCO (without communication channel)
      /people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
RFC lookup with communication channel.
                 /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
Lookup using JDBC adapter.
      /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
      /people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
CSV file lookup.
      /people/sundararamaprasad.subbaraman/blog/2005/12/09/making-csv-file-lookup-possible-in-sap-xi
Thanks and Regards,
Chirag Gohil

Need help on RFC look up in PI 7.0

Dear experts ,
I am working on Jdbc to Abap Proxy scenario where i need to perform a RFC Look up . I have searched in SCN and found some help ful blogs, but still need more information in below points.
My requirement is need to fetch Cost Center (KOSTL) by taking Personal number(PERNR) as Input parameter.
1) Do we have to create and import the RFC into PI ?
2) Do we need to create a UDF ? If yes, Kindly provide some useful links.
Thanks in Advance,
Mohammed

Hi indrajit,
i had written : java.util.Map map;" in the import secion of UDF. but still i am getting the following errors
Source code has syntax error: /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:3: cannot resolve symbol symbol : class map location: interface java.util.Map import com.sap.aii.mappingtool.tf3.*;import com.sap.aii.mappingtool.tf3.rt.*;import java.util.*;import java.io.*; import java.lang.reflect.*;import java.util.Map.map; ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:257: cannot resolve symbol symbol : class RfcAccessor location: class com.sap.xi.tf._MM_RMF_TO_SAP_ RfcAccessor accessor = null; ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:262: cannot resolve symbol symbol : class Channel location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Channel channel = LookupService.getChannel(BS_SAP_R3,CC_RFC_LOOK_UP_CRMNEXT); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:262: cannot resolve symbol symbol : variable BS_SAP_R3 location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Channel channel = LookupService.getChannel(BS_SAP_R3,CC_RFC_LOOK_UP_CRMNEXT); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:262: cannot resolve symbol symbol : variable CC_RFC_LOOK_UP_CRMNEXT location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Channel channel = LookupService.getChannel(BS_SAP_R3,CC_RFC_LOOK_UP_CRMNEXT); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:262: cannot resolve symbol symbol : variable LookupService location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Channel channel = LookupService.getChannel(BS_SAP_R3,CC_RFC_LOOK_UP_CRMNEXT); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:264: cannot resolve symbol symbol : variable LookupService location: class com.sap.xi.tf._MM_RMF_TO_SAP_ accessor = LookupService.getRfcAccessor(channel); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:268: cannot resolve symbol symbol : class XmlPayload location: class com.sap.xi.tf._MM_RMF_TO_SAP_ XmlPayload payload = LookupService.getXmlPayload(inputStream); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:268: cannot resolve symbol symbol : variable LookupService location: class com.sap.xi.tf._MM_RMF_TO_SAP_ XmlPayload payload = LookupService.getXmlPayload(inputStream); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:270: cannot resolve symbol symbol : class Payload location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Payload result = null; ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:275: cannot resolve symbol symbol : class DocumentBuilderFactory location: class com.sap.xi.tf._MM_RMF_TO_SAP_ DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:275: cannot resolve symbol symbol : variable DocumentBuilderFactory location: class com.sap.xi.tf._MM_RMF_TO_SAP_ DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:276: cannot resolve symbol symbol : class DocumentBuilder location: class com.sap.xi.tf._MM_RMF_TO_SAP_ DocumentBuilder builder = factory.newDocumentBuilder(); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:277: cannot resolve symbol symbol : class Document location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Document document = builder.parse(in); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:278: cannot resolve symbol symbol : class NodeList location: class com.sap.xi.tf._MM_RMF_TO_SAP_ NodeList list = document.getElementsByTagName("I_KOSTL"); // The lookupValue is available as WA tag in the response ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:279: cannot resolve symbol symbol : class Node location: class com.sap.xi.tf._MM_RMF_TO_SAP_ Node node = list.item(0); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:283: cannot resolve symbol symbol : variable returnValue location: class com.sap.xi.tf._MM_RMF_TO_SAP_ returnValue = node.getNodeValue(); ^ /usr/sap/XD1/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map2d519647b0c211e39616000000844522/source/com/sap/xi/tf/_MM_RMF_TO_SAP_.java:290: cannot resolve symbol symbol : class LookupException location: class com.sap.xi.tf._MM_RMF_TO_SAP_ } catch (LookupException e) { ^ 18 errors
so can you please explain, how can i import those files.

Urgent : Error in RFC Look Up using JCO.

Hi,
I have a scenario od accessing a database table by passing the name through XI and also giving the Where condition ,passing the fieldnames and getting back the field values . The FM that id used for this on ABAP side is RFC_READ_TABLE.
For this Scenario I inserted a Java Code using JCO's in th UDF for the RFC Look Up's.
I got errors while activating the MM which i am not able to rectify.Please Help me in this.
Activation of the change list canceled Check result for Message Mapping MM_Notes_2_ED_Z_SDIDOC |
Starting compilation Source code has syntax error: /usr/sap/EXD/DVEBMGS49/j2ee/cluster/server0/./temp/classpath_resolver/Map303c42607df411dc8b1d00e000c553d9/source/com/sap/xi/tf/_MM_Notes_2_ED_Z_SDIDOC_.java:1539: cannot resolve symbol symbol : method createClient (java.lang.String,java.lang.String) location: class com.sap.mw.jco.JCO JCO.Client mConnection = JCO.createClient("200","EN"); ^ /usr/sap/EXD/DVEBMGS49/j2ee/cluster/server0/./temp/classpath_resolver/Map303c42607df411dc8b1d00e000c553d9/source/com/sap/xi/tf/_MM_Notes_2_ED_Z_SDIDOC_.java:1578: cannot resolve symbol symbol : variable result location: class com.sap.xi.tf._MM_Notes_2_ED_Z_SDIDOC_ result.addValue(resultSet[pos]); ^ 2 errors
This is an Urgent Requirement. Please reply ASAP.
Regards,
Priyanka.

Hi Priyanka,
The error message says there are 2 errors:
1. createClient
2. result.addValue
For the first one, I guess you might not have included all the API required for lookup
For second one, please check what is the type of object you are adding to the resultset, maybe you can just say result.addValue(resultSet[pos] + ""); to typecast it.

RFC Look Up with MultiMapping in PI 7.1

Hi All,
I have created a multimapping with one source & two target messages. I am using a RFC look Up for one of fields inside mapping.
But, when I used this multimapping in interface determination in PI 7.1, at runtime i got an error.
Error - is variable (Say XYZ) used while creating parameter for RFC look Up in message mapping doesn't exist.
If I execute multimapping without RFC look Up, it worked absolutely fine.
I have used RFC look Up in number of normal message mappings, it worked fine.
Not sure, if this is a issue with PI 7.1, that multi-mapping with RFC look Up isn't supported at enhanced interface determination.
Please provide inputs for this or if anybody has hands on experience using this with PI 7.1
Thanks,
Venkat

Hi,
Please go through the thread:
Re: Global Variables declaration in PI 7.1
and check whether its useful.
Regards,
Vineetha.

IDOC to IDOC....... RFC look up

Hi Friends,
Iam new to SAP XI and have some questions.Answers to this query will be my pleasure.
my scenario:
sender :idoc1 (delivery)
receiver: idoc2 if customer present
 else idoc3 to create "customer" and then idoc2 to create "sales order"
Message mappings:
1 for idoc1 to idoc2
1 for idoc1 to idoc3
and 2 interface mappings for the above message mappings.
Please explain me how can i use one mapping if condition is false and then mapping2
and how to use second mapping if condition is true.
Also given below is mapping for a field .Please check and explain:
source field:E1ADRM1-PARTNER_ID
Mapping/Transformation rule:E1ADRM1-PARTNER_Q = 'WE' Select KUNNR from KNB1where ALTKN = E1ADRM1-PARTNER_ID and BUKRS = 'GR11' Value = KNB1-KUNNR and check that KNA1-STCD2 = 999839383 with KNA1-KUNNR=KNB1-KUNNR if no entry found in KNB1customer must be created
Target field: PARTN_NUMB
Please explain.I got an answer previously that i have to use RFC look up, if so please explain where and how to write the RFC look up.
Thanks in advance,
Harish.

Hi Kinthali,
I think I am not getting your question correctly...
You need to map from Idoc1 to idoc2 or if idoc 2 is not the idoc1 to idoc3... right??
>>Please explain me how can i use one mapping if condition is false and then mapping2 and how to use second mapping if condition is true.
Which condition are you talking about here?? Check the condition in the interface determination and then choose the needed interface...
Regards
Suraj

Cannot perform RFC Look UP

Hi All,
When I executed the RFC Look up function in the mapping could see the following error.
"Run time exception when processing target field mapping. Cannot perform RFC Look Up".
I performed the below steps but still could find the same error again:
1.In the test tab of the message mapping I have assined a channel which I configured in the Interface determination of the configuration and also assigned a value to that channel.
2. Has given the values for the parameters in the operation mapping and also the binding is done successfully.
3. The function module I assined is also existing and could test the same for output values for the given input values.
Please help me resolve the error.
Thanks & Regards,
Kumar.

Hi,
This is the error I could see in the communication channel monitoring of RWB.
"Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>"
Help me with this error.
Thanks,
Kumar.

Reg. RFC look up

Hi All,
I am working on RFC look up. My Scenario is IDoc to IDoc. The IDoc has a segment say E1 where the occurence is 0---5 and two fields inside that i.e. QUALF and IDTNR. The requiremnt is like when QUALF is equal to 002 then fetch the value of material number from SAP and map to IDTNR. Also this material number is picked only when QUALF is equal to 003 and the field IDTNR has some value i.e. article number in SAP. So I need to get value of the material number equal to this article number.
I am using RFC look up for this mapping condition in order to fetch value from SAP.
Can anyone help me on this to configure the RFC look up in PI?
Thanks and Regards,
Neethu

Hi All,
For my requirement I have used this UDF,
String content = "";
MappingTrace importanttrace;
importanttrace = container.getTrace();
// filling the string with our RFC-XML (with values)
String m ="<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:ZSD_EAN_MATERIAL_GET xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><P_EAN11></P_EAN11></ns0:ZSD_EAN_MATERIAL_GET>" ;
RfcAccessor accessor = null;
ByteArrayOutputStream out = null;
try
// 1. Determine a channel (Business system, Communication channel)
Channel channel = LookupService.getChannel("RD9","CC_RFC_RECEIVER_LOOKUP_I040");
// 2. Get a RFC accessor for a channel.
accessor = LookupService.getRfcAccessor(channel);
// 3. Create a xml input stream representing the function module request message.
InputStream inputStream = new ByteArrayInputStream(m.getBytes());
// 4. Create xml payload
XmlPayload payload = LookupService.getXmlPayload(inputStream);
// 5. Execute lookup.
Payload result = accessor.call(payload);
InputStream in = result.getContent();
out = new ByteArrayOutputStream(1024);
byte[] buffer = new byte[1024];
for (int read = in.read(buffer); read > 0; read = in.read(buffer)) {
out.write(buffer, 0, read);
content = out.toString();
catch(LookupException e)
importanttrace.addWarning("Error while lookup " + e.getMessage() );
catch(IOException e)
importanttrace.addWarning("Error " + e.getMessage() );
finally
if (out!=null) {
try {
out.close();
} catch (IOException e) {
importanttrace.addWarning("Error while closing stream " + e.getMessage() );
// 7. close the accessor in order to free resources.
if (accessor!=null) {
try {
accessor.close();
} catch (LookupException e) {
importanttrace.addWarning("Error while closing accessor " + e.getMessage() );
//returning the result u2013 RFC-XML.response
return content;
While executing this UDF I am getting the output as:
<?xml version="1.0" encoding="UTF-8"?><rfc:ZSD_EAN_MATERIAL_GET.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Materialnumber></Materialnumber></rfc:ZSD_EAN_MATERIAL_GET.Response></IDTNR>
<KTEXT />
instead of value
Can anyone suggest me on this?
Thanks and Regards,
Neethu

RFC Look up Caching Results

Hello Experts,
I am facing an issue in PI7.1 while using RFC Look up functionality. I use this in a high usage interface and now I see that it actually caches the results somewhere and does not actually make the RFC call to the backend system.
I refered some threads, but could not get answers. Has anyone else faced this issue ? If yes, could you let me know what the solution is to get around this issue?
Thanks,
Karthik

Thanks Arpil, We are calling the RFC look up once per mapping. We get results into a global variable and process it thereafter. But this interface that has this mapping itself gets called very frequently, around 30 calls per second.
We are using the RFC look up wizard in PI7.1 and hence not building any new java code etc..but the results are cached. If the data changes in the back end system, the RFC still fetches us old data and only a forced cache refresh is causing it to pick up the new results..

Using RFC Look Up in Java Mapping

Hi All,
I need to do an RFC Look Up in a Java Mapping program. The response structure of the Function Module to be called consists of only one node called RESULT. In order to read the value exported by the function module in this export parameter RESULT, I am using the following code:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = null;
factory.setNamespaceAware(false);
factory.setValidating(false);
Document docResponse = null;
InputStream in1 = result.getContent();
docResponse = builder.parse(in1);
String output = docResponse.getDocumentElement().getFirstChild().getNodeValue();
The function module works correctly and returns the expected result when tested in SE37. However, on running the above code, the statement docResponse.getDocumentElement().getFirstChild().getNodeValue(); always returns the value NULL and not the expected value that is actually returned by the RFC.
Kindly let me know where could I be going wrong.
Thanks in advance.

Hi Sreehari,
Your DOM code looks correct, it might be something with the overall code of java mapping. Just have a look at this blog /people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes
and compare you code with it. See whether you can fine tune your coding to get the rigth response.
Regards
Suraj

How to use Infocube in Look ups

Hi Experts,
i have a requirement that i have Infoset as source and Infocube as target. For the two key figures in the target i neet to get the values from some other Infocube by comparing some characteristics using look ups..
Before i have used Look ups to get the data from DSO..now i have a question that how to get the values from Infocube ..
thank you..

Hi,
also see following function module
RRW3_GET_QUERY_VIEW_DATA
Thanks and regards

RFC Look ups

Similar Messages

Maybe you are looking for