Creating InfoProviders

Objectives

After completing this lesson, you will be able to:

  • Create BW InfoProviders

InfoProviders

Now that we have designed master data, we'll have a look at transactional data. In our scenario, this means line items (sales orders) for sales data. The DataStore Object (advanced) is the SAP BW Bridge object for persistent storage of data.

Note
The usage of Data Store Objects (advanced) is not limited to storing transactional data. For some scenarios, a Data Store Object (advanced) can be used to store master data, but this is not covered in this course.

DataStore Objects (advanced) can be used for different levels of integration and purpose. The following are the most prominent types.

The image shows different possible Purpose of ADSO: The image shows different tables with examples for raw data and above it, the purpose: On the left, discount per product, as reference data for lookup. In the middle, product and quantity with different levels of aggregation: detailed historical raw data as Corporate Memory, data after lookup as harmonized data, aggregated data as Propagation.
  • Corporate Memory: storing a history of rather granular raw data, often purely field-based (no InfoObjects)
  • Inventory Management Data: storing initial numbers at the beginning of a period together with all incoming and outgoing changes. Think of the following examples:
    • Number of employees, hired and fired employees.
    • Goods on stock, commissioned goods.
  • Harmonization Layer: storing already integrated and harmonized data, typically based on a few fields and mainly InfoObjects
  • Propagation Layer: generating a change log, which provides a delta mechanism for further targets in SAP BW Bridge or SAP HANA core tenant. When changed values are updated to the DataStore object (advanced), a storno of the outdated vaule and a new after image is stored in a queue of changes
  • Reference Data: storing reference values physically for a data lookup or quantity conversion. Think of the following examples:
    • Expected payment delay per customer and payment method, based on historical behavior
    • Product-specific quantity conversion factors, such as the weight per liter or the number of packages per palette

The InfoObjects can be integrated in ADSOs. An ADSO typically combines several InfoObjects and fields that are not InfoObjects.

This image shows how transactional data and master data is combined. It displays two ADSOs that contains the InfoObject (of type characteristic) for Product. One ADSO contains additional fields, such as Order ID and Item, and an additional InfoObject (of type characteristic) for Customer. The reference to the InfoObjects is displayed as dashed lines. Each InfoObject contains two tables: Attributes and Texts.

Launch the following video to learn how you create an ADSO.

As a next step, you must find sources with the required data (DataSources) and map source fields to target fields or InfoObjects.

Log in to track your progress & complete quizzes