This Techspert Talks session covers:
- Completing connection requirements
- Setting up SAP connection to Qlik Talend Cloud Data Integration
- SAP data best practices
Chapters:
- 01:13 - Data Movement Gateway Architecture
- 01:54 – Prerequisites
- 02:22 - Downloading the Data Movement Gateway
- 03:31 - Installing the Data Movement Gateway
- 05:00 - Creating a Data Space and Gateway Setup
- 06:46 - Installing the SAP Drivers
- 09:11 - Creating a Data Connection to SAP
- 10:48 - Creating a Data Project task
- 13:19 - Comparing Data in SnowFlake and SAP
- 14:16 - Q&A: Can the Data Movement Gateway connect to Sense?
- 14:47 - Q&A: Can the same Gateway be used with multiple sources?
- 15:28 - Q&A: How to fix tables in Suspended status?
- 16:12 - Q&A: Where are the drivers found?
- 16:54 - Q&A: How to fix the "Cannot connect" error?
- 17:37 - Q&A: Does the Movement Gateway need an extra license?
- 18:29 - Q&A: Where can we learn about Data Pipelines?
- 19:00 - Q&A: Is it possible to filter data in the task with extractor?
- 19:33 - Q&A: Can a task be uploaded using SQL script?
Resources:
- Setting up Data Movement Gateway
- SAP HANA (Database)
- Introducing Qlik Talend Data Integration
- Creating a data pipeline
- Exploring Qlik Cloud Data Integration
- Qlik Learning
Q&A:
Q: How do you do this for tables with huge volume, BSEG and MSEG?
A: In SAP, BSEG is a table that stores line item data for financial transactions, while MSEG is a table that stores material-related document segment data. Both are standard tables in SAP R\3 ERP systems.
Explanation
- BSEG
The BSEG table stores the segment or item data for financial transactions in SAP. It's a cluster table, which means it references values from other tables, such as BSIK, BSAK, BSID, and BSAD. BSEG data can be used as a data source for other functions.
- MSEG
The MSEG table stores material-related document segment data in SAP R\3 ERP systems
Extracting data from SAP tables like BSEG (Accounting Document Segment) and MSEG (Material Document Segment)
Option 1: Using SAP SE16N/SE16 Transactions, creating a Join between BSEG & MSEG Tables
Option 2: Using a SAP ABAP Program, extract data from BSEG and MSEG Tables
Q: Why is temp space required for the extraction process while using SAP endpoints?
A: In brief When extracting data from SAP systems temp space requirements: Intermediate Staging Large Volumes of Data, Applying Data Transformation, SAP-Specific Integration Requirements such as IDoc and RFC Buffering, Network and Endpoint Constraints, Data Integration and Parallelism
Q: Can we use a through filter in SAP endpoints?
A: Yes, you can use pass-through filters when extracting data from SAP using Qlik or Talend Cloud. Implementing them at the SAP endpoint level improves efficiency by reducing the data volume extracted and processed. Ensure proper configuration, test the filters, and monitor system performance for the best results
