本文详细解释了在使用RfcAdapter处理消息时遇到的异常，即功能模板从仓库中获取到的名称为null的情况。分析了可能的原因包括非RFC-XML文档的XML内容、元数据仓库中不存在对应功能模块等，并提供了修正建议。
MessageID
com.sap.SOA.apt_rfc.0303
Equivalent MessageIDs
n/a
Detailed Information
Exception text: Functiontemplate from repository was <null>
Possible Reasons: After receiving a message from the Adapter Engine, the RfcAdapter 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'. This name 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 Impact
Since the RFC adapter was not able to find the function module name, it cannot find a matching Sender Agreement and hence the processing stops
Next Steps
The possible reasons are:
The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository
The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37
Please correct the above stated points
com.sap.SOA.apt_rfc.0303
Equivalent MessageIDs
n/a
Detailed Information
Exception text: Functiontemplate from repository was <null>
Possible Reasons: After receiving a message from the Adapter Engine, the RfcAdapter 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'. This name 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 Impact
Since the RFC adapter was not able to find the function module name, it cannot find a matching Sender Agreement and hence the processing stops
Next Steps
The possible reasons are:
The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository
The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37
Please correct the above stated points
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
