Call RFC In ABAP XSLT

Hello Experts,
I have a requirement where in i need to call RFC(Which is created in R/3 system) In ABAP XSLT Mapping(defined iN xi system).
Can some one help me to achieve this??
**ITS URgent****
Thanks and Regards,
Prakash Babu.

Hi James,
Check here............
/message/5182263#5182263 [original link is broken]
RFC connections
/message/5102602#5102602 [original link is broken]
Regards,
Vijay.

Similar Messages

Web Service to ABAP Proxy, Calling RFC from ABAP Proxy

can any body send me the notes or Step by step process of Webserice of calling RFC using ABAP proxy, I am new to XI. send me detail process of this perticular scenarios

Hope this helps
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
also refer to
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
Rgds,
Kumar
Message was edited by:
Kumar

Call RFC on non ABAP-Host

Hi experts,
we try to integrate a machine into SAP.
Therefore we want to use RFC-Communication.
This means, the machine will call RFC-FMs on SAP.
I know that this works and I only need to create a "normal" RFC-FM.
But how can I call a RFC-FM on the machine out of SAP?
Do I need to make a an RFC-FM like in ABAP but the destination is the machine (which is defined in SM59)?
Kind regards

Hi ,
Please learn this link Connections to Non-SAP Systems (SAP Library - ALE Programming Guide)
http://help.sap.com/saphelp_nw04/helpdata/en/52/16aafa543311d1891c0000e8322f96/content.htm
You can take a look into idocs. For idocs processing you require RFC Library of the RFC Software Development Kit (RFC-SDK) on the non sap system side for processing RFC's.
Regards,
Sivaganesh

WD Program calls RFC. How to start external ABAP debugger to see the data

Hi Experts,
I have created WD program which calls RFC. I want to see the value passed from WD to ABAP. I have to see the values once data reaches ABAP. How I can do so?
I did following.
1) se 37 . Open the proram. Inside the fucntion near a select statement I placed the cursor. Then clicked on controlshitfF9 (set/delete external brakepoint icon).
2) I clicked on WD screen - Save push button.
3) The data goes from WD to R/3. Some processing takes place. I can see message from R/3. However debugger never got triggered.
How to resolve the issue.
Regards,
Gary

go to following link.
External debugging of ABAP from NWDS in web dynpro java
I hope it helps.
Regards,
Rohit

How can I call RFC FM from webdynpro application for ABAP? Please help!

Hi Experts,
I have a requirement where I have to make a call to RFC enabled function module passing some data from webdynpro for ABAP application. How can I achieve this? Any tutorial or links or docs will be very helpfull.
I have seen some tutorial on Adaptive RFC but it talks about webdynpro for Java.
Can I use "Call function XYZ destination A10" statement in webdynpro for ABAP application?
Thanks
Gopal

am doing same thing for my current SRM implementation.I am taking data to SRM server from another R/3 server .
This is solution I have used
1) First of all I have made ABAP connection in SM59 .
Go to SM59 .In ABAP Connection creat ABAP connection with system with which u want communicate .
Eg I am connection with Systems PB1.
So i developed Connection call PB1CLNT800.
2) In my requirement I have taken data in my context from another r/3,
I have give called RFC in my supply function of node.
Call to RFC is as usual.
In my case,
CALL FUNCTION 'RFC_MATNR'
DESTINATION 'PB1CLNT800'
TABLES
IT_MATNR = IT_MATNR.
Onwards I have read my itab IT_MATNR and populated data to context.
Hope solution will serve your purpose.
Give point if it works .If any problem i have other ways.
Cheers
Parag Bhise

The webdynpro/ABAP (WDA) calling RFC enabled FM of other ECC systems

The webdynpro/ABAP (WDA) has problem calling RFC enabled FM of other ECC systems.
WDA expects all the ABAPs, RFC FMs of remote system(DEV, QA..) to reside inside its own instance.
It is hard to transport and maintain these ABAPs FMs into a portal ABAP WDA instance.
Proxy generation at WDA client:
=======================
1. If we can make an XI enable an ABAP or RFC enabled FM of the remote ECC,
I think the XI proxy classes can be generated at the client WDA system.
Other options?
How do I do it? Can you give some tips.
2. How do I manually code the RFC Call to BAPI/FM from Webdynpro controller or other interface?
I am stuck with the above as the webservice option is not available at our ECC server. It does not have a java engine installed for webservice to be available.
Can you help on the above 2 options?

