2016-02-25 28 views
0

我试图通过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侧的对象似乎是真正相同的(两种基本类型,没有扩展名等)

+0

不知道该怎么回事,但可能[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)可能会有所帮助 –

回答

0

来自Ravindra HV的说明是正确的,这个问题是由SAP侧的错误配置引起的。 为了解决这个问题,SAP团队必须在自定义IDOC类型中释放自定义细分(ZHEADER)。 查看对此的答案:http://scn.sap.com/thread/3436578