on 04-22-2015 1:19 PM
Hi Experts
I am working in ws..>sap pi..>Rfc sync scerio
when I have entered the data in RFC its working fi9 but I am using SOAPUI to test it, it's giving me error:
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: 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>
pls note that I have reimported the RFC
pls suggest!
Hello,
Test your data with the mapping,
Is there any error in the receiver RFC channel while sending the data?
Check the receiver channel.
Regards,
Manigandan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Refer to question no 16 under the below note
730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter
Q 16: While sending a message to the RFC Adapter the error "... functiontemplate from repository was <null>" is shown. What is the reason?
A: After receiving a message from the Adapter Engine, the RFC Adapter extracts the payload from the message. Normally this should be an XML document in the RFC-XML format. In this format the root element of the XML document represents the name of the function module and is enclosed in the fixed RFC namespace 'urn:sap-com:document:sap:rfc:functions'. But this only will be checked at a later point, when the conversion from XML to native RFC is done. As prerequisite of this conversion the structures and types of the function module parameters has to be known. This is also called metadata or function template. To get this function template the name of the function module is extracted from the root element of the XML document and is queried against the metadata repository of the communication channel. If the metadata repository doesn't have a function module with this name, the exception named above is thrown. Possible reasons are
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nunu,
Did you change anything in RFC? If you change anything the changes are not reflected automatically to RFC meatada cache, you need to below to refresh the metadata.
Q 29: When a function module is changed in the backend, are the
changes published to the runtime at real-time?
A: No, an update made to a function module in the backend is not
informed to the runtime. This is because the function module metadata
is cached by the system during the first invocation of the module. All
the subsequent references to this function module are directed to the
cache. Any update made to the function module in the backend will not
be notified to the runtime, unless the cache is cleared.
The cache is cleared when any of the following happen:
- The corresponding RFC channel is restarted
- The RFC channel is changed in the Integration Directory
- The RFC adapter service is restarted
- The Dependent J2EE services are restarted (MessagingSystem,
CPACache, and so on)
- The J2EE server is restarted
Regards,
Praveen.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.