Many organizations have strategic investments in ERP (Enterprise Resource Planning) Systems, such as SAP, Oracle, SalesForce, Sage, Microsoft Dynamics, etc. In many cases, there is substantial need to integrate such ERP data with "local" data defined by the business.
This page explains various alternatives for integrating such data with "local" SQL data:
Observe the focus of Espresso support is the integration and automation of ERP data with local SQL data. Espresso is a complement to other products in this space, such as Data Integration and Enterprise Application Integration products.
ERP systems store their data in relational database, but direct access to the underlying data is a very bad idea, since it bypasses the business logic. Most organizations therefore prohibit such access via standard JDBC drivers.
Yet, SQL access provides many benefits, such as reporting, Business Intelligence, etc. Some integration vendors have therefore recognized the opportunity to build 'special' JDBC drivers that link in the ERP business logic. We refer to these are ERP JDBC Drivers, as distinct from (generic) JDBC access. Such vendors include Progress JDBC (formerly Data Direct), RSS Bus, and others.
These products unlock substantial value in Espresso: since the ERP data looks like SQL Tables, Espresso SQL automation can be applied to ERP data, including:
For these reasons, we advocate this as the preferred approach. Please work with your Espresso representatives to engage this functionality.
Some systems, such as Microsoft Dynamics, expose Stored Procedures which you can use to read / update data. In these cases, you can also use Stored Procedure Resources to access ERP data. These Stored Procedures encapsulate the business logic, maintaining database integrity.
Access such Stored Procedures by defining an additional Data Source for ERP data access. We recommend disabling all direct SQL access by unchecking Default Access Levels.
Then, you can access your ERP data in variety of ways:
You can learn more here.