SAP Adapter Hanging After New Fields Added to IDoc (Doc ID 2236601.1)

Last updated on FEBRUARY 22, 2017

Applies to:

Oracle SOA Suite - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.0.0 version, Technology Adapters

After changes were made on the SAP side, inbound iDOCs are not processing correctly. They seem to contain extra fields. When the first iDOC with these fields are received by the SAP Adapter, no more iDOCs can be processed through that channel.

The error below is seen in the logs

<Jan 24, 2017 9:49:12 AM CET> <Error> <oracle.soa.adapter.sap.inbound> <BEA-000000> <Exception while Adapter Stop watch intialization
java.lang.NullPointerException
at java.util.AbstractMap.toString(AbstractMap.java:524)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at oracle.tip.adapter.sap.inbound.SAPFunctionHandler.handleRequest(SAPFunctionHandler.java:189)
at com.sap.conn.jco.rt.DefaultServerWorker$FunctionDispatcher.handleRequest(DefaultServerWorker.java:1041)
at com.sap.conn.jco.rt.DefaultServerWorker$FunctionDispatcher.handleRequest(DefaultServerWorker.java:977)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:148)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3685)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:3163)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2986)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2880)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2679)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:275)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:356)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:232)
at java.lang.Thread.run(Thread.java:745)


When the IDoc is manually submitted, it works fine. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms