on 11-09-2012 5:10 PM
We have the XMIIIDOC01 Listener working just fine.
Now we need to configure XMIIRFC01 Listener to connect the same ERP with the same MII.
Some how, we always get the same error message. We have followed the document http://scn.sap.com/docs/DOC-1775
and the notes described by Michael Appleby at http://scn.sap.com/thread/3259123.
We are using SAP MII 12.1.10 and the error is
com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: no Beans listening for name ZRFC_XXXX registered for XMIIRFC01 on system SERVERXX_MID_00
together with this message we got the following message as well
[JRA]ReaderManaged_Application_Thread_22, onRollback(), no bean for given tid=0A010033133850915E220598
Any suggestion what it could be?
Regards
Italo Stefani
Vetta Group
Hi Italo,
Yes, they can both co-exist. There is no reason for them to be in conflict given they were both installed correctly and are not sharing the programId or other resources.
One other comment is that if you made changes to the NW settings, there were issues where values were cached and not fully being purged when changes were made. Sometimes it is worthwhile to simply start from scratch with a different RFC Listener. In other words, do a "clean" config on a different RFC Listener. Leave the binding at the default (it is different from the IDoc List.)
I have not played around much with the RFC Listeners since the Batch Manufacturing project and RDS days a few years ago. The "BEAN" messages occur in the IDoc Listeners as well and there is a note in the latest IDoc Listener Config Doc regarding some common error messages and their causes.
Regards, Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Mike.
I just solved the problem! We had couple issues.
1) I restarted both tc~sapjra~temp and xapps~xmii~ear application and the messages started to be sent correctly.
2) I am not sure if the restart is really necessary, I was convinced it was until I found a duplicated configuration. Someone configured the XMIIRFC01 and XMIIRFC10 and I did not see. So, after the application restart all messages had been received by XMIIRFC10 Listener, whatever was the destination in the SAP ECC. So, I left only the XMIIRFC01 listener working and the messages are ok now.
Thank you very much for your help. The steps were very helpful!!
Just to register the steps I have followed, I will paste it here. The complete thread can be found in here http://scn.sap.com/message/13635104#13635104.
The helpful steps described by Mike:
-----------------------------------------------------------------------------
Here is what I found in my notes for setting up the ERP side:
On the MII side:
Important Comment Number 1:
I will admit to a lot less experience with RFC Listeners than IDoc Listeners, but the basic processes are very similar. One thing is that you do not use the ProgramID in multiple places on either ERP or MII. The common result is seeing some of your documents showing up and some disappearing.
Important Comment Number 2:
NW self-registers the ProgramID when you complete the MII operations above. If you manually register your ProgramID with NW, it will now reside in two locations in NW - see Important Comment Number 1.
-----------------------------------------------------------------------------
Italo Stefani
Vetta Group
Looking at the discussions one thing I notice about our setup that differs from Mikes Doc is that our MDMP & Unicode Settings are Non-Unicode and MDMP Settings Inactive. Once I got our setup working I never really had the time or need to track down why it had to be that way to work but our SAP system isn't Unicode so I would guess thats the reason. Probably not your issue if you have your idocs working already but maybe worth a look.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
6 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.