on 11-23-2010 6:34 PM
Hello experts,
A communication issue was detected in our XMII system that impacted the operation of the background processes that are scheduled in the system
When performing a connection check from the TCP connection that is configured in the backend (ECC) pointing to the XMII we received the following error:
Error when opening an RFC connection
ERROR: program MIMANMAAA not registerd
LOCATION: SAP-Gateway on host haerpp11 / sapgw00
DETAIL TP MIMANMAAA not registered
COMPONENT: SAP-Gateway
COUNTER: 58078
When checking in the XMII under the Data Server connector that is configured having the target as the Backed we detected the connection status as "Stopped", in order to solve this problem we needed to performed a reboot of the XMII application.
Do you know if is it possilbe to reestablish the communication of this connector without restarting the full application?
Thanks and regards,
Hi,
Please check the help document for connecting MII to ERP
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563
And regarding Data servers are you connected to SQL databases or any other database, if so please check the path you are passing for connecting the database.
Best regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on Dec 8, 2010 8:24 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rodolfo,
I have read through this thread several times and I am still not sure what you are trying to do or how. Are you trying to send IDOCs to MII or execute remote functions from MII?
If it is IDOCs, please use the document Sudhir Kumar linked to in his message. Once configured, you should be able to verify the connection with a simple SM59 Test Connection or go to POIT and send a production order or planned order to MII.
(From your error message, it sounds like you are sending an IDOC and the IDOC Listener is not configured properly in either MII or in ECC.)
If it is BAPI or RFC remote function calls from MII, try using the same credentials to log into the target ECC system and test the calls from either BAPI or SE37 t-codes. Then follow Rajesh's suggestinn on creating a transaction in the Workbench. You need to create an SAP Server Editor entry with the ID and Pwd you tested in ECC.
Create the transaction, add an SAP JCO Interface action block. configure it using the SAP Server you just created, type BAPI_PRODORDCONF* into the Search Pattern, then hit the Get LIst button. If it returns a list of BAPIs, then you have a good connection (the Get List button actually executes a specific RFC to return the list of BAPIs).
If you are still having problems, please provide some more details on what you have done and how you are testing it. I would also suggest more information to be gathered from the NW Logs.
Regards,
Mike
Hi.
Kindly let us the know the version of SAP MII & SAP ECC system.
If you are facing communication issues between SAP MII & ECC system, include SAP Basis team (From ECC side) to solve connectivity issues.
Note : Ensure you have provided proper ECC system details with SAP MII.
Thanks
Rajesh Sivaprakasam.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Kindly check whether SAP ECC system is configured correctly with SAP MII
http://help.sap.com/saphelp_xmii120/helpdata/en/index.htm
Once SAP ECC is configured, Open SAP xMII Workbench -> New -> Transaction
Create a new action "SAP JCO Connector" . Try to pull any BAPI details.
If connection between ECC & MII is established successfully, you can able to access BAPI in MII. If not, Include SAP Basis team for connectivity issue.
Thanks
Rajesh.S
User | Count |
---|---|
12 | |
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.