on 07-13-2004 2:26 PM
In this presentation ( https://www.sdn.sap.com/content_documents/.../SAP%20XI%202.0%20-%20Features.pdf page 20), the following limitations are listed for the RFC Adapter for XI 2.0:
Functionality
Synchronous RFC
No support forRFMsthat use update task without COMMIT WORK
No SAP GUI
No callbacks
No session handling
No RFCs to non-SAP systems (using RFC client or server libraries)
tRFC: Support for exactly-once delivery for one message/call
Not all tRFC functionality
No bundling of multiple calls
With version 3.0, what are the current limitations??
SAP Documentation states the following:
Constraints
Note the following restrictions:
· Assignment is only guaranteed for transactional RFCs (tRFCs), that is, for messages with quality of service Exactly Once (EO).
· There is no transactional context for more than one RFC call for each LUW (Logical Unit of Work).
· Not provided: SAPGUI, callbacks, and qRFC (quality of service Exactly Once In Order (EOIO)).
· RFC library clients (RFC SDK) are not supported.
· The context in the called system is not kept open over multiple calls (calls are stateless; there is no session).
· Only the payload of a received message is evaluated. Additional attachments are ignored and not forwarded.
· The receiver adapter can only process valid RFC XML documents, for example, those generated by the sender adapter or by the SAP JCo.
available at: http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
best Regards
Christien
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
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.