Skip to Content
avatar image
Former Member

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

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.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 13, 2018 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.


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 16, 2018 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 ,


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      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...