Hi Mike ,
 Answer of 2.
How do I manually code the RFC Call to BAPI/FM from Webdynpro controller or other interface?
I am doing same thing for my current SRM implementation.I am taking data to SRM server from another R/3 server .
This is solution I have used
1) First of all I have made ABAP connection in SM59 .
Go to SM59 .In ABAP Connection creat ABAP connection with system with which u want communicate .
Eg I am connection with Systems PB1.
So i developed Connection call PB1CLNT800.
2) In my requirement I have taken data in my context from another r/3,
I have give called RFC in my supply function of node.
Call to RFC is as usual.
In my case,
CALL FUNCTION 'RFC_MATNR'
DESTINATION 'PB1CLNT800'
TABLES
IT_MATNR = IT_MATNR.
Onwards I have read my itab IT_MATNR and populated data to context.
Hope solution will serve your purpose.
Give point if it works .If any problem i have other ways.
Cheers
Parry B

ABAP XSLT Extensions or XSLT (XI imported archive)?

Hi all,
I would like to know which is having better performance in a scenario with a significant number of messages.
I know that ABAP XSLT Extensions is based in XSLT 1.0 and have some features of XSLT 2.0. So, for me it means some limitations and a disadvantage compared with all of XSLT 2.0 standard can offer.
But, my question is related with performance and I just want to know which is faster.
Thanks in advance,
Cheers,
Ricardo.

Hi Ricardo,
abap xslt has one great advantage
abap stack does not have to communicate with
java stack to perform the - so no RFC calls for mapping
with many messages that might influence their flows
but it wuold be best if you could just test it
in YOUR environment (there are many test tools -
like Loadrunner from Mercury) or you can write your own scripts
and just test in your particular examle which one is better
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

FileName in ABAP XSLT Mapping

Dear SDN,
In an integration scenario we are using sender File Adapter and a ABAP XSLT Mapping.
Is there any way to get the source FileName from such mapping. Im trying to use the adapter-specific message attributes, but it doesn't work, and I didn´t find an example, probably I and doing somthing wrong.
regards,
GP

Thank you for your help,
I just try to access the adapter-specific attibutes using:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">
<xsl:variable name="filename" select="key:create('http://sap.com/xi/XI/System/File', 'Directory')" />
</xsl:stylesheet>
but the following error raised:
<SAP:Stack>Error while calling mapping program YXSLT_TEST (type Abap-XSLT, kernel error ID CX_XSLT_RUNTIME_ERROR) Call of unknown function</SAP:Stack>
have you had this situation?

Reg ABAP-XSLT mapping

Hi All,
One of my inetrfaces i am using ABAP-XSLT mapping some times i am getting the following erre "Error while calling mapping program ZXXXX_XXX (type Abap-XSLT, kernel error ID CX_XSLT_RUNTIME_ERROR) No valid source context supplied"
What does it mean and what is the reason for that error.
Regards,
Rama
Edited by: Ramakrishna Balusu on Oct 27, 2009 1:35 PM
Edited by: Ramakrishna Balusu on Oct 27, 2009 1:36 PM

Check this discussion:
XI Error
Regards,
ravi

ABAP-XSLT mapping.

Hi ALL,
I am using i scinario in my project of type IDOC to PI to SOAP . In this one my mapping is of type ABAP-XSLT . the interface is runnign fine for all the idocs except one idoc. When that particula idoc comming from r/3 it is giving short dump and the message is staying at queue as scheduled. When i am trying to reprocess the message it is giving the same dump. In the ST22 t code it is saying the XSLT_RUNTIME_ERROR and the error is XSLT "xxxx"program was termintaed scince it encounterd a statement that could not be executed. I tried to monitor the trace for the both successful messages on the same inteface. But the both the traces are same it seems. what could be the reason how to eliminate.
Regards,
Rama

