SAP Knowledge Base Article - Preview

3681010 - Deprecation of SAP Java Connector (JCo) 2.x in MII and Migration to JCo 3.x

Symptom

During the usage of SAP MII (Manufacturing Integration and Intelligence), issues may occur in JCo-based integrations, particularly after recent system upgrades, support package updates, or the application of MII patches: 

  • Destination <destination name> does not exist

  • null object returned from com.sap.conn.jco.JCoDestination.getLanguage

  • JCo action block fails calling a BAPI due to unsupported data type int8

  • SSO login does not work for JCo actions when destination is used

These issues occur because older JCo 2.x interfaces are no longer supported or compatible with recent SAP Java Connector (JCo) 3.x updates. 


Read more...

Environment

  • SAP MII 15.4 and higher(affected action blocks: JCo Interface, JCo Function, JCo Action)

  • SAP ME 15.4 and higher

Product

SAP Manufacturing Execution 15.4 ; SAP Manufacturing Execution 15.5 ; SAP Manufacturing Integration and Intelligence 15.4 ; SAP Manufacturing Integration and Intelligence 15.5

Keywords

MII, Manufacturing Integration and Intelligence, JCo, RFC, JCo2, JCo3, BAPI, S/4HANA, INT8, Deprecated, Migration, Destination, Connection Alias, SSO, Java Connector, Manufacturing Integration, MFG, Manufacturing, Visiprise , KBA , MFG-ME , SAP Manufacturing Execution , MFG-MII , SAP Manufacturing Integration and Intelligence , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.