SAP Connector FAQ

Transport packages have to be installed on the SAP system. In addition, you need:

1. A technical user with the proper access rights
2. Jedox Integrator to extract the relevant data out of SAP, including master data, either from ERP or BI
3. Predefined Kickstart packages for a quick start, including ETL projects and report bundles.

During data loading on the SAP system, one single RFC request is started in a work process. It only reads data; it does not modify data. There is no footprint after the RFC call, and no report is generated. Relevant SAP data is stored in an analytical way in the Jedox In-Memory DB and can therefore be used for planning purposes, such as workflow planning, viewing different versions, and state-of-the-art web/mobile reporting.

SAP systems interacting with non-SAP systems always require individual, internal review by the customer to ensure compliance with SAP's license terms. Jedox customers should be fully informed about the SAP license rights they agreed to before connecting to an SAP system.

Not on the SAP side. In the SAP system, queries are raised in one single work process. This should not slow down SAP performance.

Jedox uses its own extract types within the Jedox SAP Connector to get SAP data easily loaded into Jedox. Data can also be easily transformed, with no programming needed.

Jedox extracts relevant data out of SAP, transforms and enriches this data, and loads it into a Jedox cube. The loads can be scheduled and used in different modes, e.g. full loads or incremental loads.

As many as needed. There is no limitation on the amount of data you can pull out of the SAP system.

Both options are possible. After loading all relevant data once, you can use incremental loads to reduce the job duration of data loads.

ETL processes can be scheduled individually. For most projects, a daily run of the ETL process is sufficient. However, if needed, the job can be scheduled to run every few seconds, depends on the run time and amount of data you need to extract.

Benchmark for SAP table COEP: 1 million transactions take approximately 10 minutes.

There is only one SAP user needed, with RFC authorizations for the data loading.

Master data, including structure and attributes, can be loaded very quickly and easily. Extracting BW cubes at a high level of detail may be slow, in comparison to other databases. Logic, e.g. switching accounts, have to be defined in the project. Overall, we have had very good customer feedback.

First statement is correct. So far, there was never a real performance issue as far as you do daily loading.

Yes, many Jedox customers use the SAP connector to connect to their operational SAP system. Please have a look at our customer success stories.