on 03-10-2005 6:01 PM
Hi,
I'm trying to test the RFC-XI-RFC connection using STFC_CONNECTION fn.module, I end up getting this error
"com.sap.engine.services.rfcengine.RFCException: Bean STFC_CONNECTION not found".
Any idea is appreciated.
Regards,
felix.
Hi,
The probelm "com.sap.engine.services.rfcengine.RFCException: Bean STFC_CONNECTION not found" is not a problem with SP levels. This is the problem that you encounter when u specify the Program id "SAPSLDAPI_PXI" and Gatewayhost-- XIServer.
Solution:
The Program id that you mention in technical settings has nothng to do with J2ee Visual admin settings.
The program id can be any arbitrary name that should match with the program id that you provide in RFC sender Adapter.
The gatewayhost name should be the name of the SAP system gatewayhost & gatewayservice from which you are sending the request, and not the XIServer.
In RFC sender adapter, the RFC Server Parameters correspond to the SAP system from which you are receiving the request.
Hope this solves your problem.
Regards,
Siva Maranani.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
what level of XI 3.0 are you on? SP?
There were issues with the RFC Adapter, we had a problem when there is no return parameter XI dies and only a patch for SP10 help it. We used BAPI_TRANSACTION_COMMIT.
Cheers
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Felix,
to better help you where do you get the error.
Are you able to send the RFC to XI, e.g. XI receives it and creates an SXMB_MONI record for an incoming message and then gets a status of failed?
Or are you not able to send the RFC to XI at all and it dumps on the R/3 side?
The connection from R/3 to XI is not the same SM59 which you would use for IDOCs, e.g. it is a type T for the JCO call. JCO receives it and maps it into RFC-XML and then sends to XI.
Cheers
Stefan
Stefan,
Not able to send the RFC to XI, connection dumps on the R/3 side. Not seen in XI monitor.
Yes, it is 'T' connection type with registered program id "SAPSLDAPI_PXI" (same in J2EE side). When I test the connection in SM59 it is ok.
Here are the settings: (R/3-Xi-R/3)
Here both sender & receiver are same R/3.
R/3(SM59)settings :
RFC - SAPSLDAPI
Program ID - SAPSLDAPI_PXI (registered server id)
Gateway host - nemo
Gateway services - sapgw00
Fn.module called - STFC_CONNECTION (se337)
RFC target system - SAPSLDAPI (parameter passed)
XI settings:
service - R_TO_R
sender config:
Adapter type - RFC
transport protocol - RFC
message protocol - RFC (RFC XML)
adapter engine - Integration Server
adapter status - active
application server - sap-bw
application server service(gateway) - sapgw06
program id - SAPSLIAPI_PXI
application server - sap-bw
system number - 06
user - user6
paswd - xxx
logon lang - EN
logon client - 800
receiver config:
Adapter type - RFC
transport protocol - RFC
message protocol - RFC (RFC XML)
adapter engine - Integration Server
adapter status - active
application server - sap-bw
system number - 06
user - user6
paswd - xxx
logon lang - EN
logon client - 800
Your help is appreciated.
Regards,
felix.
Hi felix,
You need to use a unique program ID in your RFC adapter config which is different from any other existing program IDs in your XI system. When you activate the RFC comm. channel, XI will generate an entry in J2EE JCO RFC Provider service using the same program ID.
Make sure you can see your connection in transaction SMGW.
Hope this helps.
Hart
Hi Felix,
I have a similar error situation.I am not able to send the RFC to XI, connection dumps on the R/3 side. I don't see anything in the XI monitor.
I am using XI 3.0 SP12. When we test the connection in SM59 on the R/3 Side it is OK.
I know , you had a similar error situation before. How did you get rid of this situation?
Help please!
Thanks,
Raghu
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
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.