Skip to Content

Why SAP MII JCO connection keep the SAP Server name configuration in cache?

Apr 12 at 02:51 PM


avatar image

We've transported a transaction using JCO interface action block which was auto-populated with DEV connection settings. when running in QA, it's trying to connect DEV ERP instead of QA. for some reason it doesn't refresh the fields, unless you manually open the transaction in QA and reset the connection selection. this action is not possible in QA as the project is deployed and using CTS for transport.

JCO cache was already refreshed - XMII/JCOProxy?Mode=Reset.

Any idea will be appreciated.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

christian libich Apr 13 at 02:51 PM

This shouldn't happen and sounds like a bug. I would check for any relevant sap notes and/or log a ticket with SAP.


Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks Christian!

Neha Kshirsagar
Apr 16 at 09:00 AM

Hello Ellias ,

Could you try below step .Generally in migration projects we do this activity for transactions.

1) Clear xml samples

For transaction it is possible that transaction action block still holds an old xml response which could be pointing to old dev.

Hence right click on the each action and clear response ,save and execute .

Thank You ,


Show 1 Share
10 |10000 characters needed characters left characters exceeded

Good idea Neha, but even after clearing the responses it is failing. It will clear the Request/Response structures, but the value in cache is the SAPServerName link...