FAQ XI BC Adapter
1. Q: What is discussed in this document?
A: This document discusses questions about the XI BcAdapter.
2. Q: Are there some terms used with respect to this FAQ?
A: The abbreviation BC is used for the "SAP Business Connector", BcAdapter for the "XI SAP Business Connector Adapter".
3. Q: Which version of Business Connector is supported by the BcAdapter?
A: BcAdapter supports the SAP Business Connector 4.7.
4. Q: Which type of documents can be processed with the BcAdapter?
A: The BcAdapter supports these types of documents:
RFC-XML: For receiver channels a normal RFC-XML document is supported. Such a document can e.g. be created with the XI RfcAdapter. When sending this document to BC, BcAdapter does a conversion into the special form of RFC-XML with an envelope that BC expects. For sender channels this special form of the RFC-XML document with envelope, as created by the BC, is supported. Such a document will be converted by the BcAdapter into the normal form, like known by the XI Integration Repository.
IDoc-XML: For receiver channels the payload of the XI message has to be an already completed IDoc-XML document. In case of a sender channel the XI message header is built from the IDoc-XML control record. The rules which are used to build the header are the same as for the XI IDoc Adapter. They are described in detail in the documentation of the BcAdapter sender channel.
5. Q: Which quality of service (QoS) is supported?
A: For receiver channels QoS BE (Best Effort) will result in a synchronous call (sRFC) , QoS EO (Exactly Once) will create a transactional call (tRFC) to the BC. For sender channels a synchronous call (sRFC) will result in a message with QoS BE, a transactional call (tRFC) will result in a message with QoS EO.QoS EOIO is not supported by the BcAdapter.
6. Q: Which transport protocol is used during communication between BcAdapter and BC?
A: The transport protocol is always HTTP (or HTTPS) as configured in the communication channel.
7. Q: An error message like 'XRFC_DOC_TYPE_UNKNOWN not supported as Payload' is raised. What does this mean?
A: When the BcAdapter receives a document that is not of type 'RFC-XML' or 'RFC-XML with envelope' this error happens. See question 4 for more information on supported document types.
8. Q: What is the URL for BC Adapter sender channels?
A: The URL is
The values for <protocol>, < host> and <port> are the configured values of the SAP J2EE Engine. The <protocol> value can be http or https.
9. Q: How does a 'RFC-XML with envelope' document look like?
A: Such a document basically is a normal RFC-XML document like it is generated by the SAP XI RfcAdapter sender channel. As addition this type of document is wrapped in an XML envelope. Here is an example of this envelope:
< sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
< sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
< saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">FROM</saptr:From>
< saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">TO</saptr:To>
NORMAL RFC-XML DOCUMENT
Here is an explanation of the individual tags.
From: The sender of this document. 'FROM' in this example.
To: The receiver of this document. 'TO' in this example.
Transaction: If the document represents a synchronous call (sRFC), the whole tag can be omitted. For a asynchronous call (tRFC), the value enclosed by this tag must be the tRFC TID. 'TID' in this example.
Body: The normal RFC-XML document is enclosed by this tag.
10. Q: How is the XI header built from the payload in a BC sender channel?
A: A BcAdapter sender channel expects an 'RFC-XML with envelope' document like described in Q9. The 'From' tag must be a concatenation of the SYS-ID and the client of the sending SAP system, e.g. 'ABC123'. This also has to be upper case. The value of this field is matched to the adapter-specific identifiers (RFC) in the Integration Directory. Only partyless services are taken into account during this search. This way a partyless service is found in the Integration Directory. The value of the 'To'-tag is ignored, because the XI receiver is determined during the routing step in the Integration Server.
If this procedure is successful, a XI message with the following header fields is created:
Sender Party: ""
Sender Service: The XI service found via the adapter-specific identifiers (RFC)
Reciver Party: ""
Receiver Service: ""
Interface: The name of the root element tag of the normal RFC-XML document enclosed by the Body-tag of the 'RFC-XML with envelope' document.
Namespace: The namespace of the root element tag of the normal RFC-XML document enclosed by the Body-tag of the 'RFC-XML with envelope' document.
11. Q: How is the 'RFC-XML with envelope' document built from an XI message for BcAdapter receiver channels?
A: A BcAdapter reciver channel expects an RFC-XML document like it is produced by a SAP XI RfcAdapter sender channel. This RFC-XML document is wrapped into an envelope. The result is a 'RFC-XML with envelope' document (like described in Q9). The Header-fields of this document are filled from the XI message header fields after this scheme:
From: A lookup of the adapter-specific identifier (RFC) for the XI message sender Party/Service is done. If it is found, the fields System-ID and Client are concatenated and used as From. If it is not found, the name of the XI message sender Service is used as From.
To: A lookup of the adapter-specific identifier (RFC) for the XI message receiver Party/Service is done. If it is found, the fields System-ID and Client are concatenated and used as To. If it is not found, the name of the XI message receiver Service is used as To.
Transaction: If the XI message is asynchronous (QoS EO) this tag is filled with a TID representing the XI message-ID. If the XI message is synchronous (QoS BE) the whole tag is suppressed.
12. Q: Is it possible to use an HTTP proxy for the HTTP/S communication?
A: See note 816022 question 19.