Document

Table mapping feature in SAP BO 3.1

Description

This intends to help the user\developers to effectively use the table mapping feature which plays pivotal role in creating same report with different data depend in different user groups

     

Table of Contents

  1. 1.. Document Objective. 3
  2. 2.. Table Mapping Feature. 3
  3. 3.. Case Study. 3
  4. 3.1    Application Background. 3
  5. 3.2    Database part 4
  6. 3.3    BO Solution. 5
  7. 4.. Advantages. 16

 

1.    Document Object

This paper is written to highlight the importance of the ’Table Mapping’ feature in SAP BO Universe designer. It is observed that most of the developers don’t use this feature as efficiently as it could have been in their projects. This paper is an attempt to throw more light on this feature which can enable BO developers to fit this function into their applications wherever applicable.

2.    Table Mapping Feature

The main functionality of this feature is to provide different data set for different user without making any changes to the underlying universe. To put it simple, the base table for the data selection could be dynamically changed based on the user group while the universe and webi report remain same. It is imperative that the table structure should be same for the base tables that will be changed dynamically.

This feature enables to create a single universe and webi report with different set of data based on the user group hence it plays an important role in keeping the reporting system very simple. The maintenance also becomes easier when there is an enhancement to the report, as the change would be enough at only one place.

3. Case Study

The case study would help to understand this feature better.

3.1 Application Background

Let us consider a Sales& Marketing/Banking/Finance applications. It is an international  and data is loaded into the database system from different regions of the globe on daily basis.

This daily data is the base for sales calculations. So it is very important to validate the data by  users before they get loaded into the data-sensitive fact tables for calculations.

Let us say there are 12 different applications (regions) from where the data is loaded on daily basis –India,Malaysia, German, Singapore, China, UK, US, Russia, Finland, Denmark, Sweden and Norway. There are 12 separate staging tables to receive the data from these applications.

The database system receives the data by 10 AM every morning and the business users run the report by 9.30 AM to validate the data. Once the sign off is received from business the data is loaded into fact tables and business critical calculation is started.

The aim of this whitepaper is to create a single universe and report which fetches different data set based on the different user groups.

3.2 Database part

The following staging tables are created in the database, which receives the base data from 12 different applications.

  • STG_DAILY_DATA_INDIA
  • STG_DAILY_DATA_MALAYSIA
  • STG_DAILY_DATA_GERMAN
  • STG_DAILY_DATA_SINGAPORE
  • STG_DAILY_DATA_CHINA
  • STG_DAILY_DATA_UK
  • STG_DAILY_DATA_US
  • STG_DAILY_DATA_RUSSIA
  • STG_DAILY_DATA_FINLAND
  • STG_DAILY_DATA_SWEDEN
  • STG_DAILY_DATA_DENMARK
  • STG_DAILY_DATA_NORWAY

The table structure is same for all the tables.

CREATETABLE STG_DAILY_DATA_INDIA

(

customer_idNUMBER,

periodNUMBER,

Product_typeVARCHAR2(50),

corporate_typeVARCHAR2(10),

currencyVARCHAR2(10),

amountNUMBER

);

The sample data is for INDIA

CUSTOMER_ID

PERIOD

PRODUCT_TYPE

CORPORATE_TYPE

CURRENCY

AMOUNT

100

20150601

DEPOSIT

SME

INR

10000

200

20150601

LOAN

SME

INR

20000

300

20150601

DEPOSIT

LARGE

INR

30000

400

20150601

LOAN

LARGE

INR

40000

500

20150601

DEPOSIT

MEDIUM

INR

50000

600

20150601

LOAN

MEDIUM

INR

60000

The business user verifies the report at product, corporate and asset_liability level before loading the signed off data into production fact tables

3.3 BO Solution

BO reports to be designed for each country to get the data at product, corporate and asset liability level so that the business users can validate the data before loading into application for critical calculations.

There are so many ways to achieve the solution.

  • Creating different universes for each table (12 universes) and one webi report for each country (12 different webi reports)
  • Creating one universe by including all the tables and 12
  • webi reports one for each country
  • Creating one universe for all the tables and one webi report for all the countries.

In this paper, we have been discussing about the solution 3, which helps us to avoid complexities by making the system very simple for maintenance

                 

3.3.1    Final Report

The final report that the business user wants to see is as below.

t3.PNG

Note:

   To collect data from multiple universes then get complexities

                               (OR)

  One operation report lots of vertical tables, chart, which have lot of complexities in formating,  i archive with relative position between cross tab, vertical & chart

3.3.2    Steps to create Universe

  1. Insert any one table that we created above

t4.PNG

2. Go to Tools-> Manage security -> Manage Access Restrictions

  t5.PNG

3. It opens the following screen. Click on NEW to create new restriction

  t6.PNG

4. Click on Table Mapping tab to select replacement table

  t7.PNG

5. Enter the original and replacement tables and clickOK

t8.PNG

  6. The new restriction rule is created as below

t9.PNG

   7. Name the restriction rule and Click OK

t10.PNG

   8. Mapping rule is now created successfully. To apply this mapping rule with respective business user click on ‘Add user or group’

t11.PNG

    9. The screen opens for user selection.

t12.PNG

     10.   Select the user and click on >  and then click on OK

t13.PNG

     11.   Click on Apply and OK to apply the mapping rule to the particular user.

t14.PNG

     12.  Click on Preview in the previous step to preview the newly created mapping.

t15.PNG

3.3.3    Webi Report with Dynamic changes

The same report fetches different set of data based on the user who executes the report.

t16.PNG

4.    Advantages

  1. 1.    Complexity of the system is eliminated by creating just a single report which serves multiple purposes. Single report displays different data sets depending on the user groups thus by creating multiple reports is avoided.
  2. 2.    Data security is attained as the sensitive data is protected based on user group.
  3. 3.    This feature will play pivotal role in the stand point of enhancement. The enhancement can be done at only one place and the change is reflected to all users thus saving lot of manual effort and time.
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply