# Ignition SAP interface **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [May 27, 2025, 12:20am UTC](https://forum.inductiveautomation.com/t/ignition-sap-interface/106699 "2025-05-27T00:20:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\ **Post date:** [May 27, 2025, 7:24am UTC](https://forum.inductiveautomation.com/t/ignition-sap-interface/106699/2 "2025-05-27T07:24:39Z")
Just fetch data from SAP and display it. You don't need Sepasoft at all. 2 fetching approaches: Option 1: SAP RFC > [@Connecting to SAP with 3rd party Python lib or SAP JCo jar](https://forum.inductiveautomation.com/t/connecting-to-sap-with-3rd-party-python-lib-or-sap-jco-jar/40712/9): > > I’m using SAPJco3 for RFC calls to SAP and it works nicely. Place the SAPJco3 library in a folder on your gateway. (c:\SAPJco3 for example) Be sure to get the bit version to match your Java environment. (i.e.: 64 bit SAPJco3 library) Edit the ignition.conf file and add wrapper.java.classpath.3=c:\SAPJco3/sapjco3.jar # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=lib/wrapper.jar wrapper.java.classpath.2=lib/catapult.… Option 2: SAP HTTPs API --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-sap-interface/106699)._