Skip to main content

Capturing Data with the SAP Extractor

The SAP Extractor is a program in SAP ERP that can be both customized or taken from a standard Data Source. It prepares and captures data through an extract structure that can be transferred to the Business Warehouse of SAP. Both the options of the SAP Extractor help to describe a delta load process or various types of full load. The SAP BW can remotely access the various data transfer activities of the SAP Extractor.



For more on SAP Extractor, click here.

SAP Extractor executes SAP data extraction in three ways.

The first is Content Extraction used to extract BW content, FI, HR, CO, SAP CRM, and LO cockpit. The second is Customer-Generated Extraction where the SAP Extractor is used for LIS, FI-SL, CO-PA. The third is Generic Extraction which is based on DB View, Infoset, Function Modules. The SAP Extractor used for a specific extraction activity depends on the particular needs of an organization.

Data capturing and extraction with the SAP Extractor is initiated with the help of several application-specific extractors. After being hard-coded for the Data Source, these are then delivered together with the BI Content for the BW. The SAP Extractor is so designed that it exactly matches the structure of the Data Source.      

Moreover, there are several generic extractors that are used for extracting SAP data from source systems and transferring to the SAP BW. As the complete data capturing process is automated, the SAP Extractor will automatically know which data has to be extracted and from which tables the data has to be read. A major advantage here is that SAP data extracted can be moved directly to Excel sheets with users having the option to generically extract SAP data.     

Comments

Popular posts from this blog

The Change Data Capture (CDC) Feature in Microsoft SQL Server

  Several issues are faced by organizations today in the areas of data security and safety and ramping up systems for preservation of historical data. Leading database platforms took steps in this regard by launching data audits, timestamps, complex queries, and triggers, one of them being Microsoft. It led the innovation when in 2005, it introduced the SQL Server CDC   with the “after date”, “after delete”, and “after insert” features. SQL Server CDC   captures and records all activities like insert, update, or delete that are applied to a SQL Server table. Changes made are available in a user-friendly relational format and metadata and information that are required for posting changes to the target databases are captured in modified rows. These are stored in change tables with the same structure as the columns in the tracked source tables. SQL Server CDC   also tracks and records changes in the mirrored tables with column structures that are the same as the source ...

The Working of Microsoft SQL Server CDC

  Modern-day businesses have to preserve historical data and take measures to prevent data breaches. In this regard, Microsoft took the lead in 2005 when it launched the SQL Server CDC. The 2005 version of SQL Server CDC   had certain flaws which were ironed out in an updated release in 2008. Some of the functionalities included tracking and capturing all changes that take place in the SQL Server database tables without taking the help of additional programs and applications. Till 2016, SQL Server CDC   was offered by Microsoft in its high-end Enterprise editions but later was available in the Standard version too. SQL Server CDC   captures and records all activities like Insert, Update, and Delete applied to a SQL Server. Column information and metadata required for posting changes to the target database are recorded in modified rows that are then stored in change tables representing the architecture of the columns in the tracked source tables. SQL Server CDC ...