Spend Management Blogs by Members
Check out community member blog posts about spend management and SAP Ariba, SAP Fieldglass, and SAP Concur solutions. Post or comment about your experiences.
cancel
Showing results for 
Search instead for 
Did you mean: 
lukekrogh
Explorer
0 Kudos
463

SAP BW/4HANA, as a modern data warehousing solution, offers businesses the ability to process, analyze, and report on vast amounts of data in real-time. One of the key features enabling this functionality is the capability to extract data from different sources efficiently, making the data readily accessible for analysis. Generic DataSources in SAP BW/4HANA play an essential role in customizing and enriching the data extraction process, especially when the standard DataSources don’t meet specific business requirements.

What Are Generic DataSources in SAP BW/4HANA?

In SAP BW/4HANA, DataSources serve as the extraction structure from source systems to the BW environment. Generic DataSources provide flexibility when extracting data from SAP and non-SAP systems, allowing custom-defined data extraction based on the particular needs of a business. They are particularly useful in cases where:

  1. Standard DataSources do not exist for the data you need to extract.
  2. Standard DataSources exist but do not meet your exact requirements, such as data granularity, format, or other business-specific parameters.

Generic DataSources can be created to source data from tables, views, function modules, and SAP database tables directly, offering a flexible way to manage data extraction in SAP BW/4HANA.

Creating Generic DataSources: Key Steps

Setting up a Generic DataSource in SAP BW/4HANA is a straightforward process, but it requires attention to detail to ensure data accuracy and efficiency. Here is an overview of the steps involved in creating a Generic DataSource:

1. Define the Data Source and Data Extraction Object

  • In SAP GUI, go to the DataSource Maintenance transaction (RSD1 or RS02) to create a new DataSource.
  • Determine the type of extraction: whether it will pull data from database tables, views, or other sources like function modules.
  • For database table or view extraction, specify the source table or view name and define the fields you need.
  • For function module-based extraction, ensure that your function module is built with an appropriate structure for data extraction.

2. Define Extraction Logic

  • Customize your extraction logic based on your business requirements, which can include setting filters, transformation rules, or criteria that define which records to pull.
  • Ensure data fields in the DataSource align with the data structure in SAP BW to simplify the data transformation process.

3. Manage Delta Extraction

  • One of the benefits of using SAP BW/4HANA is its capability to handle incremental (delta) data loads efficiently.
  • Configure the delta mechanism in your DataSource settings, which enables incremental data updates to avoid full data loads every time.
  • Common delta mechanisms include timestamp-based or numeric pointer-based increments, where only changed data is fetched during subsequent loads.

4. Schedule and Test Data Extraction

  • After setting up the Generic DataSource, it’s essential to perform testing by loading a sample set of data into SAP BW/4HANA.
  • Schedule regular data extractions using SAP BW/4HANA’s Process Chains to automate the load process.
  • Monitor extraction jobs to validate data integrity and consistency. Any anomalies in data should be addressed by refining the extraction logic or troubleshooting the source data.

Advantages of Using Generic DataSources in SAP BW/4HANA

Leveraging Generic DataSources provides numerous advantages:

  • Flexibility and Customization: Unlike standard DataSources, generic options allow users to design the DataSource precisely according to their data extraction needs.
  • Efficient Delta Management: Configurable delta mechanisms mean that only relevant data is loaded, reducing load times and system resource use.
  • Enhanced Data Quality: By customizing the extraction logic and filtering unwanted data, users can ensure higher data quality in BW/4HANA.
  • Real-time Reporting: With timely data extraction and delta loads, business users have quicker access to recent data, facilitating real-time insights and reporting.

Best Practices for Implementing Generic DataSources

When designing and implementing Generic DataSources for sites like Celebian, several best practices can help streamline the process and maximize efficiency:

  • Use Only Necessary Fields: Limit the number of fields in your DataSource to essential data points only, reducing data volume and improving performance.
  • Test Incremental Loads: Always validate the delta mechanism with test runs to ensure data accuracy and efficiency.
  • Optimize Performance: Use indexes on source tables and views to enhance data retrieval speed, especially if the tables are large.
  • Document the Extraction Process: Keeping detailed documentation of your Generic DataSource setup and logic will help in future maintenance and troubleshooting.

Generic DataSources in SAP BW/4HANA offer a robust and flexible solution for businesses needing tailored data extraction beyond standard capabilities. By understanding the setup process, customizing the extraction logic, and following best practices, companies can build a dynamic data extraction framework that powers strategic decision-making.

 

2 Comments
EduardS
Product and Topic Expert
Product and Topic Expert

Hello,

Generic DataSources as known from SAP NetWeaver BW are not available in SAP BW/4HANA.

SAP Note 2470315 - BW4SL & BWbridgeSL - Generic and Export DataSources.

To support generic extraction from tables or views, it is recommended creating corresponding ABAP CDS views and using source system type ODP with ABAP-CDS context in the target system. During the conversion it is possible to convert generic datasources from the myself connection to ODP ABAP-CDS or ODP-SAPI.

Furthermore, in SAP BW/4HANA modeling takes place with the BW Modeling Tools (BWMT).

Transactions like RSD1, RSO2 do not exist in SAP BW/4HANA.

Best Regards,

Eduard

roland_szajko
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi

I have a some observations regarding the content:

  • SAP BW/4HANA does not support the creation of SAPI generic extractors (RSO2 has the "Create" option disabled). I assume this is about the creation of generic extractors in a non-BW/4HANA system (like S/4HANA, Netweaver, etc) and then loading into a BW/4HANA system.
    See: 2443863 BW4SL - S-API DataSources (SAP BW/4HANA as Source)
  • Transaction RSD1 is the emaintenance for Infoobjects (and does not exists in BW/4HANA).
  • I assume you meant RSO2 (with an 'O' and not a zero and this also does not exists in BW/4HANA)
  • The way it is described, the datasource will not be replicated to a BW/4HANA system as a datasource. The extractor must be exposed to ODP with RODPS_OS_EXPOSE (2232584-Release of SAP extractors for ODP replication (ODP SAPI))
  • The document Maintaining Generic DataSources contains further technical details.

Thanks,

Roland

Top kudoed authors