SAP BAPI functionality does not work correctly in eGate SRE 5.0.5 Update 2
(Doc ID 1513990.1)
Last updated on MARCH 14, 2019
Applies to:Sun Schema Runtime Environment (SRE) - Version 5.0.5u2 and later
Information in this document applies to any platform.
After migrating from 5.0.5 SRE U1 to U2, the following problems are seen when using the SAP BAPI eWay:
- Transactions are no longer committed to SAP.
- The disconnect() method no longer works.
- ETD Builder fails with compilation errors related to setValue() methods when building from a SAP BAPI:
Error in Call to Compile BAPI CompilerCompiler errors.
C:\egate\client\bin\Data\Etds\com\mytest\me\RFC\mybapis\RFC\Z_TEST_GET_DATA.java.1145: cannot find symbol
symbol: method setValue(double,int)
location: interface com.sap.conn.jco.JCoTable
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document