通過JCO連接器訪問SAP後端時出現SEGMENT_UNKNOWN錯誤

我試圖通過Java中間件（Dell Boomi）連接到SAP系統以檢查現有文檔類型。檢查基本IDOC類型（例如ORDERS05）時，一切正常。當嘗試檢查一個自定義類型（例如ZORDERS05）我從Java的JCO類一個默默無聞的例外：通過JCO連接器訪問SAP後端時出現SEGMENT_UNKNOWN錯誤

Feb 25, 2016 6:56:56 PM CET WARNING [com.boomi.connector.sap.browse.SAPIDocSchemaBuilder buildSchema] Unable to find IDoc base type: ZORDERS05, extension: 
com.sap.conn.jco.AbapException: (126) SEGMENT_UNKNOWN: SEGMENT_UNKNOWN Message 257 of class EA type E, Par[1]: ZHEADER, Par[2]: 740 
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:2083) 
    at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1185) 
    at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1014) 
    at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1458) 
    at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1428) 
    at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:332) 
    at com.boomi.connector.sap.SAPConnection.executeFunction(SAPConnection.java:103) 
    at com.boomi.connector.sap.browse.SAPIDocSchemaBuilder.buildSchema(SAPIDocSchemaBuilder.java:49) 
    at com.boomi.connector.sap.browse.SAPSchemaBrowser.buildIDocProfile(SAPSchemaBrowser.java:210) 
    at com.boomi.connector.sap.browse.SAPSchemaBrowser.browse(SAPSchemaBrowser.java:84) 
    at com.boomi.connector.custom.CustomConnectorBrowseAction.browse(CustomConnectorBrowseAction.java:77) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:606) 
    at com.boomi.util.ClassUtil$InvokerWithClassLoader.invoke(ClassUtil.java:360) 
    at com.sun.proxy.$Proxy72.browse(Unknown Source) 
    at com.boomi.connector.BrowseMessageHandler.handle(BrowseMessageHandler.java:116) 
    at com.boomi.container.core.MessagePollerThread$BaseTask.handleMessage(MessagePollerThread.java:657) 
    at com.boomi.container.core.MessagePollerThread$AsyncTask.run(MessagePollerThread.java:742) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
    at java.lang.Thread.run(Thread.java:745)

關於如何解決此問題的任何提示？ SAP側的對象似乎是真正相同的（兩種基本類型，沒有擴展名等）

來源

2016-02-25 Simone Avogadro

不知道該怎麼回事，但可能[this]（http://scn.sap.com/thread/3436578）或[this]（https：// developer.ibm.com/answers/questions/191133/why-does-the-websphere-adapter-for-sap-get-the-com.html）可能會有所幫助 –

來自Ravindra HV的說明是正確的，這個問題是由SAP側的錯誤配置引起的。爲了解決這個問題，SAP團隊必須在自定義IDOC類型中釋放自定義細分（ZHEADER）。查看對此的答案：http://scn.sap.com/thread/3436578

來源

2016-02-25 22:53:33

通過JCO連接器訪問SAP後端時出現SEGMENT_UNKNOWN錯誤

回答

相關問題