Hi,
I think there is an option to debug the XSLT programs that are generated using call transformation command:
http://help.sap.com/saphelp_nw70/helpdata/en/07/88273c3f2b3c7ce10000000a11402f/content.htm
Can you try debugging the XSLT program?
Also check if there are any invalid characters like angled braces, ampersands etc in your IDOC data.
It might sometimes create issues.
Regards,
Ravi kanth Talagana

Error while calling RFC when using BSP Web Interface

Hi,
we have a problem with the Authorization when we use an Web Interface for BSP. We have assigned all roles to the user which were mentioned in the SAP standard documentation:
R_AREA
R_METHOD
R_PACKAGE
R_PARAM
R_PLEVEL
R_PM_NAME
R_PROFILE
R_STS_PT
R_STS_SUP
R_WEBITF
S_RS_ADMWB
S_RS_AUTH
S_RS_COMP
S_RS_COMP1
S_RS_DAS
S_RS_ICUBE
but we still get the error message: "Error while calling RFC".
When using a user with SAP_ALL, it works.
What can we do?
Thx for your time.
Joerg

Actually that's surprising - because BSP (Business Server Pages) and RFC (Remote Function Call) are not related; they use totally different transport protocols (http vs. RFC). Even if an BSP application is calling a function module remotely (acting as RFC client) no authorizations for S_RFC are required - in the calling system (but in the called system, i.e. the RFC server).
Since assigning SAP_ALL seems to "cure" the problem, it seems to be an authorization issue, indeed. In that case it makes sense to use the authorization trace (ST01 - notice: that's specific to one single ABAP application server; you might have to activate the trace on multiple instances) to find out which authorizations are checked / demanded.

Error while calling RFC

Hi all WebDynpro Gurus
I am using EP7.
I am developing an WD application for KM functionality in which I need to call RFC from backend. I followed the "Creating WD application accessing ABAP function" example.
But when I executed the application I got following exception.
Root Cause
The initial exception that caused the request to fail, was:
com.sap.lcr.api.cimclient.CIMClientException: java.net.MalformedURLException: URL must have a host part
Correction Hints
Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
I checked JcO connections in the webdynpro content admin. There the status is unknown and create tabs are disabled.
I checked the SLD connections in content admin , the entries are as below:
Host name : blank
Port: -1
User: blank
Url: http://.-1/sld
Where could i configure these SLD settings and what should be the new entries ?
I dont have permission to view WebDynpro console.
Please help me out.

Vinod,
Claim: "Hello, World" application with WD and RFC is the "Hello, World" application with most complex configuration.
Prove:
1. You need to run http://host:port/sld and import CIM context
2. You need to add technical WebAS ABAP systems to SLD (same URL)
3. You need to run Visual Administrator and setup SLD connection parameters (host, port, user, password)
4. You need to (re)deploy your WD application
5. You need to run web-based WebDynpro Content Administrator and configure JCO connections.
Fortunately, [1]-[4] is necessary only ones per server, [5] is necessary per every application.
Valery Silaev
SaM Solutions
http://www.sam-solutions.net
P.S. After I'd started working with XI I understood that procedure described above is not complex at all

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

Java Error in RFC Lookup in XSLT Mapping usinf Java helper class

Hi All,
I am doing RFC Lookup in XSLT Mapping using Java Helper class.
The Lookup works fine when called one RFC at a time However my requirement is I want to do 2 Lookups.
Both Lookups works when done individually however when I call both lookups in one mapping I get following error "javax.xml.transform.TransformerException: DOMSource whose Node is null."
Following is the code I have written in XSLT for the lookup:
 <xsl:template name="Lookup_1">
 <xsl:param name="STDPN"/>
 <rfc:RFC_READ_TABLE>
 <QUERY_TABLE>KNA1</QUERY_TABLE>
 <OPTIONS><item><TEXT>
 <xsl:value-of select="$STDPN"/>
 </TEXT></item>
 </OPTIONS>
 <FIELDS>
 <item>
 <FIELDNAME>KUNNR</FIELDNAME>
 </item>
 </FIELDS>
 </rfc:RFC_READ_TABLE>
 </xsl:variable>
 <xsl:variable name="response" xmlns:lookup="java:urn.mt.pi" select="lookup:execute($request, 'BS_D, 'cc_RfcLookup', $inputparam)"/>
 <xsl:element name="STDPN">
 <xsl:value-of select="$response//DATA/item/WA"/>
 </xsl:element>
 </xsl:template>
 <xsl:template name="Lookup_2">
 <xsl:param name="BELNR"/>
 <xsl:variable name="Query">AGMNT = '<xsl:value-of select="$BELNR"/>'</xsl:variable>
 <xsl:variable name="request1">
 <rfc:RFC_READ_TABLE>
 <QUERY_TABLE>ZTABLE</QUERY_TABLE>
 <OPTIONS><item><TEXT>
 <xsl:value-of select="$Query"/>
 </TEXT></item>
 </OPTIONS>
 <FIELDS>
 <item>
 <FIELDNAME>KUNAG</FIELDNAME>
 </item>
 </FIELDS>
 </rfc:RFC_READ_TABLE>
 </xsl:variable>
 <xsl:variable name="response1" xmlns:lookup="java:urn.mt.pi" select="lookup:execute($request1, 'BS_D','cc_RfcLookup', $inputparam)"/>
 <xsl:element name="BELNR">
 <xsl:value-of select="$response1//DATA/item/WA"/>
 </xsl:element>
 </xsl:template>
My Question: Am I doing anything wrong? Or Is it possible to call multiple lookups in one XSLT?
Thanks and Regards,
Atul

Hi Atul,
I had the same problem like you had.
The main Problem is that with the example code the request variable is created as NodeList object. In XSLT a variable is somekind of a constant and can't be changed. As the request object is empty after the first request the programm fails at the following line:
Source source = new DOMSource(request.item(0));
So I've created a workaround for this problem.
In the call of the template I've put the request as a parameter object at the template call:
<xsl:with-param name="req">
<rfc:PLM_EXPLORE_BILL_OF_MATERIAL xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<APPLICATION>Z001</APPLICATION>
<FLAG_NEW_EXPLOSION>X</FLAG_NEW_EXPLOSION>
<MATERIALNUMBER><xsl:value-of select="value"/></MATERIALNUMBER>
<PLANT>FSD0</PLANT>
<VALIDFROM><xsl:value-of select="//Recordset/Row[name='DTM-031']/value"/></VALIDFROM>
<BOMITEM_DATA/>
</rfc:PLM_EXPLORE_BILL_OF_MATERIAL>
</xsl:with-param>
With this change the request will be provided as a String object and not as a NodeList object.
Afterwards the RfcLookup.java has to be changed to the following:
package com.franke.mappings;
import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.PrintWriter;
import java.io.StringWriter;
import java.util.Map;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Source;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import com.sap.aii.mapping.lookup.Channel;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.lookup.RfcAccessor;
import com.sap.aii.mapping.lookup.LookupService;
import com.sap.aii.mapping.lookup.XmlPayload;
* @author Thorsten Nordholm Søbirk, AppliCon A/S
* Helper class for using the XI Lookup API with XSLT mappings for calling RFCs.
* The class is generic in that it can be used to call any remote-enabled
* function module in R/3. Generation of the XML request document and parsing of
* the XML response is left to the stylesheet, where this can be done in a very
* natural manner.
* TD:
* Changed the class that request is sent as String, because of IndexOutOfBound-exception
* When sending multiple requests in one XSLT mapping.
public class RfcLookup {
 * Execute RFC lookup.
 * @param request RFC request - TD: changed to String
 * @param service name of service
 * @param channelName name of communication channel
 * @param inputParam mapping parameters
 * @return Node containing RFC response
 public static Node execute( String request,
 String service,
 String channelName,
 Map inputParam)
 AbstractTrace trace = (AbstractTrace) inputParam.get(StreamTransformationConstants.MAPPING_TRACE);
 Node responseNode = null;
 try {
 // Get channel and accessor
 Channel channel = LookupService.getChannel(service, channelName);
 RfcAccessor accessor = LookupService.getRfcAccessor(channel);
 // Serialise request NodeList - TD: Not needed anymore as request is String
 /*TransformerFactory factory = TransformerFactory.newInstance();
 Transformer transformer = factory.newTransformer();
 Source source = new DOMSource(request.item(0));
 ByteArrayOutputStream baos = new ByteArrayOutputStream();
 StreamResult streamResult = new StreamResult(baos);
 transformer.transform(source, streamResult);*/
 // TD: Add xml header and remove linefeeds for the request string
 request = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>"+request.replaceAll("[\r\n]+", "");
 // TD: Get byte Array from request String to send afterwards
 byte[] requestBytes = request.getBytes();
 // TD: Not used anymore as request is String
 //byte[] requestBytes = baos.toByteArray();
 trace.addDebugMessage("RFC Request: " + new String(requestBytes));
 // Create input stream representing the function module request message
 InputStream inputStream = new ByteArrayInputStream(requestBytes);
 // Create XmlPayload
 XmlPayload requestPayload =LookupService.getXmlPayload(inputStream);
 // Execute lookup
 XmlPayload responsePayload = accessor.call(requestPayload);
 InputStream responseStream = responsePayload.getContent();
 TeeInputStream tee = new TeeInputStream(responseStream);
 // Create DOM tree for response
 DocumentBuilder docBuilder =DocumentBuilderFactory.newInstance().newDocumentBuilder();
 Document document = docBuilder.parse(tee);
 trace.addDebugMessage("RFC Response: " + tee.getStringContent());
 responseNode = document.getFirstChild();
 } catch (Throwable t) {
 StringWriter sw = new StringWriter();
 t.printStackTrace(new PrintWriter(sw));
 trace.addWarning(sw.toString());
 return responseNode;
 * Helper class which collects stream input while reading.
 static class TeeInputStream extends InputStream {
 private ByteArrayOutputStream baos;
 private InputStream wrappedInputStream;
 TeeInputStream(InputStream inputStream) {
 baos = new ByteArrayOutputStream();
 wrappedInputStream = inputStream;
 * @return stream content as String
 String getStringContent() {
 return baos.toString();
 /* (non-Javadoc)
 * @see java.io.InputStream#read()
 public int read() throws IOException {
 int r = wrappedInputStream.read();
 baos.write(r);
 return r;
Then you need to compile and upload this class and it should work.
I hope that this helps you.
Best regards
Till

Easy RFC lookup from XSLT mapping using a java class (getting Error)

Hi All,
I am trying to implement the sample scenario for calling RFC from xslt with the help of wrapper class. I am getting following error.
com.sap.aii.mapping.lookup.LookupException: Internal lookup service is not registered. Invoking the lookup service is only supported in the Integration Builder test environment or in the Integration Server runtime environment. at com.sap.aii.mapping.lookup.LookupService.getService(LookupService.java:400) at com.sap.aii.mapping.lookup.LookupService.getChannel(LookupService.java:285) at com.sap.aii.mapping.lookup.LookupService.getChannel(LookupService.java:318) at dk.applican.xi.mapping.lookup.RfcLookup.execute(RfcLookup.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.execute(JLBFunction.java:145) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:54) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:41) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:49) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:125) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:228) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:256) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.callTemplate(XSLStylesheet.java:1310) at com.sap.engine.lib.xsl.xslt.XSLCallTemplate.process(XSLCallTemplate.java:102) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:228) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:241) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:228) at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:241) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:228) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:256) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:445) at com.sap.engine.lib.xsl.xslt.XSLApplyTemplates.process(XSLApplyTemplates.java:158) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:228) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:256) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:445) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:381) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:392) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:234) at com.sap.aii.ibrun.server.mapping.MappingTransformer.transform(MappingTransformer.java:153) at com.sap.aii.ibrun.server.mapping.XSLTMapping.executeStep(XSLTMapping.java:67) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor482.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy22.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162
I am SAP XI 3.0 SP-9

Hello,
I have the same issue as stated above.
At runtime sometimes the mapping fails however when executing the mapping from ESR (test operation mapping) with the same payload it is executed succesfully (lookup is to system that is the senderservice of the scenario).
Anybody a clue.
Also clearing mapping cache etc. did not solve the problem.
Thanks,
Emile

Call RFC In ABAP XSLT

Similar Messages

Maybe you are looking for