o9 Solutions integration with SAP
o9's integration platform is a flexible and fully featured solution that can connect to a wide variety of data sources, including ERP systems, cloud data stores, and streaming data. The platform supports both batch ingestion for large master datasets as well as real time integration via APIs for transactional data.
In this video, we will discuss a typical o9 integration process, setting up a data load from SAP. The four basic steps involved are:
1. Setting up the connection: This involves configuring the o9 adapter to connect to SAP and specifying the target tables and frequency for data extraction.
2. Data mapping: This involves defining the mappings between the SAP data and the o9 data model.
3. Ingestion logic: This involves specifying the logic for how the data will be ingested into o9, including any transformations or filtering that needs to be applied.
4. Oversight and monitoring: This involves setting up alerts and metrics to track the performance of the integration process.
We will also discuss how o9's data staging area and transformation logic bring all of these types of data together in o9's in memory graph cube EKG.
o9 has a flexible and fully featured integration platform.
Supporting all forms of data ingestion from batch transfers via SFTP, rest API, soap XML, and streaming data. o9 has connectors and mapping templates to connect to ERPs and enterprise systems, including SAP Snowflake, Oracle, Google BigQuery, and many more.
Let's look at a typical o9 integration process.
Here we will set up a data load from SAP, but the same steps apply for other ERPs and data sources.
There are four basic steps: setting up the connection, the data mapping, the ingestion logic, and finally the oversight and monitoring of the process.
The connection to SAP requires minimal configuration on the SAP side.
The o9 adapter monitors the SAP change logs and extracts the data for transfer via SFTP or API.
The o9 platform ingests the data via platform staging APIs.
The o9 data staging layers prepares transforms and optimizes the data for loading into o9's graph cube data model.
The first step is to set up the connection and configured the data transfer.
o9 supports SFTP, rest API, and streaming data protocols.
Within SAP, the target tables and frequency are configured for extraction and upload.
Data mapping, filtering and conditional logic is set up within the o9 integration framework.
Data mapping, transformation, normalization, error handling, and outlier detection take place within o9's data staging layer. This is also where the data is formatted and optimized for EKG's graph cube data architecture.
The data staging layer is where data is cleansed, transformed, and ultimately optimized for Graph cube store.
The graph cube allows o9 to model relationships as well as aggregations of data elements and provides high performance through hybrid queries, of cube nodes and graph relations.
Once the data is loaded into the graph cube EKG, it is directly accessible through o9's user interface.
The data can be displayed in many ways, according to user requirements, and the graph cube structures can be configured and manipulated if required to align with any specific data requirements.
Oversight and monitoring of the integration process is built into the o9 platform.
Alerts are sent to admin users and can be configured to track key steps in the integration and transformation process.
Metrics and statistics give visibility on performance over time.
o9's integration framework connects many types of sources from ERP systems to cloud data stores with structured and unstructured data.
o9 supports batch ingestion for large master datasets as well as real time integration via APIs for transactional data.
o9's data staging area and transformation logic brings all of these types of data together in o9's in memory graph cube EKG.
Get free industry updates
Each quarter, we'll send you a newsletter with the latest industry news and o9 knowledge. Don’t miss out!