Skip to main content

The SAP BW Extractor and its Operational Features

 SAP BW Extractor is a program that captures and prepares data in SAP ERP via an extract structure that can be transferred to the BW (Business Warehouse). The program may be customized or run from a standardized Data Source. Both instances define a full process load of various types or a delta load process. The data transfer facets of the SAP BW Extractor can be accessed remotely by the SAP Business Warehouse.

Is all data lost if the SAP BW Extractor is moved to S/4HANA or even other SAP BW Extractors that are compatible with S/4HANA?

Only transactional and operational activities can be carried out and not analytics by the SAP ECC system. Thus, to analyze ECC data, SAP BW Extractor is necessary to extract data from the SAP ECC system to an SAP BW system. After the SAP BW Extractor is linked to a BW system, the latter can be made to perform analytical activities by connecting to the Business Intelligence system.


Data extraction with SAP BW Extractor is initiated by multiple application-specific extractors. These are then hard-coded for the Data Source and delivered along with the BI Content in the BW. The structure of the Data Source is matched by the SAP BW Extractor.

Three types of SAP data extraction with the SAP BW Extractor -

1.     Content Extraction: It is used to extract BW content, FI, HR, CO, SAP CRM, and LO cockpit.

2.     Customer-Generated Extraction: Here, SAP BW Extractor is used for LIS, FI-SL, CO-PA.

3.     Generic Extraction: This is based on DB View, Infoset, Function Modules.

Which is used by a business depend on specific requirements. 


Comments

Post a Comment

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 ...
Post a Comment
Read more

The Evolution of Technology of Oracle Change Data Capture

Oracle change data capture ( CDC) was first launched with the 9i version as an in-built tool of the Oracle database. It was a tool that recorded and monitored all changes made in the user tables in a database. These changes were then stored in change tables and used in ETL applications for later processing and transferring to other data warehouses and databases. The release version of Oracle change data capture   had triggers placed in the source database. However, database administrators found this technology very invasive and did not favor it. Ultimately, Oracle changed the Oracle change data capture   technology and released it with the 10g version after naming it Oracle Streams.  The working of this release was different. Oracle change data capture   used the redo logs of the source database along with a replication tool of Oracle Streams. This technology turned out to be very successful and a highly optimized method to identify and move change data to a target ...
Post a Comment
Read more

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 ...
Post a Comment
Read more