Troubleshooting
Problem
When client has different message flows invoking more than one BAPI using the WebSphere Adapter for SAP, the first call to the BAPI succeeds, however the subsequent BAPI calls fail.
Symptom
The subsequent BAPI calls fail with the following error:
'session reference is null. SessionReferenceProvider:
com.ibm.j2ca.sap.ext.JCo3SessionReferenceProvider, scope type:null'
No further information on why the BAPI calls failed when executed.
Cause
The BAPI calls fail as the transaction goes from Stateful to Stateless Mode.
Resolving The Problem
This problem has been addressed in APAR JR37273. Check the latest Recommended Fixes whether it is available online, otherwise, contact IBM Support to get the fix.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21450625